This linker noticeably improves rust development happiness on an exploratory, chunky repo of mine that is trying to be a big ole web monolith (uses SeaORM and axum/tokio). You don't want to know the size of my `target` directory, but incremental builds are snappier!

I need to play around with mold:

  15:55 $ du -Hs --si target/
   11G    target/

just in case I confused: i'm not sure mold helps with the size of that directory :D. I was commenting on how big my rust repo is really, just saying that mold seems to help big builds like mine

Looks slick for how quickly it was built. I was surprised by the download size and RAM footprint, but... if it was easy to do cross-platform, I'm thinking this is still ahead of electron on footprint? Or at least competitive. Interesting!

A lot of the ram usage is actually coming from the wgpu backend. You can use ICED_BACKEND=tiny-skia to try software rendering and the footprint should be a lot smaller.

The footprint should be very consistent throughout the lifecycle of the app. Message history is pretty small and we only keep opened buffers in memory. Everything else is flushed to disk.

Now compared to Electron, there is no comparison for speed and responsiveness

same. Back in ~2009 I had the pleasure/horror of debugging/fixing "TCL drivers" for a piece of Java software that aimed to integrate with various pieces of hardware. I'll never risk putting anyone else through a similar torture if I can help it. ...then again I've left a trail of Ruby/Rails behind me that might get the same job done :)

Also we slowly lose upper atmosphere to the solar winds, when the magnetic fields fail to deflect it enough.

It's getting pretty old now (maybe renewables have progressed) but Union of Concerned Scientists made a solid attempt: https://www.ucsusa.org/resources/cleaner-cars-cradle-grave

> Already deployed apps will keep running, but customers cannot update or manage apps.

Pretty sure some of their cron/scheduling stuff is affected too :-\

For their next trick apps will hit their "pseudo random 24 hour forced restart" and not restart. I'm hoping they remember to turn that off.

Yes - our scheduled jobs aren't running - no doubt if it can't deploy new apps it also can't start dynos to run scheduled jobs.

My team is building something cool for running scheduled job. Let me know if you are interested

Takes me back to my BF1942 days, careening around maps in planes and tanks. I was dirt poor. I usually had to get a ride to the video rental store to rent console games. I'm thankful to have kept busy thanks to these groups. It kepted me interested in computers and exposed (a little) to software dev. ...and awesome music! Man, the music...

Here here. I backed Onivim hoping it was going to shine a light in the darkness, and it seemed promising, but ultimately was abandoned? I think, unsure.

Looks like zellij follows the same behavior as screen, if I'm testing right. I also prefer screen/zellij's choice here.

I remember reading about PropelAuth somewhere and thinking that Rust might slow down development -- something I wanted to be proven wrong about since I've been learning rust off and on, and like some things about it. It seems it's ending up up a mixed bag, and the negatives in the bag are still light enough that you're carrying it forward. Thank you for this blog post!