The JavaScript community grew by an impressive four million users in the past 12 months, solidifying its status as the most widely-used programming language globally.
Document ObjectModel. Think using code to add a JavaScript to make a drodown menu appear like for a navigation bar. That would be manipulation. And I think there’s so much more Angular and React do with DOM that I don’t know enough to explain it.
thanks to wasm any language is a browser running language. JS is relegated to some token binding boilerplate as part of any framework and with things like servo/tauri rendering html will be pure rust
thanks to wasm any language is a browser running language.
Theoretically yes, practically you may have to deliver a whole runtime depending on the languagey making websites even bigger and slower to load initially. And unless it’s a webapp with data processing on the client the perceived performance benefits may be negligible.
It’s because it’s a great language. Legitimately cannot understand why anyone would dislike it, especially with the the ES5+ editions and the advent of Typescript.
I started with C#, and have used Python, Java, PHP, and Ruby in professional capacities and still find Typescript to be my favourite by a significant margin.
People dislike JS because it’s packed full of moronic footguns and technical debt. The “standard library” is full of baffling decisions and, much like the language, rarely does what you expect. Even its creator agrees it’s a terrible language and should have been replaced by now.
TypeScript is better, but at the end of the day it’s just an illusion. Add an any anywhere, which will happen, and you’re back to square one. It also still inherits some of the weirdness of JS, because it is just JS with fake types bolted on. Plus, the amount of work one has to do to create a proper library with TypeScript support completely undermines the few advantage of JavaScript. Might as well use a real statically typed language at that point, at least you’d be sure your types are actually enforced.
Also, the whole web ecosystem is ass.
The hoops one has to jump through nowadays to do web development are absolutely batshit crazy. And no, having a create-whatever that sets things up for you is not a real solution.
It definitely isn’t in some circumstances.
Frankly I’d put C/C++ in a similar category when it comes to compilation.
Dealing with Make, CMake, linkage and all that can be a nightmare.
The ecosystem is a little bit better though in my opinion. If nothing else you get a proper standard library and don’t have to rely on thousands of dependencies to get anything done… or you often roll your own if you are in C… which is meh.
I find Rust, C#, Go and anything slightly more modern to be a great or at least good experience.
Python as well if you use venv and your runtime and package versions align.
My point is, there is no perfect platform and ecosystem, but the web is generally regarded as one of the poorest.
I’m not saying someone can’t enjoy working on web stuff, they most certainly can. But it is objectively overcomplicated.
I won’t argue that the web is complicated, but a lot of that complexity comes from the necessity of supporting so many different environments that you can’t control.
I’d also like to ask when the last time you used JS was-- we use one UI framework (Angular) but no lodash, jquery, etc. to provide library functionality. Everything’s just built into JS now.
I can understand accounting for different environments. That’s unfortunately unavoidable. But I found web framework developers in particular have a weird tendency of piling up ungodly amounts of abstractions just for the sake of it.
It’s kind of a cultural problem in modern software development in general imo. It’s not limited to web dev by any means, but it’s particularly bad there because JS lends itself to it quite well.
I had to go back to working with React just recently.
I’m technically using TS, but the standard library is the same anyways. It hardly has everything imo.
It does have what it needs to interface with the browser, and quite a few -sometimes poorly thought out- facilities, but not much more.
Don’t get me wrong, for a web scripting language it’s plenty, but if one wants to use JS for stuff that isn’t just putting a simple page on a screen, that’s not enough.
You can’t write files without Node specific APIs.
You can’t even do proper bitwise operations because everything’s a float.
Binary serialization is a pain and proper deserialization in general is not enforced, even in TypeScript, because types are an illusion.
Up until recently there were no synchronization primitives, though now the idea of having them in JS seems terrifying.
There are no other data structures than arrays and maps, which are often not enough.
It’s just not a language I’d use for anything more than… well… Scripting.
But even though other, better solutions exist for cross platform development, people insist on using JS, so here we are.
For all the hate PHP gets (or used to get) it’s ecosystem is amazing. And so is the language and standard library itself for the most part. It still inherits some of the original issues, but a lot of work has been done to minimize them.
People dislike JS because it’s packed full of moronic footguns and technical debt.
Lol, no it’s not. The literal only footgun is the truthiness aspect of equality and using ===, and it’s really not hard to figure out and avoid. Especially given that linters will automatically flag it for you.
TypeScript is better, but at the end of the day it’s just an illusion. Add an any anywhere, which will happen, and you’re back to square one.
It is extremely easy to not let any slip into your code, you do this little thing called review code before merging. Crazy, I know, but by just following the most basic software development practices it turns out you can also avoid other basic junior mistakes! Wild right?
And lmao, oh my god the web ecosystem is ass because a framework for producing robust complex applications isn’t just an html and CSS file? Lmao bruh, tell me you’ve never coded in a different language without saying you’ve never coded in a different language. You think a .csproj or a .gradle file is simpler and more intuitive?
You’re mistaking basic junior programming mistakes for issues with the language.
Lmao bruh, tell me you’ve never coded in a different language without saying you’ve never coded in a different language.
I’ve been a software developer for over 10 years, on both on the front end and the back end.
I’ve worked with jQuery, React, plain old DOM manipulation, god damn PHP. I’m not new to web development.
Outside of web technologies, I’ve worked on nautical charts processing software and microcontroller firmware in C, C++ and Rust.
I’ve worked on native GUI applications with C++, Java and C# using JavaFX, WPF, GTK, Qt.
All under strict corporate standards.
I also work on compilers and rendering engines in my spare time.
So no, I’m not a “junior programmer” making “basic junior programming mistakes”. Your favourite language is ass.
You shouldn’t immediately jump to the conclusion that someone has never written a line of code only because they say so.
Sorry if it hurts your feelings, but even senior developers, web or otherwise, say it. I’m not the one swimming against the current, you are.
And lmao, oh my god the web ecosystem is ass because a framework for producing robust complex applications isn’t just an html and CSS file?
Alright, let’s do a little experiment, shall we? Let’s try and create an empty electron app with React and TypeScript.
A quick create-electron-app and some configuring TS, ESLint and WebPack later we reach a whopping 3_087_725 lines of code. 3 million lines. ~700MB.
This all requires a linting step, a pre-compilation step though tsc, multiple additional translation steps through webpack for older ES versions.
All of that for an empty page on a webview.
This is batshit crazy. And I come from fucking CMake for crying out loud.
There is nothing robust about this, the slightest misstep and your sourcemaps are fucked.
Whoops the author of left-pad decided to pull it from npm - half the JS ecosystem on its knees.
Whoops the author of is-even one day decides it’s a stupid package to need - half the JS ecosystem on its knees.
Web developers are standing on a crumbling, fermenting pile of shit. Get over it.
…
With that said, you can still enjoy JS and all the web stuff, there’s nothing wrong with that…
Sorry if it hurts your feelings, but even senior developers, web or otherwise, say it. I’m not the one swimming against the current, you are.
Lmao bro, I don’t think I’m the one with hurt feelings given your unhinged credential boasting and several paragraphs of unprompted bitching about electron.
You make basic JavaScript mistakes that should be caught by linters, and certainly by any intermediate to senior level reviewer. Get over it and learn to be better and not make basic mistakes.
You seem to confuse “people making mistakes” with “a language that is designed in such a way that those mistakes are not only common, but integral part of the experience.”
I’m not saying I make such mistakes, I say the design is crap. It’s not a skill issue, it’s a design issue.
People say null pointers were a mistake. I’m inclined to agree. Not because I get a null pointer exception every five minutes, but because there are better ways to handle cases like that.
You said I was a rookie, I proved you wrong.
You said there was nothing crazy about web application complexity, I provided you with a common, glaring example. There’s nothing unhinged in saying “look I installed Electron and React and not my project has 3 million lines of crap I have to worry about”.
Everything else was just emphasis for the sake of it.
But when you don’t have a valid argument, you resort to personal attacks. Maybe it’s you that should learn to be better.
Hi, I don’t really code besides computation stuff in Python. You seem to be really knowledgeable, could I ask, what does the future of the web look like? Is it Rust and WASM? Or will JS and TS always have a place even a decade from now?
The fairly unique thing about the web is that the tech stack is pretty much entirely dependent on what browsers are “winning” at any given time. There are web standards, but Chrome steamrolls them regularly (either by ignoring them or by pressuring the committee to standardize what they want). This is why browser monoculture is bad, and why people recommend Firefox and other non-Chrome (or really, non-WebKit) browsers, as a matter of principle.
So right now, with Chrome’s dominance, Mozilla’s struggles, and the extremely slow progress of WebAssembly and WASI, it definitely feels like JavaScript will remain dominant for a long while. But since Chrome does support WebAssembly and Google participates in WASI, and since there’s no fundamental reason why WASI can’t eventually provide everything that JS does today, there’s good reason to expect the JS stranglehold not to last forever.
And the great thing about WASM/WASI is that, since it’s designed as a compilation target rather than a language, there won’t be any remaining reason for a single language (such as Rust) to dominate. Rust got an early lead in WASM because they put the effort into making it a viable target platform for the compiler, and because it’s the kind of language that attracts people who dislike JavaScript (such as myself). But there’s no reason a different language couldn’t rapidly become the most commonly used WASM language if, say, a web framework in a previously-niche language becomes popular. (After all, Rails, a back-end framework, is what popularized Ruby.)
I’m not saying I make such mistakes, I say the design is crap. It’s not a skill issue, it’s a design issue.
That’s what people with skill issues tend to say.
You learned how to write == in every other language, but you can’t figure out === in typescript?
You’re bitching and whining about a tiny syntax issue that enables backwards compatibility for literally every web site ever created.
You said I was a rookie, I proved you wrong.
You apparently still bitch and whine like a rookie. Maybe work on your emotional maturity if you want to come across as an experienced senior and not just a Reddit-read edge lord.
You said there was nothing crazy about web application complexity, I provided you with a common, glaring example.
No, you didn’t.
There’s nothing unhinged in saying “look I installed Electron and React and not my project has 3 million lines of crap I have to worry about”.
Yes, there is, given that the vast majority of web applications run in this thing called a web browser, and you decided to instead choose the project example where you install a whole web browser alongside operating system shims into your project.
Not that’s what people who can recognize genuine architectural defects and aren’t blind fanboys say.
You apparently still bitch and whine like a rookie.
Only to your eyes since apparently pointing out genuine problems is whining. It’s okay for people not to like the stuff you like. And no, using a few swear words for emphasis doesn’t make someone immature, nor does listing what one has worked with for context.
You learned how to write == in every other language, but you can’t figure out === in typescript?
…you still haven’t realised that === is not what I have a problem with have you? It’s literally a non issue. In fact, equality in general is a non issue. It’s the wonky standard library, lack of proper support for binary operations, serialization and almost everything being an afterthought that I have a problem with.
Does it prevent me from using the language and write proper, stable software? No. But it’s not good.
you install a whole web browser alongside operating system shims into your project
Except that amounts to a mere ~180_000 lines of the 3 million. Did a plain create-react-app without Electron, still over 3 million.
Now, since it’s impossible to have a genuine conversation if the other party’s response is “haha you suck” to any genuine, documented criticism, are you gonna grow up or are you gonna keep acting like an offended 13 year old who can’t find a better retort?
Which is faster, getting a squiggle instantly or discovering a silly bug at runtime later? So happy I could write code in Typescript and be confident it would do what I expected when it ran without digging out the debugger.
As much as people like to make fun of JS/TS, I think you’re right, especially compared to the languages you mentioned. It’s my second-favorite language after Rust.
I think I would put Swift above it as well, except I don’t really use it since it’s too domain-specific in practice.
The newest iteration of the language might be okay, but the ecosystem is an absolute mess.
Working with npm projects is always a pain, everything changes all the time for no reason, and often enough in subtle ways you can’t anticipate.
Plus, there’s just an army of not very good and/or inexperienced developers vomiting their incompetence into the ecosystem.
Languages are not isolated. Java doesn’t force abstractFactoryBuilders, yet hundreds of developers follow that pattern. So Java in practice is rather verbose.
The language and its standard libraries lead developers towards common patterns. Javascript’s standard library is pretty sparse excluding browser-only web apis, so there are tons of external libraries to fill the gap for better or worse.
Languages are not isolated. Java doesn’t force abstractFactoryBuilders, yet hundreds of developers follow that pattern. So Java in practice is rather verbose.
Java basically does because it did not support functional programming forever forcing most of the base standard libraries to eschew those patterns (looking at you spring), and because even today it does not treat functional programming as first class and it is difficult to accomplish the same things with it then with other languages.
It is also missing many extremely common shorthand syntax expressions like optional chaining.
Not really, no. The over-abstraction Java is often doing is a question of mindset. Java devs tend to be very keen on reusability , which is fine, but often enough the result is unusable.
The problems behind abstractFactoryBuilders are not inherently unsolvable without these constructs, it’s just that Java devs chose this rather weird approach.
I absolutely agree with you. If I can avoid NPM I will indeed do so. Sometimes that means using Deno, but sometimes it can be a valid reason to avoid using the language altogether. And sometimes we have to suck it up 🤷♂️
I wish death upon it, but it just won’t die. I guess that’s cuz it’s the only frontend. Or at least the only frontend that allows DOM manipulation.
That’s exactly it. Every single webapp in the world has some level of javascript in it.
Noob question here. What’s DOM manipulation?
Document ObjectModel. Think using code to add a JavaScript to make a drodown menu appear like for a navigation bar. That would be manipulation. And I think there’s so much more Angular and React do with DOM that I don’t know enough to explain it.
thanks to wasm any language is a browser running language. JS is relegated to some token binding boilerplate as part of any framework and with things like servo/tauri rendering html will be pure rust
Theoretically yes, practically you may have to deliver a whole runtime depending on the languagey making websites even bigger and slower to load initially. And unless it’s a webapp with data processing on the client the perceived performance benefits may be negligible.
correct
good languages like rust have tiny bundles and initialize in microseconds, of course :)
It’s because it’s a great language. Legitimately cannot understand why anyone would dislike it, especially with the the ES5+ editions and the advent of Typescript.
I started with C#, and have used Python, Java, PHP, and Ruby in professional capacities and still find Typescript to be my favourite by a significant margin.
People dislike JS because it’s packed full of moronic footguns and technical debt. The “standard library” is full of baffling decisions and, much like the language, rarely does what you expect. Even its creator agrees it’s a terrible language and should have been replaced by now.
TypeScript is better, but at the end of the day it’s just an illusion. Add an
anyanywhere, which will happen, and you’re back to square one. It also still inherits some of the weirdness of JS, because it is just JS with fake types bolted on. Plus, the amount of work one has to do to create a proper library with TypeScript support completely undermines the few advantage of JavaScript. Might as well use a real statically typed language at that point, at least you’d be sure your types are actually enforced.Also, the whole web ecosystem is ass. The hoops one has to jump through nowadays to do web development are absolutely batshit crazy. And no, having a
create-whateverthat sets things up for you is not a real solution.I don’t recall the experience being even equally pleasant in other languages, let alone better.
It definitely isn’t in some circumstances.
Frankly I’d put C/C++ in a similar category when it comes to compilation.
Dealing with Make, CMake, linkage and all that can be a nightmare.
The ecosystem is a little bit better though in my opinion. If nothing else you get a proper standard library and don’t have to rely on thousands of dependencies to get anything done… or you often roll your own if you are in C… which is meh.
I find Rust, C#, Go and anything slightly more modern to be a great or at least good experience.
Python as well if you use venv and your runtime and package versions align.
My point is, there is no perfect platform and ecosystem, but the web is generally regarded as one of the poorest.
I’m not saying someone can’t enjoy working on web stuff, they most certainly can. But it is objectively overcomplicated.
I won’t argue that the web is complicated, but a lot of that complexity comes from the necessity of supporting so many different environments that you can’t control.
I’d also like to ask when the last time you used JS was-- we use one UI framework (Angular) but no lodash, jquery, etc. to provide library functionality. Everything’s just built into JS now.
I can understand accounting for different environments. That’s unfortunately unavoidable. But I found web framework developers in particular have a weird tendency of piling up ungodly amounts of abstractions just for the sake of it.
It’s kind of a cultural problem in modern software development in general imo. It’s not limited to web dev by any means, but it’s particularly bad there because JS lends itself to it quite well.
I ❤️ abstraction. I’m an abstractionpilled layercel. I’m in my abstracting era.
Ah that’s fine. There’s nothing wrong with abstraction, until it becomes too much.
I had to go back to working with React just recently. I’m technically using TS, but the standard library is the same anyways. It hardly has everything imo.
It does have what it needs to interface with the browser, and quite a few -sometimes poorly thought out- facilities, but not much more.
Don’t get me wrong, for a web scripting language it’s plenty, but if one wants to use JS for stuff that isn’t just putting a simple page on a screen, that’s not enough.
Maybe you mean Node instead of JS?
What kind of standard library features are you looking for that don’t exist?
Anything that isn’t plain web browser stuff.
You can’t write files without Node specific APIs.
You can’t even do proper bitwise operations because everything’s a float.
Binary serialization is a pain and proper deserialization in general is not enforced, even in TypeScript, because types are an illusion.
Up until recently there were no synchronization primitives, though now the idea of having them in JS seems terrifying.
There are no other data structures than arrays and maps, which are often not enough.
It’s just not a language I’d use for anything more than… well… Scripting. But even though other, better solutions exist for cross platform development, people insist on using JS, so here we are.
C# with the M$ echosystem sucks ass though. It’s like at first wow nice language, now how do you do this or that basic stuff and it’s just crap.
I want a Map. map map; ? Oh no ; Map map=new(); ???
Where are the destructors?
Etc.
I get the feeling it’s too steered by the corporate and not enough open source.
For all the hate PHP gets (or used to get) it’s ecosystem is amazing. And so is the language and standard library itself for the most part. It still inherits some of the original issues, but a lot of work has been done to minimize them.
I think it probably could be, in Lisp. Like the one they used in early MIT computer labs (Scheme).
Many of the best ever known programmers came out of MIT computer labs, and for good reason.
Lisp on the web is a fascinating alt history scenario
Yes. And I want academics online like Matt Parker to discuss it with me.
Lol, no it’s not. The literal only footgun is the truthiness aspect of equality and using ===, and it’s really not hard to figure out and avoid. Especially given that linters will automatically flag it for you.
It is extremely easy to not let
anyslip into your code, you do this little thing called review code before merging. Crazy, I know, but by just following the most basic software development practices it turns out you can also avoid other basic junior mistakes! Wild right?And lmao, oh my god the web ecosystem is ass because a framework for producing robust complex applications isn’t just an html and CSS file? Lmao bruh, tell me you’ve never coded in a different language without saying you’ve never coded in a different language. You think a .csproj or a .gradle file is simpler and more intuitive?
You’re mistaking basic junior programming mistakes for issues with the language.
I’ve been a software developer for over 10 years, on both on the front end and the back end.
I’ve worked with jQuery, React, plain old DOM manipulation, god damn PHP. I’m not new to web development.
Outside of web technologies, I’ve worked on nautical charts processing software and microcontroller firmware in C, C++ and Rust.
I’ve worked on native GUI applications with C++, Java and C# using JavaFX, WPF, GTK, Qt.
All under strict corporate standards.
I also work on compilers and rendering engines in my spare time.
So no, I’m not a “junior programmer” making “basic junior programming mistakes”. Your favourite language is ass.
You shouldn’t immediately jump to the conclusion that someone has never written a line of code only because they say so.
Sorry if it hurts your feelings, but even senior developers, web or otherwise, say it. I’m not the one swimming against the current, you are.
Alright, let’s do a little experiment, shall we? Let’s try and create an empty electron app with React and TypeScript.
A quick
create-electron-appand some configuring TS, ESLint and WebPack later we reach a whopping3_087_725lines of code. 3 million lines. ~700MB.This all requires a linting step, a pre-compilation step though
tsc, multiple additional translation steps throughwebpackfor older ES versions.All of that for an empty page on a webview.
This is batshit crazy. And I come from fucking CMake for crying out loud.
There is nothing robust about this, the slightest misstep and your sourcemaps are fucked.
Whoops the author of
left-paddecided to pull it from npm - half the JS ecosystem on its knees.Whoops the author of
is-evenone day decides it’s a stupid package to need - half the JS ecosystem on its knees.Web developers are standing on a crumbling, fermenting pile of shit. Get over it.
…
With that said, you can still enjoy JS and all the web stuff, there’s nothing wrong with that…
Lmao bro, I don’t think I’m the one with hurt feelings given your unhinged credential boasting and several paragraphs of unprompted bitching about electron.
You make basic JavaScript mistakes that should be caught by linters, and certainly by any intermediate to senior level reviewer. Get over it and learn to be better and not make basic mistakes.
You seem to confuse “people making mistakes” with “a language that is designed in such a way that those mistakes are not only common, but integral part of the experience.”
I’m not saying I make such mistakes, I say the design is crap. It’s not a skill issue, it’s a design issue. People say null pointers were a mistake. I’m inclined to agree. Not because I get a null pointer exception every five minutes, but because there are better ways to handle cases like that.
You said I was a rookie, I proved you wrong.
You said there was nothing crazy about web application complexity, I provided you with a common, glaring example. There’s nothing unhinged in saying “look I installed Electron and React and not my project has 3 million lines of crap I have to worry about”.
Everything else was just emphasis for the sake of it.
But when you don’t have a valid argument, you resort to personal attacks. Maybe it’s you that should learn to be better.
Hi, I don’t really code besides computation stuff in Python. You seem to be really knowledgeable, could I ask, what does the future of the web look like? Is it Rust and WASM? Or will JS and TS always have a place even a decade from now?
The fairly unique thing about the web is that the tech stack is pretty much entirely dependent on what browsers are “winning” at any given time. There are web standards, but Chrome steamrolls them regularly (either by ignoring them or by pressuring the committee to standardize what they want). This is why browser monoculture is bad, and why people recommend Firefox and other non-Chrome (or really, non-WebKit) browsers, as a matter of principle.
So right now, with Chrome’s dominance, Mozilla’s struggles, and the extremely slow progress of WebAssembly and WASI, it definitely feels like JavaScript will remain dominant for a long while. But since Chrome does support WebAssembly and Google participates in WASI, and since there’s no fundamental reason why WASI can’t eventually provide everything that JS does today, there’s good reason to expect the JS stranglehold not to last forever.
And the great thing about WASM/WASI is that, since it’s designed as a compilation target rather than a language, there won’t be any remaining reason for a single language (such as Rust) to dominate. Rust got an early lead in WASM because they put the effort into making it a viable target platform for the compiler, and because it’s the kind of language that attracts people who dislike JavaScript (such as myself). But there’s no reason a different language couldn’t rapidly become the most commonly used WASM language if, say, a web framework in a previously-niche language becomes popular. (After all, Rails, a back-end framework, is what popularized Ruby.)
Edit to add: I say “fairly unique”, but in fact there’s a very analogous situation with C: https://faultlore.com/blah/c-isnt-a-language/
That’s what people with skill issues tend to say.
You learned how to write == in every other language, but you can’t figure out === in typescript?
You’re bitching and whining about a tiny syntax issue that enables backwards compatibility for literally every web site ever created.
You apparently still bitch and whine like a rookie. Maybe work on your emotional maturity if you want to come across as an experienced senior and not just a Reddit-read edge lord.
No, you didn’t.
Yes, there is, given that the vast majority of web applications run in this thing called a web browser, and you decided to instead choose the project example where you install a whole web browser alongside operating system shims into your project.
Not that’s what people who can recognize genuine architectural defects and aren’t blind fanboys say.
Only to your eyes since apparently pointing out genuine problems is whining. It’s okay for people not to like the stuff you like. And no, using a few swear words for emphasis doesn’t make someone immature, nor does listing what one has worked with for context.
…you still haven’t realised that === is not what I have a problem with have you? It’s literally a non issue. In fact, equality in general is a non issue. It’s the wonky standard library, lack of proper support for binary operations, serialization and almost everything being an afterthought that I have a problem with. Does it prevent me from using the language and write proper, stable software? No. But it’s not good.
Except that amounts to a mere ~180_000 lines of the 3 million. Did a plain create-react-app without Electron, still over 3 million.
Now, since it’s impossible to have a genuine conversation if the other party’s response is “haha you suck” to any genuine, documented criticism, are you gonna grow up or are you gonna keep acting like an offended 13 year old who can’t find a better retort?
THANK YOU
I worked for a company that refused to use TypeScript because it “slowed devs down”. It was…a laughable period in my life.
Which is faster, getting a squiggle instantly or discovering a silly bug at runtime later? So happy I could write code in Typescript and be confident it would do what I expected when it ran without digging out the debugger.
typescript is a linter
While the rest of the world shifted left dudes went ahead and shifted right
As much as people like to make fun of JS/TS, I think you’re right, especially compared to the languages you mentioned. It’s my second-favorite language after Rust.
I think I would put Swift above it as well, except I don’t really use it since it’s too domain-specific in practice.
The newest iteration of the language might be okay, but the ecosystem is an absolute mess.
Working with npm projects is always a pain, everything changes all the time for no reason, and often enough in subtle ways you can’t anticipate.
Plus, there’s just an army of not very good and/or inexperienced developers vomiting their incompetence into the ecosystem.
Languages are not isolated. Java doesn’t force abstractFactoryBuilders, yet hundreds of developers follow that pattern. So Java in practice is rather verbose.
The language and its standard libraries lead developers towards common patterns. Javascript’s standard library is pretty sparse excluding browser-only web apis, so there are tons of external libraries to fill the gap for better or worse.
Java basically does because it did not support functional programming forever forcing most of the base standard libraries to eschew those patterns (looking at you spring), and because even today it does not treat functional programming as first class and it is difficult to accomplish the same things with it then with other languages.
It is also missing many extremely common shorthand syntax expressions like optional chaining.
Not really, no. The over-abstraction Java is often doing is a question of mindset. Java devs tend to be very keen on reusability , which is fine, but often enough the result is unusable.
The problems behind abstractFactoryBuilders are not inherently unsolvable without these constructs, it’s just that Java devs chose this rather weird approach.
I absolutely agree with you. If I can avoid NPM I will indeed do so. Sometimes that means using Deno, but sometimes it can be a valid reason to avoid using the language altogether. And sometimes we have to suck it up 🤷♂️
B-b-b-but you can’t do that!!1! What if my customer wants to calculate
5+"three"*[]???