Right? also, where's the thunderbolt ports? and it needs about another inch? maybe half inch on the screen. And really, 16gb is the new minimum. There's a whole bunch of acceleration and co processing features in the m series missing from the a series, so they really should put an m5 in there instead...
Seriously though. Every feature someone says is missing and should have been added would be another $100 on the cost. This is already likely a low margin product meant of someone who's only using a browser and maybe a few apps.
This largely shows how far standards have fallen - it’s not that long ago that 8 gigabytes of RAM was unthinkable in a desktop class machine - much less one that cost nothing once inflation was taken into account. It required buying an E10K style machine for tens to hundreds of thousands to get 64GB. And all of those hardware gains have been squandered by the electron people.
That said, we are where we are - I wouldn’t buy a machine with only 8GB for any purpose at this point.
“If you see anybody [building electron apps] in a restaurant, at a department store, at a gasoline station, you get out and you create a crowd. And you push back on them, and you tell them they're not welcome anymore, anywhere!” - a reasonable person, probably
How anyone could think their chat app or text editor should be able to bring a 32GB 8-core machine to a crawl is beyond me. I can have about 200 browser tabs open, but one discord chat open in the background and I’m stuttering. It’s offensive.
If you know what a user agent is, let alone how to change it, CORS is not meant for you.
Its guide rails to help the tech illiterate not get hacked. It raises the bar on what gets through. It’s not going to stop a determined attacker, but will catch enough to make a dent. Defense in depth and all that.
CORS (or rather the same origin policy, of which CORS is an explicit server-side opt-out) is not a generic security improvement, it solves a very specific problem: (Code on) website A being able to make requests to website B with the cookies of B (often implying user login state/authentication at B) and read the response.
In a (possibly better) parallel universe, cross-site requests just don't send cookies or other ambient authentication state like that by default, and we wouldn't need CORS.
Yeah.... The code isn't the hard part. That's not where the value is.
This hard part when you're doing in house stuff is getting a good spec, ongoing support, and long term maintenance.
I've gone trough development of a module with a stakeholder, got a whole spec, confirmed it, coded it, launched it, and was then told it didn't work at all like what they needed. It was literally what they told me... I've said 'yes we can make that report, what specific fields do you need' and gotten blank stares.
Even if you're lucky and the original stakeholder and the code are on the same page, as soon as you get a coworkers 'wouldnt it be nice if...' you're going to have a bad day if it's hand coded, vibecoded, or outsourced...
This has always been the problem, it's why no-code never _really_ worked, even if the tech was perfectly functional.
Seriously though. Every feature someone says is missing and should have been added would be another $100 on the cost. This is already likely a low margin product meant of someone who's only using a browser and maybe a few apps.
reply