You should read the release notes for any RHEL minor release. They do all kind of crazy stuff in their enterprise kernel. The entire KVM virtual machine layer for example, that came in with RHEL 5.2, a minor update that you got automatically. They also break stuff occasionally, but I've not had that happen very often.
You know there are reasons why Jessie is still in testing and has not been released yet? If you want something that works you should use the stable version, which is currently Wheezy.
A developer fixes a bug, and writes a comment on github.
Technically he was @-mentioned (or whatever it's called nowdays), got a notification from the GitHub thread in his email and responded to it from his email. He did not write a comment on GitHub. GitHub took his reply and posted it automatically.
They have outsourced parts of their business to companies in China, but that does not make them a Chinese company.
The solution is not that Apple should take iMessage to every platform out there, but that we start using open protocols instead like XMPP.
Actually he/she is right. OS X does support running 64 bit binaries on a 32-bit kernel. OS X didn't even have a 64 bit kernel until 10.6 and it wasn't until 10.7 when OS X started to boot into the 64 bit kernel by default, but you could still run 64 bit programs just fine back to 10.2 just as long as you had a 64 bit CPU.
That was exactly his point: you can hire another company to continue the maintenance.
I guess you missed his/her point as well. With Windows you got free updates up until July this year. With Linux you would have had to finance that yourself. Installing Linux in 2003 and paying someone to make updates for you would most likely not have been cheaper.
With Windows, there is no such option even if you were ready to throw cash on the table.
Yep, absolutely. You're screwed once MS stops their support. In their defense though, it is quite good that they provided updates for 12 years.
20 pages are barely enough to even introduce ZFS. Another 200 page book is more reasonable.
Yep, that's why the Roslyn compiler is so interesting.
Yes. And the problem is that VB is MS only. It is a vendor lock in. What about stuents that have a Mac or Linux at home? He chains them to MS.
On Debian 7:
$ uname
Linux
$ vbnc
Visual Basic.Net Compiler version 0.0.0.5943
Copyright (C) 2004-2010 Rolf Bjarne Kvinge. All rights reserved.
Error : VBNC2011: No files to compile! Cannot do anything!
Compilation took 00:00:00.2141430
https://packages.debian.org/je...
Also, the new Microsoft
VB.NET is certainly not C# with a different syntax. They both compile to IL and run on the CLR, and they have similar features but they are different.
Naming a book "Storage Essentials" and then not talking about ZFS was a mistake. If you're going to be building any type of NAS, you're going to want to use ZFS for it's scalability, reliability and stability. While you might get away with UFS for a couple of terabytes, you're going to have a bad time of it when you've got 40TB worth of storage space to manage.
Essentials means "the essentials," not "everything you should know about X."
After quickly looking through the table of contents, I don't think there's actually enough room in the book to even introduce ZFS. What should he have taken out? Smart? RAID? Encryption? I would argue that all that is way more "essentials" than ZFS. ZFS deserves its own book.
What the gods would destroy they first submit to an IEEE standards committee.
