columbus@lemmy.world to Technology@lemmy.worldEnglish · 1 month agoHow JavaScript Overuse Ruined the Webdonald.catexternal-linkmessage-square43fedilinkarrow-up1199arrow-down122
arrow-up1177arrow-down1external-linkHow JavaScript Overuse Ruined the Webdonald.catcolumbus@lemmy.world to Technology@lemmy.worldEnglish · 1 month agomessage-square43fedilink
minus-squareKairos@lemmy.todaylinkfedilinkEnglisharrow-up1arrow-down5·1 month agoedited my comment to include the excruciatingly obvious assumption.
minus-squarewatty@lemm.eelinkfedilinkEnglisharrow-up1·1 month agoSeems like you read the first two sentences of my post and stopped there, so you completely missed the point. It’s not JS that is the problem. It’s an issue of client resource use. That would be true no matter what language is being used.
minus-squareKairos@lemmy.todaylinkfedilinkEnglisharrow-up1arrow-down1·1 month agoNot necessarily. Programmers are heavily influenced by the language they use. There’s a reason there’s so many JS frameworks.
edited my comment to include the excruciatingly obvious assumption.
Seems like you read the first two sentences of my post and stopped there, so you completely missed the point.
It’s not JS that is the problem. It’s an issue of client resource use. That would be true no matter what language is being used.
Not necessarily. Programmers are heavily influenced by the language they use. There’s a reason there’s so many JS frameworks.