![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
Sure, I mean I want them to focus their energy on it.
There are a lot of anti-features (studies, pocket, telemetry, “sponsored suggestions”, etc…) that are justified in “we have to make money somehow” but then they spend it on this stuff.
Sure, I mean I want them to focus their energy on it.
There are a lot of anti-features (studies, pocket, telemetry, “sponsored suggestions”, etc…) that are justified in “we have to make money somehow” but then they spend it on this stuff.
maybe its just me, but as useful and nice to know as this is, I really want Mozilla to focus their efforts on making a good browser, not to spend money doing everything but that.
There are a lot of anti-features (studies, pocket, telemetry, “sponsored suggestions”, etc…) that are justified in “we have to make money somehow” but then they spend it on this stuff.
[edited for clarity]
thats awesome!
isn’t working =(
its difficult because different users have different usage patterns.
for example, two users who never post and are never online at the same time really take no resources from each other. they are effectively “one” user.
one user who posts 10gb of content a day, and is constantly posting would be equivalent to hundreds of “normal” users.
It’s very possible they weren’t unused.
Docker builds their images out of layers, and all the layers are used during runtime!:
https://sweetcode.io/understanding-docker-image-layers/
The idea is that you can essentially change PARTS of an image, without rebuilding it entirely, which saves space and bandwidth.