Maybe, but that's assuming their war economy lasts for that long, that they still have people to run those things, etc. Besides, Europe was caught with its proverbial pants down; in 5-10 years, they will (should) have their military up to speed again, with fresher, better equipped and better trained people than Russia has. The border countries have all upgraded their defenses already, and if they invade a NATO country they suddenly have all of Europe and - if still applicable at the time - the US on their back.
There are no scenarios in which Russia can have any significant victories. The only thing they maybe have is nukes, but nobody wins if those are deployed.
Not a single serious war. A war against Russia will be similar to ww1 and ww2. meaning men from all age groups will die in large masses. Or you believe a war will be similar to sandal terrorists.
> We do a staged roll-out before publishing APKs. As far as I'm aware neither are at 100% which is a requirement for posting the builds. The APK is available from automation in the meantime if you want: https://firefox-ci-tc.services.mozilla.com/tasks/index/proje...
Since I don't want to tinker every weekend with my distro anymore I need something stable. openSUSE Leap, based on SLE, offers this. Additionally KDE is a first-class citizen and just works as intended.
There's also a rolling release version, Tumbleweed, but I didn't try it yet.
FWIW, I run Tumbleweed on my private desktop, and it works pretty well for the most part. The only major annoyance is that I have to reinstall the nVidia driver every time a new kernel comes around, but other than that, it is very nice.
The last time I checked, the only thing I could find were instruction on how to install the nVidia driver manually. Turns out nVidia has a repository for Tumbleweed! =D
Just to be clear, things do break a little sometimes. But on the plus-side, openSUSE uses btrfs snapshots - every time updates are installed, the system creates two snapshots, one before and one after installing the updates. So if something breaks, one can always roll back to a known good state and wait for a couple of days before giving updates another try.
Worth noting that GNOME and Xfce are also first-class citizens in those respective versions of openSUSE. openSUSE is the reason why I don't hate GNOME3 with a burning passion, and the Xfce version is what I tend to install on desktops by default.
> Since I don't want to tinker every weekend with my distro anymore
Do many people actually do this, though? A few years ago, I used Arch as my main distro, and, besides the initial setup, almost never tinkered with it. I would imagine that more approachable distros would be more tinker-free too.
It really depends on what you qualify as tinkering. I switched to Debian stable as I found the constant upgrade cycle of rolling distros to require to much tinkering.
It's true that the most approachable distros (SUSE, Fedora, Ubuntu and its derivatives like Elementary OS) are more or less "tinker free" these days.
For those of us who still like to tinker while maintaining a stable base, there are distros like Debian, Slackware, Void, and so on. And finally, for those who consider Linux a hobby or pastime (or who are comfortable living on the bleeding edge) there are projects like Arch, Neon, and Gentoo.
No, because Arch is a rolling release whereas you have to run Unstable and -current respectively in Debian and Slackware to be closer to the bleeding edge. But having said that, I should actually have put Void in with Arch and Gentoo.
It doesn't have to be "build everything from source", they have installs based on different stages. You can even do a binary only install if you wish. And it is rolling, so it does fit in with Arch and Void in that sense.
Well, I'm not saying you can't tinker with those, just that you don't have to in order to get a working desktop out of the box. I have yet to run across a Linux based OS that outright discourages getting under the hood, except perhaps Android.
I guess what I was trying to say is that instead of dealing with the default parental guidance features of RH and Fedora
(which usually ends up with impatient users disabling SElinux and then disabling the stock packet filter) and having to suffer the eccentricities of RH/Fedora systemd and 'socket' activation of an interfering frankenservice you could more profitably spend your time tinkering elsewhere.
Gotcha. Yep my goto hacking/tinkering/learning distros are Slackware, Alpine, and (on the BSD side) OpenBSD. I also consider all of those suitable as server/container OSes for varying reasons.
I run Elementary OS as my daily driver these days; no fuss, no muss, just log in and get to work. About the only thing I do on a fresh install beyond changing the background is setting up my tools. Surprisingly git isn't installed from the outset, but it's just a sudo apt install away. Likewise, I enable ppa support, add the ppas for Waterfox and Oracle Java, and install the ubuntu-restricted-extras package for better media support. Beyond that, the built in apps and programs suit my needs almost perfectly, and the OS fades into the background unlike Windows 10 or other flashy "LOOK at ME not your WORK!!" type OSes/DEs.
OpenBSD is very nice but it used to be a bit painful for a desktop. Funny, I ran linux on the desktop from 2000-2016
and then went back to windows because I'm getting old. :)
I lumped it in with the more bleeding edge distros because its goal is to showcase the latest and greatest that KDE Plasma has to offer. In that sense, it's a bit unstable on the user-facing front. Also, KDE itself is a pretty wild beast that takes a ton of tinkering to get it to any one person's liking. I'm not saying it's unusable out of the box, but it definitely is a tweaker's wet dream; its options have their own options in nearly every configuration panel.
I totally agree. My main point against Scala is the mass of features, it's like a modern C++. In the worst case you end up with a dev team in which everyone codes in his very own style.
We had to redo an inhouse Electron app in WPF because we came to the point where we had to do some stuff within windows, e.g. printing or create a heavily customized MSI file. Both is possible with Electron but with the native Windows solution it's easier to fine-tune behavior.
I think for UI and some web stuff Electron might really be superior. Especially if your team is already fluent with the web stack. But it has it's limits and if you reach them or have very specific requirements you might be better of with WPF or UWP apps and the initially higher effort of developing in C#/XAML might pay off.
Saying this I believe the existence of Electron is a great possibility for UI devs.
