Speaking only for myself, this sort of behavior is a great way to break the Trust Thermocline [1]. The point where I am so frustrated, so fed up, so expectant that said company will abuse me again, that I refuse to do business with them at all, under any circumstances, no matter if it is inconvenient to avoid them or not. 1. x.com/garius/status/1588115310124539904

This post does seem to be summarizable as: "we should maybe start looking at the fact that these drivers crash (and recover) pretty frequently". Which is, like, a kind of low bar. :) It's interesting seeing how open-source faces the hurdles of change. X vs Wayland, OSS/ALSA/PulseAudio/PipeWire come to mind as examples, or systemd in a variety of SysV-ish shell scripts. Being willing to do the rewrite, to change the stack for good technical cause has been an interesting fulcrum, is a much harder to find similar purchase for when you're also supporting so much legacy. The task of making organizations care about the software is hard. Orgs everywhere are so driven by "shiny new things," new markets, new features. How & where we find the caring, the will to go improve things because they're in a bad way is a stunningly hard case to make apparent, to get folks onboard with. It feels like it doesn't affect the bottom line. Or put another way... company's dont really know how close they are to the Thermocline of Trust[1][2], don't recognize when instability & chaos & inconsistency overtake the organization or product. [1] twitter.com/garius/status/1588115310124… [2] every.to/p/breaching-the-trust-thermocl…...

The most spectacular one I've seen in recent years was the Freenode takeover and subsequent implosion. But Reddit, like Freenode and Twitter before it, seems headed for the trust thermocline: twitter.com/garius/status/1588115310124…

The trouble with the learning-by-crashing strategy is that it worked great for rockets, OK for self-driving cars on closed tracks, and terribly for Twitter because Twitter has people "aboard". Every time he tweaks the rules and "crashes" twitter, a bunch of people leave, build a new network elsewhere, and never come back. Or are permanently banned and can't appeal through the back channel like pg. (edit: the @garius "trust thermocline" concept is a good elaboration twitter.com/garius/status/1588115310124… )

It's a shame, too, because I'm a professional React dev, and I was really excited to try this! But there's some sort of thermocline-of-trust issue with a self-identified manufacturer of software engineering tools can't correctly detect or name my OS, nor presumably understand why this makes me wary of trusting my development loads to a tool that is packaged in this way. twitter.com/garius/status/1588115310124… Suggestion to Wix: Go take a look at how another closed-source app with excellent cross-platform support is packaged -- say, reaper.fm. This website lets me pick from several different flavours of Linux in an unobtrustive, practical way. (I mention 'practical' because I know that the idea of supporting more than one flavour of an OS is seen by newcomers as 'impractical', but that's just how we do business in Linuxville, and since we've been doing it for a while, we've got lots of examples of doing it successfully, practically, and sustainably. Welcome! Sorry about the mess!) Instead of assuming everyone is on .deb, here are some alternatives: - Flatpak (most preferred) - AppImage - Docker image - Snap (least perferred) Once it's possible for anyone to use the Flatpak, say, it makes sense to begin producing artifacts for common platforms like .deb for ubuntu x64 etc. Put your CI/CD on it. But don't start there. Start with flatpak. Start with appImage. Start, if you must, with a docker image and `localhost:3000`. But whatever you do, don't equate linux with Ubuntu or even Debian, it makes everyone feel weird