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 :)
I think of contexts as being Go's answer to dynamic variables in earlier languages, like Lisp, and less like thread local storage (like Pthreads). Much like how Go works with errors, explicit is favored over implicit -- being able to see the context pass through, and whether a function expects a context, tells you a lot about the function you are about to call.
If a function does not take a context, you know it probably cannot be interrupted, just like when a function does not return an error, you know it should not fail. In my work projects, this is also a cue that the function does not do any logging since we always carry a zerolog.Logger in our contexts enriched with trace information about the request and handler.
This also makes life easier for me as a reviewer -- I can see the context passing, I can spot when there is a bad pattern, like retaining a context, or failing to handle an error. It does not require me to maintain a detailed mental map of which functions employ dynamic variables or can throw exceptions.
You can bypass a Nushell command by prepending "^". To use MacOS open, this would be "^open cat.gif"
This tic drives me nuts when I hop between fish (which I use for two features, better tab completion and background jobs) and nu. With 0.86, it might just be for background jobs, which is something Nushell has avoided dealing with entirely. CTRL-Z and "bg" is just muscle memory for me, much like "open."
Thanks, just bought a base model + dock. I've got a bunch of 128GB SDs, and my only current plans are to use it for PC-98 emulation, so load times shouldn't be a problem.
You can work around this somewhat by moving things to external storage and they symlinking it back to the original spot (or so I've heard, I have the top end model and haven't filled it up yet).
only issue with microsd is very slow writing speed. For games that are in the dozens of gigabytes you will wait a LOOOOONG time for the process to finish,
