You could try Tinc but it’s fairly involved to get running. Pretty nice if you have a root server and want to get several people wired up, though. There are probably easier solutions for your use case.
You could try Tinc but it’s fairly involved to get running. Pretty nice if you have a root server and want to get several people wired up, though. There are probably easier solutions for your use case.
Copy of Outlook Final (2) (new)
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.
Android already does that, no AI required. Some fairly simple math is enough.
The device first charges to 80% and holds there. It also calculates how long it will need to charge from there to full and when it will need to resume charging so that it will hit 100% just before the next alarm goes off. Then it does that.
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.
How about autoscrolling shmups where you don’t die after every hit and get to upgrade your ship between missions?
The oldschool entry in this niche would be Tyrian – released in 1995, made freeware in 2004, then ported to modern OSes.
2004 was also when Jets’N’Guns came out. It looks more modern, has a quirky sense of humor and a badass metal soundtrack. It also has a sequel.
Both games can be found on your (PC) digital marketplace of choice.
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.
I have to disagree on one point – that iOS home screens somehow look more orderly because they’re full of icons arranged in a strict top-left-to-bottom-right fashion. It doesn’t look any less cluttered than an overly full Windows desktop.
I found desktops that limit themselves to core functionality and maybe a nice wallpaper to be better looking and more usable since the days of Windows 95 and that hasn’t changed since.
That “strict grid of icons” look certainly is uniform across iDevices and that’s what appeals to Apple but I never found it to be particularly attractive.
I actually went back to a light gray theme for my new Linux machine after I’ve been stuck with Windows’s options of “flat pure black with hairlines” and “flat bright white with hairlines” for too long.
I don’t actually need dark mode that much (except for coding) if a bright mode theme is easy enough on the eyes. Windows 10 is just so ugly that only the dark mode is halfway palatable.
If only the old themexp.dll hacks still worked I could have a decent looking desktop on all of my machines…
True. It’s just the automated transfer that doesn’t work.
I didn’t bring up F-Droid’s very existence as an argument because iOS also allows a form of sideloading these days. Android still makes it a lot easier but Apple isn’t entirely out of the loop anymore. Baby steps, I guess.
I’m the spirit of fairness I will nitpick you.
Firstly, porting apps over between Android devices works seamlessly only if those apps come from the Play Store. Android has no provisions for auto-transferring e.g. F-Droid and its apps. So it’s no wonder you can’t transfer your iOS apps (which might not even have Android versions). But it is true that auto-transfers of Play Store apps between different Android spins is seamless.
Secondly, whether and how easily you can modify or replace your Android is dependent on the phone’s manufacturer. A Pixel is a very different beast from an Xperia in that regard. Still, Google do provide AOSP and are very mod-friendly on their own devices. Apple very much aren’t.
Garuda’s gaming spin should. At least mine runs on Plasma 6 + Wayland and I didn’t do anything special to get there.
Soon they will launch their new product, Copy of New Teams Classic (work or school) (2).
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.
Good to know. We initially set that network up well over a decade ago so my knowledge isn’t exactly current.