> But I do take some issue with the alarmist framing of what's going on.
On the contrary, your framing is quite defeatist IMO. The fact that stores get robbed frequently does not mean we should just normalize that and accept it as a fact of life.
How many American lives would you sacrifice for that? The people who made the decision to fire a missile at this place didn't decide to start the war, once you have started the war you have to make ugly tradeoffs like being too liberal or too conservative with targeting decisions.
> How many American lives would you sacrifice for that?
For what? Removing a suspected mine or missile stash that had it existed would be used to target ships in the Strait? For that you're in favour of killing 170+ schoolchildren?
> The people who made the decision to fire a missile at this place didn't decide to start the war,
The people that decided to fire missiles are the people that decided to start a war by firing missiles .. during negotiations no less.
The people that drew up a potential target list did so years before .. the people that chose to start a war have had a full 12 months to re vet the target list a remove sites that are now schools ... but they failed to do so.
> The people that drew up a potential target list did so years before
And the building was a military installation years ago. Then Iran made it into a school, nobody is omniscient here, collateral damage will always happen in war.
If things stayed static and simple as you think they are, if Iran let US military spies freely go around and note targets, or if Iran updated USA when they move their military ops around, sure collateral damage would easily get avoided, but the situation isn't like that.
> The people that decided to fire missiles are the people that decided to start a war by firing missiles .. during negotiations no less.
No, the people who made the target list are not the same people who started the war. Trump isn't there picking which building to fire it if you thought that, its guys much further down. Nobody said "we want to kill a bunch of schoolchildren first day!", they tried hard to avoid such events or many more would have died, but you can always do more and its a tragedy that it happened once.
Two problems:
- people would need to know how to effectively include dependencies in a way that allows them to be tree shaken, that's a fragile setup
- polyfills often have quirks and extra behaviours (eg. the extra functions on early promise libraries come to mind ) that they start relying on, making the switch to build-in not so easy
Also, how is this going to look over time with multiple ES versions?
> people would need to know how to effectively include dependencies in a way that allows them to be tree shaken
Is the need for tree-shaking not 100% a side-effect of dependency-mania? Does it not completely disappear once one has ones dependencies reduced to their absolute minimum?
Maybe i'm misunderstanding what tree-shaking is really for.
You wouldn't if you look more deeply at this. He doesn't push for simplicity but for horrible complexity with an enormous stack of polyfills, ignoring language features that would greatly reduce all that bloat. .
That's also a problem. I've written JS that would work on any browser from the latest ones all the way back to IE5, and I'm not even a professional JS developer. It's not hard.
Maybe "professional" is the problem: they're incentivised to make work for themselves so they deliberately add this fragility and complexity, and ignore the fact that there's no need to change.
Next is the Microsoft Sharepoint of the JavaScript world. It’s a terrible solution to just about anything, and yet gets crammed into places and forced on people due to marketing-led decision making.
My 10 minute Next build was replaced with a 1 minute 30 second Vite build.
And such an extrodinary different is usually holding the tool wrong, but Next has years old open issues for many of the causes here (like forced output tracing) and has just ignored them. Possibly because the Next team's preferred deployment environment isn't affected?
Not meant as a gotcha but I'm surprised because people always tout it as being so much faster than Next. (4m with Turbo would have to be a crazy huge app IME)
An example that is hard to follow defeats the point. It's just showing what pattern is possible and you can imagine the abstraction layers and indirection that would make it happen accidentally.
On the contrary, your framing is quite defeatist IMO. The fact that stores get robbed frequently does not mean we should just normalize that and accept it as a fact of life.
reply