HN user
https://mazanec.dev
Yes, I had really cheap Windows Phone, and prior to Windows 10 Mobile, Windows were super fast and the phone was really fun to use. After Win 10 release, it become unusable - slow, rendering issues, etc.
Don't read it then. Why waste enrgy on complaining?
how hard would it have been really to type these two sentences by hand, in your own natural voice
On the other hand, do we have to complain about every seemingly AI written text?
People have been working on huge code bases without types for a VERY long time with no issue
People have been successfully writing assembly, your argument is useless.
You really should just not assume things about people with no reason other than "they dont like the things i like
That's not the reason for my comment. I truly don't understand how after so many years someone "isn't sold" on TypeScript. Sure, you don't have to use it if you don't want to, but if don't see how it's truly essential in current JS development, I don't know what else to assume, other than OP doesn't have enough experience.
it was created by microsoft
It was created at Microsft, but it was crated by Anders Hejlsberg who, I'm pretty sure, didn't want to just "create a safehaven to C# and java devs", he was actually solving real problems with JS development, completely orthogonal. You can argue that TS's first syntax was very C/C# inspired, and that Anders also created C#, but that's not what OP meant (or at least how it read).
I am still of the opinion that well organized and named JS is all that anyone needs
You probably didn't work on any medium or large codebase and didn't have to do a refactor.
it has always just felt like a maneuver to create a safehaven to C# and java devs scrambling to find roles in the modern landscape
What a nonsense. Perhaps read history of TypeScript and you'll learn why it was created.
"Across 660 trials with Claude Code, code cleanliness does not change the agent's pass rate. However, it substantially alters the agent's operational footprint: agents working on cleaner code use 7 to 8% fewer tokens and reduce file revisitations by 34%. Our findings suggest that traditional maintainability principles remain highly relevant in the era of AI-driven development [...]"
Probably because TypeScript is too important to leave it purely to AI. The gall to question Anders Hejlsberg :D
I'm looking not only for better build times, but for lower memory usage - running few LSPs on a large TypeScript codebases currently takes a lot of RAM.
For me, the main thing I love about Tailwind is that I don't have to create ad-hoc class names. No more BEM.
Almost accurate, but it's »Almost accurate. It's not "the route", but "a route".«.
When he dropped out in July their simply isn't enough time to run a functional primary and campaign for the vote in November.
That's only problem in the USA. Other western democracies are able to have snap elections done in two months.
You’d think that Jobs’ success
You mean his luck and other people's actual skills, right?
Nate Silver concurs and has some data on it [1].
[1] https://www.natesilver.net/p/the-sad-and-self-inflicted-decl...
Look at the typical React dev. They have zero leverage and can be replaced by vibe coding kiddies straight out of school or sourced from literally any company on earth.
Good luck maintaining such code. As we know from constant whining here on HN ("Hooks are too complicated..." "I don't understand useEffect"), React's model feels slightly more complex than other frameworks' models.
I can even argue that the more popular React is, the more React developers are needed.
I'm talking about how a single product is produced, not about its evolution through centuries. Anyway, the point wasn't to compare specific details, it's just an analogy.
I'm not arguing against the core arguments of the article (I agree with most of the points), but on the other hand, software development is (at least currently) an essentially iterative process - one that differs greatly from other production processes (e.g. buildings, cars). We all know how difficult it is to estimate how much development time something takes. Planning is hard and outcomes have therefore greater variability.
My guess is Gatsby wasn't chosen because it was a bad framework that is practically deprecated [1]
[1] https://www.smashingmagazine.com/2024/03/end-of-gatsby-journ...
They probably don't know Chesterton's fence [1].
[1] https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_...
If you're not into web development, Hacker News discussions about React are really bad way to gain unbiased perspective - it's been really popular here for last few years to just hate React (usually they know nothing, e.g. anyone who claims hooks compose worse than class components). But there's a reason why React is still used the most (large ecosystem, fast development and backwards compatibility). Of course, it's easy for inexperienced developer to produce slow and buggy apps (maybe slightly easier than in other frameworks, but that's practically unquantifiable), to include unnecessary or even badly written dependencies, etc. - but it's not the tool's fault when it's being used incorrectly.
https://simonsarris.com - My site
Too small page margins.
Gatsby was sunset because it was a bad framework build on bad decisions [1]. I tried to use it when it was new, and it was immediately obvious that "GraphQL for everything" leads to horrible DX.
What's there to contrast? It's basically the same experience as I had.
Just before Covid when everything was cancelled I booked some tickets through Kiwi and it was the worst decision - I spent year (!) getting my money back. I'm not saying Ryanair is a good company, but for their flight (i.e. one of those which I booked through Kiwi) they reimbursed me immediately. The second flight was EasyJet and they said they already sent the refund to Kiwi, while Kiwi said they got nothing. In the end it was Kiwi who sent me the rest, and in my view they truly are parasites (they also got a Covid loan from the Czech government). Maybe in the days of Skypicker when their search engine was good they provided some value, but nowadays I advise everyone to avoid them.
Raising kids is expensive, and today young people can't afford their own home - how can they have children? Sure, other things may also be affecting this, but IMO raising inequality correlates very well with lower birth rates (at national level); anecdotally, all my friends with high income are having at least two kids.
I'm assuming John Ousterhout's book A Philosophy of Software Design [1], which I would recommend reading before reading about design patterns, because it's more fundamental.
An hour later, I shipped a release build
I would love to see that pull request, and how readable and maintainable the code is. And do you understand the code yourself, since you've never done this before?