Yep. I run Garuda and the main pull is that it’s a more user-friendly Arch with a lot of stuff I want to use preinstalled. I don’t really care about how XTREME it is or whether I might potentially get 1 FPS more.
Yep. I run Garuda and the main pull is that it’s a more user-friendly Arch with a lot of stuff I want to use preinstalled. I don’t really care about how XTREME it is or whether I might potentially get 1 FPS more.
Also, Ubuntu is moving towards using snaps for everything so they’re pretty much the successor to PPAs.
Mostly yes but there’s one other option that simplifies the whole thing: Chromebooks. They’re actually pretty decent for someone who doesn’t need much beyond a browser, a mail client, and a basic office suite.
Sure, they’re tied to Google with all that entails but they can be a real option for someone like a senior who relies on relatives for tech support.
I use interactive rebases to clean up the history of messy branches so they can be reviewed commit by commit, with each commit representing one logical unit or type of change.
Mind you, getting those wrong is a quick way to making commits disappear into nothingness. Still useful if you’re careful. (Or you can just create a second temporary branch you can fall back onto of you need up your first once.)
Or, if the team does allow refactoring as part of an unrelated PR, have clean commits that allow me to review what you did in logical steps.
If that’s not how you worked on the change than you either rewrite the history to make it look like you did or you’ll have to start over.
Garuda’s gaming spin should. At least mine runs on Plasma 6 + Wayland and I didn’t do anything special to get there.
I think Latte-Dock has been unmaintained for some time now. It’s a dead project and maybe doesn’t even work properly with Plasma 6. So it’s a good time to drop it.
On the one hand I like the basic idea, on the other hand I think that some fundamental problems aren’t fully solved yet. There big use case are passkeys and direct password manager integration – neither mesh well with the idea of software that isn’t allowed to talk to most of the system.
I’m certain that this will be resolved at some point but for now I don’t think Flatpak and its brethren are quite there yet.
True, although that made people think that Windows 2000 was the intended successor to Windows 98 – me included. Not that I minded; in my opinion Windows 2000 was straight up better than Windows XP until XP SP2 came out. Anyway, Microsoft spends far too much time getting cute with version numbers.
CUDA was there first and has established itself as the standard for GPGPU (“general purpose GPU” aka calculating non-graphics stuff on a graphics card). There are many software packages out there that only support CUDA, especially in the lucrative high-performance computing market.
Most software vendors have no intention of supporting more than one API since CUDA works and the market isn’t competitive enough for someone to need to distinguish themselves though better API support.
Thus Nvidia have a lock on a market that regularly needs to buy expensive high-margin hardware and they don’t want to share. So they made up a rule that nobody else is allowed to write out use something that makes CUDA software work with non-Nvidia GPUs.
That’s anticompetitive but it remains to be seen if it’s anticompetitive enough for the EU to step in.
They could’ve sold Windows 2000 as Windows NT 5 and Windows Me as Windows 2000; that would’ve kept the “NT X” versioning scheme for the professional line and the year-based scheme for the consumer line.
But the versioning scheme for the NT line is all kinds of weird in general. Windows 7 is NT 6.1. Windows 8 is NT 6.2. So we’ve established that the product name is independent of the version now. That means that Windows 10 is NT… 10.0. Windows 11 is also NT 10.0.
Okay.
True, but those are not the people the men’s is making fun of. It makes fun of perfectly healthy people who decide they need gluten free everything because they heard that gluten is bad and they can’t do any research on how and why. Same with vegans who are only vegan because it’s trendy (and who probably cheat every other meal because a vegan lifestyle actually requires a fair amount of effort and learning about nutrition).
Compared to other languages it’s still very barebones – but admittedly some of the bloat is also because the JS world is kinda set in its ways. I still see people use jQuery for basic selector queries and SASS for basic CSS variables.
Another factor is that developers these days assume that users have fast unmetered connections. Loading 800 kB of minified gzipped JS from ten different domains is seen as no big deal. When the cost of adding piles of dependencies is considered nil there’s no impetus to avoid them.
The lack of a standard library is really the worst offender. Most of a given node_modules directory is filled with middleware to handle JS’s lack of everything.
And it’s matched by .+@.+
as it contains an @.
Remember, we’re taking about regular expressions here so .+
means “a sequence of one or more arbitrary characters”. It does not imply that an actual dot is present.
(And I overlooked the edit. Oops.)
Which ones? In RFC 5322 every address contains an addr-spec at some point, which in turn must include an @. RFC 6854 does not seem to change this. Or did I misread something?
You can use a regex to do basic validation. That regex is .+@.+
. Anything beyond that is a waste of time.
There’s also oh-my-fish.
Fork.
Copy of Outlook Final (2) (new)