[1] http://www.slideshare.net/bcantrill/illumos-lx
[2] http://us-east.manta.joyent.com/patrick.mooney/public/talks/...
[1] http://www.slideshare.net/bcantrill/illumos-lx
[2] http://us-east.manta.joyent.com/patrick.mooney/public/talks/...
- What about lack of all the Linux/OS X GUI software?
- What about lack of all the UNIX OS features?
- What about all those billions and billions of Windows malware, viruses, adware etc.
- What about all the spying and restrictions that Microsoft has integrated into the Windows? (e.g. cannot block Microsoft spy server in the hosts-file, forced updates etc.)
- What about the fact that OS X and Linux have always been at least decent from developers point of view but Windows has always had problems and then things like Vista and Win8 happen.
- What about the advertisements served to you in the login screen?
- What about all the future shit MS will throw at you?
- Other stuff can't remember now
If and IF this will actually work out well, I would say this finally makes Windows usable for software development however I don't see any reason why anyone would change from UNIX based system to Windows unless they plan to make even bigger changes in the future...( like rewriting whole Windows to be UNIX based for example. :) )
I'm someone who doggedly persisted trying to dev on my windows box because the stability, speed, app support, GUI niceness of windows is just far superior to Ubuntu (I won't speak to OS X since I've only done minimal dev on it). I won't go into a lengthy defense of this claim - but will if pressed.
I put up with all the failed python module installations - the hunting around for the right VisualStudio compiler... the 64bit python install issues... on and on... I put up with it all... only to be defeated in the end by various node modules failing to install because they use ridiculous depth in their directory file structure that the windows filesystem can't handle. Our projected needed those dependencies. Something had to give.
So I tried vagrant VM with virtualbox - and shared folders... so I could keep my windows GUIs without needing to sshing everything to the VM. Somehow - even though the shared folders thing means the VM is ultimately using the windows filesystem - the node modules would install okay. BUt then I had problems with symlinks (which was solveable with effort)... But the worst thing was that various files, and sometimes whole directories would randomly have their permissions changed inextricably such that NO ONE - not even an admin user could touch them. The VM would get locked out, I would get locked out... it was horrid. It happened in the middle of a rebase once. Sad times... Sad... sad times.
So - I ditched vagrant and shared folders and use a totally contained VM with the ubuntu GUI... it's slow and horrid and it makes me cry... but at least I can alt-tab and waste time in a browser in the windows GUI if I want to.
So anyhoo - my concern. This approach by MS is going to mean everything plays with the same windows file-structure yeah? Or does the ubuntu thing get it's own self contained filey-bits to play with?
Cause if the former... then I will have the fear... THE FEAR... when I try to use it.
Is it really that bad? At one former job I ran Ubuntu under VirtualBox with guest additions installed (new Linux team in an old MS shop).
Performance was OK, at least for the things I used - terminals, vim, Firefox. The only thing that really annoyed me in this setup was the need to switch between the VM and Outlook every now and then. Fortunately, Outlook's notifications worked even in VM running fullscreen (IIRC).
I was going to agree with you and admit I was being melodramatic...(well - I mean, saying that it makes me cry was certainly melodramatic - I don't really), but y'know what... it's definitely not ideal.
e.g. Scrolling in my ide.. sometimes lines of code don't refresh properly until I scroll back and forward a few times.
And with dev server, webpack watchers, test watchers open plus browser with a few tabs... yeah - it can get pretty sluggish. Maybe I'll try throwing a few more gig ram at the VM.