1. Yes, the size. I don't spend a lot of time thinking about "do I really want to bother with this in my pocket, I'm just going to the store."
2. The ecosystem. There's a lot of different firmware forks, people tinker and optimize. Which is important, because that helps with..
3. The UI. There's only a few buttons, no touch screen, so the power on experience sends you straight into the last page you were reading, and there's not a lot of farkles trying to drive engagement.
4. No touch screen. The buttons aren't very soft, and there's no touch screen, so you can just toss it back in your pocket, without turning it off, and pick it back up.
5. It's cheap, and it is not linked to my accounts. I'm not terribly worried about theft or someone accidentally knocking it out of my hand.
All that comes down to just.. no ceremony. No unlock the screen, push past the notifications, find the app, wait for Kindle to pass some advertising back and forth with Amazon. Nothing. Pick up the book, read the next page while you are waiting for coffee to steep.
That said, there's some suck to be had:
6. No frontlight. You can't read in the dark without a separate light.
7. No, the font rendering is not perfect, the DPI is pretty low. This is not the most beautiful screen. But it's pretty readable. I got over it.
8. It's a pretty small screen. If you have awful eyesight, you're going to go through a lot of page turns. But if you are prone to skipping ahead and scanning, you might actually read more of the book this way.
9. It is not fast. The firmwares I have used all do some indexing at the start of each chapter, and it can take a few seconds.
10. The vendor either doesn't quite understand its customers (it seems like xteink got lucky sometimes) or is scrabbling through parts bins and unable to communicate with its customers. The X4 Pro really confused its fans.
I think it really just comes down to "this thing is too simple to become more fucking adtech pretending to be useful."
Oh my yes. EVE Online can experience issues when a conflict in a solar system exceeds a certain number of players. Each system in EVE is a monolithic process, so, if a conflict gets out of hand, things get slow.
This is referred to as Time Dilation (TiDi) in EVE -- https://wiki.eveuniversity.org/Time_dilation -- it's an interesting engineering rathole, Fenris f/k/a CCP has been pretty open about their stack, and the challenges that have built up.
Anything that speeds up EVE lets more players cram in without experiencing TiDi, and this might let the devs escape Stackless Python, which is another interesting engineer rathole. (It's ratholes all the way down, and this is the one that got EVE on my radar, and has kept it there.)
Amusingly, when a coworker was looking for this postmortem, they found a different postmortem of three Claude issues that caused decay. This one was in the platform, not in Claude Code:
I think there's a certain amount of running with scissors going on here. I appreciate the transparency, but the time to remediation here seems pretty long compared to the rate of new features.
Would you mention some portable OLED models that are well made and dirt cheap? Was looking for such a thing before, right now I do not see anything below €400 on german Amazon. There are some "keyboard smash" random character string brands that do look shady.
Once this is done, you should be able to use Anthropic if you have an API key. (This was available before today's announcement and still works today as of Zed 0.149.3)
It's hard for me to read the Culture novels and not hear Porno for Pyros' "Pets" on loop in my head.
It is amusing that this essay starts with "Government" and does not get down to the intelligences until halfway through -- in my mind, it's all just the intelligences watching the funny monkeys play at still having meaningful role in the Culture and the surprising things they do at the edges of its influence.
Plenty of Culture Minds value humans/pan-humans in the books. They get involved, too, just look at the effort expended by the Sleeper Service in Excession for such a personal agenda.
Not to say that there isn't a good deal of joking at humans' expense by Culture ships, but in the end, all are Culture citizens.
Came here to say the same. I was fully expecting the irony of seing the world's smallest (and standard) text editor re-implemented in the most infamous bloat monster. Also, every software ever written is being rewritten in Webshit these days anyway.
I tried compiling it as suggested by the GitHub page.
The build folder weighs in at 618MB and it took 5 minutes and 139 packages to compile on a decent 2019 machine. The final executable is 84M (debug, 11MB after stripping)
It then takes something like 10MB of RAM for opening an empty file, of which 1MB is on the heap.
It is not Electron, but for an "ed" remake, it is definitely a bloat monster. Overall, it is 100 to 1000 times heavier than "ed".
EDIT: speaking of bloat, I remember when EMACS was nicknamed "Eight Megabytes And Constantly Swapping" as a joke on how bloated it was. Times have changed...
Most of the initial data on the heap is all of the embedded pre-formatted syntax definitions, which I decided was a small price to pay for a quicker startup (and since `cargo install` is unable to include any bundled syntax definitions).
Aside from that I guess I have included some pretty big libraries, which due to static linking basically add directly to the binary size. I'm open to replacing most of them for smaller versions, but I won't do it myself.
When I checked the memory usage I saw that bash is using 11 MB and hired 9.2MB, so I'm pretty satisfied with that. If you want some memory usage horror though, note that due to having unlimited undo/redo hired will constantly increase its memory usage for every change you make until you close it. (It is at least diff-based, so it doesn't blow up on larger files unless you change every line.)
Yep, decidedly a different time. Very different expectations about what functionality should be expected in a tool, and when it is meaningful to try to reduce memory usage.
It isn't too late yet, you can be the one to bring The Standard Editor to the Webshit masses!
The backing library https://github.com/sidju/add-ed could either be run through https://neon-bindings.com/ , or compiled into web assembly for that matter. Should just be a weekend project to create an electron `ed`, and if that isn't sufficiently bloated you can `node install everything`.
I was going to say that I expected the Webshit version to use different NPM packages for cursor-blink-on, cursor-blink-off, and cursor-blink-toggle (not to mention telemetry and the requirement to create a cloud user account), but it seemed out of context :)
1. Yes, the size. I don't spend a lot of time thinking about "do I really want to bother with this in my pocket, I'm just going to the store."
2. The ecosystem. There's a lot of different firmware forks, people tinker and optimize. Which is important, because that helps with..
3. The UI. There's only a few buttons, no touch screen, so the power on experience sends you straight into the last page you were reading, and there's not a lot of farkles trying to drive engagement.
4. No touch screen. The buttons aren't very soft, and there's no touch screen, so you can just toss it back in your pocket, without turning it off, and pick it back up.
5. It's cheap, and it is not linked to my accounts. I'm not terribly worried about theft or someone accidentally knocking it out of my hand.
All that comes down to just.. no ceremony. No unlock the screen, push past the notifications, find the app, wait for Kindle to pass some advertising back and forth with Amazon. Nothing. Pick up the book, read the next page while you are waiting for coffee to steep.
That said, there's some suck to be had:
6. No frontlight. You can't read in the dark without a separate light.
7. No, the font rendering is not perfect, the DPI is pretty low. This is not the most beautiful screen. But it's pretty readable. I got over it.
8. It's a pretty small screen. If you have awful eyesight, you're going to go through a lot of page turns. But if you are prone to skipping ahead and scanning, you might actually read more of the book this way.
9. It is not fast. The firmwares I have used all do some indexing at the start of each chapter, and it can take a few seconds.
10. The vendor either doesn't quite understand its customers (it seems like xteink got lucky sometimes) or is scrabbling through parts bins and unable to communicate with its customers. The X4 Pro really confused its fans.
I think it really just comes down to "this thing is too simple to become more fucking adtech pretending to be useful."
reply