118 karma · joined August 25, 2023
I have 99th percentile typing speed on QWERTY thanks to using PCs when too young for traditional touch typing to work. My arms fly around the keyboard and I have never gotten RSI _from typing_. Using the mouse precisely for a summer where vim was forbidden (thanks big banks) did yield almost instant RSI. Trying traditional touch typing (with no movement) also agitates my arms. But imo folks should learn speedtyping techniques for qwerty to avoid RSI and skip the rabbit hole of alternate layouts and keyboards. Lot of inconvenience and more wasted time than will likely ever be saved.
The only true advancement is steno / charachorder. The actual charachorder lite isn't quite there imo (chord detection sketchy) but one of these days I will use ZMK to add the most common chords to my qwerty keychron k2 with gateron browns. Not to mention ZMK has far more features (like modtap) that you find yourself wanting once you use something like Charachorder, and Charachorder is still not open source ("someday").
If you're really in need of even faster typing than "faster than anyone you know", first reevaluate your decision-making framework, then voice dictate.
Though it's no surprise Spotify failed at hardware given their general software competency. Broke the Chromecast app for years after the big mobile redesign. Not sure how it's possible to have such bugs in an app that shows three buttons, a progress bar, and a picture, but 2,000 engineers will find a way. Liked page on the phone app doesn't even load with bad service, which is like your umbrella not opening in the rain.
Anyone know of alternatives, even alternative clients?
So it's not just about being slightly better in some ways, but smoothing over so many paper cuts that it can be hard to see how they have added up overtime across ecosystems, like CPython and co having so many of its own vocab types, or HPC libs.
For example, the problem with this macro that causes this wouldn't even be problems in a well written Rust macro. They're artifacts of smart people trying to work around C's limitations.
But then the macro wouldn't have been written anyway because this is a port of a native Rust feature (which means it gets taken advantage of in community software).
This library on the other hand addresses a nasty papercut whose presence usually stops folks with modern language experience from choosing C when it might otherwise be valid. Plus you can't beat C's long-term stability.
Though I agree that 90+% who _think_ they still need C should probably move on to making Rust work for them, instead.
Have you tried downloading the file from s3 to /tmp, opening it with pandas, iterating through 1000 row chunks, pushing to DB? The default DF to SQL built into pandas doesn't batch the inserts so it will be about 10x slower than necessary, but speeding that up is a quick google->SO away.
I have since found Kuzu Db, which looks foundationally miles ahead. Plus no jvm. But have not yet given it a shot for rough edges. At the time, it was easier just to stay in plain application code.
Hopefully the workload intended by this tool won't notice the bloat. But it would be nice to be able to dump huge loads of data into this knowledge graph as well, and let the GPT generate queries against it.
https://www.theintrinsicperspective.com/p/why-we-stopped-mak...
https://adamdrake.com/command-line-tools-can-be-235x-faster-...