Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)M

mox

@ mox @lemmy.sdf.org

Posts
45
Comments
309
Joined
3 yr. ago

  • Youtube - Bryan Lunduke - Sanctions Hit Linux Kernel, Russian Programmers Banned

    Jump

  • Netflix has closed its AAA gaming studio

    Jump

  • They had one?

  • The empire of C++ strikes back with Safe C++ proposal

    Jump

  • Unfortunately, I don't think D is good enough to prove your point. From your follow-up comment:

    A language that for all intents and purposes is irrelevant despite being exactly what everyone wanted,

    As someone who uses D, I can attest that it is not what everyone wanted; at least not yet. Despite all the great things in the language, the ergonomics around actually using it are mediocre at best: Several of its appealing features quickly turn it into a noisy language, error messages are often so obtuse as to be useless (especially with templates and contracts in play), and Phobos (the standard library) is practically made of paper cuts. Also, the only notable async support is a fragile mess, and garbage collection is too deeply embedded into both the stdlib and the ecosystem.

    (To be fair, D could be vastly improved with better defaults and standard library. That might happen in time, as Walter and the other maintainers have shown interest, but it's just wishful thinking for now.)

    Also, D is an entirely different language from C++, and as such, would require code rewrites in order to bring safety to existing projects. It's not really comparable to a C++ extension.

  • The empire of C++ strikes back with Safe C++ proposal

    Jump

  • The empire of C++ strikes back with Safe C++ proposal

    Jump

  • Given how long and widely C++ has been a dominant language, I don't think anyone can reasonably expect to get rid of all the unsafe code, regardless of approach. There is a lot of it.

    However, changing the proposition from "get good at Rust and rewrite these projects from scratch" to "adopt some incremental changes using the existing tooling and skills you already have" would lower the barrier to entry considerably. I think this more practical approach would be likely to reach far more projects.

  • Deleted

    Permanently Deleted

    Jump

  • Your hypothetical energy savings from new hardware is nothing but a wild guess since you don't know his actual usage, and meaningless anyway unless you subtract from it the energy use from manufacturing and distributing a new system, as well as that from disposing of the old one.

    Also, you haven't addressed the other problems mentioned at all.

  • Deleted

    Permanently Deleted

    Jump

  • Government comprises many departments and organizations, which do many things. It's not a single blob of all good or all bad.

    Also, not all back doors and CPU bugs are government-imposed.

  • Deleted

    Permanently Deleted

    Jump

  • I'm online, and I commend you for continuing to use your hardware for as long as it does the job, instead of adding to the world's energy, material, and e-waste problems. Well done.

  • Deleted

    Permanently Deleted

    Jump

  • According to the translation I read, the security-related complaint in CSAC's post is mainly about Intel Management Engine. And you know what? They're right. It is a back door, and it is a security risk. Not a new or obscure one, though, and not just for China.

    The risks imposed by Intel Management Engine and AMD's Platform Security Processor have been known for several CPU generations. Obviously, a lot of us are unhappy about this and would like a way to disable them.

    https://support.system76.com/articles/intel-me/

    https://hackaday.com/2020/06/16/disable-intels-backdoor-on-modern-hardware/

    Instead, these components have been made more and more integrated with core system functionality, making the prospect of disabling them less and less practical. I fear it may take legislation to give us back control of the computers we supposedly own.

  • Former Intel CPU engineer details how internal x86-64 efforts were suppressed prior to AMD64's success

    Jump

  • Former Intel CPU engineer details how internal x86-64 efforts were suppressed prior to AMD64's success

    Jump

  • Intel was all about market segmentation

    See also: ECC memory.

  • Deleted

    Permanently Deleted

    Jump

  • Khan is indeed doing good stuff, but I was referring specifically to corporations interfering with our ownership and repair of the things we buy.

  • Deleted

    Biscuit the cat says "Lookout a window today!"

    Jump

  • I just did. Thanks, Biscuit.

  • Deleted

    Permanently Deleted

    Jump

  • Tractors seem as good a starting place as any. Let's not stop there.

  • What Would It Take To Recreate Bell Labs?

    Jump

  • Or to put that another way, it would take putting the teeth back in regulation (among other things).

  • What Would It Take To Recreate Bell Labs?

    Jump

  • TIL about the differences between flotsam, jetsam, lagan, and derelict

    Jump

  • Steam and Mastodon.

    Jump

  • idk how you spare the effort.

    When you've been building networked systems for longer than JavaScript has existed, it no longer takes effort to spot design choices that put users at risk. When you've watched endless vulnerabilities be exploited over the years, it's not paranoia, but a real-world problem that impacts real people. At that point, the flaws are impossible to responsibly ignore.

    Spreading awareness and showing people how to build safer systems does sometimes get tiring, but I think it's important.

  • Steam and Mastodon.

    Jump

  • I love this in principle.

    I just wish Mastodon instances were viewable without JavaScript. Opening the door to many types of browser exploit and fingerprinting shouldn't be required just for reading.