Correct. It is extremely false. And it's an extremely well documented event, as well.

> Then you beg the question with a bit of a straw man fallacy thrown in.

I expressed my opinion. I did not misrepresent that person's argument (i didn't represent it at all). As for begging the question, well, I'm not sure what you're referring to, unless you mean the intensely cut and dry sequence of historical events? In which case... well, they're so unaligned with reality that it's comical.

> Sony heard about Nintendo partnering up with Philips for the SNES CD expansion, so Sony made their own console

This is completely inaccurate in every way possible. You even have the order of events backwards (Nintendo and Sony partnered first). There is in no way in which even the most charitable interpretation of this statement could bear out. Just about the only correct part is that you have some (but not all!) of the relevant parties involved.

If you're wrong about such a well documented, cut and dry matter of historical record, then what else are you wrong about? :)

i said modern containers. and you do have a FUNDAMENTAL MISUNDERSTANDING. you are repeating falsehoods throughout this entire thread.

> That will not happen for common docker use

again you are asserting a "common" use of software, when the people youre replying to are clearly using it for development

> where you don't control the apps and base OS completely

stopping saying "you" to me. id tell you to speak for yourself but you seem incapable of doing that

> And for all these "let's have just a big static binary and put it into a container" containers, that don't really have/or need a real full OS userspace under them, there's barely any difference deployment wise from just running them without docker.

ironically enough it does have differences, glaring big differences. like ironically the deployment differences are about the only reason to use docker in this situation

another stark example of you popping off with incorrect assertions. and yes there are reasons not to do use docker for this as well but it depends on multiple factors

> In fact docker is just a very complicated additional duplicated layer in this case for what systemd does, that most people already have on their OS. So that's another RAM waste and additional overhead from what is now reduced to a service manager in this use case scenario.

there are so many misconceptions in there asserted as if theyre the entire truth. yes people can use docker containers poorly but its not everyone.

> The moment you start pulling random dockerfiles from random sources, you'll be wasting colossal amounts of resources compared to just installing packages on your host OS, to share maximum amount of resources.

its a good thing that I'm not doing that! ive already stated that im using them to build software, not just "pulling random dockerfiles from random sources"

you are digging your heels in and you are now trying to assert a set of conditions and situation in which youre correct, even though youre dead wrong for the use cases that the people youre replying to are describing

you have repeated falsehoods as fact repeatedly and seem unable to adjust to people telling you "im not doing that thing youre complaining about"

frankly, i think youre out of your depth on this subject and youre trying to do anything you can justify your original claim that 1GiB is enough, or whatever

TLDR

feel free to have the last word, im sure youll have lots of them. maybe youll get lucky and a few will be correct. im exiting this conversation

you dont get to define "where it matters" for a hobbyist

> which is where you are installing random third-party apps/containers that you want to run on your SBC locally

this is such a consoomer take. for those of us who actually build software, we have actual valid reasons for using it during development

> they're completely different architectures, so I can't avoid the differences anyway

ironically this is a side benefit modern containers are useful

i think you have a fundamental misunderstanding of how containers work and why theyre useful for software development. based on your other posts in this thread only makes me more sure of that. im not saying containers/etc are a perfect solution or always the right solution, but your misconceptions are separate from that

On your computer reading this, you're probably not moving the screen. That is time that the GPU can sleep. That is a lot of power saved, regardless of display.

So yes, "generating all this light" takes up a lot of power. But just because it does, doesn't mean that overall battery life wouldn't be benefited from improvements elsewhere.

And in fact, the average backlight is about 5w, maybe 10w. The average laptop GPU when idle and awake, consumes about 5w as well. If you can get that idle GPU consumption down substantially, that's a potential 20% (or more!) improvement in battery life.

ironically, in high end hotels, there's often a lot less cctv. not none. just less. rich people enjoy privacy

And yet, it’s the fundamental technology enabling always on phone and smartwatch displays

The intent of this is to reduce the time that the CPU, GPU, and display controller is in an active state (as well as small reductions in power of components in between those stages).

The assumption is that the window should be the size of the content of the document inside.

It turns out that this approach works well for many applications, especially what the mac was designed for in the 80s and 90s. And it's horrid for modern "pro" applications.

As a semi professional eagle enjoyer, if the day before was trash day, then she might have been telling the truth. I’m not joking, they have bald eagle proofed dumpsters in Alaska.

They’re basically smart seagulls with talons.

Or they believe that it has serious issues in a consumer SKU or consumer application.

well that makes perfect sense, if its a consumer or prosumer grade raid controller, to be honest.

It depends on the hospital and it might also be regional.

At the hospital I go to in California, green is for surgery and everyone else seems to be in a free for all. I know they reserve dark red for visiting specialists, but the doctors and nurses both wear whatever they want.

They explicitly do, even among their own customers and plans. If you Google the carrier name plus QCI, you’ll find tables where people have documented, which plans are in which priority group

Extremely sure. There are both numerous private, academic, and governmental agencies that are constantly searching for both collision paths, and collision debris.

The debris cloud alone would generate an extremely visible signature.

> Would it be always observed and caught outside of SpaceX?

Yes.

In a refresh or two when they up it to the next a-series pro chip and 12GB ram, it’s going to be an unambiguous deal.

I don't. This snark really lets you downplay them and willingly ignore people who are concerned about a real problem. And then you'll act surprised when they get traction and you've been laughing the whole time.

I think there is a solution, and it's to prevent companies from offering social features to children. Full stop. No age verification, just make it a "ban on sight" thing.

Frankly, this is false. There's a lot of well intentioned people writing these laws and pushing for them.

> Obviously, it's a technocratic trojan horse for increasing surveillance capabilities on digital systems.

However, it is also this.

And that's not a tradeoff I think we should make as a society.

i also dont know whats going on, although it is a obscure drama from a relatively small community

i think maybe that is this disconnect. that relatively small community is extremely important to you but many other people here lack similar footing. i dont think the hostility is warranted but i can feel myself furrowing my brow and asking out loud what is happening when i read some of the posts from bluesky users in this thread

i guess i am glad i never got big into twitter or bluesky or the attention economy