"The best thing we can do today to JavaScript is to retire it"

submitted by [deleted] from devclass.com

all 4 comments
sorted by:
top
newinsightfulfun

[–][deleted] 3 insightful - 2 fun3 insightful - 1 fun4 insightful - 2 fun -  (0 children)

Well, my experience with TypeScript certainly hasn't sold me on it, nor has the addition of the "class" keyword and faux OOP to JavaScript really added much useful that I can discern. Sometimes the answer is, "leave the damned thing alone," and I say this as someone who's done a lot of backend development in strongly-typed languages.

[–]fschmidt 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (0 children)

While Javascript is bad, obviously this depraved modern scum piece of shit wants to replace Javascript with something much worse. Thankfully Javascript can't be replaced since that would break the entire web. The real ideal solution would be for browsers to support multiple languages with some standard API for adding languages. But that makes too much sense and modern scum never do anything that makes sense.

[–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

Black Lives Matter will riot and pillage if Ebonics is not the next programming language.

[–]IMissPorn 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

The whole problem is that "web apps" are a stupid idea. I can understand why they people wanted to make them, but web pages and applications are two different things, and mashing them together was always going to give a substandard result IMHO.

JS might be fine for adding simple dynamic elements, creating a new text box when you click "reply" for example, but I don't think it was ever meant to turn entire web pages into into pseudo applications. If you need an application, Java was a more sensible compromise: An actual executable (or something close to) which you can load over the web, instead of forcing the web page itself into becoming something it wasn't designed to be.