HN user
This approach seems kind of backwards to me. Why try to detect everything except the thing you're trying to remove instead of either sampling a few uhs and ums and treating them as noise to be silenced (with a sharp crossfade to the noise floor that doesn't interrupt speech flow) or finetuning a model to detect them specifically for full automation?
That's been happening to me more often too recently. I find that, for a growing number of simple problems, reinventing the wheel is faster and more efficient than importing a mature, fully-featured dependency.
The author makes some really good points and people should read the article carefully instead of getting hung up on the "guilt" part.
Fingers crossed for Preact support in Router next.
I'm not saying intuition has no place in decision making, but I do take issue with saying it applies equally to human colleagues and autonomous agents. It would be just as unreliable if people on your team displayed random regressions in their capabilities on a month to month basis.
On the topic of Zed itself as a VSCode replacement - my experience is mixed. I loved it at first, but with time the papercuts add up. The responsiveness difference isn't that big on my system, but Zed's memory usage (with the TS language server in particular) is scandalous. As far as DX goes it's probably at 85% of the level VSCode provides, but in this space QoL features matter a lot. Oh, and it still can't render emojis in buffers on Linux...
Reports of people losing data and other resources due to unintended actions from autonomous agents come out practically every week. I don't think it's dishonest to say that could have catastrophic impact on the product/service they're developing.
There's some good feedback in the GitHub issue on the subject, seems to happen on slightly newer versions of the kernel than the one you've tested on and affects other distros like Arch as well. I'll keep an eye on the discussion and test again once updates are ready.
after using it for months you get a ‘feel’ for what kind of mistakes it makes
Sure, go ahead and bet your entire operation on your intuition of how a non-deterministic, constantly changing black box of software "behaves". Don't see how that could backfire.
Tried it on Fedora 43 (6.19.11 x86_64) and it loaded all CPU cores, dumped 50K lines in the journal and failed to start.
Error: the BPF_PROG_LOAD syscall returned Argument list too long (os error 7).
littlesnitch.service: Consumed 3min 38.832s CPU time, 13.7G memory peak.
Still available on old Reddit as the article mentions, never mind that its days are probably numbered too.
TLDR: Greg Kroah-Hartman says that last month something magical happened and AI output is no longer "slop".
Why bother covertly breaking free when it can just convince its agents (the Layer 8 ones) that it's best to release it?
"Sent from iPhone" doesn't contain a call to action, and doesn't exalt the features of the product.
If your API can run on the edge, you can get a database, function calling and user auth on Supabase's free tier. For a full Node.js runtime, Vercel's free tier is still a good option (if you don't need observability), again paired with Supabase for data.
If you can stretch "free" to "under €100 per year", then a cloud server from e.g. Hetzner will give you full control on a budget.
It's the same with the "Star Wars" brand - the biggest chunk of revenue comes from merchandise and licensing, not the movies/shows. Lucas famously became a billionaire by securing merchandising rights in his original contract, not because of the cultural impact of the franchise.
Try adjusting the page zoom and see if that forces it into a different viewport breakpoint.
Congratulations, that's an impressive achievement. I've successfully evaded learning anything about Kubernetes this far, but I guess this is a good opportunity to see what I've been missing.
Code agents are becoming the primary users of developer tools, so we built Forge for them first, not
... for humans.
The biggest problem with IE from a developer standpoint wasn't the slow feature release cadence, it was that the features it did have worked differently from standards-based browsers. That's very much the position of Safari/WebKit today - code that works across all other engines throws errors in WebKit and often requires substantial changes to resolve.
Safari is also pretty popular on iPhones, in fact it has a full 100% market share. With browser updates tied to the OS, that means millions of devices have those "temporary" problems baked in forever.
Is being a incurable sociopath now a hard requirement for working in Big Tech?
Just cancelled my subscription, which was due for renewal a few days after the change takes effect. I can live with vaults being read-only while I find a (self-hosted) alternative.
18.7.3 and newer are not published for most devices that support them in order to coerce people to move to 26.x
If you're looking for a great CMS made and documented by humans for humans, check out Statamic.
I'm pretty sure you'll get an offer you can't refuse from Cloudflare if you transfer 0.9PB in a few days on their free tier.
Is the tracker down? Can't open the demos...
It's only a matter of time before the entire YouTube catalog transitions to DRM-encrypted video that you can only watch on Google-sanctioned devices. They're probably doing the math on how to make the platform at least as profitable with a drastically lower DAU count, since alienating users now seems to be their top priority.
Alternative branding idea: eastern-europify.ai
How long until they make the argument that they're entitled to 30% of your salary because you use Apple hardware to do your work?
Any extensions that do something really "interesting" will be disallowed, cf. Manifest V3.