From their FAQ:
https://nuejs.org/docs/faq.html#the-codebase-isnt-using-typescr
## The codebase isn't using TypeScript. How can I take this seriously?
The React ecosystem has created a culture where every project, no matter how simple, must become a complex TypeScript application. This mindset assumes JavaScript is a toy language and pushes developers away from understanding how the web actually works.
But look at the most sophisticated web applications today. Figma's vector engine achieves its power through clean separation and WebAssembly, not TypeScript definitions. Notion's real-time collaboration comes from proper system architecture, not component types. The web's most ambitious applications succeed through architectural clarity, not type annotations.
This is about proper separation of concerns. When you break free from the TypeScript-everywhere mindset, you can focus on what truly matters: system programming for complex business logic, design engineering for sophisticated interfaces, UX development for seamless experiences. Use true static typing where it adds value — in your core business logic — while keeping your presentation layer clean and semantic.
The web platform itself is incredibly powerful. Instead of wrapping everything in types, you could be exploring what's possible when each technology focuses on what it does best. This is about understanding where TypeScript adds value and where it gets in the way of genuine innovation.
dtonon / daniele
npub100…8vwqk
2025-04-02 19:00:13
in reply to nevent1q…yl04
Author Public Key
npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqkPublished at
2025-04-02 19:00:13Event JSON
{
"id": "000031a5c74c79e81ed168513ae7f70b5a20cacba47d58f05907ed467e854336",
"pubkey": "7bdef7be22dd8e59f4600e044aa53a1cf975a9dc7d27df5833bc77db784a5805",
"created_at": 1743620413,
"kind": 1,
"tags": [
[
"p",
"11b9a89404dbf3034e7e1886ba9dc4c6d376f239a118271bd2ec567a889850ce"
],
[
"p",
"6e468422dfb74a5738702a8823b9b28168abab8655faacb6853cd0ee15deee93"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
],
[
"e",
"085d0f51ada912d4d8ab8e163263db2bf7e09560c9309b1aca36281e5465afa8",
"wss://wot.dtonon.com/",
"root",
"7bdef7be22dd8e59f4600e044aa53a1cf975a9dc7d27df5833bc77db784a5805"
],
[
"e",
"2732a4a78334224f21f277b617d12182e0f12b39eb7fdaabdfc05a4bb7b556d0",
"wss://wot.utxo.one/",
"reply",
"11b9a89404dbf3034e7e1886ba9dc4c6d376f239a118271bd2ec567a889850ce"
],
[
"nonce",
"28640",
"18"
]
],
"content": "From their FAQ:\nhttps://nuejs.org/docs/faq.html#the-codebase-isnt-using-typescr\n\n## The codebase isn't using TypeScript. How can I take this seriously?\n\nThe React ecosystem has created a culture where every project, no matter how simple, must become a complex TypeScript application. This mindset assumes JavaScript is a toy language and pushes developers away from understanding how the web actually works.\n\nBut look at the most sophisticated web applications today. Figma's vector engine achieves its power through clean separation and WebAssembly, not TypeScript definitions. Notion's real-time collaboration comes from proper system architecture, not component types. The web's most ambitious applications succeed through architectural clarity, not type annotations.\n\nThis is about proper separation of concerns. When you break free from the TypeScript-everywhere mindset, you can focus on what truly matters: system programming for complex business logic, design engineering for sophisticated interfaces, UX development for seamless experiences. Use true static typing where it adds value — in your core business logic — while keeping your presentation layer clean and semantic.\n\nThe web platform itself is incredibly powerful. Instead of wrapping everything in types, you could be exploring what's possible when each technology focuses on what it does best. This is about understanding where TypeScript adds value and where it gets in the way of genuine innovation.\n",
"sig": "34739525119c5caf94e699200851b3882bafd4cc3c89aec767981e1f9c6ec43134ab27e68054e2e652c5b3c37fdb8691a266a845be5941c705ee9cd865573e61"
}