Problem is let's say there is a bug that is causing your web app to constantly run out of threads or restart?

Who do you call for support? Let's say you think it is mono causing it? WIth VS.NET on Windows you see the bug is not there. Or if it is you can go to MSDN and find others with the same issue and work arounds and a promise from QA that it will be worked on if it is big enough in a Windows update.

I do not like Mono for this reason.

Like C++ there is a big difference between one written for Unix and one with Win32. .NET is great but not if you make calls that emulate Windows. That is not good. Winforms is an example too which uses dcom/com underneath. It would make more sense to use GTK calls if it is a Linux app.

I am not a metro fan at all.

I am typing this on Windows 7. But really people do not use servers as a desktop and your thing with VPN's is a non issue in a server.

There are younger folks who have no problem with the start screen after they get used to it. It is just different and requires muscle memory. For a server I only use server manager which opens by default or the tools at my desk. I do not run it on a laptop where I will VPN from a hotel room.

More than likely when the release comes next month it will have a 10 UI with a start menu and yes some applets come with 10 but will probably be absent for the server..

I do not see what the big deal is on a server?

Desktop by default loads up with Server manager. As long as you do not hit the Windows key the start screen doesn't pop up. You can with powershell install Windows Server 2012 headless with no gui at all!

90% of the work on servers is done from a system admins desk anyway with MMC and the associated server tools. Very rarely does one log in unless something is wrong. Powershell version 4 means you can do alot without walking into the server room and plugging in a monitor and keyboard.

Now on a desktop this can be frustrating to get used to if you use it for 8 hours a day.

MacOSX left init in 2006 man.

Solaris left Init too. It is gone because it is not adaptive or event driven. This is not just because of performance at startup but because it makes a dynamic environment that respond to events such as a disk failing, hacking attempt, waking up on a different network etc.

In init you need to think of every possible action and every sub action in that action and write complicated scripted to get anything done.

It wasn't a problem in 1985 when RC was new when a Unix server had 50 programs at the most and did 1 thing and stayed in a computer room somewhere. A linux distro or a mac or even a modern server talking to virtualizers and serving traffic with thousands of programs is a different manner

Do not tell IT anything and then blame them and throw them under the bus when it doesn't get done. Give a wonderful Window at 3pm on a Friday for somehting that needs to be ready by Morning. Also having IT management do 15% layoffs each quarter do wonders for morale too

Never invite them to meetings as they are a cost center. Create a culture of constant reminders of this and you will obtain the best and brightest talent

Have you used SystemD?

It is quick and wonderful. Only hate is from trolls who like to start flamewars which he is since he went on about VS and Apple and system administrators who do not want change and have thousand line rc filed which are really programs with logic and data together with nested if/else which reference other scripts in a unholy mess of thousands threads that boot at startup who see nothing wrong with that??

Windows may have it's flaws.

But the kernel is not one of them. I played with a Nokia Windows phone 8 for work on low end hardware where Android would be downright sluggish.

It was fast, bug free, and had no issues or reboots. It is the legacy code and a million services that give it a bad name. Windows 8.1 is a fast quick OS ... but with a terrible gui which is buggy.

In many ways GPL is compared to a more open BSD or MIT.

There's also another bit that I fail to understand.

If the Chinese Firewall guys wanted to DoS github, they could just do it. Playing synthetic traffic against github, for example.
Instead, we say that they hijacked their users computers, so they could generate traffic that in the end would have to go through the firewall.

From the firewall point of view, that wouldn't be a DDoS, because the attacker is always them, no distribution happens. It doesn't make sense, and it's a lot more work than just doing the DoS attack themselves.

Of course, MITM is something they can do, they might be doing that kind of thing, and hijacking clients computers for other reasons, but for this attack, it doesn't make a lot of sense.

Firefox is very outdated.

Chrome and IE (yes IE) have since 2009 used per process for each tab for security and reliability. So you maybe fine if you have 6 tabs. 30 tabs?? One bad javascript and BAM all the rest of the 29 tabs go with it. One malicious javascript in a tab can sniff the others through an exploit too.

So yes Chrome is better just from an architecture point of view.

Firefox is known to have forks in its database stored in your Firefox profile. This means very slow startups too over time. Chrome and IE do not have this issue.

Spartan is a firefox style rewrite similiar to Firefox from Mozilla a decade ago.

The roles have reversed in the browsers.

Google is notorious into making Google HTML 5, not W3C HTML 5 with sites like www.html5test.com which are Google based.

IS MSE part of W3C?

Speaking of this as Firefox was Netscape reborn after a complete rewrite ... Spartan is the Firefox of IE a complete rewrite.

IE/trident desperately needs this.

FYI IE was a great browser in the 1990s. Even IE 6 in 2001 had some bugs but was a decent 2000 era compliant and modernbrowser for its time. IE invented CSS, ajax, dynamic html, etc.

It because very buggy, insecure, extremely outdated, and poorly managed FAST last decade and by 2004 it was a POS compared to Opera and Mozilla (pre Firefox).

Spartan is still behind at 2012 levels but man it works well and is fast and has a future if MS keeps adding features into its new base.

Odd I am routing for Spartan not identifying as webkit.

Reason being is if webmasters only see -webkit they will ignore W3C and Firefox will be toast as websites won't look right.

It will be 2004 all over again with a new IE 6. IE and Firefox are the ones fighting which is strange and so opposite of 10 years ago.