AFAIK, Microsoft and/or Intel pushed to remove the usual sleep S3 state and use a less sleepy state to be able to access network and display notifications. As if it was a tablet or a Macbook.
This is (of course) badly done, and tested as well the rest of Windows, so it results in laptops waking up in bags, choking thermally, and not going back to sleep.
Just like the other replier, people who put words into others mouths are extremely annoying. And in both of your cases, come off as fanatical. I'd love to run Linux on a laptop (and have tried many times) but have actual work to get done.
> But this time the regulation was captured pre-emptively, to the point that following best scientific advice for your health is illegal is most of the developed world.
Please cite your sources then. And no the other article you linked is not proving your claim
Where does this article mention LED lights vs other types of artificial light-at-night?
What I could find regarding light color:
> However, most studies relied on satellite-images with a very low resolution (1 to 5 km, from the Defense Meteorological Program [DMSP]) and without information on color of light
> noted that data quality suffered from many limitations due to the types of satellite images used and the focus in the vast majority on visual light levels only rather than considering the circadian-relevant blue light component, among others. Future studies should consider improved satellite-based ALAN technologies with improved resolution and information on spectral bands and apply these technologies to a variety of cancer sites to yield better estimates for the potential risks between ALAN and cancer.
So nothing conclusive about LED being bad for your health (vs other types of light).
You're playing so defensive (for LEDs) wonder why - just to argue? If one uses the same logic - does anybody states that LED are GOOD for the health? What the lack of such statements means - they're bad, or have no effect?
At the end - is it your business at all if I want to use incandescent lights, or CFLs, because I find them more suitable for my personal needs in MY home?
No I just refute a claim on which the provided source does not prove or indicate in any way.
I'm not arguing LED to be better or worse, I'm just looking at a proof of some kind to what is argued.
But it seems like it's too much to ask? I should just accept whatever comments I read without any critical thinking?
It will get better, but the rate at which it does may not continue to be exponential. Past performance is not indicative of future results.
While the agents models seem to continue to improve, I think LLMs as a whole have started seeing less and less benefits from the current scaling approaches.
I get your points but I'm not sure I agree. Kubernetes is a different kind of difficulty but I don't think its so different from handling VM fleets.
You can have 220 vms instead and need to update all of them too.
They also are full of state and you will need some kind of automatic deployment (like ansible) to make it bearable, just like your k8s cluster.
If you don't configure the network egress firewall, they can also both pull whatever images/binaries from docker hub/internet.
> To get around this you end up having to cache images which means more infrastructure to maintain
If you're not doing this for your VMs packages and your code packages, you have the same problem anyway.
> When there's a CVE
If there is a CVE in your code, you have to build all you binaries anyway. If it's in the system packages, you have to update all your VMs. Arguably, updating a single container and making a rolling deployment is faster than updating x VMs. In my experience updating VMs was harder and more error prone than updating a service description to bump a container version (you don't just update a few packages, sometimes you need to go from Centos 5 to Centos 7/8 or something and it also takes weeks to test and validate).
I mostly agree with you, with the exception that VMs are fully isolated from one another (modulo sharing a hypervisor), which is both good and bad.
If your K8s cluster (or etcd) shits the bed, everything dies. The equivalent to that for VMs is the hypervisor dying, but IME it’s far more likely that K8s or etcd has an issue than a hypervisor. If nothing else, the latter as a general rule is much older, much more mature, and has had more time to work out bugs.
As to updating VMs, again IME, typically you’d generate machine images with something like Packer + Ansible, and then roll them out with some other automation. Once that infrastructure is built, it’s quite easy, but there are far more examples today of doing this with K8s, so it’s likely easier to do that if you’re just starting out.
> If your K8s cluster (or etcd) shits the bed, everything dies.
When etcd and/or kubelet shits the bed, it shouldn't do anything other than halt scheduling tasks. The actual runtime might vary between setups, but typically containerd is the one actually handling the individual pod processes.
Of course, you can also run Kubernetes pods in a VM if you want to, there have always been a few different options for this. I think right now the leading option is Kata Containers.
Does using Kata Containers improve isolation? Very likely: you have an entire guest kernel for each domain. Of course, the entire isolation domain is subject to hardware bugs, but I think people do generally regard hardware security boundaries somewhat higher than Linux kernel security boundaries.
But, does using Kata Containers improve reliability? I'd bet not, no. In theory it would help mitigate reliability issues caused by kernel bugs, but frankly that's a bit contrived as most of us never or extremely infrequently experience the type of bug that mitigates. In practice, what happens is that the point of failure switches from being a container runtime like containerd to a VMM like qemu or Firecracker.
> The equivalent to that for VMs is the hypervisor dying, but IME it’s far more likely that K8s or etcd has an issue than a hypervisor. If nothing else, the latter as a general rule is much older, much more mature, and has had more time to work out bugs.
The way I see it, mature code is less likely to have surprise showstopper bugs. However, if we're talking qemu + KVM, that's a code base that is also rather old, old enough that it comes from a very different time and place for security practices. I'm not saying qemu is bad, obviously it isn't, but I do believe that many working in high-assurance environments have decided that qemu's age and attack surface is large enough to have become a liability, hence why Firecracker and Cloud Hypervisor exist.
I think the main advantage of a VMM remains the isolation of having an entire separate guest kernel. Though, you don't need an entire Linux VM with complete PC emulation to get that; micro VMs with minimal PC emulation (mostly paravirtualization) will suffice, or possibly even something entirely different, like the way gVisor is a VMM but the "guest kernel" is entirely userland and entirely memory safe.
I think his point is that instead of hundreds of containers, you can just have a small handful of massive servers and let the multitasking OS deal with it
The subject is productivity. Time to merge is as useful metric as Lines of Code to determine productivity.
I can merge 100s of changes but if they are low quality or incur bugs, then it's not really more productive.
this guy has elsewhere in this thread cited "a16z revenue benchmarks" as evidence of productivity. you know, the sector most famous for setting more money on fire faster than anyone in living memory.
I want to do the opposite: Give curly braces to all the indentation based languages. Explicit is better than implicit, auto format is better than guessing why some block of code was executed outside my if statement.
Yes, because (1) they spent that money badly as can be seen from the non-Google revenue numbers of Mozilla and Firefox's market share and (2) people are comparing practices of a company that gets $500M for free and a practices of a company that is essentially bootstrapped, which makes no sense.
Of course it's probably not the same user base. But the point imo is that users did use it and get value out of it, even if die hard users cried hard their browser was invaded and that Mozilla lost the plot.
We even have commenters here saying Pocket lost Firefox some market share (without any evidence or argument in favor, so a gut feeling too), but nobody to say that maybe the feature was used by some? And maybe that was a pull for Firefox vs Chrome. (I'm not saying it was, I'm just saying we don't know)
If they support it and have an incentive to listen to their customers and not shareholders, gladly. We can't keep using those logic of being afraid to invest then be mad when companies find someone who will.
reply