71–80 of 247 posts
And from the linked post on the same website.
> if you write vanilla HTML, CSS, and JS, all you have to do is put that code in a web browser and it runs.
Very (very, very) few large projects use plain JS (instead of TS) these days. Let's stop acting like all these people don't know what they're doing.
This post is probably applicable to selected tiny and small projects. And for some of those, it may be better if there was no JS at all.
Isn’t using something like the Google closure compiler considered a good thing? This post seems to suggest tools like that in your pipeline should be avoided.
The problem isn't the tool or the dependency—it's the developer's temptation to over-engineer. We grab a framework because we lack the discipline to keep something simple. Is self-control in coding just a lost art now?
As a rationalization, sure, but never as the reason.
They do offer more than coding standards.
> Always, Always Require a Compilation Step And from the linked post on the same website. > if you write vanilla HTML, CSS, and JS, all you have to do is put that code in a web browser and it runs. Very (very, very) few large projects use plain JS (instead of TS) these days. Let's stop acting like all these people don't know what they're doing. This post is probably applicable to selected tiny and small projects. And…
There are much better arguments to use TypeScript than "five billion flies can't be wrong". Most other popular tech choices are in fact rather silly.
> Always, Always Require a Compilation Step And from the linked post on the same website. > if you write vanilla HTML, CSS, and JS, all you have to do is put that code in a web browser and it runs. Very (very, very) few large projects use plain JS (instead of TS) these days. Let's stop acting like all these people don't know what they're doing. This post is probably applicable to selected tiny and small projects. And…
They certainly have their reasons and they definitely aren't stupid, but it would be more useful to know what those reasons are and in what scope they are applicable.
You forgot to add containers and self host (and configure the server)
Im pretty sure that most packages and frameworks break less than your own code…
I think the issue is API breakage. Does your 5 year old NextJS project still work after npm update? Probably not! What about your simple Go server or FastAPI server. Probably yes.
Patient: Doctor, it hurts when I do this.
Doctor: Don't do this than.
Im pretty sure that most packages and frameworks break less than your own code…