I suppose that instead of destroying them, they’d need to be sold in a second hand clothes store or to be refurbished, and not just dumped into Africa or China… right?
Isn’t that, like, better than just destroying them tho? I get it this is a pretty mild and inconsequantial reform in the grand scheme of things but it feels like you’re just being contrarian for the sake of it.
Oh my god dude you sound so pathetic right now. If you actually do hold radical left beliefs of any kind and it’s not just a cute online label for you (really doubt that but I’ll give you the benefit of a doubt) go outside, touch some fucking grass, and organize IRL, or at least talk to people IRL about it. We’ve all heard your bullshit “anti tankie” tirades from people like you a thousand times over, you’re not changing any minds and are not impressing anybody with your arguments, I can absolutely guarantee you that.
I haven’t done this in years but I’ve always found open source solutions to this to be quite clunky and usually barely worked. What always just worked fine for me was Teamviewer. Yeah it’s proprietary and has crappy licensing but it’s mostly a smooth ride.
Do try the open source options first tho, it’s quite possible they got way better in the last few years since I’ve done this.
It’s not THAT complicated but I wouldn’t call it dead simple. When you understand how git works internally yeah it’s pretty simple but people usually start with the idea that it’s a tool to put your code on a server to synchronize with other people and only later learn that you have both a local and a remote (or multiple remote) tree and how the tree really works.
The researchers estimate that if the system is scaled up to the size of a small suitcase, it could produce about 4 to 6 liters of drinking water per hour and last several years before requiring replacement parts. At this scale and performance, the system could produce drinking water at a rate and price that is cheaper than tap water.
Sounds too good to be true tbh but I’d very much like to be wrong.
Eh, that’s unfortunate. Yeah the whole ecosystem is still a bit wonky, probably more wonky than most popular languages but tbh I rarely used a stack that just worked out of the box, it almost always took some dicking around, I’d rather do the dicking around with a language that doesn’t always seem to work against me.
because no compiler can check to see if you thought of everything.
We can try to get closer to that with better language design. You’ll never get there but I think there are obvious benefits as to why you’d want to do that.
I write way less bugs in Rust than I have in Java or C++, and that’s mostly thanks to the language design.
I’m just tired of people entirely dismissing languages like C because they don’t have these features. Especially when the operating systems their code runs on and their languages may even be implemented in C!
Because that code has been review and re-reviewed and patched by experts in the field for years. You’re not gonna write a backend for an app with short deadlines in C because that would be absolutely fucking insane.
How long ago was this? I think the ecosystem got waaay better in the last 1-2 years. 3-4 years ago it was rough but shit still worked with a bit of trouble.