621–630 of 933 posts
Earlier quoted context omitted.
Confirming you can feed a .sln file to msbuild (I did it the other day), no idea about whether nmake accepts them. Source: https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin3... .
Ah, shit. I couldn't remember if the damn thing was called msbuild or nmake. [0] I guess one should replace all instances of nmake in my comment with msbuild. [0] I do know that they are both parts of the VS build tooling. ;)
My heart skipped a beat when I saw that that ssh is going to be available. And tmux is being worked on! But will I be able to change shells? Will I be able to put zsh with oh-my-zsh on it?
ssh is already available natively if you install msys git
A few random thoughts: - Wow, hell is really freezing over! - The hardest part of running bash and other posix things under windows is filesystem access. Windows uses drive letters and backslashes, unix has a root filesystem with forward slashes. It seems they are taking the same route as cygwin by "mounting" windows drives in /mnt/c (or /cygdrive/c). - If you just wanted bash and some posix tools, the harder but nic…
How do these ubuntu tools interact with the rest of the windows system that they are running on ?
Can I 'kill -9 explorer.exe' ?
Can I touch a file in /mnt/c/(whatever)/Desktop ... and have that file actually show up on my windows desktop ?
Earlier quoted context omitted.
You jest, but I agree. I might accept a GNU/Windows machine as a working computer, but I would be a lot more weary of accepting just a Windows machine.
Would this be possible? How far could anyone (outside of Microsoft) strip down Windows to leave behind just a kernel with a functioning GNU environment (let's say, a shell and file access) ?
I have successfully installed KDE on this (via Cygwin plus a mesa/llvmpipe build of opengl32.dll). It seemed to work OK.
Earlier quoted context omitted.
Yea, I think they are going after developers who use OS X because it is UNIXy. Smart move given how en vogue Apple laptops have become for developers these days.
>Yea, I think they are going after developers who use OS X because it is UNIXy It's a bit more than UNIXy, (the proper term is Unix-like), it literally is UNIX. It meets the UNIX 03 specifications . Also, the motivations for these move predate the rise in popularity of Apple. For years, one of the biggest complaints about Windows was the lack of a good command line interface. There was the legacy CMD.EXE, which provi…
Err. As a Mac user from when system 7 was fancy looking, and who learned some basic bash in order to do useful stuff like use curl, grep, cat, ls > .txt, rm's based on partial name matches, etc. my only response is "How about we talk about it over breakfast, lunch, and dinner?"
Bash is simultaneously graceful and nimble, yet clumsy. While it's certainly appropriate to worry that any reduction of the clumsy side would have a net negative effect, to not see, or not ack the many issues just continues to deny its utility to non-expert users.
Earlier quoted context omitted.
They'd laugh, because NT already had posix system calls http://social.technet.microsoft.com/wiki/contents/articles/1...
POSIX calls, which have always been there but require a recompiled binary, are different than the binary compatibility announced today. This additional step is actually quite an impressive feat of software engineering. To think that Microsoft would care so much about maintaining compatibility would have seemed ridiculous just a few years ago.
Earlier quoted context omitted.
Or you could just use ubuntu... It amazes me that people will rag on linux because its "hard" and then build these elaborate Rube-Goldberg machines to avoid the most obvious solution.
> It amazes me that people will rag on linux because its "hard" and then build these elaborate Rube-Goldberg machines to avoid the most obvious solution. It amazes that people don't understand that one's usage patterns might be different, so "just use Ubuntu" wouldn't be applicable (e.g. UNIX savvy guy who appreciates the shells and userland, but nevertheless wants to do Windows .NET development, or work with native…
All the yakka spent on avoiding the obvious solutions to justify "usage patterns", should signal any half-aware dev that those precious patterns are broken.
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.
Earlier quoted context omitted.
I've been "stuck" with a 2010 Macbook since Apple isn't refreshing it's laptop hardware soon enough. Plus I'm sick of soldered in RAM and other BS. For devs that do heavy Linux work (but have stuck with a Mac OS for GUI/app reasons), is it time to move (back) to Windows? If so, what would be a good laptop to get at the moment?
Go to a brick and mortar electronics store, pick out a laptop that meets your desired specs, and do something realistic with it for a while. There are lots of little things I took for granted about Apple MacBooks that no Windows laptops could match. Touch pad, high dpi display, and cooling were never quite done right, but they are crucial for every day operations.
I'm surprised to hear someone preferring macbooks cooling though, my macbook always gets so hot relative to other laptops