The Controversial State of JavaScript Tooling
1–10 of 160 posts
Re: The Controversial State of JavaScript Tooling
#2At Asana we now just Bazel [http://www.bazel.io] and TypeScript for our front end code. It made the tooling dramatically simpler.
Re: The Controversial State of JavaScript Tooling
#3A fantastic post. If only to find someone else talking about the downsides of hypermodularization.
> Unfortunately, the spirit and praise of the web in Remy’s post isn’t shared by many of these articles. To the contrary, the web development community is flooding in skepticism, negativity, and pessimism.
I started building on the web a year or two after Remy. I believe one reason for the lack of praise is the reason people came to the industry. He & I came because we loved the web, we loved to see what could be done.
Today, the web's an entirely different commercial being. People do this as a job (as do I, which I'm very thankful for), they have less time to see what can be done (constructive contributions take effort) and time is money, so let's develop fast and move on, slagging off everything as we go.
I've been jaded, I'm guilty of being negative about everything.
But I do see hope.
Re: The Controversial State of JavaScript Tooling
#4The web community is flooded in negativity because it was swamped by kids with overly idealistic, unrealistic, and heroic ideas about what the web was going to be post-Facebook.
Those people then realized that the web is, like all things, both real and imperfect. So now they're upset. This is all part of growing up.
People who have been involved with the web for a while are not in any way more jaded then before. They already witnessed PHP, PERL, Java Applets, Flash, the browser wars, and so on.
Re: The Controversial State of JavaScript Tooling
#5I thought this was a decent survey of where we're at, but I'm not sure what to take away. I don't care for "opinionated" as a description of tools or code, nor its opposite. It doesn't really mean anything, in my... opinion.
Re: The Controversial State of JavaScript Tooling
#6A fantastic post. If only to find someone else talking about the downsides of hypermodularization. > Unfortunately, the spirit and praise of the web in Remy’s post isn’t shared by many of these articles. To the contrary, the web development community is flooding in skepticism, negativity, and pessimism. I started building on the web a year or two after Remy. I believe one reason for the lack of praise is the reason p…
I heard similar opinions in 1998. I think it probably has less to do with the state of the industry & more to do with the state of the career of the observer.
Re: The Controversial State of JavaScript Tooling
#7It's interesting how none of the JS/tooling fatigue discussions mention Ember, which has one public-facing tool.
Re: The Controversial State of JavaScript Tooling
#8Web developers need more homotopy type theory, and to curb their NIMH hypermodularization epedemic.
Re: The Controversial State of JavaScript Tooling
#9Web developers need more homotopy type theory, and to curb their NIMH hypermodularization epedemic.
What could this comment mean, I wonder.
Re: The Controversial State of JavaScript Tooling
#10The modern JS ecosystem have that enterprise java feel to it of 2010.