Skip Navigation

Posts
9
Comments
275
Joined
3 yr. ago

  • Then it really is authentic Boston Pizza!

    (No seriously I found maybe 3 good pizza places while I lived in Boston and I'm pretty sure 2 of them technically weren't even in Boston. The pizza there is mid at best)

  • It's worth noting that support for pixel 10s is currently in alpha and incredibly buggy

  • Is raccoon still being developed? The last commit that isn't a dependency bump was 3 months ago and the last release was 8 months ago. I'm still using it for now because I like the UI but I feel like a lot of the formatting is kind of jank

  • COSMIC is early on enough that you'd probably be better off opening an issue on their GitHub, this is very likely a bug

  • Kirigami is built on top of Qt by KDE

  • To be fair, Linux isn't developed on GitHub (it's developed on the Linux Kernel Mailing List and kernel.org) and most of the spammers knew that going into it. The PRs on that repo were mostly just people trolling any bystanders that took it seriously until the internet did what they do best and took the joke too far.

    In this specific example they didn't waste anyone's time or resources because it was never being used or monitored in the first place.

    Edit for more additional context: Linus (who created git in the first place) mentioned not liking centralized git servers so he's specifically said for multiple years that he never considered actually moving development over to something like GitHub

  • I think the problem is that roads not designed for bikes in Europe are also old enough to have not been originally designed for cars, so things usually end up working out to some degree.

    In the US (especially for infrastructure built from scratch in the 1900s onward, i.e. most of the US except for some parts of the east coast) most roads and town layouts were designed specifically around cars and travelling at car speeds, and are explicitly hostile to anyone who isn't travelling in the biggest truck you've ever seen in your life. Blame oil/motor companies for bribing politicians throughout the 1900s (and honestly still today)

  • The company says it is now developing an “advanced flow that allows experienced users to accept the risks of installing software that isn’t verified.” This installation flow will include safeguards to protect people who are being coerced into installing a dangerous app, or tricked by a scammer, along with “clear warnings to ensure users fully understand the risks involved.”

    Seems like there will also just be a toggle somewhere (probably developer settings) that lets someone install from any source

  • I know they said they're using fex for x86 emulation but how far down does that go? AFAIK arch Linux doesn't have official arm support yet (alarm exists but they've had a lot of problems keeping packages up to date) so I wonder if Valve is planning on helping with upstream arm support

  • To be clear this was not a recommendation lol I completely agree with you

  • If you want to do both at the same time without knowing which side any given task will fall under use NixOS

  • Or source code at this point, AOSP is still missing the 16 QPR1 release that came out for pixels at the beginning of September

  • Release QPR1 source code first though it's been 2 months 😭

    (Or at the same time, that would be good too)

  • I think a lot of the confusion comes from the ambiguity of the phrase "memory leak." Rust is designed around preventing insecure memory access (accessing out of bounds for an array, use-after-free, etc.) and devs call that a memory leak. But another form of memory leak is just not freeing up memory when its no longer needed (e.g. continuously pushing a bunch of things to a global vector and never clearing it). That is more of a fundamental program design issue that rust can't do anything about. (and really, neither could any turing complete language)

  • 'Use-after-free' bugs are a specific type of memory access bug that Rust was designed around preventing. It literally refers to trying to access a block of memory after it has already been freed by the memory allocator. Unless you go out of your way to use the "unsafe" keyword in rust (which in most cases, you shouldn't) then this type of bug is not possible.

  • Do you know what a use-after-free bug is? Rust was literally designed to make this type of memory bug impossible.

  • But then the kernel wouldn't be free! Free as in 'use-after-free'!

    (/s in case it wasn't obvious)

  • That's exactly my point. Giving away the exact town you live in to strangers on the Internet is not good advice to give people generically.

  • Maybe I could see country or even general region, but town?? Why would I want to publicly give away my location like that?

  • Nix / NixOS @programming.dev

    Clangd LSP support for C/C++ on NixOS?

  • Linux @programming.dev

    Pipewire/Wireplumber set volume based on node name

  • 196 @lemmy.blahaj.zone

    celeste rule

  • Programmer Humor @programming.dev

    Only 5 years out of date now 🙃

  • Programmer Humor @programming.dev

    C++ try not to add footguns challenge (impossible)

  • linuxmemes @lemmy.world

    Yes, yes we can

  • Programmer Humor @programming.dev

    Good luck web devs

  • Linux @lemmy.ml

    Reminder to clear your ~/.cache folder every now and then

  • Programmer Humor @programming.dev

    the myth of type safety