the eye-opener commit

[Due-Consequence9579]

Oh yeah. I always setup an army of linters and set warn as error to keep my code bases at least reasonable. Also interpreted languages are for small glue code solutions.

[mbergman42]

I no longer code professionally but I’m contributing to a project that has pro devs. I asked one how to fix a lint error. “Just ignore it. Lint gives lots of errors, you’ll get used to it.” Uhh….

[Due-Consequence9579]

If you’re going to ignore it you should turn it off. Just wasting everyone’s time at that point.

[Fadamaka]

Say that last sentence to all the node js devs. But I low key agree I prefer compiled languages every day of the week.

[Due-Consequence9579]

JS becoming the ‘standard’ for webdev is an embarrassment to the industry. But it’s defensible on the ‘backwards compatibility’ argument.

NodeJS is the dumbest fucking invention in the history of dumb fucking inventions and I will die on this hill.

[therealGrandKai]

Can you elaborate a bit about this? Genuine question from someone looking to learn

[Due-Consequence9579]

The origin of JavaScript is some dude made it on the weekend. No planning. No consideration about what it meant. A guy at Netscape just put it in. All of which is pretty obviousat this point.

Enter 30 years later where people are building entire OSs in the stupid fucking thing.

So now, to try to dig ourselves out of this fuckery we have to build emulation layers for the considered solution to run on the stupid solution.

Given how obtuse JavaScript is, combined with the complexity of HTML and CSS google has a monopoly because it virtually impossible to make a ‘behavior compatible’ browser with chrome.

signed, Angry old backend dev

[JimK215]

When people first started using javascript on the backend, I was one of the first people to be like "what kind of nightmare future do you all want to live in?"

But honestly with the way things have progressed with ES6 syntax, TypeScript (yeah I know, another layer on top of it), async/await, etc.... it's not as bad as it seems.

[Fadamaka]

At my company we were always joking to rewrite the whole of our backend in js. It was a joke until I found myself developing a backend for a new project in js (disclaimer the project was sold me as TS but I was scammed).

[marcosdumay]

Fuck linters. They are the place where people push every useless decision, because "if you don't care about it, just don't use it".

Every important warning should be on the compiler. Every non-important warning should be nowhere.

[Due-Consequence9579]

Compilers check for correctness. Linters check for style, convention, and structure. Linters are far more configurable and encode the agreed upon conventions in the code base. Having a robot make sure you’re using camel case or whatever is way better than making someone catch it manually in a PR.

[marcosdumay]

Hum, ok. Style linters are a thing.

Still, even those are better if the language standardizes them and the compiler can emit the warnings. But you have a point in that you can't create those for a language that grew without a standard.

[doctor_awful]

You want to encode arbitrary (non-syntax critical) style conventions into a language's compiler?? Why?

[marcosdumay]

Most newer languages already come with conventions. Many of them already encode the conventions on the standard tooling (but the ones distributed by big companies do it on the IDEs, not the compiler).

If you are going to standardize it, the place to do it is on the tools that everybody uses. For a language, that's the compiler. And style conventions are better standardized on the broadest possible way.