Windows 10 will be "the last version of Windows" according to
Microsoft; they are going to push everything out as "updates" from
now on. This could mean a number of different things. Ideally it
"Updates" belongs in quotes, yes. The major updates that they release every 3-12 months, akin to what used to be called service packs or updated release images, are installing by a process that looks a lot like a full upgrade install.
Also take a look at the support lifetime schedule. It hasn't really changed. Windows 10 "released in 2015" will be supported for the usual length of time. Then presumably you have to upgrade to windows 10 "Released in 2020"
"Last version of windows" is really playing semantics.
changed. Windows 10 "released in 2015" will be supported for the usual
length of time. Then presumably you have to upgrade to windows 10
Naturally. The question I have in mind is, will you be able to install Windows 10-2015 on a new computer and upgrade it to Windows 10-2020 simply by running updates and taking lots of reboots ... or will that only take you as far as, for example, Windows 10-2018 before it insists that you "obtain an upgrade"
This is an ACTUAL CORPORATE MESSAGE that was sent out by a Microsoft recruiter.
They have acknowledged that the message is authentic (but are already trying to walk-it-back after the entire Internet laughed at them).
HEY BAE INTERN! <3
Hi! I am Kim, a Microsoft University Recruiter. My crew is coming down from our HQ in Seattle to hang with you and the crowd of bay area interns at Internapalooza on 7/11.
BUT MORE IMPORTANTLY, we're throwing an exclusive after party the night of the event at our San Francisco office and you're invited! There will be hella noms, lots of dranks, the best beats and just like last year, we're breaking out the Yammer beer pong tables!
HELL YES TO GETTING LIT ON A MONDAY NIGHT.
Yes that's right, youngsters: Microsoft is hip and cool. Cool like IBM when they did the commercial with a pair of nuns talking about OS/2 in Latin. Bill Gates must be rolling over in his grave (ok, Gates is not dead, but I wish he was). If there was ever any doubt that Microsoft's best days are behind it, this should clear that up.
HEY BAE INTERN! <3
More and more Exchange customers are switching from on-premise Exchange to Office 365.
Imagine ... they built a product so unreliable, so obtuse, so high-maintenance and expensive to run, that people are willing to pay them to run it for them.
Talk about Stockholm Syndrome!
I have one client that uses on-premise Exchange, the SBS 2011 variety. Which I installed in late 2013, because their previous SBS ate itself when C: ran full, because nobody had turned on backups and the logs ate all the space. It never recovered from a 30 gig log file.
The new Exchange had a seizure last year in August (precisely on my second day of summer vacation...). It never fully recovered and now needs attention like Kim Kardashian. I might be installing it again soon. Comparing the price for the SBS itself and my maintenance fees makes renting it in the cloud look really cheap. And I get to yell at a technician instead of being on the receiving end. Or spending two nights in a row at the office, trying to fix it.
(The second night became really funny when I shambled back to my car, wondered why it drove so shabby, only to realize I had a complete flat front tire. Which I then replaced while it was cold and snowing at 5 am. Next stop was a gas station to inflate the changed tire and buy half a litre of fine local beer, which I drank on the way home. Fuck Microsoft!)
Well, that's kind of the point. You can't just pop an Exchange CD into the drive and walk away with an email system an hour later, like you could with older versions. You're basically stuck using one of two megabucks models:
1. Install domain controllers and mailbox servers and front end servers, requiring an MCSE who has paid megabucks to Microsoft to learn that you need a half dozen servers to run even the most simple of Exchange environments.
By the time it's built and tuned and working properly, it's time to upgrade.
Pay through the nose forever.
2. Subscribe to O365, charges for every user, every mailbox, every month.
Pay through the nose forever.
This is Microsoft innovation today?
For those not paying attention, the "Windows 10 Anniversary Edition" (or whatever they called it) came out this week.
No big deal, it's just a service pack, but the important piece is that you no longer have to be running an "insider build" (beta quality code) to get your hands on the Windows Subsystem for Linux, aka "Ubuntu for Windows." This is a fairly big deal for those of us who live in a mixed Linux/Windows world. I've used MobaXterm for a year and a half and have been loving it, but this is even better because it's 90% "real Linux" -- basically a Linux userland running over a Windows subsystem that emulates the Linux kernel.
(I guess Richard Stallman would have an autistic tantrum unless we called it "GNU/Windows" or something)
By the way, the new version of MobaXterm is compatible with WSL so you don't have to use Microsoft's shitty terminal window. And when you run WSL inside MobaXterm you can run X11 applications and they work just fine.
So it's not as nice as a true Linux desktop, but it beats the hell out of having to run virtual machines to have both operating systems running at the same time.
Oh, I'll have to play with that. Hmm... I might need to, now that I think about it. Gah... another build machine...
Still playing around today. Obviously the first thing I did was "apt-get install citadel-client" so I could run my Citadel client natively in the environment, but I've already removed that and set up a complete Citadel build environment to see how well it would work. So far the fidelity is quite good. For those who remember "colinux" -- which was basically a Linux kernel running with a Windows OS as the underlying "hardware" -- this feels a lot like it. It could also be compared to User Mode Linux, which ran a Linux kernel over another Linux, but in this case it's Windows sitting underneath.
To be sure, this is NOT a transformation of Windows into a legitimate Linux.
There's no Linux kernel and no D-Bus. And the filesystem integration with the host is not "deep"
in any way; it simply maintains its own filesystem hierarchy within the host.
You don't have to create a virtual block-device with ext4 or whatever on it; it sits within the host's filesystem but there's no meaningful integration between the two other than that you can use normal file management tools to move data back and forth.
For someone who has a use for both operating systems, though, this is *much* more comfortable than running virtual machines to have both at the same time.
As I mentioned earlier though, Microsoft's terminal window is still a piece of crap; definitely use MobaXterm if you are going to spend any reasonable amount of time in this environment.
All else being equal, I'd still rather be running Linux natively. And it's kind of sad that in one fell swoop, now Windows is a better and more usable Unix than Mac OS is, simply by virtue of the entire Debian/Ubuntu userland showing up all at once.
All else being equal, I'd still rather be running Linux natively. And
it's kind of sad that in one fell swoop, now Windows is a better and
more usable Unix than Mac OS is, simply by virtue of the entire
Debian/Ubuntu userland showing up all at once.
I have no idea what planet you're on that you could claim that.... Pretty much any unix utility you could want is already there in OSX. There are some things that are missing, but there are usually some equivilent avaialble.
And there are lots of ways to get other OSS on the system if you need it....
OSX is kinda-sorta there but it isn't a real Linux. And to use it you have to put up with the rest of Mac OS, which, as I've pointed out before, I simply don't like.
Honestly, get your fingers on a mac, fire up Terminal and start fiddling around. Unlike cmd.exe, this is a rather useful terminal, but I would still recommend iTerm2, feels more real.
You might need to install the X11 Window stuff, if you want gui. But that is rather trivial, and iirc, it will offer you the download the first second you start a gui app.
I can "ssh -Y" into any linux and fire up a program, (almost) right out of the box.
Right now, I am circumventing the nanny-functions in the OSX window manager, which wouldn't let me copy files from a case-sensitive backup to a case-insensitive computer. I use the builtin rsync for that.
Other useful built-in *nix commands I have used are dd, nano, vi(m), emacs. And guess what, you have full access to /dev, if you want to clone a disk, for example.
The default OSX users might not make any use of all this, they might not even know about it, but if you come from linux, you can have much fun in the cli. There are some things to enchance that, you can install a complete Gentoo userland, if you are masochistic. Or you could install brew ( http://brew.sh ) as package manager and simply fill your disk with pure OSS joy. For example, there is no wget, only curl, in native OSX.
If I need windows apps, I try wine first. If that doesn't help, I use virtualbox. I need a few windows configuration tools for telephone system configuration at client's sites.
Been there, done that. I have owned three Macs. Eventually decided I didn't dig the scene and punched out. It has unix-like functionality but it's not a real Linux.
Well, using windows as a main machine has not been an alternative for me since 2003 or so. I have it mostly for weird software and some games.
Anyway, I have a real reason to bitch about MacroShit software:
Upgraded a whole client office to win10, they have this bastard SBS2011 I ranted about in an earlier post. Because they are cheap as shit, too, they didn't buy any CAL and so no computer is joined to the domain, they only use the Exchange features. In Office2010, everything kept working fine after the upgrade. Only now, that I want to add new exchange accounts to Outlook, I find that the demented cesspool of a sorry excuse for a proper mailclient does not store any password in the credentials manager anymore. No "MS.Outlook:email@example.com:PUT" entries are created. This happens on a freshly created local account and on two computers.
I'd count this as normal MS behaviour, random as fuck, but usually at least a few other people on the web rant about similar problems. In this case, noone does seem to have this trouble. Will try a fresh install of office tomorrow, so long I have to resist the urge of torturing that clients laptop to junk.
That's the situation on the ground today, of course. It remains to be seen whether they will continue to support it or if it's simply another embrace-extend-extinguish play. We just don't know yet ... with both Bill Hitler Gates and Steve MonkeyBoy Ballmer gone, they might behave. Or they might not.