We're still a long ways off from BEV "Just Working™" across the nation. The electric grid and road infrastructure needs a lot of work done to accommodate complete BEV adoption from supportability, policy changes, public transit conversions, road redesigns, etc.

Had we gone with an EREV transition bridging gasoline ICE and BEV, we could have given ourselves a lot more time to appropriately plan and implement the necessary infrastructure and incentives across the nation to enable folks to adopt these greener technologies.

Looking at things from the US perspective, had manufacturers dug in to EREV models from the start, we'd be much further along in the transition to net-zero. Alternative fuels could have been employed by now at a wider scale without placing increased stress on the grid to handle the load.

With advancements in hydrogen engines, Chevy could have propelled efficiency in later generations by trading a gas powered engine for a hydrogen one. Pair an H-engine with a solid state battery when they're viable and we would have an amazing vehicle that doesn't also weigh a ridiculous amount.

The use of an ICE as a generator and having the vehicle be all-electric was groundbreaking. The second generation had noticeable improvements to its capabilities. I know a few people that have/had one and they swear by the car. It really could have been the future of American car manufacturing.

Wordle too, it pulled a good-luck-have-fun combo today. There are three character patterns I absolutely *adore* (mega /s here), and today was one of them. 😒

Suffice it to say my streaks in both games ended today...

I've read a bunch of varying opinions on the matter, and I don't know if it'd be better to use the same model without reasoning for the delegated tasks or use the other tiers like Sonnet and Haiku for execution. Even mixing model providers, though I'm thinking of sticking with Anthropic for this...

I have a project planned for this holiday break purely to play around with LLMs and software development. I've been trying to figure out the best way to take advantage of them from an interaction/delegation standpoint. e.g. using Opus w/reasoning to plan things then execute on it with Sonnet.

For fun I posed the question to an #LLM (@anthropic.com's #Claude #Opus 4.5 model in this instance) and was given a response that I was expecting but not fully sure of. #Rust devs, do you agree or disagree with its analysis?

gist.github.com/omenos/cadd1...

Would doing this actually provide increased safety? Is it generally a reasonable strategy? For example, providing an OpenSSL API/ABI compatible version of libssl and libcrypto.

Convert underlying components to memory-safe languages and provide them without needing to upend entire platforms.

👍/👎?

In today's software ecosystem which is deeply rooted in C, would it make any sense to effectively create "C" libraries in Rust? I'm thinking about this from the perspective of multi-language binding interop, and enabling existing non-Rust projects to acquire more safety with drop in replacements.

If anyone wants to join in, there's still time to donate to the project!

It's nearly crowdfunded 1 MILLION dollars, it's would be insane to see it actually cross that line!

Every backing extends the fundraising time by another 10 minutes, and it is well into overtime!

#NailHouse #RocketJump

ed discourse.txt

a
if you are not using vim, why?
it is the gold standard of editors.
.
1s/vim/ed/
2c
it should be all one needs in life.
does this not seem simpler to use?
.
w

Apologies in advance if I missed a callout to it or if I haven't gotten to the section where it happens 😅

I first heard about it on the Cup o' Go podcast and have been using them since to help better understand the practical changes in a release.

cupogo.dev

Listening to this now, but thought I'd throw this out there before I forget:

@antonz.org's fantastic blog includes an interactive exploration of each Go release. Some less-developer-impacting minutiae is skipped, but it focuses on the meat and potatoes of the feature release!

antonz.org/go-1-25/

It'll be a great discussion regardless, I'm very much looking forward to it!