I was just saying this to my colleagues after seeing these. Decades of political sabotage has done significant damage to our transition to renewables. I'm hopeful (perhaps a bit too wishful) that we'll see more of a push for renewables in the coming election cycles, but I'm staying realistic as the last 20 years of climate debate has been frankly shameful. At least rooftop solar is so ubiquitous.

I'm hopeful that the advent of the Teals might generate some momentum here. I believe there are some very large wind farms in progress across NSW too, which is good news. Home solar / battery installations also seem to be on the rise in low density areas (I don't have hard data to back that up though).

I'd also love to see solar panels on top of every Bunnings, Westfield, and other warehouses/complexes, as well as above every outdoor carpark, which would have the added bonus of preventing hand roasting in summer.

I've found this book to be a good way to learn a new language, because it forces you to do a bit of reading about various language features and patterns to create equivalent implementations. For languages that lack some of the features in Java, it can be tricky to learn how to apply similar patterns, but that's half the fun (for me).

In that case the maintainer needs to have some self-restraint and accept that they don't owe them anything. If somebody depends on the maintainer's package for a critical component then they should consider paying them and possibly drawing up an explicit contract. That's what we did at my work for a critical open source component, where we paid the maintainer to add several features we needed.

It's commendable that your organization did this.

But...

> the maintainer needs to have some self-restraint and accept that they don't owe them anything.

Assumes (especially in cases where "maintainer == original author" psychological capabilities that simply might not exist in the maintainer.

I don't know of a good way to deal with this, other than to be kind and try to notice potential signs of impeding burn-out before an implosion.

After 10 years on zsh I finally switched 6 months ago and I haven't looked back. If I need POSIX, I'll just run scripts with the right shebang or pipe it to sh.

I think it just depends on the person or the type of project. If I'm learning something or building a hobby project, I'll usually just use an autocomplete agent and leave Claude Code at work. On the other hand, if I want to build something that I actually need, I may lean on AI assistants more because I'm more interested in the end product. There are certain tasks as well that I just don't need to do by hand, like typing an existing SQL schema into an ORM's DSL.

I've made the complete switch recently (been using Linux on and off for years, including WSL as well) after my pleasant experience with the Steam Deck and it's been fantastic, but not without issues. A recurring issue over the years of trying Linux has been WiFi drivers; I really can't afford to have WiFi not work as I can't run an Ethernet cable to my computer room. I get that Linux heavily relies on volunteer work, but a broken WiFi driver due to an update is a big roadblock.

Beside that though, I'm happy to have left Windows behind completely.

You often need to verify it though. I've been using Perplexity due to the way it sources the results and presents the sources it generated the answer from, which means that I often still have to make the jump out to the web.

Do you think you'll explore some of the same problem spaces as Rust? Lifetimes and async are both big pain points of Rust for me, so it'd be interesting to see a fresh approach to these problems.

I couldn't see how long-running memory is handled, is it handled similar to Rust?

I'm going to try and avoid lifetimes entirely. They're great in Rust! But I'm going to a higher level spot.

I'm totally unsure about async.

Right now there's no heap memory at all. I'll get there :) Sorta similar to Rust/Swift/Hylo... we'll see!

So if you don't have a garbage collector, and you don't have manual memory management, and you don't have lifetimes... What do you have?

The plan is something like mutable value semantics and linear types. I'm figuring it out :)

It may have been more useful to link to the blog post [0] which gives more of an introduction than the front page at this point.

[0] https://rue-lang.dev/blog/hello-world/

I posted that, and also https://steveklabnik.com/writing/thirteen-years-of-rust-and-...

Just to link them all together. This is the one that the algorithm picked up :)

What are they exploiting? Are they violating the terms of the license? The point of OSS is that there aren't arbitrary restrictions to its use; you can do what you like with it and the open source maintainer has absolutely zero obligations to continue supporting the software, or implement any of your requests.