> It feels really wasteful to burn CPU and spin up fans every time I save a file. I find it hard to justify using 30+ GB of memory to run an LSP and compiler.
Have you tried using RustRover. I've never seen it go above 2-3GiB of RAM, but I don't write the most complex of software in Rust.
> I hate how crates.io requires a GitHub account to publish anything.
You don't need Github account to publish iirc, you need it to authorize to crates.io. You can use any Git host, but your account is tied to GitHub.
On the contrary, OSS is precisely where this kind of spying on your users is least useful, since there's already a culture of them telling you, sometimes with code, what they need.
If that's the issue, that's a problem. They are telling you X. People, if they tell you, don't give their honest feedback. Or they might be a loud minority.
If you ask people what coffee they want, they will all tell you low-sugar, very bitter black coffee. Then you see what they buy, and they keep buying sugary and creamy coffee that contains almost no caffeine.
Telemetry isn't spying. At least when done properly. How do you figure out rare OOM crashes without some telemetry data? What if the reporter doesn't know how to figure out their OS and installed software that's required for debugging?
I'm NOT saying telemetry should capture everything and sell that data to info brokers. I'm saying, done properly it give you valuable feedback. And you should be transparent about it.
> Telemetry isn't spying. At least when done properly. How do you figure out rare OOM crashes without some telemetry data? What if the reporter doesn't know how to figure out their OS and installed software that's required for debugging?
Recording information about someone's computer and then sending it to the developer without their knowledge or consent is spying. If you want to include a feature in the software to report a bug or collect crash info or whatever that tells the user what it's going to send and gets their affirmative consent, then yeah that's totally fine and not spying, but that's not what we appear to be talking about here. To use your analogy,
> If you ask people what coffee they want, they will all tell you low-sugar, very bitter black coffee. Then you see what they buy, and they keep buying sugary and creamy coffee that contains almost no caffeine.
That might be true, but it doesn't justify sticking a camera in their pantry to find out.
> Aircraft typically carry hundreds of people and can crash to the ground.
Cars are more numerous and could spontaneously either plow into pedestrians, or rear-end someone, causing chain damage and, quite often, a spillage of toxic chemicals (e.g., a cistern carrying acid/fuel/pesticide).
Plus, you have a problem of hostile actors having easier access to cars compared to planes.
That's the thing with evaporation: you don't want your water to leave stuff behind after it evaporates because that will foul your equipment and cause lower efficiency.
You could in principle design systems with enough fouling mitigations that you'd be fine, but its likely that the cost of those mitigations is roughly the same as just purifying the water up-front.
Short answer: several operators already do. The barrier isn’t technical, it’s proximity to a municipal wastewater source and willingness to invest in on-site treatment (pre-filtration, ultrafiltration, partial RO, ongoing biocide dosing). Recycled water typically costs 30-50% less than potable once the treatment infrastructure is in place.
It's interesting to note the discrepancy between replies to this blog here and, say, lobste.rs (which is neutral to it).
Here it's very concerned about complexity, while on lobsters it's mostly about needing this feature - yesterday.
reply