They've got Zed, VSCode, Jetbrains... But no Emacs or NeoVIM
12,532 karma · joined May 15, 2016
They've got Zed, VSCode, Jetbrains... But no Emacs or NeoVIM
I say it in past tense because Bourbon drinkers in Canada are switching to similar liquors. "Corn Whisky" is selling well, now.
America doesn't need anything from the rest of the world, or so is claimed, so the rest of the world should not burden itself with purchasing American exports.
The problem is that it appears to do this via an AI Agent. This broadens the security concerns significantly.
They always have to squeeze, crush, and destroy. Rob every customer, ruin every product, so they can enrich themselves.
My local library has access to Kanopy, Libby, and Blackstone. And as a Canadian, I've got CBC gem as well.
The available library of films, documentaries, books, and so forth is enormous. All bereft of ads, and mostly bereft of slop.
So I block chrome, and require my permission to install any app. They get thirty minutes a day on devices that lack a browser or social media apps. Not even any YouTube.
They can browse the web on PCs that are visible to the whole living room.
I am not affiliated in any way with this company; it's simply that their website brought me joy and I wish to share that joy.
Art has utility, of course; but we're discussing primary goals.
Many other niche projects have enjoyed enough velocity to have meaningful utility, in my lifetime. Linux was still niche when I started using it in '94.
I've been following Haiku since it was announced. In that time a couple of personal friends have passed on, and a number of family members. In that time children have been born, gone to school, grown into adults, and had children of their own.
Projects that drag on forever make for an interesting artistic statement, but if their goals in any way include utility then velocity is important because time is important.
What is Emacs the best at these days?
It takes significant usage and training to overcome the overhead that Emacs imposes. There are other tools that are fast, free, and capable which do not have this problem.
Even tools which are reasonably extensible. Like VSCode. There's good reason that all the new agentic development environments aren't forks of Emacs or NeoVim.
And yes, much of Emacs is broken out of the box and it's been that way a long while. That's not a good thing.
Emacs isn't ready for the masses. Broken defaults, and a brittle experience once features are made working is standard.
I've used Emacs for thirty years now. I don't recommend it to new users.
They host binaries already; why not host all of the binaries necessary for the supported features to function?
What's important is that _you can change it_. Good defaults ensure that Emacs doesn't repel new users and casual users and users who are not interested in fiddling.
And this isn't a matter of color theme default, or font default; this is a shipped feature that _does not function_ without changes to the defaults! By default, it does not work.
But note that this is not the default. Users have to enable that behaviour, and know to enable it. That's a bad default.
Eglot won't help you get your system ready for LSP work, it will only avail itself if what's there. It doesn't even auto detect and configure that, either. There's no user prompting, so you'll have to read the docs to know that this even needs to be done.
Similarly, tree sitter support doesn't include the grammars! And those aren't typically sitting in your package repository, so users have to find a grammar and compile it themselves. There's not even a good recommendation given by Emacs on where to get them, leaving users to hope that whatever repository showed up on a Google search is both in good working order and safe to use.
It's really quite a failure on Emacs.
I often wonder if the current model has been driving away contributors, since it _feels like_ contributing effort to support someone else's paychecque.
It has good emacs support with geiser-chicken.
I wrote the initial support for chicken some 11 years ago; it wasn't _great_, but I see that Jao and others have worked on it some since then. Glad to see it's working well! - Strings and symbols passed to foreign code are not copied, they are
passed directly, any mutations done by external code will be visible on the
Scheme side.
- Complex numbers, C structs and unions can now be passed directly as
arguments and returned as results when interfacing to C code.
Those were major bottlenecks for any FFI-heavy Chicken Scheme app, and would often result in brittle and unsafe abstractions to work around. Glad to see this changed.https://dev.to/hyenast2/neal-stephenson-s-cryptonomicon-and-...
> “Most economists will acknowledge that technological progress can cause some adjustment problems in the short run. What is rarely noted is that the short run can be a lifetime.”
The redundant professionals will need to find other ways of generating wealth from their productivity, and that may not be possible in a reasonable amount of time. Not in the scope of their remaining lifetime.
It is possible to have excess productivity. AI allows an existing labour pool to rapidly surpass necessary productivity levels for the existing demand.
IE, let's say I live in a small town and I open a machine shop. Should I hire every mechanic that walks in the door, forever? No, absolutely not; there is an optimal number of mechanics to hire for the demand for services.
If somehow a tool comes to exist that doubles the productivity of mechanics then laying off half the mechanics is next.
It's awful. Earthworm Jim and Sonic 2 are both great examples of how the art suffers; and the why is in the video I linked.
The waterfall in Sonic 2 was not meant to look like a fence.