The concern for code duplication is valid, but as the article mentioned it is also a while off until the Nova project is mainlined. I honestly never thought of how the work to bring in Rust to mainline may in effect lead to a more complete deprecation of older hardware as we start to change API’s older/unmaintained components aren’t updated. On the flip side, trimming out older stuff might save maintainer work going forward.

Rust’s cargo is great, I’d say it would be best to make the switch sooner rather than later once your code base is established. The build system and tooling alone is a great reason to switch

Honestly executives and board members who receive performance bonuses and golden parachutes should carry extra liability, such that these perks can be denied or even clawed back (and used to help the damages) when their decisions have these sort of outcomes. Nothing wrong with making more when things go well, but if you’re going to take a larger piece of the pie, then you need to be prepared to take a smaller piece when things go wrong (aka, cut executive pay before layoffs, etc.).

But you spotted it

🥺

I never received this survey and I fly Southwest specifically because I found their boarding process to be less of a hassle (for a single traveler who doesn’t care where they sit). The only way I could see this being beneficial is if they board people in order of assigned seat in such a way as to optimize time to seat, not the BS boarding that other airlines do to try and maximize price of fair, otherwise they will have lost the whole reason I like(d) to fly them… Their simplier, no bs, boarding process.

P.S. I really don’t get people liking to pidgen hole themselves to a specific spot for any of these things, just makes it easier to inflate the prices later