The only thing that would make catching up easy is if they stopped making movies. I think I've seen
With all of the reboots and remakes and rights bouncing from one studio to another comic book movies are as much of a confused mess as their source material.
It's not just about storage and transfer costs. It's just a shitty ass solution for sharing documents.
Why the hell would I want a hundred and forty-three copies of slight revisions of the same document spread across a half dozen mail threads when you could toss out a link to an online document?
And frankly, people seem awfully dismissive of the cost of storage and transfer here. That shit absolutely adds up, and email is now a predominantly free service with high quotas, meaning it's either razor thin margins or a full on cost center. If you want MORE embedded ads, go right ahead and demand the ability to send 1GB videos through email. And then enjoy having ads injected into them.
If you have a library that simply assumes reliable transport and doesn't handle exceptions your library is broken. And I fail to see how Project Loom creates new opportunities for that kind of brokenness.
The whole point of the approach is that in maintains the same programming models as exist in Java already, with the same error handling frame work, and largely the same concurrency model. The advantage is preserving execution context (e.g. ThreadLocal variables) without unnecessarily coupling it to an OS level resource (i.e. "native threads").
The idea that an arguably more primitive and cumbersome approach is better because it "forces awareness" sounds like a rehash of the arguments assembly and C programmers have levied against higher level languages in general. I tend to think that expecting programmers to (mostly poorly) implement cooperative multi-tasking was never a particularly good solution to the concurrency problem.
You can do the same with the Kobo reader, no need to even root it.
I once was working on a project to use a Pi Zero and Debian with the Pi 7" touch screen to make a little reader - not bad, but I got stuck when I needed to get a 3D printed case made.
I currently do all of my ebook reading (and that's a LOT of reading) via only DRM-free platforms and read them on my little lenovo android tablet.
Doesn't solve the textbook issue obviously, though stuff like OpenStax is a step in the right direction.
I hope FSF has success in this area.
What is not funny is how the faithful just lap that stuff up and never understand.
Windows has "faithful"? I'm sure you're right, I just can't imagine anyone who owns windows going out of their way to actually procure it.
It's only been macOS since 2015. Prior to that it was "OS X" for a few years.
I've been an IT professional for over twenty years, supporting exclusively Linux servers. I had a choice when I got my last work laptop, and took Windows over MacOS without hesitation. I can't stand the Apple ecosystem.
I also switched over from Linux to Windows for my last personal computer. I bought a Surface because it was the form factor I wanted, with the expectation that I would install Linux or at least dual boot. Once I started looking into the abysmal state of Linux support for things like high DPI displays, I decided not to bother.
Since virtually everything I do is on remote servers anyway, I've lived in a combination of browser and terminal windows for years. Being able to run Linux apps local with WSL was just extra gravy.
*shrug* It's my browser of choice.
I have a box mostly full of cords I will never use, plus a few I will be thankful I kept. Given that I don't necessarily know in advance which is which, and given that it really doesn't take very much space, this seems an eminently rational thing to do.
Not only is the commonly promulgated story of how QWERTY was designed almost certainly apocryphal, there is scant evidence that Dvorak has any appreciable advantage.
If you actually look at the TIOBE rankings, it's #11 (not #12 as claimed in the article), and back on the upswing. If you look at RedMonk, which they say they looked at but don't reference with respect to Ruby, it is a respectable #8, being one of the top languages on GitHub and Stack Overflow.
We are certainly past the glory days of Ruby, when it was the Hot New Thing and everyone was deploying Rails, but to suggest that it is "probably doomed" seems a somewhat hysterical prediction.
I can unironically say that, from a feature standpoint, the original Edge has been my preferred browser for the last couple years, compatibility issues aside. Nice clean layout, built-in and accessible reading mode and translation, the ability to annotate pages and share them, the ability to save tab sets.
Some of those features are missing in the new version of Edge, but assuming they're in the pipeline I would jump on the chance to standardize my browsing experience between work and home.
I only just installed it, but the new browser seems to be missing all the features that made Edge my default browser. No inking support. No tab groups. No translate button in the address bar. No built-in reading mode.
Sigh. I hope this gets better.
You haven't given any useful information that would suggest criteria. What is the employee going to be doing on the laptop? Are they going to be traveling? Will their activities be confined primarily to that machine, or will they be primarily accessing remote resources? And if they are going to be doing on-device work, do you have existing plans, tools or infrastructure to deal with date security and integrity, like off device syncing and backups?
TL;DR: You're terrible at asking questions, so I won't bother answering. If the individual is familiar with Windows though, I see little good reason to force them to learn a new platform unless something else compels that decision.
Happiness is twin floppies.
