My handwriting has degraded from consistent keyboard use over the last 30 years. Obisidan has replaced my paper notebooks, mostly because of this. However, it is handy to be able to mesh those notes with hyperlinks, LLM output snippets, quotes from other sources, embedded images, etc. Doing all of those other things would be laborious to impossible with paper.

Looking back, this was usually a substantial stumbling block for adoption of new tooling. Things have changed. All one has to do is look at what JS programmers will go through to scratch build entire toolchains on the back of npm. IMO, the bar has been moved up to allow _some_ installation friction rather than none.

IMO, if the tool is a solid improvement and installation is a one-liner, use it and promote it loudly so it continues to get support.

> The whale itself has never been sighted: it has only been heard via hydrophones, but its call has been detected since the late 1980s in a pattern that matches the migration of the blue whale and the fin whale. Those species call at 10 to 39 Hz and 20 Hz respectively.

So not only lonely, but sings in a falsetto by whale standards; a weirdo. A lonely fellow with a distinctly high-pitched voice.

I'm with you. While I'm no fan of the risk involved with missing a CC payment, there's a mountain of difference between credit and debit when it comes to fraud. It's literally you trying to get your money back (debit) versus some giant corporation trying to get _its_ money back (credit).

https://www.carsdb.com/en/news/1476

I get that's an apples-to-oranges comparison, considering that labor and material costs (not to mention subsidies and regulations) are probably not the same. But even at $40k, it would be cost-competitive with other EVs if nothing else.

Consider Japan's Kei car initiative, for example.

https://en.wikipedia.org/wiki/Kei_car#Description

https://en.wikipedia.org/wiki/Kei_car#Taxation_and_insurance

One route is to provide incentives, if not regulations, to force innovation on US automakers. The goal would be to yield products that are head-to-head competitive with imports.

> It seems to me though that the current strategy seems to be very short term thinking - trying to just hold back the tide.

I'm seeing that too, but from a different angle. The era of big trucks seems to be as much an effort to extract cash from the economy as it is taking advantage of a peculiar set of EPA and DOT regulations. Basically, "gettin' in while the gettin's good." It's not a long-term strategy because, at some point, people can't afford these behemoths and will go for the used car market next for cheaper goods. EVs may get caught up in that too, considering that they're aimed squarely at the sub-luxury tier and above. As we have no good cheap EV options at the moment, I think it's the same story.

I feel like the idea of fixed-point is under-utilized and very under appreciated. There are loads of applications where this is a better choice, let alone more performant.

In the worst case, if your local municipality sides with business over the little guy, that means potential brownouts and water shortages for you.

Sadly, the product line got worse before VSCode came out. Things are much better now.

That said, my gamer-brain wants to call this "Save-scumming at scale." Which is to say, a lot of people already know that this approach works, but maybe they haven't made the connection to abstract CS stuff.

Another strategy that can be used to build robustness is to build your workflow out of idempotent operations. That can be useful for situations where the workflow state is too large to back up. Instead, you just run the job from the top and it's a bunch of no-ops until you start making progress again.

At this point, I'm seriously considering what it would take to build a reasonable budget-AI box that's self-hosted. It wouldn't need to blow the doors off of Claude, just get me most of the way there. Maybe even build it out of used and/or last-gen GPUs and a beefy motherboard.

The "speed" loop reminds me a lot of RAD. In fact, AI might be _the_ thing that helps us deliver on RAD's promises from decades ago.

https://www.geeksforgeeks.org/software-engineering/software-...