Jason Knight , ah yes, we're talking about different things. I was referring to a terminal software called Hyper (https://hyper.is/). In article I used 'Hyper Terminal' instead of only 'Hyper' so it's misleading. My bad, I'll correct article when I catch some time. But to be honest it's ridiculous that new Hyper is called like that because there already is terminal with basically same name.

Hi Jos Fabre , I briefly covered WSL in this article. I didn't cover it in depth because this is only overview of approaches. I like it too. However since it's still pretty new I'm skeptical about its stability and in some use cases there is more setup then on regular Linux installation. Also, there is no init system so you have to manage processes yourself. If you have complex stack that could lead to complications. Also, if you work on multiple projects where each project has its own strict rules in terms of software stack and versions, then virtual machines are probably better solution since they are easier to manage and distribute in teams.

Jason Knight - 'since if you're making native binaries you are NOT making web applications.' I never mentioned 'making native binaries'. I used term 'running native binaries'. What I meant was instead of running virtual machines and installing dev dependencies there, you could install dependencies directly on Windows. For example if you're a PHP developer you could install Apache, PHP, MySQL directly on Windows and run them as native Windows binaries (or Windows specific term - .exe file). I used term binary because it's more common for Linux and MacOS folks then executable file.

Hi Jason, I recommend that you read this article one more time. There are multiple statements where you can see that I don't mix up terminal and shell as same things. One example: My favorite is Hyper Terminal because I like its cross platform consistency and it looks and "feels" the best. However, since it's Electron app it is a bit slower than the rest. Also, it doesn't come with any sort of Bash emulation shell so it's using Command Prompt out of the box. If you want Bash emulation you can install GitBash and configure Hyper Terminal to use Git Bash shell. Regarding your other point, this article is not a tutorial on "how to do X in Y". It's also not about how to set up specific tools for your specific needs and requirements. It is more general than that and only acts as a starting point for web developers that are coming from Linux and MacOS to Windows 10. I simply cover development environment approaches (Virtual machines with Vagrant, Docker, native binaries on Windows, native binaries on WSL), what do they mean and what are pros and cons. For these folks Windows is not really developer friendly platform since they're used to UNIX-like tools and OS.

Jason Knight You need to be less angry and more constructive. IDEs and editors don't break "good practices" themselves. It takes ones lack of knowledge and experience to break good practices. And FYI "good practice" is a) very broad term and b) it's relative and very volatile term. 10 years ago we had different "good practices" then we have today. Code quality has nothing to do with editor and there's no cheating here. I never seen anybody using Dreamweaver as a tool at professional level. You're totally ignoring IDE's from JetBrains and Microsoft which have a lot of handy stuff. OF COURSE that actual code editing part is the most important aspect of any editor or IDE but having additional tools that are more situational doesn't make IDE's gimmicky (which is basically what you're trying to say). I'm interested to hear other people experiences and preferences but not in your kind of way. Just because your boss (in your words REAL business owner) is giving you shit doesn't give you right to call people fools for having different choice in fucking tool for developing software, especially not somebody experienced who actually tried out a lot of things.

"Anything fancier is typically just covering up for incompetence." This and few other lines are pathetic to hear from a grown up man. Grow up already and stop being a man-child with that "only mine opinion is valid, everybody else are idiots if they don't follow" attitude. There are valid points for and against IDE's or whatever software you like for editing code, but in the end it comes down to personal preferences and specific needs and workflows your projects need. You don't have to be a dick if you don't like something.

Marco Alka Are those figures net or gross salaries?

You have a good point with "right tool for right job" argument against JS. I get the feeling that it's getting forced to use everywhere, anytime. However, there is also one compelling counter argument: it's either JS or nothing at all. For a lot of individuals or small companies (with web development background) it's basically impossible to implement their idea using native technologies. Time and money are 2 major issues to do that. You either need to invest a lot of time to learn things yourself or need to invest in good developer(s) with that kind of specialty which can be expensive, even hard to find. I don't think Slack would exist if they had to build fully native application themselves. So I guess you're right, but I would also add that "good idea implemented okay(ish) is better than good idea not implemented at all" and JS and web technologies enable that today. By "good idea" I would say is something that brings value to users/customers. Edit: and also, while better performance is always welcome, we live in a world of compromises so app developers and their users need to decide when and where performance matter the most. Video games require top notch optimization while some "glorified lists" apps probably don't. So no need to make native app every time. It comes down to requirements, users expectations and available resources.

Linux distros have their own share of problems which don't exist on MacOS. They are mostly related to user experience and software support. My primary OS is Linux Mint and I use it 90% of the time. I had a brief period of using MacOS when I had Macbook Pro in company. Bottom line: I talk from experience not from "shiny ads on TV". So, Linux has easily most terrible Hi-DPI support, even Windows did it much better and is usable in most of cases. MacOS is leading in this, basically almost any app will look good at any high resolution since you can configure scaling at OS level. Try to use FullHD resolution on 13.3'' laptop with Linux, not usable for most of people, and scaling options are really bad. Easiest "solution" is to lower your display resolution which is stupid. So no fix here. Chromium based browsers lack proper support for hardware video decoding. Many video chips (basically ALL Intel integrated graphics used in every ultrabook in last 5 years) are not supported in Chrome so when you watch videos anywhere your CPU will be used for software encoding, although your iGPU has all types of video decoders. That means your CPU will get more load, be hotter, fans go on and battery life is affected. On Windows and MacOS you can watch YouTube videos and listen music for much longer time without high CPU usage and fans turning on, your machine lasts longer and is cold and silent. In order to "fix" this you have to get a custom build of Chromium which enables proper hardware video acceleration. Nothing official yet, although there is a pull request so it could become official in Chromium in the next few months. A lot of software is non existed or lacks features that are implemented on Windows and Macos version. Productivity software like whole Adobe CC suite, Microsoft Office, Google Drive Sync client, proper fully featured Skype that is not web application. Also, there is no alternative to MacOS's Spotlight. Also, there is a whole lot smaller productivity apps related to form filling or smart clipboard history software that MacOS has. And let's not talk about new hardware and drivers compatibility. If you're using Linux it's best to avoid new hardware since there is big chance something won't work properly (be it CPU, GPU, WiFi chip or some external device). It can manifest in subtle but very annoying issues like screen tearing or weird UI stuttering. Yuck. These are important issues that are not resolved on Linux. I have to deal with them on Linux, I have to invest time and effort to fix or research them and spend hours to find proper solution or workaround (if any). In my opinion MacOS is the best OS for developers. Not that you can't work with Linux, but they have old and stupid problems that are affecting almost everyone. It comes down whether you can live with lost hours on debugging and finding fixes. I can so I'm using Linux, but we have to be aware of these thing and criticize them objectively.

You didn't specify what kind of e-commerce website you want. I'll presume it's standard B2C (so basically like stores, you sell your goods to consumers) and in that case I can't agree with the answers. For e-commerce website there is no need to have advanced front-end frameworks like Angular or React. I mean, I don't say that you shouldn't use them, but they have their use cases and you need to know whether they are suitable for what you need. And back-end is almost irrelevant here cause the hardest part is reliable logic. If you expect serious traffic I recommend using some of the industry standards like Magento. Magento is a full blown e-commerce CMS with huge feature list. Everything from login/registration, cart, categories, products, product types, order management, integration with various services, payment gateways etc. It is made with PHP and it is one of the major players in PHP and e-commerce world. There is no need for reinventing the wheel with trending technologies since they all come and go very quickly. E-commerce sites need stability and reliability so go with mature technologies that are still widely used (Java, PHP, C#/ASP.NET etc.). and have rich ecosystems.