I feel like that’s a lot of assumptions based on OP’s brief, but I don’t disagree with anything you said.

If this causes networking issues, your setup is already too complicated to manage through a flat set of docker containers. That’s not a bad thing, this just isn’t the horse for that course so to speak.

If you’re very concerned just have your prod environment and kick up test services in docker containers and test your tweaks and changes there.

Doing this ad-hoc will be easier and more practical than trying to maintain two full environments like you’re a series B startup finding it’s feet!

Describing the outcomes in terms of functions over shell states, as you have, is the quickest and most transparent way of demonstrating that they aren’t the same.

The article was a fun “scenic route” to the same conclusion, though.

Oh so you’re saying the companies are not altruistic? I’d agree. I thought you were saying that the people making the FOSS were not being altruistic.

How does a corporation using it obstruct independent developers from using it under the same license? I don’t see a compelling case for them being mutually exclusive

And they are mutually exclusive, in your eyes?

Is giving away your software in a way that doesn’t use a copyleft license, not altruistic? Seems like a pretty narrow definition.

Yes but those are inferior because they aren’t in a rage-baiting meme format

Please write the “C considered harmful blog post”. I just want to see everyone’s faces. Pleeeeeease.

This was peak peakness. The rest of history is a footnote.

Tmspk egssts tuh

Which mail provider are you using?

The lack of ABI stability in Rust means they don’t have to commit to language changes that may prove to be unpopular or poorly designed later.

Swift went through the same growing pains and, IMO, has suffered for it a bit with even quite basic code often needing lots of availability checks. This may seem counter intuitive but Swift is in the unique(-ish) position of having to serve both a huge corporation demanding significant evolution on a regular basis and a cross platform community that don’t want to write an encyclopedia every time a major version of the language is rolled out.

Rust doesn’t have this issue and I think it’s right for them to allow themselves the freedom to correct language design errors until it gains more traction as a systems language - and it’s quite exciting that we’re seeing that traction happen now in realtime!

Swift is a pretty fully fledged systems language at this point … however, it’s far from tried and tested for use cases like this and cross platform support is still garbage, so still a pretty questionable choice.

Reddit, when the walls fell

I can only speak from personal experience but for me they jacked up the price significantly after year one and then sent my domain straight to auction after I decided not to pay. I respect that there are reseller-focused providers out there but they aren’t for me.

On the other hand, I’ve had nothing but quality service from namecheap for the best part of a decade.

Namecheap. Avoid Dynadot.

I’m using memos in a docker container.

I like it because it has few features but they all work well. It’s great for taking quick notes or writing whole journal entries.

1. Try increasing hotend temp for first few layers and hotbed temp throughout
2. Try moving z closer for first layer
3. Repeat both of above in small increments

FWIW, those PEI sheets usually need higher bed temp than the regular sheets