In my experience Cygwin works better for the "compile software targeted mostly at Linux users" use case, but Microsoft definitely pursued the "make Windows a Unix" approach. Sadly Interix saw limited adoption (probably due to pricing) and has been discontinued, so we're left with the user-space emulation approaches (like Cygwin).
cygiwn is one of the first thing i install when I bring up a new windows box.
Modifying Windows to be administrable through a POSIX shell would change what Windows fundamentally is. I'm not sure that's a great idea.
Personally, I enjoy working with Powershell much more than I enjoy working with Linux in the traditional way (through a shell), and I currently don't personally own a Windows machine.
I don't think a shell is a very good interface for direct use; it's entirely non-discoverable past man pages. It's a great interface for developing reusable tools, though. I strongly dislike having to use it directly, preferring to develop scripts that I can access from my text editor.
As a developer, I think what you want from a shell is different from what a Windows admin wants from their shell. The Windows admin wants to manage the services they have installed; the developer wants to manage whatever files they have in their source tree. I don't think it's particularly terrible that Windows should be bundled with a tool for administrating Windows, rather than a tool for developing new software.
I would buy it, if these criterias were met:
1) I can install an unpopular Linux distro onto it (NO VM!).
2) I won't get serious issues on Linux, due to no drivers being found compatible, overheating, hybrid-gpu switching problems, touchscreen issues, jumping stylus, battery dead in <3h
3) UEFI isn't causing as much trouble, as I've heard.
4) The keyboard is much better than the crappy colored plastic it looks like. I want a high quality keyboard with backlight. I would pay $200 extra for that.
5) It has HDMI, USB3 and a way to increase the internal storage and ram.
@smrtinsertShould, would, could. But they didn't, for about two centuries, sorry シ There is so much hope in your writing, hope that Microsoft recognizes where it erred and where it did it right. Alas, there might be no such plan, because they haven't found a way to directly capitalize on that yet, or political/strategical/management reasons.
I don't have any prejudices against Windows, OSX, Linux, BSD and alternative OS users, but I like all of them. What makes me and probably others turn off the ears are hardcore evangelists of any kind just as well as fanboys/fangirls. This is not directed to you, you're ok check ✊ . I just want to say that, there are such people whom you can innocently ask, why they've installed Windows onto their Mac (for example) and all you get is arrogance and hatred plus a bunch of prejudices on how one can question the superiority of windows. On another case I talked with a Windows Phone developer and she was such a hard knock evangelist, I was kinda feeling attacked, just because I asked how she plans on integrating with the back-end software we've developed to deploy the final app to various app stores.
I found it pretty easy to put Linux on my Surface Pro 2. The problem is that once it's on there, it kind of sucks. Poor hardware support, extremely poor touchscreen UI.
Is it possible to still install Ubuntu through the Windows Installer?
http://www.gnu.org/licenses/gpl-faq.html#MereAggregation
You can even ship it with a proprietary installer.
It still seems that you can't for instance launch an executable that runs cigwin in the background.
[citation needed]
The corporate lawyers that I've talked to at my previous day jobs have told me that this is an obviously legal thing to do.
How does bundling mean combining it into an _executable_ file? Sure, this could be the case for an installer, but that one could also just download/copy the files.
"If the modules are included in the same executable file, they are definitely combined in one program."
Piping programs into each other is okay, but once you start bundling it's all up in the air.
The example of an installer can't be more unambiguous. I quote "No. The installer and the files it installs are separate works. As a result, the terms of the GPL do not apply to the installation software." No. Full-stop. GPL does not apply.
If an installer of GPL software doesn't have to be GPL then certainly unrelated software which happens to come in same disk/download doesn't have to be.
I believe Task Manager eschews the common control library and reimplements a lot of UI stuff itself. Same reason.
It puts you straight into processes tab and can be done with one hand.
I went looking for the source but I only found this blog post from Raymond Chen [1]. Based on that discussion, it looks like winlogon.exe is responsible for launching the Task Manager both ways, so perhaps that more recent discussion was incorrect.
[1] http://blogs.msdn.com/b/oldnewthing/archive/2012/01/30/10261...
Now, once you've got ConEmu or something like it that will resize nicely and do other things, you'll still be stuck on the crappy DOS-style prompt though. :)
If I'm using a non-built-in terminal, and a non-built-in Unix compatibility layer, why am I using Windows?
My point, perhaps poorly stated, was this: I prefer a terminal-heavy development environment because that is the most efficient way of interacting with remote servers for the work that I do. I can't consider using Windows without a sense that they've made it a priority to address my use cases and scenarios, and the single lowest hanging fruit possible in that regard is to spend half a dev team (2-3 devs) on modernizing the terminal to the point where when I'm at home and want to check something on a server, I use my Windows desktop instead of switching to my Mac laptop. Even better would be dedicating one or two dev teams to supporting a Unix environment natively, so Cygwin isn't necessary.
For what it's worth, I much prefer the Windows GUI to either Mac or Linux. I was a test developer at Microsoft for Windows 7 and part of 8, and I wrote this comment on my home PC running Win7. I would like to be able to use Windows for the UI and the familiarity I have with it, but those two things, a good terminal and a Unix-like environment, are requirements for my job. And I know from experience that this scenario is absolutely the furthest thing from the minds of the people working on Windows.
Also Powershell is pretty awesome if you take the time out to learn it.
Anyone know why that is?
There is even project to bring ConEmu + Far Manager, and there is even way to make Far Manager work with cygwin's bash (I have separate link for it).
Give it a try - it's zip-installable, and has real installer too. Lots of plugins (including zip browser, exe browsers, ftp/ssh/etc.)
If they haven't managed to fix some of the most basic and most user-visible flaws in the past decade or more, what other cruft is lurking in places users don't regularly see? Additionally, as a software professional myself I see a whole lot more of the ugliness under the hood than most users and it does nothing to suggest to me that my first impression was wrong.
Edited to add: I know you didn't actually disagree, and your suggestion is a good one. I felt it would be taken by many as a reason to discount the original opinion though, and wanted to emphasize what I feel to be the more important aspect of the original notion.
At work I'm stuck with Windows, but at home use OSX & croutonized debianized chromebooks.
In my regular Windows toolbox are: Far manager, cygwin (full install), SysInternals, NirTools, Windows 8 SDK/DDK, emacs-win, but haven't time to get around and learn Powershell...
I do agree with the core of your point though; an actual terminal with actual commands that actually work well would be great.
Windows Powershell is actually really fascinating from one point of view though: the idea that instead of passing raw (inconsistently formatted) ASCII/Unicode data between pipes, the data is actually presented in terms of a data structure; thus you can easily say 'sort by the third column descending' or 'show every second record'. A significant amount of my bash scripting on-the-fly tends to be chaining several commands together to munge output data solely for the purpose of letting the next command parse it properly. Powershell, in some ways, takes care of this.
I never understood why some people make such a big fuss out of it.
Sometimes you need to change your prompt to be a different size and an annoying 5 step thing is a big fuss
You can thank me later.
Should be fairly easy to script deploying that to all your machines.
I expect Microsoft's partners will increasingly continue to push other operating systems into the market on their devices, even if initially it's not exactly what the market wants. But they will do it anyway, because they will increasingly hate Microsoft.
And it will work, because the PC ecosystem is much bigger than Microsoft, and Microsoft won't succeed fighting against it. They will lose more money from lost licenses than they will be making (in profit, since so far Surfaces have continued to lose them money) than they will be making from these devices.
There could be a multi-part strategy. Both Google & Microsoft probably covet the revenue and margins Apple received from selling their own devices. Those margins, in terms of phones and tablets are probably un-repeatable. Some next iteration of device however could contain offer big margins. That is something that could double Google's market capitalization. At the least Microsoft and Google understand that they need something to give them hardware experience.
Second, it allows Google & Microsoft to lead in hardware. Even if the Surface 3 flops, the OEMs have a guide pointing what is possible and which direction to go (or not to.) I imagined this was part of the reason why Google has had different manufacturers built their Nexus products.
The Surface buys Microsoft some time. The number of people who need Office and legacy systems is going to continue to shrink as special use case stuff is built -- whether from the analytical side like Tableau to something like FarmLogs. The operating system itself may very vanish in to the background, leaving us with some unix-based combination of Android and Chrome OS.
I use a virtual machine running Windows to take care of software my Mac won't run natively. I could just as easily run Linux or BSD in a virtual machine on a Windows box. Or even OS X, if I were in a EULA-violating mood.
Because I currently work mostly on the command-line, having a rich command-line environment with access to a powerful shell and great tools is really important to me, and I wouldn't want that to be restricted to a VM.
Moving back and forth between working on the same codebase on both the Mac and Windows sides is also a little irritating; I find the best way to do this is pumping the data back and forth between them using Git. But that would be what I have to do if they were separate physical machines, too, so I'm not terribly prepared to whine about it.
In terms of architecture, Windows is a VMS descendent and although there have been multiple UNIX compatibility layers, both from Microsoft and third parties, very few people really cared about it. As of Windows 8, Microsoft killed their own implementation and is pointing people to Cygwin.
Not really. It's much easier to port Unix-native applications to a Mac than it is to port them to Windows. Most of the time, everything just seamlessly compiles on OSX (even if they may need X to run). Also, being "closer" to the environment the app will actually run is a great feature.
Microsoft's strategy has always been to make it easy to port other apps to Windows (offering POSIX services since ever) but to make it as difficult as possible to port away Windows apps. Offering a full-featured Unix environment would go against that.
This article covers some of the Apple internal history of iOS
Of course the app store revenues don't hurt, but at the most basic level they don't want the user to screw up the 'it just works-nesss' of it.
I still use a Mac but i don't use any OSX specific software apart from some small tools which i could easily replace on other OSes.
Just a note, if you have VirtualBox or VMWare installed and you go to enable HyperV (on Win8), you may get a BSoD.
i will eat my hat if you open vim in OSX and be able to copy/paste. The + register just goes to nowhere. OS X is broken unix.
windows sucks in many regards, but it always had million more devs than OSX... i know implementing fixes on top of windows goes against the free software philosophy, but there are already too many. I can run remote X apps from another box easier on windows than OS X.
The only leverage apple ever had was IOS. you are forbidden by law to emulate IOS or OSX on any non-apple hardware. so people started to be forced to use macs. it wasn't natural adoption. And IOS is only relevant while we have dumbed down smart phones. Now that this became a standard tabled (a full computer, that you can run windows or even install linux) IOS will lose appeal, and apple will be sidelined to the history of computer history as it always manages to get it self into.
downvote with all the hate you want. you know it to be true :)
UNIX is a separate standard from X. IMO part of really appreciating UNIX is appreciating what is part of UNIX and what sits on top of it. I think that most server-side UNIX installs have a "broken" clipboard in vim too.
The standard distribution of vim includes integration with X11 and Windows, and that's where console vim on linux gets its clipboard from. MacVim on OS X integrates with OS X and I just fired up the console vim and saw that the "+y and "+p use the Mac clipboard.
Unfortunately, I don't think Microsoft will convert many OS X devs unless they make some changes to their software. One of the advantages of OS X is that it's a Unix, and lots of Unix software runs on it. It's not hard to compile tools such as nmap, Vim, or steam locomotive.
It would be very interesting if Microsoft made Windows a Unix. They could bundle bash or zsh, add the typical BSD tools, and (most importantly) build a cc front-end for the Visual Studio compiler. They'd also have to ship a libc of their own. To save effort, they could base it on BSD's libc. It'd be like Cygwin, but installed by default and officially supported and maintained.
With such a set-up, you'd be able to run your unix tools alongside Adobe CS and Outlook. You wouldn't have to worry about driver support, since Microsoft made the hardware and the OS (just like Apple). The only thing missing would be the ability to dual-boot OS X (to test on Safari or other OS X stuff).