Sure, that's yet another aspect. #Javascript (#ECMAscript to be precise) evolved a lot. Where we came from was a very limited standard and browsers doing their own incompatible thing, also adding "random" bugs, which btw triggered development of #jQuery, back then an extremely helpful thing, nowadays more or less obsolete. I'm sure writing a well-working #SPA with nothing but vanilla JS is perfectly possible these days, it just requires some planning and design, you'd probably end up with a (minimal and tailored to your needs) "framework" as part of your project. But from my experience, most "frontend devs" are indoctrinated into a strong belief you absolutely need super-fat frameworks for everything.
What I was talking about is that these you mentioned (React, Angular) are designed with nothing but SPA in mind. So, everything will end up being an SPA, which just makes no sense for 95% of "web apps". There's a nice set of architecture guidelines for web apps called #ROCA, which is in line with the initial design of #http and the web in general: https://roca-style.org/ -- and then, you decided in your organization to follow that, you have the need for some enhanced UI components in JS, and these frontend guys basically keep telling you "we need our awesome framework here". Oh boy. 🤦
In the end, I see the resident set of my local browser and have no questions left...
zirias (on snac) /
npub1w9…99l6c
2024-10-03 05:32:32
in reply to nevent1q…el7x
Author Public Key
npub1w96l7dwwzzmd6taq8qzhgh80hdsad2y0shrank8whyrksa2fkwasz99l6cPublished at
2024-10-03 05:32:32Event JSON
{
"id": "b6d0a902b532b5162e0bd2e3b0367f3581dcb6a5456a3fd0d2cad1b682844e06",
"pubkey": "7175ff35ce10b6dd2fa03805745cefbb61d6a88f85c7d9d8eeb907687549b3bb",
"created_at": 1727933552,
"kind": 1,
"tags": [
[
"p",
"b04a7d2ee17ac634dffda6c1c59350075fd3941b9bc0872603f6c5b0caa51b96",
"wss://nostr.sprovoost.nl"
],
[
"e",
"4d6627012f0023e131f7530bc9b6bede376427922b404c8bb7fcd9fade9cb0b3",
"wss://nostr.sprovoost.nl",
"reply"
],
[
"t",
"javascript"
],
[
"t",
"ecmascript"
],
[
"t",
"jquery"
],
[
"t",
"spa"
],
[
"t",
"roca"
],
[
"t",
"http"
],
[
"proxy",
"https://snac.bsd.cafe/zirias/p/1727933552.653644",
"activitypub"
]
],
"content": "Sure, that's yet another aspect. #Javascript (#ECMAscript to be precise) evolved a lot. Where we came from was a very limited standard and browsers doing their own incompatible thing, also adding \"random\" bugs, which btw triggered development of #jQuery, back then an extremely helpful thing, nowadays more or less obsolete. I'm sure writing a well-working #SPA with nothing but vanilla JS is perfectly possible these days, it just requires some planning and design, you'd probably end up with a (minimal and tailored to your needs) \"framework\" as part of your project. But from my experience, most \"frontend devs\" are indoctrinated into a strong belief you absolutely need super-fat frameworks for everything.\n\nWhat I was talking about is that these you mentioned (React, Angular) are designed with nothing but SPA in mind. So, everything will end up being an SPA, which just makes no sense for 95% of \"web apps\". There's a nice set of architecture guidelines for web apps called #ROCA, which is in line with the initial design of #http and the web in general: https://roca-style.org/ -- and then, you decided in your organization to follow that, you have the need for some enhanced UI components in JS, and these frontend guys basically keep telling you \"we need our awesome framework here\". Oh boy. 🤦\n\nIn the end, I see the resident set of my local browser and have no questions left...\n",
"sig": "511b6f870f12cc0094c27e913134cd4f99ffb3d78a1d49b557fffe316c9672cbdb4a550b293a754649f17c1390646c0191503a322ec6f7fe2be2fb11b73a53d1"
}