JavaScript is a good language.
>>109084835Perl is superior to JavaScript
>>109084835I cant forgive JS for not having strict scoping and lacking OOP support. Otherwise modern JS is passable.
>>109084835It prints cash
It's better than TypeScript, that's for sure. I don't understand people complaining about JavaScript (so long as it's not used for horrible shit like React and friends). Sure it's not your typical compiled language, but it werks for browser shit. I've written a big JS framework, it's fine.
>>109084835Yes, for small scripts, but idiots like to pretend it's on par with real programming languages and then wonder why their webapps are filled with weird bugs and glitches that a real language would've caught at compile time or at least made easier to track down.
>>109084835It's terrible, but it's 10000000x better than other sloplangs out there, including rust, python or c.
>>109088860Yes, unironically it's slightly better than typescript is. Typescript is just a big meme pushed because pajeets can't program at a basic level.React also is shit, but still gets too much hate. It's slow and poorly made, becoming a huge mess real quick when considering non-trivial side-effect interactions and things like the rule of hooks, but it sure is convenient. The main issues related to react are really everything around react and not react itself, at least with the functional interface.
>>109088890This is a common misunderstanding among you zoomers who have very little real world programming experience outside webshittery. The real reason why apps are littered with weird bugs are browser behavior and implied behavior from dependencies and frameworks like react. The problem is that of programming culture, not so much the language.The issues with the language that used to lead to weird glitches have largely been addressed over time. As for what remains, it's an artifact caused by the language being meant to run on clients in a web browser, i.e. you can afford to fail to render something or for an animation to stutter, but you can't afford to crash the whole page or something similar.It is also absolutely possible to catch all kinds of bugs statically with js, such as using more advanced linters. This is routinely done in production environments. Meanwhile a lot of compiled languages don't catch basic mistakes that they should catch as well, hence why they, too, benefit from static analysis tools of all sorts.
>>109084835It is shit. It only qualifies as prog lang because you can write good software with it, with enough effort. And can even write readable code since ES6. And what those ecmascript standards are... It's basically adobe's ActionScript 2 and 3 that they used in flash runtime.The original JS is a meme not capable of anything at all. Modern JS is basically AS3 from Adobe Flash.
>>109084835besides the ugliness of UTF-16 strings and automatic semicolon insertion, JavaScript is pretty good.it is the ecosystem making it terrible: npm, webpack, node and all that shit.we made a fast JIT language for you, but you added a compile and build step anyway because it didn't seem like a serious language for you.
Yes
>>109084835robot sex will never happen.he has spoken.
>>109090272>The real reason why apps are littered with weird bugs are browser behavior and implied behavior from dependencies and frameworks like react.Exactly. A language that behaves this differently depending what you run the same code on sucks.>This is routinely done in production environments.And yet the resulting code still breaks far more often than native apps. I wonder why.
Rust is taking over everything. The trannies won.
morning sir, become polyglot,, many good language, parl include
>>109090379A robot is not a person, so it would be masturbation at best. No one says a women "had sex" with her vibrator.
>>109084835it is, I would even say it's the best language on the planet.I am a big fan of JavaScript
>>109092726>And yet the resulting code still breaks far more often than native apps. I wonder why.I don't think that's true. I think the breakage mode is simply different. That is, again, because of the fault tolerance model difference in the two cases (i.e. where you don't want to crash everything if your js dies in the browser, but you do want to do that in other languages as the default behavior).
>craft a simple language for the web>continue crafting shit until web development has become a dependency hell of frameworks and librariesI can't believe how much they fucked it up.
>>109092760Yet every time a native app moves to Electron or similar, or offers a web version of itself, that new version is a bug-ridden heap of shit that runs slower, eats way more memory, and has weird mysterious glitches.
>>109092776>runs slower>eats way more memoryBecause instead of running the program, you're now running a browser AND the program. Also, memory management is defined browserside, and browsers actually behave poorly in general and inconsistently on this. Fun fact.>bug-ridden>weird mysterious glitchesProof? I argue it's the same shit, but whereas you'd get silent corruption or a crash in the native version, you instead get weird animations or stutters in the electron version.
>>109092776I don't know anon, vscode is a pretty good example of an electron program that is quite good if the programmers know what they do.
>>109092844vscode still groids out the mouse cursor on light themes when combined with AMD GPUs on Windows. For over 2 years now.>https://github.com/microsoft/vscode/issues/204103
>>109092857And visual studio community edition?
>>109084835it is, actually way better than python, but in bad hands sadly, used to bloat the entire internet. normies try to implement typing system into it instead of using a proper typed language
>>109086657I think it has objects as far as I remember
>>109084835Yes, well designed, consistent, safe.
>>109094254Type systems are a brainlet meme.
>>109092909no, because that's part of the problem. vs code is a glorified web browser and issues with chromium are present in vs code.
>>109096111And what about visual studio community edition, numbnuts?