CSS sourcemaps, being a basic assets in frontend tooling for many years, are still unsupported in Vite(https://github.com/vitejs/vite/issues/2830). Being an open issue for that long, while sourcemaps are supplied for free with tools like ESBuild & SCSS, are perhaps an indication of too much complexity in Vite? About build performance; ESBuild(and SWC as well) happily build large projects within reasonable time(<200ms). I doubt that skipping bundling all-together, by using ES-Modules during development, is worth the extra hassle in tooling. It made sense during the Webpack/Vuepack/Parcel 1 era, but not that much anymore since ESBuild happened. Spending some extra time in writing a custom buildscript (ESBuild + SCSS + simple async task manager + Chokidar + Tinylr or something similar) pays itself back really quick when a project gets larger.
HMR is nice, but the added complexity seems to make basic stuff like sourcemaps support difficult. Would be nice to have something that adds HMR with the flexibility of a custom build stack(esbuild + a better livereload)
To be fair, I put down the money knowing that I might lose it and not receive anything. I ordered mine at the start of 2019, I do not have my hopes up.
Edit: Their estimate for the new orders comes from the information from the CPU suppliers, which say the same thing. Every time they can get the CPUs, they ship another bunch of phones. See also: https://forums.puri.sm/t/estimate-your-librem-5-shipping/112....
Purism's shipping claims and estimates have been way way off even before there were any supply chain issues. At one point they even lied to be shipping devices, with pictures from the devices "in the wild", when it later turned out to be prototypes given to some employees.
Teams only show 4 streams at a time on Linux, the video/audio quality is mediocre and the video quality in the webclient is worse than the one using an Electron container, probably to force the app. Screensharing always tends to get stuck after a while, and they ignore any requests to start supporting Wayland, even while it takes minimal changes(update Electron).
Nowadays it's easy to setup your own conference server, and use webbased clients that don't require yet another Electron container. For instance, Galene(https://github.com/jech/galene) is an excellent resource-friendly SFU built on top of Pion(Golang).
In case anyone is looking for an alternative to hosted services like Zoom/Teams: https://github.com/garage44/pyrite is an open-source Vue frontend for The Galène videoconference server(Pion/Golang).
