Gregory's Server
@jonny …and so on. a lot of this was probably latent in the fundamental architecture of the web + the decision to have a language runtime at all.
js *as a language*? it sucks but also there are some neat things. ecosystem is a far bigger problem than the language itself. to a 1st approximation, i could say these things about any language people actually use.
i don't see a reason to think that a different *language* design would have changed most of the things i don't like about the situation.
@brennen @jonny yeah, one other point I’d like to add is that JavaScript is fine when writing webapps and the problem is only when everything is an app. Documents have many positive aspects and forcing people to use an app (anything with Javascript) means that almost always the experience degrades: less accessibility, less freedom in layout, theming, archiving, printing, navigation, and so on. The two problems are thus: apps instead of documents, and badly designed apps. In the case of things that are in fact apps that run on the virtual machine that is the browser, I have nothing against Javascript and use it myself. The fact that the virtual machine is super hard to implement and wouldn’t be necessary for simple hypertext online adds insult to injury.
@brennen @jonny yeah, one other point I’d like to add is that JavaScript is fine when writing webapps and the problem is only when everything is an app. Documents have many positive aspects and forcing people to use an app (anything with Javascript) means that almost always the experience degrades: less accessibility, less freedom in layout, theming, archiving, printing, navigation, and so on. The two problems are thus: apps instead of documents, and badly designed apps. In the case of things that...