

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.
made you look
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. YouTube 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.
And PeerTube ideally, though it doesn’t seem to work properly at the moment. You can see channels (as a community), but posts don’t seem to be resolved.
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.
The CPU usage spikes aren’t necessarily from React Native itself being particularly heavyweight, but rather from the fundamental architectural choice of running a web-based rendering engine for core system UI elements.
The likes of both Microsoft and Apple are openly hostile to such frameworks (QT and GTK come to mind).
Funny thing, the OneDrive client app that ships with Windows, uses Qt
React Native doesn’t render using a browser instance, it’s native code (as the name implies), it’s actually a layer over WinUI 3 (Previous versions used WPF/UWP)
So it’s in the same boat as MAUI, which is also a layer over WinUI 3.
Wouldn’t have to order them to do anything, they’d gleefully offer to do it first.