indolering

They could at least use Flatpak and containers instead of choosing a given distro or package manager.

They 100% make excuses for the guy and buy his bullshit. Nothing screams cognitive dissonance like believing that Elon had no idea that his Nazi salute would look like a Nazi salute!

Why is the launcher not at least public source? GOG's value add is the service it provides, not the specialness of its launcher.

Hopefully they will pursue a container/Flatpak native system but probably not!

This is exactly what TSMC does and they have taken money customers placed in escrow. NVIDIA's investment in Intel is a hedge against TSMC. The hyper-scalers are free to invest in a second source if they want.

I do wish Intel an Samsung would cooperate on open source EDA (etc) software to make switching to other fabs less risky and capital intensive.

Yeah, routing is still a major PITA.

It's just that almost anything is better than wifi in concrete/stone houses. I can see point-to-point outside with an unobstructed view being reliable enough. But point-to-point through 3ft of concrete is [HN is a neglected Xennial hobby and doesn't support emojis]!

Certainly worth reconsidering wired when that P2P hardware goes EOL.

Bacteria are larger than viruses, so yes.

Citation? Microban et al are marketing bunk.

I really like that project! Why don't y'all hand it over to someone willing to do maintenance or at least archive it?

It looks like it was done to not delay the 4.0 release. Since they follow semvar, that means it won't get the axe until 5.0 [1]. Pretty wild considering that 3.0 was released 10 years ago.

But maybe they will scope this one better: they were talking about getting 4.0 released in 2020 back in 2019!

[1]: https://github.com/jquery/jquery/pull/5077 [2]: https://github.com/jquery/jquery/issues/4299

I love that they support ES6 modules, Trusted Types, and CSP! The clearing out of old APIs that have platform replacements is nice to see too!

It's hard to rule out intentional side channels without access to source.

CHERI is undeniably on the rise. Adapting existing code generally only requires rewriting less than 1% of the codebase. It offers speedups for existing as well as new languages (designed with the hardware in mind). I expect to see it everywhere in about a decade.

Spinlaunch is also promising drastically reduced cost per launch. The payload size for their first launcher is pretty small and they appear to be struggling to get the kinetic launcher online.

Please elaborate!

The healthcare industry is basically locked into 365 due to a lack of alternatives supporting HIPAA.

Google Workplace theoretically can be configured, but it doesn't cover basic stuff like information in contacts. So if ANYONE in your organization (like an outreach coordinator) adds a patient and puts notes into the contact field, it's a HIPAA violation. There is no way to effectively police that.

I wish the regulations were written such that messaging apps, office suites, etc over a certain percentage of revenue had to qualify for HIPAA by default. It's absurd how many small shops just do everything in over WhatsApp/iMessage/Gmail/iCould, etc.

Yes, it's technically possible. But what you are suggesting is basically a dynamic filter. The problem is that codes are designed for end delivery and have very specific practical constraints.

For example, we could GREATLY improve compression ratios if we could reference key frames anywhere in the file. But devices only have so much memory bandwidth and users need to be able to seek while streaming on a 4g connection on a commuter train. I would really like to see memes make use of SVG filters and the like, but basically everyone flattens them into a bitmap and does OCR to extract metadata.

It's also really depressing how little effort is put into encoding, even by the hyper-scalers. Resolution (SD, HD, 4k and 8k) is basically the ONLY knob used for bitrate and quality management. I would much prefer to have 10 bit color over an 8K stream yet every talking head documentary with colored gradient backgrounds has banding.

Finally, there is the horror that are decoders. There a reference files that use formal verification to excise every part of a codec's spec. But Hollywood studios have dedicated movie theaters with all of the major projectors and they pay people to prescreen movies just to try and catch encoding/decoding glitches. And even that fails sometimes.

So sure, anything is possible. Flash was very popular in the 56k days because it rendered everything on the end device. But that entails other tradeoffs like inconsistent rendering and variable performance requirements. Codecs today do something very similar: describe bitmap data using increasingly sophisticated mathematical representations. But they are more consistent and simplify the entire stack by (for example) eliminating a VM. Just run PDF torture tests through your printer if you want an idea of how little end devices care about rendering intent.

They were going to shut it down due to upstream Fedora considering ending 32-bit support. Sticking to upstream wouldn't have helped you avoid that issue.

It would be helpful in automating the busy work of many verification aware programming languages. At least the Dafny authors are excited about it.

While I'm sure the creators would love to see their work become commercially successful and widespread, I don't think that a very interesting criteria to judge what's essentially cool computer science research.

I've never understood why anyone would use a wizard to install software: they are unstable old men with magical powers and they are NOT to be trusted!!!

Now you are going to have one write out instructions for an AI?! I guess we know how the AI apocalypse gets started!

Don't use IPv4 and NAT < firewall.

Why would IP based routing be inherently more power hungry?

Any particular advantage to Suzi over Thread? Why didn't they adopt an IP based standard that is interoperable with ... all major networks since ~1995 (if not before)?

It's absurd that the list is so long considering the PR to fix it would only take a couple of hours.

Have they done anything to mitigate this? Like client side filters or message scanning for new direct messages?

WINE, CodeWeavers, Mesa, Red Hat, and plenty of others have been pumping money into the Linux graphics subsystems for a very long time. It's cool that Valve was able to use its considerable wealth to build a business off of it. But they came in at a pretty opportune time.

Windows support had gotten a boost from .NET going open source as well as other stuff MS began to relax about. It also helped that OpenGL was put to rest and there was a new graphics API that could reasonably emulate DirectX. I don't know much about the backstory of Mesa, but it's pretty cool tech that has been developing for a long time.

It is not common outside of security inclined communities like cryptocurrencies. It should be and we are slowly moving there.

Wtf is up with the clown car that is floating point standards?

Thankfully, there are regulatory regimes that require physically segregated systems for most cars, airplanes, power stations, etc

However, safety critical is not limited to cars: it also includes the phones of activities and journalists living under authoritarian regimes.

Monolithic kernels written in portable assembly mean that such bugs DO grow on trees [1] and the lack backporting means they just drop to the ground: the poor are sold phones that may never receive a security update. So even sugar tax activists in Mexico are the target of spyware!

We have seen the sophistication of these attacks ramp up as cryptocurrency has made them profitable and the North Koreans have made a killing exploiting these bugs.

Maybe you are right and it is very difficult to find these bugs but that just means low demand is what is keeping the price down. But that's probably because there enough LPEs and known RCEs that they are not needed most of the time.

[1]: https://www.cvedetails.com/vulnerability-list/vendor_id-33/L...

I mean, they do all the time. The value is generally in keeping access, however, and operational security and access control is helpful. You can knock a system out but then you just get kicked out and have to start over.

It's in a proto state due to anemic academic funding. We need to throw cash at the problem.