

And on the upside for them, no Gnome, since the devs are making systemd a hard dependency.
made you look
And on the upside for them, no Gnome, since the devs are making systemd a hard dependency.
I am entirely unsurprised that people who hate systemd also hate wayland.
Wouldn’t have to order them to do anything, they’d gleefully offer to do it first.
Then there’s accessibility functions, which wayland breaks almost by design by denying apps access to each other. Even something as simple as an on screen keyboard becomes nearly impossible to implement.
That’s a side effect of just dumping everything into X11, once you switch from it you lose all the random kitchen sink warts it grew over the years.
Like an on-screen keyboard shouldn’t be fiddling with a display protocol to fake keyboard inputs, it should be using the actual OS input layer to emulate them (So then it’d work with devices that read input directly and not go via X11). Same with accessibility, there’s a reason other OSs use separate communication channels with their own protocol.
Yeah this is a perfect use case for torrents, could go a step further and keep track of a downloader’s ratio to stop people leaching.
deleted by creator
Tizen (resting place of Meego)
I’d say SailfishOS is the final resting place of MeeGo, especially since it’s maintained by ex-Nokia devs.
Ironically enough, the only reason I know politicians appoint judges in Queensland, is because of a rather infamous appointment we had.
I mean, the point of the init process is to bring up the filesystem and disks, if the configuration is wrong that’ll be the process to complain about it.
So how the OS already catches links to e.g. YoyuTube and offers to open it directly in the app, it could also do that for apps that weren’t installed and it’d just download and run them automatically. One of the examples was Vimeo, instead of loading the website it’d download a cut down variant of the normal app and load the video in that instead.
The idea was to push people towards using apps instead, but now Google control the web they can just make that their app store instead, so native apps aren’t as relevant anymore.
I’m not convinced LLMs as they exist today don’t prioritize sources – if trained naively, sure, but these days they can, for instance, integrate search results, and can update on new information.
Well, it includes the text from the search results in the prompt, it’s not actually updating any internal state (the network weights), a new “conversation” starts from scratch.
“No, go away.”
That’s a perfectly valid way to deal with toxic contributors. There’s always people with better social skills and equal developer skills out there, you don’t have to accept and include toxic people just because they wrote some code.
That’s only if you’re running an x86 container right? It should be native with an ARM64 one.
Also, compared to something like the Switch? I don’t see MS remotely bricking these devices if you run “homebrew” on them.
I’d double check, if you haven’t picked an option specifically it might just default to the fallback (i.e. BOOTX64) It’ll be under the boot device order section.
(Not my picture, stole it from Reddit)
Here it’s listing all the possible boot options this mobo can find, but there’s a generic “UEFI OS” option which I’d bet is the fallback. And once a choice is made it’s kept unless something resets it, so if it just happened to be set to the fallback once it’ll stick with that until a change is forced.
When installing windows while there is a Linux install, windows will see the EFI partition already there and just decides to share it, and doesn’t create its own.
That’s what it’s supposed to do, it’s a plain FAT32 partition, the bootloaders are just files you put in there.
Part of the issue is that while a well-made motherboard will look for all bootloaders on the partition and present them as options in the firmware UI, bad ones will only look for a specific file (\EFI\BOOT\BOOTX64.EFI
) and use that. For an OS to have a chance of booting on those boards it has to overwrite that file, blowing away whatever other bootloader was there before.
It’s annoying, since Windows is mostly well behaved here (It puts the main copy of the bootloader at \EFI\Microsoft\Boot\bootmgfw.efi
and Linux bootloaders can see that and offer it, the reverse isn’t true) and can co-exist with Linux well (Well…), but manufacturers cutting corners causes more problems for everybody.
Unfortunately I’m not finding much explicit information on the specific processes, just that it’s possible.
Now of course just because it can be recycled indefinitely, doesn’t mean it is in practise. Could be contamination, colouring, or just plain cost.
If these AI researchers really have no idea how these things work, then how can they possibly improve the models or techniques?
Like how they now claim all that after upgrades that now these LLMs can “reason” about problems, how did they actually go and add that if it’s a black box?
Yeah, there’s a mysticism that’s sprung up around LLMs as if they’re some magic blackbox, rather than a well understood construct to the point where you can buy books from Amazon on how to write one from scratch.
It’s not like ChatGPT or Claude appeared from nowhere, the people who built them do talks about them all the time.
Now that is cool.