It seems like since my generation had "If you put something on the Internet it'll be there forever" drilled into us as kids, many of us feel entitled to "the internet" preserving our data for us. Most people don't realize how much labor and resource usage goes into preserving data forever.
ScreaminOctopus
Idk about Amsterdam, but in a lot of places half of a comparable rent might be his whole mortgage, depending on how long he's owned the property.
What's your setup for self hosting? Do you use a vps or host on your own network?
I feel like I did at one point, but I should probably try again
Yeah I'm not super surprised... It used to work well when I bought it back in '17 but it's become worse and worse with updates.
I'm not a home theater power user, but this is good info to make sure my setup is future proof for when I finally get a new TV. All these different standards get really confusing.
How dies it perform in bright sunlight? One of the nice things about the pebble was the epper display that was always visible
There are tons of other brands and the co2 tanks are standardized, I have a Phillips
One specific example I encountered was ndarray. I couldn't figure out how to make a function take an array and an arrayslice without rewriting the function for both types. This could be because I'm novice with the language, but it didn't seem obvious. I ended up giving up after trying to dig through the docs for a few hours and went back to C++.
Maybe for your use cases that's OK, but there are many situations where the size and ease of upgrading provided by shared libraries is worthwhile. For example it would suck to need to push a 40+ GB binary to a fleet of systems with a poor or unreliable internet connection. You could try to mitigate this sort of thing by splitting the application up into microservices, but that adds complexity, and isn't always a viable tradeoff if maximizing compute efficiency is also a concern.
In my understanding, you can't interface with the C abi without using an unsafe block.
Blanket removing Section 230 does literally the opposite. Without it platforms are only liable for user generated content if they moderate it. before if a platform moderated content published by users, it would be considered a content publisher, like a newspaper or magazine, and would be liable for user generated content. If they didn't moderate they would be considered a content distributor, like a bookstore, which isn't liable for the content of the material they distribute. So repealing it means any website with user generated content would effectively be required to operate like 4chan or Usenet.