I've had the same experience with things like vim emulation in vscode but I switched to LazyVim from vim a few months ago and it's been a smooth experience for me.
Databases on the other hand are built for this. After years of dissatisfaction with plain text accounting and many hours spent trying to improve it, I now use SQLite and it has been an enormous improvement.
Plaintext is nice for git but I only feel that when fixup-ing a single or small number of transactions. It does feel nice to be have all the details of a transaction in one place in a visually useful way. For one-off hacking and such it definitely feels easier to write O(n^4) python looping over trying to describe things with SQL and working at a scale where it doesn’t matter.
Plaintext as a UI into a SQL store seems an interesting project. I would love a git integration for committing changes after diff review and being able to stage individual txns or parts. Many years ago I was frustrated with ledger’s more loosey goosey syntax and trying these things and eventually gave up whatever the idea was at the time. I like the idea of a constant bidrectional sql<->plaintext that provides a requirement for reproducible parsing and serializing
In Portland, we did similar combined sewer pipe. But they didn't size it to handle the largest rainfall. The sewers still overflow a couple of times a year, but it is much better than dozens of times. Especially since it now only happens in the winter when no one is using the river. It would have cost a lot more to handle peak rainfall. It is already expensive, sewer costs twice as much as water here.
Portland has also been working on the “next steps” pointed out in this article. Street bioswales provide absorption and holding capacity. Downspout disconnection programs and new build codes drain rooftop rain locally on the property or out to the street instead of directly in to the sewers.
I think we have an easier time due to our lower density. Most lots have decent amount of exposed ground for rain infiltration, and the area has well draining soil. Tougher for cities more tight and built up. I think Seattle codified water management before the latest building boom so hopefully they will do alright too!
I could see that yabai could be a solution but haven't committed to a proper setup.
Anyone else using a single large monitor? FancyZones on Windows (PowerToys feature) looks pretty good, but I got sick of autoupdate BS random driver breaks (common linux thing) and went full mac.
My custom grid for 4K 43" snap zones in case anyone's interested: - diagram: https://imgur.com/a/axTw1tI - 3840x2160 1:1 grid: https://imgur.com/a/pUSoafG
For what it's worth, Dart has had synchronous and asynchronous generators (including `await for` statements) for as long as its had async/await. They are neat features. I've definitely written code using synchronous generators that would be hard to manually transform into a custom Iterable implementation.
But they add a large amount of complexity to the language implementations and it turns out are very rarely used in practice. Here's a quick scrape I did of the most recently published 2,000 packages on our package manager:
-- Style (64317 total) --
59409 ( 92.369%): normal =================================================
4842 ( 7.528%): async ====
42 ( 0.065%): async* =
24 ( 0.037%): sync* =
Async/await is clearly pretty useful with there being one for roughly every ten normal functions. But generators and async generators are barely used at all.Rust might be a in a different situation because efficient concurrency may be much more important in a systems language, but it's not clear to me that those same features carry their weight in Dart.
What could be better than that?
How about a drip coffee maker? A drip coffee maker creates little steam explosions to push water vapor to the top of the unit where it condenses and "drips" down over the coffee.
Since steam is being produced, in essence, distilled water is being used which if I understand the physics correctly, should be relatively free of metals.