414 karma · joined March 14, 2013
NT itself is flipping marvellous :)
As for all the symbolic links, they all still work. They're only there for compatibility reasons and will disappear at some point (WinSxS is a worry though).
I disagree about sendmail though - that was a stinking turd and I have been ever grateful since postfix arrived on the scene :)
As for design errors, they are hard to prevent anywhere.
You can't really have a totally safe systems programming language (correct me if I'm wrong here).
To be honest, windows just pretty much works these days.
I have no idea why they came to these conclusions.
20MiB is impressive.
I genuinely feel sorry for the people on both sides Of this conflict as they're all going to suffer if it kicks off.
If the international community gets involved as well, its going to drag out even longer than Afghanistan or Iraq.
Its ugly whatever happens.
This whole thing has to play nice with a windows DFS cluster as well.
Serious Apple have always done a crappy job of online services - why would you expect any more.
The only use case I can see for it really is rapid scaling but that seems only viable for content delivery as your data back end architecture is way harder to scale than click the magic cloud button. Back in the old days we used to do content via CDN (Akamai etc) which actually works out cheaper per GiB.
Then we approach things like S3 which is terribly unreliable (some of our clients use it for storage as it's cheaper than a SAN but they suffer for that). Drop outs, unreliable network requests, latency, rubbish throughput and buggy as fuck SDK.
Its like consuming value line products from a supermarket. Sure there's quantity but its lacking in quality.
We did have a testing period which was unfortunately run by a Muppet who decided the loss was acceptable. Muppet now no longer works for organisation.
Either the hypervisor scheduler is shit or the abstraction is costly. I reckon its down to the reduction in CPU cache availability and the IO mux.
This was HP kit end to end, VMware certified, debian stable on and off ESX 4.
That's enough abstraction.
We understand it. The numbers sold are not the numbers gained.
The entire infrastructure deployment was planned around virtualization, DC failover and resilience using VMware's guidelines and solutions (VMware were even paid to consult on this). It never delivered and doubled our administrative and licensing overhead.
The outcome is pretty grim.
I'm not really a fan of virtualization myself. We canned it at our organisation a couple of years ago. We had 30 ESX/vSphere managed hosts across 3 data centers which hosted app servers, web front end servers, virtual load balancers and some other minor infrastructure. The final straw was the upgrade costs. Not only that we had problems with volume size limits on our SAN which would require more expense and hackery to work around. Also, we couldn't host our database servers on top of it due to performance problems so we had to have dedicated machines there anyway.
The whole thing at the end of the day just added complexity, expense and didn't improve reliability, security or load distribution as our architecture was sound on that front already.
We've gone back to the original virtualization system: processes and sensible distribution of them across multiple machines. Performance, cost and sanity have improved.
I can understand that virtualization is useful when your resource requirement is less than one machine but above that, I doubt there are any real benefits. It's snake oil.