Live data from Hacker News

Ubuntu on Windows

blog.dustinkirkland.com

671–680 of 933 posts

Re: Ubuntu on Windows

#671
post #233

Surprised I don't see anyone else mentioning this. This looks to me like typical Microsoft strategy that they utilized a lot 25 years ago. 1. when not leader in given market, make your product fully compatible with competitor 2. start gaining momentum (e.g. why should I use Linux, when on Windows I can run both Linux and Windows applications) 3. once becoming leader break up compatibility 4. rinse and repeat Happened…

Could you name a single company that doesn't follow where the market is and try to monopolises it later? Plus, Windows is still the leader in the desktop and laptop market until today. They are facing some tough competition but "not leader in given market" is not true.

> Could you name a single company that doesn't follow where the market is and try to monopolises it later?

I think your argument actually supports parent's position, so this "plus" in the next sentence seems out of place :)

Re: Ubuntu on Windows

#672
post #233

Surprised I don't see anyone else mentioning this. This looks to me like typical Microsoft strategy that they utilized a lot 25 years ago. 1. when not leader in given market, make your product fully compatible with competitor 2. start gaining momentum (e.g. why should I use Linux, when on Windows I can run both Linux and Windows applications) 3. once becoming leader break up compatibility 4. rinse and repeat Happened…

I wonder how they are going to work ads into the command line?

I thought everybody has seen this "vi assistant" gif by now...

Re: Ubuntu on Windows

#675
post #233

Surprised I don't see anyone else mentioning this. This looks to me like typical Microsoft strategy that they utilized a lot 25 years ago. 1. when not leader in given market, make your product fully compatible with competitor 2. start gaining momentum (e.g. why should I use Linux, when on Windows I can run both Linux and Windows applications) 3. once becoming leader break up compatibility 4. rinse and repeat Happened…

It's called "Embrace, Extend, Extinguish".

They also tried to do this with Java, but people were alert.

Re: Ubuntu on Windows

#676
post #244

Earlier quoted context omitted.

> I grew up a Windows user, and switched to OS X because of the unix-like command line environment that more closely matched the servers I was working with in my job environments. Out of curiosity, why would you not just go with a Linux desktop for that?

Linux on the desktop is awful, and anyone who says otherwise is in denial.

That being the opposite of my experience. While we're making bland sweeping gestures, I have been having it easy developing on Linux (specifically Bodhi with Moksha DE) while fixing my partner's Windows PC every week because it fails constantly. Hell, Windows can't seem to go from location A to B and change networks without a meltdown. It's an awful OS with awful usability, a file explorer that is awful to use and a file system that makes development feel like physical pain.

There, now we're even. Let's get back to EEE, and the real porblems and advantages with this news.

Re: Ubuntu on Windows

#677

  A team of sharp developers at Microsoft has been hard at work adapting some 
  Microsoft research technology to basically perform real time translation of 
  Linux syscalls into Windows OS syscalls.  Linux geeks can think of it 
  sort of the inverse of "wine" -- Ubuntu binaries running natively in 
  Windows.  Microsoft calls it their "Windows Subsystem for Linux".
Sounds a lot like Rosetta [0], which Apple used to transition people from PowerPC to Intel.

   --- 
[0]: https://en.wikipedia.org/wiki/Rosetta_(software)

Re: Ubuntu on Windows

#678
post #233

Surprised I don't see anyone else mentioning this. This looks to me like typical Microsoft strategy that they utilized a lot 25 years ago. 1. when not leader in given market, make your product fully compatible with competitor 2. start gaining momentum (e.g. why should I use Linux, when on Windows I can run both Linux and Windows applications) 3. once becoming leader break up compatibility 4. rinse and repeat Happened…

HN had a huge influx of developers who predominately (or only) work on the Microsoft platform, and it has been readily apparent in the stories that rise to the top, and the dominant reactions (e.g. cynical takes are quickly transparent. Exaggerated "this changes everything!" comments rise to the top). This isn't necessarily a bad thing, but it does heavily slant the coverage and slant of the conversation. And as you…

Only that all big Software or hardware companies do this... Apple keeps the doors closed to anything not in their full control, nvidia was pushing for open standards when they were the underdogs and now they have a lot of proprietary stuff, Google with Gtalk/Jabber etc etc. It's pretty ignorant to only paint MS that way imo. I also believe MS is a very different company today with a different strategy because they lost mobile. Maybe that changes again in the future but i worry a lot more about the direction apple is going.

Re: Ubuntu on Windows

#679

Earlier quoted context omitted.

Let's be honest here. Does this change make some developers actually even consider to change their OS X/Linux Desktops to Windows? Yeah it is really cool thing that we can finally use windows cmd like the terminal on unix systems however: - 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…

Data point: On Windows when you run 'npm install' on a react boilerplate/starter project chances are 50/50 that it will work out of the box. A year ago it was way worse. I thought heavily on switching to Mac for no other reason but 'npm install' success rate on Windows.

Honestly it's not much better on OS X. The solution to failed npm installs is to keep running npm install until it works. If that doesn't work after about 6 times, wipe out node_modules dir and try again. Npm got lots of laughs at EmberConf this week. Everyone hates it but we all use it because it's what everyone uses.

Re: Ubuntu on Windows

#680
post #378

Earlier quoted context omitted.

And you can also use forward slashes. I've used them in applications (Java apps, NodeJS apps, etc) and in the command line since at least Windows 7.

The forward slash (/) as a directory separator has always been acceptable to NT. One source says that it's been acceptable to DOS since DOS 2.0, although I don't have a lot of backing on that. The only place that / as a directory separator doesn't work is when interpreted by cmd, as it's then ambiguous with DOS-style switches. And even then, modern cmd tries to understand / properly when possible. Most of the time it…

> One source says that it's been acceptable to DOS since DOS 2.0

I can confirm that from personal memory.

At the time, the biggest vendor of UNIX-like systems was Microsoft (Xenix), so compatibility was a benefit. They soon sold that product off, though.

Post reply on HN