That’s a bit of evergreen topic. “stop bloating web with js” comes up fairly often and there are those people who think they found a solution and everyone should start using whatever they imagine is “best for everyone”.
In my opinion most of those people struggle with whatever they encountered in ecosystem and just want to find a way that fits them - while also trying to make others do the same.
*“You didn’t want to make things perfect. You just hated things the way they are.”*
Patternmaking for Menswear wad immensly helpful for teaching me how to create my own sewing patterns. But like anyone on HN, I draw my patterns with software I made.
fair. I used to think that too, but I find at least for golang, the sota models write tests way faster than I would be able to. tdd is actually really possible with ai imo. except of course you get the scaffolding implementation (I haven't figured out a way to get models to write tests in a way that ensures the tests actually do something useful without an implementation).
Your final sentence is interesting. I'm not a strict doctrine adherent, but in TDD, don't you write some minimal test, then implement the system to pass the test?
yes, but I find it hard to constrain it to a minimal implementation. what usually happens is it writes some tests, then an implementation, and then according to the thinking, makes some modification. it works with a relatively precise prompt, but starts to go a bit off the rails when you say things in broad terms ("write tests to ensure concurrency works, and the implementation to ensure said tests are correct")
Everywhere I've worked that uses DynamoDB, someone will invariably write a bunch of abstraction functions that become very annoying to debug, to add functionality, and can break an entire app if changed.
DynamoDB is admittedly very verbose, but it's almost always worth it to keep your CRUD operations written within the SDK rather than as an abstraction.
BTW repetitiveness is not free, it's cognitive load that a developer must deal with. An abstraction is also a bit of cognitive load that grows with the abstraction's complexity; the point is to find a balance that minimizes it.
To be fair I once spilled water all over my Macbook's keyboard. It wouldn't boot for weeks afterward. I got a new computer and then checked back a few months later and my Macbook was magically able to boot.
If we are maximising our input I should only read things I wouldn't write.
That's the beauty of communication and the free internet, what a joy to learn about someone elses way of thinking, add a little colour to my world view.
One of the things I miss most about the days of IRC chat networks, the personalities were big, broad and diverse, all mixing together. If someone is a narcissist, so be it, they still have value, knowledge, opinions to share. Online discourse these days can verge on corporate approved, totally empty. Apologies for the tangent.
Eh. My preferred subway activity is to listen to music and stare at the ground. I don't know... do I really need to stare at my computer screen every waking moment?
Safari is still the new IE. Well, not really "new", it has been IE all along. It's the only non-evergreen browser that remains, and I don't get why this isn't mentioned every time Safari is brought up. All of their spec implementations are meaningless when the only version that matters is the one forever stuck in whichever oldest iPhone n% of people still use.
Caniuse is pointless, their new "baseline" score is pointless; as long as enough people keep using their (perfectly fine and working) iPhones after official support stops and as long as they are not allowed to install a different browser (engine), that's the only data point you need to look at when choosing which browser features to use.
iPhone or iOS has the highest upgrade percentage of OS. ~85%+ are on iOS 18 or higher. Liquid Glass iOS is the first time update has been slower. But Apple generally achieve near or over 80% of latest iOS by end of its cycle i.e coming August / September.
One could argue Safari on iOS being like macOS where it could be updated standalone, but current rate isn't too bad.
it's also not possible for Safari to be the new IE because they don't have 95% marketshare. And IE's unique problem was that they pushed features that only they supported. Safari's problem is it doesn't support certain features
Also the thing is that there are plenty of features supported by Safari and Firefox that Chrome is slacking on. Nobody every complains about those features though because nobody would try to use a feature not supported by Chrome in the first place
> The only people who think Safari is the new IE are people who weren’t around for IE.
Absolutely true! I've said the same thing many times myself.
Stating that Safari is the new IE is one of the answers to:
"Tell me you didn't do web development in '90s and have no idea what you're talking about without telling me you didn't do web development in '90s and have no idea what you're talking about."
reply