71–80 of 138 posts
In place of the "tabview" command (which is a non-standard, pip-installed program) a simple "column -t" would be less trouble for most users.
Learn Just Enough Linux To Make QA, Ops, Security Hate You. Learning to do a thing and learning to do a thing well enough to create a production quality result that isn't a liability to the company are very different. That said, improving Linux knowledge among those who had little/none before is a net win in the long term IMO.
Hey, that's me!
Earlier quoted context omitted.
And git does work on Windows. There's even a windows logo on the official download page. https://www.git-scm.com/downloads
Git for Windows relies pretty heavily on MinGW, though. And it's best used from the included bash shell.
Now typically, when you install MinGW it also installs some tools that let you operate within Windows a little bit more like you're working under Linux, such as by installing a more sane terminal emulator and Windows-compatible ports of some popular programs e.g. grep. But all those tools and such are ports of Linux programs running on Windows, not standard Linux programs running atop a compatibility layer to allow them to work on Windows.
I mention the above because this was an unclear distinction to me originally. Additionally, this was based on my experience with MinGW some five years ago, and I don't know if everything I've described is still true. Hopefully this slight aside clarifies things for someone.
Earlier quoted context omitted.
> Was Linux designed for software development? Linux was designed to emulate Unix and run the pre-existing Unix-like userspace from GNU. And absolutely yes , Unix was "designed" for software development. That's exactly what it was in its early days: a hacker playground for the geeks at Bell Labs to try new ways of doing things. And windows wasn't. Early windows development (for years after it became popular) was done…
> Early windows development (for years after it became popular) was done at a DOS command line ... I could just as easily flip this and claim that Linux development is all backwards because it's still done on the command line. Given Microsoft's commitment to tooling, backwards compatibility and extensive documentation I think it's pretty lame to try and paint windows as not targeted towards developers. The difference…
This is not a surprise - the Windows ecosystem simply wasn't designed with software development in mind. Aha? What is C# and Visual Studio? Or .NET? Was Linux designed for software development? This article is so bad, I'm really getting mad over here. Stop publishing such crap, you feed a lot of people's resentment against all those hipster developers who don't want to learn by RTFM, but want to have handled everythi…
> Was Linux designed for software development? Linux was designed to emulate Unix and run the pre-existing Unix-like userspace from GNU. And absolutely yes , Unix was "designed" for software development. That's exactly what it was in its early days: a hacker playground for the geeks at Bell Labs to try new ways of doing things. And windows wasn't. Early windows development (for years after it became popular) was done…
2 decades and a completely different kernel ago, sure.
Earlier quoted context omitted.
> Was Linux designed for software development? Linux was designed to emulate Unix and run the pre-existing Unix-like userspace from GNU. And absolutely yes , Unix was "designed" for software development. That's exactly what it was in its early days: a hacker playground for the geeks at Bell Labs to try new ways of doing things. And windows wasn't. Early windows development (for years after it became popular) was done…
What?!? Are we talking about Windows 1.0 and 2.0 here? I was using Turbo Pascal and Turbo C++ quite nice IDEs on Windows 3.x. Windows has always been a popular development environment for the demoscene, and games developers. The only alternatives being Mac and Amiga, none of them UNIX friendly.
Surprised to see this on the front page. I agree with most of the feedback and criticism here.
Hopefully some readers found it helpful regardless.
One example of this is the popular version control system (VCS) called git. Developers could have written this software to work on Windows, but they didn't. They wrote it to work on the command line for Linux because it was the ecosystem which already had all the tools they needed. I think the real (and even stronger) reason is that Linus Torvalds specifically built Git to serve as the VCS for the Linux codebase.
>I think the real (and even stronger) reason is that Linus Torvalds specifically built Git to serve as the VCS for the Linux codebase. Mercurial was built for exactly the same reason (VCS for Linux), at the same time. Yet it has always been cross-platform. Linus wrote it for Linux because he didn't care about whether it would work in Windows. No other reason.
Git for Windows and Cygwin Git have some issues (I use them daily at work), but many of these can be entirely attributed to the limitations of Windows: CRLF, case-insensitivity in filesystems, problems with long pathnames, slow process forking, etc.