Hacker News Reader

Comment by jameslk | Hacker News Reader

I keeping hearing the narrative from this crowd that the MBP is on its way out of being in vogue for developers, but I don't buy it at all.

First of all, this is market share up to the release of the new MBP. It's not surprising that their market share has been slipping given that up to this point they haven't released a significant update to the MBP since 2013.

But getting to the point, the Mac ecosystem is now ingrained into open source development. Believe me I used to use a PC not too long ago and nothing would work because OS software is designed to run on top of a NIX environment. I recently had to go through this exercise with a colleague who was in denial. But over time, it ends up the same: software built to run on Linux servers runs best under an environment that is designed more like Linux. He now owns a MBP.

So Windows is out (for non .NET devs). That leaves us with what, Linux itself as the OS? Anyone who suggests doing this either hasn't done it before or has way too much time on their hands. I use macOS because I don't have time to hunt for drivers, trying to understand an obscure error discussed in a long forum thread or having all my software no longer work just because I updated a package. I've already tried that twice once with Gentoo and then with Ubuntu years later hoping it would be different. I know plenty of others who have as well. Ultimately we have jobs and we need to debug our own software.

Which brings us back to the Mac. I fully expect this release to be their Windows 8 moment, a beta event from which they will recover from given time for hardware to catch up. Not every release can be a stellar event. Give it time.

View on HN

> the Mac ecosystem is now ingrained into open source development.

Interesting...

> Anyone who suggests doing this either hasn't done it before or has way too much time on their hands.

Oh...

Quick question, when was the last time you did it?

Currently I have three full time Linux boxes:

* Custom PC build I did myself

* System76 Galago UltraPro

* Dell XPS 13 Developer Edition

Oddly enough, the one that gave me the most issues was the Dell supported XPS 13 DE but I didn't have to do a thing, just waited for driver updates from Dell which I could install via:

> sudo apt-get update

> sudo apt-get upgrade

But at the end of it I have a Linux laptop with premium build quality, 8 hour battery life (with 4K screen), and an external battery pack that easily extends my battery to a full day of work before needing an outlet.

My company gave me a Mac, but literally every other computer I personally own, right down to the Dell T710 server I have is running Linux (Ubuntu 14.04.3 specifically) without issue.

I don't expect Linux to take over the Desktop market. But for Developers I see the current MBP as just another reason to seriously consider just getting a Linux laptop from an OEM like Dell or a niche player like System76.

Let's face it, this MBP just highlights the fact that its target market is not developers or power users. Which is fine, and it probably can be a successful product with or without us...

> Quick question, when was the last time you did it?

Gentoo was circa 2005 and Ubuntu was circa 2012. I spent months trying to make it work, but it was too much. Software ran slower, installing package updates was like playing Minesweeper and worst of all, I had to use Wine. A friend of mine tried it as recently as 2014, then gave up as expected.

> Currently I have three full time Linux boxes:

I'm glad it works for you. Maybe you have more experience with Linux than I? Or maybe more patience? Or time? Or maybe I'm wrong? Regardless, for my multiple attempts over the course of months trying to make it work, I couldn't stand it. I'm sure others can and I would encourage them to try, at the very least just for the experience.

> Let's face it, this MBP just highlights the fact that its target market is not developers or power users.

That may be your opinion. Time will tell if its a trend. Given the way things stand today, I don't really see it being the case, at least in the short term. I'm waiting for the next release.

> Gentoo was circa 2005 and Ubuntu was circa 2012. I spent months trying to make it work, but it was too much. Software ran slower, installing package updates was like playing Minesweeper and worst of all, I had to use Wine. A friend of mine tried it as recently as 2014, then gave up as expected.

Ah cool! The reason I asked is that a lot has changed in the last four years or so. Dell's Sputnik (http://www.dell.com/developers) program is the one that specifically comes to my mind. But it is possible to buy a variety of Dell workstation models with Linux pre-installed with support. And according to the recent new product blog (https://bartongeorge.io/2017/01/09/welcome-the-new-ubuntu-ba...) the Sputnik project only released the first 13" DE a little less than 4 years ago.

So I was asking since I thought it might be neat to know about some of the changes in the landscape (provided you haven't attempted in a while :) ...)

Edit: Forgot to mention, that Dell's efforts generally improve the Linux driver ecosystem as well since they upstream their drivers to the kernel:

> as many drivers developed for the laptop are "upstreamed" to the Linux kernel [1]

[1] http://www.infoworld.com/article/3046115/linux/love-linux-du...

You're right, I haven't tried it recently since it became the norm for OEMs to release computers pre-loaded with Linux. Once bitten, twice shy as they say.

Installing Linux distros were only half the battle for me however. Maybe that's changed too or maybe it was because I was always trying to force everything to run on top of KDE. I'll definitely keep an eye on this development, but my expectations are that it won't change the landscape much. Who knows.

Totally fair, I myself only recently gave Linux on the laptop a try again (last 2 years or so). For a long time I had limited Linux to desktop use, but was pleasantly surprised by System76 and Dell so I feel compelled to spread the word.

At any rate, as I say in another comment, there are definitely many other things that might dissuade you from going the Linux route (gaming being my personal challenge). I was just trying to comment on the massive improvement in the driver space in recent years.

> Maybe you have more experience with Linux than I? Or maybe more patience? Or time? Or maybe I'm wrong? Regardless, for my multiple attempts over the course of months trying to make it work, I couldn't stand it.

Or... maybe different expectations? I never had audio 'just work' on various linux laptops from 2002-2008. Playing some music (amarok, whatever), then the IM client (pidgin or whatever) would make a ping, and ... music would stop. Not possible to play again until killing IM client. Oh wait... dude, don't use pulse! Use ALSA! No, wait... use the latest dev build of pulse! just upgrade your entire system! No... dude, just grab a binary from this site...

Holy crap, you want to plug in an external monitor? xrandr, kxrandr, go edit config files, install some new Xorg libs, etc.

Coming from that world, the Macbook world "just works". Yes, it's gotten a bit worse over time (2016 letdowns, etc). But I still have colleagues who spend far too much time making basic stuff work in various linuxes.

This is normally the point in the story where people either say "you did it wrong" or "yeah, dude, i feel your pain - it used to be bad, but... ubuntu 'just works' and is great now'. Trouble is, I heard that years ago too ("hey yeah, it used to suck, but it's better now") and... it wasn't any better. After going through various laptops (cheap and expensive) never having a decent "just works" experience (out of the box: printer, wifi, external monitor, audio in/out, playing dvd movies and writing to dvd all just working)... I gave up.

For people with different expectations (thinking that rebooting your session to edit an Xconfig file to get multi monitor support is acceptable, for example), they'll never believe there's anything wrong.

The second you compile one package to get any of those boxes to work, for me, the pro-linux box argument is negated. Particularly for work machines, I don't have time to compile and install just to get my box up and running. Mac worked for me for this reason, I presume the reasons are the same for many. You like the freedom and power your boxes allot you, I like the simple operation of the mac. My problem is Macs are quickly becoming more work with all of there services and issues. When I start having to search for drivers online I might consider switching to Linux, but this won't be a cure all, because I deal too much in graphics.

I guess I implied it in my comment, but I'll explicitly say it here:

> I did not search for, manually install, or otherwise fiddle with drivers for any of my current 3 personal machines.

I have done so many times in the past, but not for these three[1].

This is particularly true for the System76 which not only had drivers pre-installed and the repository configured, but also had no issues out of the box...or ever in my case.

Dell had the drivers installed and the repo pre-configured...but out of the box there were some bugs in various drivers at release...but again for me it was a matter of waiting for a fix and just doing a regular `apt-get` update process...none of the typical online support forum crawling I typically am used to.

Don't get me wrong, there are many other things that might dissuade you from going the Linux route, but driver headaches of old are largely gone, especially if you get a laptop/desktop with OEM support.

[1] Aside for the aforementioned `update` and `upgrade` combination using the `apt-get` packaging system...but the relevant repositories were already configured (or configured automatically as is the case for custom build).

My machine wouldn't boot anymore because I followed apt's suggestion to run apt-get autoremove.

There are many packages and apps out there that get released but are far from stable, and no easy way for non-devs (as in Linux devs) to opt out of unstable software.

I don't charge a crazy amount of money, but 2 hours are a long time to waste for a developer, and I've wasted many times that with Xenial. That, while being someone used to using the terminal and installing and configuring server software on a daily basis.

Xubuntu is now my first choice operating system. I have it on 2 desktops (one Dell for work and my home desktop). It also works great on an old Lenovo X-series and a Dell latitude. I can honestly say that the one machine I need to keep Windows 10 on for work causes me hours more grief than my Ubuntu-based machines.

For me, the biggest annoyance is having Office365 at work and not being able to use things like Skype etc natively. The web apps are OK and I mostly don't notice, but there are times I wish Ubuntu got the kind of software support from MS that macOS has.

> The second you compile one package to get any of those boxes to work, for me, the pro-linux box argument is negated.

This seems a strange things to say considering everyone I know who uses a Mac for dev uses homebrew, which compiles as part of the install.

Homebrew tries to download a binary for pretty much every package, and only rarely compiles from source.

True. It used to be like that at the beginning, but now it's rare.

The "to get any of those boxes to work" part is, I think, the key part of that quoted statement. Homebrew may compile things (if there is no binary download available), but you don't need Homebrew to make your Mac functional.

I just switched from Macs to a Fedora desktop and never compiled anything. Maybe I've been lucky, but my Lenovo and Dell desktops and my old IBM and new Asus laptops run with no issues.

I'm capable of solving most linux driver issues, but I've been pretty impressed that I haven't needed to during my switch. Again, maybe I've been lucky.

I was a little disappointed that installing nodejs requires a magic shell script but it didn't require any effort on my part beyond setting similar things up on Mac with Brew (or Brew itself) Otherwise, Fedora's app store has covered my needs. That said, I don't do any graphics work, so maybe you're going to run in to issue I haven't.

I have spent more time dealing with compiling from the source and handling weird package interactions on osx than on any linux system I've used recently. At least the Linux system will come with a standard package manager that supports major developer tools.

> I fully expect this release to be their Windows 8 moment

I get what you are saying and somewhat agree that naysayers are an overly represented demographically.... but...

Apple has for 5 years been operating without strong direction. By many accounts it appears to be flailing, simply living off it's cache and tech R+D created from the 3 decades of Job's rule.

It's clear Apple still makes the best hardware so that isn't in question. I do question, how they intend to stop the slow drain of talent from the company and users. They aren't supporting pros the way they did in the 80s 90s and 2000s. All the pros in movies, music, and graphic design used to use Macs. With the introduction of OS X programmers had a home. That was a strong component for influencing their coolness factor. No more. Apple alienated all of them with expensive outdated options like trashcan Mac Pro, and overly expensive unjustified new MBP. Logic isn't keeping up, FCP isn't keeping up, hardware specs aren't keeping up. iCloud is limited and isn't keeping up.

This isn't a Windows 8 moment, this a late Windows XP moment. There is a slow drain that has started. We are approaching Windows Vista when everyone really gets turned off by how broken and discombobulated every product and service gets with the current lack of strong leadership.

I do question, how they intend to stop the slow drain of talent from the company and users. They aren't supporting pros the way they did in the 80s 90s and 2000s...That was a strong component for influencing their coolness factor.

It used to be that creators doing cool things on macs was a chief driver of the Mac image. Now it seems more like it's wannabes and douchebags latching onto this former cool image, taking over as the chief drivers of image.

I find myself increasingly disenchanted with Apple's products. The removal of the iPhone7 headphone jack was an absolute disaster from my perspective.

The new MBPs with their 16GB memory limit, their removal of the esc key, and their useless touch bar, all have me looking enviously to other hardware platforms.

Recently, I tried to burn a DVD on my iMac running Sierra using the built-in Disk Utility. Apparently, Apple ripped out the DVD burning feature in that app because they're moving away from having an optical drive in all their newer products. Please don't compare the elimination of the optical drive to the elimination of the floppy on the original iMac. The floppy had one use, and Apple was boldly showing us we could do without it. DVDs, CDs, and Blu-Ray have other uses beyond just software and application data. They're still all over our consumer electronics and need to be supported as first-class citizens on a computer that attempts to be so media friendly otherwise.

To me, this is starting to feel like Apple felt in the early 1990's when their leadership appeared to be lost. I'm not optimistic that they're going to start making the sequence of good decisions that they'd need to in order to regain my personal trust in their products.

Great point. I recently bought the new MBP with Touchbar and was hesitant for the myriad reasons that were previously mentioned.

Before I pulled the trigger I went to setup my dev environment on a fresh Linux partition at home (mainly a windows machine). I was fighting things all over the place to get it to a state of usefulness and productivity. I spent too much time doing this and still kept running into little issues here and there when needing to install certain things, run particular apps, and getting to switch over to a different workflow. I couldn't afford wasting this much time in the office.

I ordered up the new MBP, installed everything, setup time machine, and bam within a few moments and pulls, npm commands, etc I was fully functional. Very little issues and it felt incredibly good. My biggest gripe was ordering a few adapters but now that doesn't pose any more issues to me.

I will disagree because difficulty of dev env setup highly depends on dev stack and most of them are easier to configure on linux. First of all on Linux you have to know what you are doing. Linux is first and foremost a system build by sysadmins for sysadmins. Of course a lot of stuff was done by developers but to properly manage dev environment installed on linux you have to be at least partially sysadmin. If you are looking to install full dev stack as all in one package then look elsewhere

I think he did which was OSX

How do you like not having a real escape key?

I don't have the new MBP, but how often do you really use the escape key? I'm use solely vim for my development work and I almost never encounter a need to use the escape key.

How do you exit insert mode?

Using caps lock as escape is pretty common. I think there is a virtual escape button on the touch bar.

There is a virtual escape. Personally, I have "jk" mapped to escape (whereas Caps Lock is rebound to Control system-wide).

How did you accomplish this without an external program?

Which, "jk" or Caps Lock? The "jk" mapping is just in Vim. As for Caps Lock, if you go to System Preferences, and the Keyboard prefpane, there's a button "Modifier Keys…" in the lower-right corner that lets you remap the modifier keys (including Caps Lock) to other modifiers. So I just use that to remap Caps Lock to Control.

I use a GNU/Linux system, and never had to hunt for drivers, or had any problems with package updates. And I'm not exactly the kind of user who enjoys rolling up his sleeves and tinkering with the system until it sort of works. When I say I had no problems, it really means no problems.

The one thing that macOS has going for it is the Trackpad's gestures, which I don't think have any counterpart on non-Apple systems, but even that doesn't matter much anymore as my workflow has become mostly keyboard-driven.

> But getting to the point, the Mac ecosystem is now ingrained into open source development...

The Mac ecosystem has been about as ingrained into OS development for over 10 years at this point.

In fact, my observation is that it is now less integrated than it was 5 years ago. I've been trying to build some OS software from source over the last year on Mavericks and then El Capitan and it's quite the minefield. Seems to be something in the shift to clang and issues of versioning with a variety of libraries. "Use hombrew" is the watchword, but the funny thing is that even if you don't use it and start going looking for help with build failure messages... the first results are still advice on the incantations that might (or might not) get homebrew to take care of it, and people still get stuck (finding info at a layer of abstraction down from homebrew seems increasingly difficult).

It got me thinking about running Linux on various PPC macs 'round about the millenium shift -- that wasn't exactly butter-smooth experience, but I think I spent less time on driver issues than I have tracking down the causes of open source build problems on OS X this year.

Meanwhile, there's the Windows 10 compatibility layer. None of the Windows dressing has impressed me much since XP, and a lot of commodity PC hardware is shoddy. But it looks to me like MS is really attempting to offer the same value proposition for developers who find a unix environment helpful -- workstation that will run your popular suite of desktop apps and give you that nix-y feeling. I can't help but be intrigued.

For my personal purchases I've bought nothing* but Apple hardware for around two decades. But the next machine I buy will likely be a PC laptop selected for use with Linux and Win 10. Think I owe it to myself to try.

   the Mac ecosystem is now ingrained into open source development.

Where do you get this from, other than screenshots with red-orange-green buttons in the window decoration on github?

   software built to run on Linux servers runs best
   under an environment that is designed more like Linux.
   He now owns a MBP.

And what does he run on that machine? If he uses it to run 'software built to run on Linux servers' he might just run Linux on the thing and be done with it. It is what I'd do, minus the MBP that is.

   That leaves us with what, Linux itself as the OS

Indeed, for the stated purpose of developing software which is to run on Linux I'd certainly use Linux.

   Anyone who suggests doing this either hasn't done it 
   before or has way too much time on their hands.

I do have a lot of time on my hands, part of which is due to my use of Linux. Integrated package management which actually works, servers which only ever go down to upgrade the kernel or because of physical damage (lightning strikes, etc), no forced upgrade path, no planned obsolescence, no need to hunt the 'net for drivers (where did you get the idea from that Linux users still need to do that? Times have changed since I started using Linux, back in 1992...). As an added bonus I can install Linux on anything I want, try that with MacOS and you'll soon know what it really means to 'hunt for drivers' or 'understand an obscure error discussed in a long forum thread'. And before you ask why you'd want to install MacOS on something else beside that which carries the Apple logo, realise that the deeper you buy yourself into the Apple world, the harder it will be for you to buy yourself out again when Apple finally decides your niche is not the market they should serve.

   I fully expect this release to be their Windows 8 moment

I think this is more comparable to their Mac Pro moment, or maybe their Macbook Air moment.

> Anyone who suggests doing this either hasn't done it before or has way too much time on their hands.

I switched to Arch Linux in 2015 after about 10 years of Apple.

Most of my dotfiles just continued working, so i could have been up and running for work within hours (basically make emacs, zsh and a browser run). But I decided to spent a weekend on configuring AwesomeWM, keyboard layouts and other handy stuff to really adapt the machine to me.

I update the whole system about once a week and so far run into less problems than with homebrew.

If you are not heavily reliant on proprietary GUI-tools, I don't see much problems in switching from OSX to Linux as long as you verify beforehand that your laptop is well supported.

From my experience, Mac's brew package manager ecosystem is actually quite unstable and prone to breaking. I know a few developers who believe that Linux's apt-get is generally more stable.

People compare the two (and I guess they both describe themselves as "package managers") but I see the use-cases as very different. Apt is what the whole OS is built around and managed by the system administrator while Homebrew is only for a subset of things and almost always managed by a user.

I've been using Homebrew for years and the consensus I've seen has almost always been positive. The only time I've had issues is where I removed dependencies but didn't rebuild the package. I've heard about multi-user issues with Homebrew but have never personally used it like that. I wouldn't describe it as "quite unstable."

I generally agree. But I'm not confident they'll change. They may have withdrawn support too quick, but what do they gain out of doubling down their efforts (especially if the market is just developers)?

I've really been surprised hearing pretty popular projects that have been around for 20+ years still have issues on Windows (like Python). Working in VFX there are a lot of domain-specific open source projects that "support" Windows, but have out of date build instructions and break often just because most of the development is done in Linux.

I really think Linux on the desktop's biggest problem is having third-parties caring about it (which is a chicken/egg issue) and people's familiarity. If you need Photoshop or your trackpad driver won't work--you're out of luck. Any of the troubleshooting or debugging I've experienced hasn't been any more difficult in Windows vs Linux other than my familiarity with how the OS works. I find troubleshooting Windows much more difficult because my familiarity has atrophied since I haven't used it heavily in years.

I do think there's hope for Windows with the Linux Bash shell, docker, and virtual environments. It has always been a bit sloppy to use your current OS as your development environment.

Personally, I just want good hardware with support and I'll probably move to Linux. Battery life, a good track pad, high DPI screen (and support for it), and build quality are the major things I haven't found yet and would really convince me.

"Just developers"

Developers are not trivial. Good developers lead to good apps, which lead to a better ecosystem. The technically savvy are also the ones who set the trends about what the rest of the curve adopts.

This is only going to grow more true as creative work (coding, design, etc) becomes a larger and larger part of our economy.

Apple Developers are a prerequisite for a good Apple third-party ecosystem. Especially if you expect the software to be idiomatic to the platform.

But in this case we're talking about web developers or developers for open source server software--not Apple desktop or iOS software. For a very long time Perl and Apache served the web while Photoshop and Illustrator ran fine on a different platform. Windows had both IIS and Adobe products but still didn't overtake Linux and OSX. Yeah, there is some bleed over to regular users and yes, losing them might be the downfall of Apple's desktop computer. But it's less than 30% of their business and the growth potential just isn't that high. My expectation is for them to milk the current situation with minimal investment (while trying to keep the perception of relevance) so they can focus on the "next big thing." I think they pushed things a bit too hard and people noticed, but I don't think they'll change course. They'll just try and change perception.

I would love for them to double-down and heavily invest in desktops and laptops, but I just don't expect it because I don't see a business case for them to.

Apple is one of the largest companies in the world. Apple can and should be capable of robustly investing in both its desktop line and its paradigm-shifting blue sky projects.

Thinking otherwise is dangerously closed minded. Apple's products are more than just the sum of their individual parts. They exist as an ecosystem that gets strengthened every time one of their products can create value through interconnection. E.g. the value of an iPhone goes up when owners of it can seamlessly integrate calls or watch videos through the phone on their Mac OS X or Apple TV device.

Thinking these other, less profitable lines of Apple's business don't matter, or should just be milked for revenue is dangerous thinking that will lead to long term decline. Bleeding some money to keep the hardcore happy, so that those hardcore continue to set trends influencing what the rest of the general public wants, is a solid strategy that Apple should be pursuing.

The Mac OS X computing line one of the golden eggs of Apple -- granted not their shiniest any more thanks to the iPhone -- but still one of their golden eggs. It would be idiotic for them to allow that goose to die.

I was going to make a similar comment.

I tried for the third time last year, and the truth is that if you're switching to Linux because the Mac is too expensive, if you take into account all the hours you waste because of bugs or half-backed apps, Linux is 10 times more expensive.

I use Linux for servers and I would never even consider using anything else. On the desktop? No way. It's just not ready, if you value your time and it's not an hobby for you.

As someone who uses Linux at work without any issues whatsoever I have to ask: What are these crazy Linux bugs people are talking about?

And why does it always happen to macbook users?

My machine wouldn't boot anymore because I followed apt's suggestion to run apt-get autoremove.

There are many packages and apps out there that get released but are far from stable, and no easy way for non-devs (as in Linux devs) to opt out of unstable software.

I'm not your average MacBook user, either. I use Linux on the server on a daily basis.

If I waste 2 hours because of something like this--which doesn't involve experimenting with config files or deleting random files, but just doing regular maintainance--it's a big deal for me and my clients.

autoremove removes packages that are no longer used and should not affect anything.

However, if you have messed with your system (eg manually copied some software or edited a configuration you should not have touched) then autoremove may remove things the system now needs to boot.

How do I know this? Because I once did exactly that (to be fair, apt-get told me this could happen and asked for a second confirmation)

I know what it should do, and I use it regularly.

That one time, it triggered or caused Xenial to stop working correctly.

> Kind if off-topic, but I have to ask. Why do you use autoremove regularly? The amount of storage that is wasted it negligible so I barely bother with it

I have lots of VMs that I update pretty regularly for clients. Many time I just chain the command after apt-get upgrade.

> I know what it should do, and I use it regularly.

Kind if off-topic, but I have to ask. Why do you use autoremove regularly? The amount of storage that is wasted it negligible so I barely bother with it, even inside vms and containers which often have tiny filesystems.

Do you have similar issues when using Linux for servers?

Nope. There's nothing better than Linux for running a server.

Agreed. If the rumored terraced batteries (that couldn't make it in time for this year's release) come through, coupled with ostensible efficiency improvements in the next gen of processors, GPUs etc, we might be able to reach that hallowed 10 hour mark again.

Well, that and hopefully there's a price drop with the second gen of touchbar MacBooks (not holding my breath there)

I think microsoft is well aware of this "issue". And they seems to be working towards it as proven by the recent Windows Subsystem for Linux https://msdn.microsoft.com/en-us/commandline/wsl/install_gui...

Microsoft will hopefully start throwing punch in that direction by trying to "win developers back" by increasing the POSIX compatibility layer. How long till we see a complete "homebrew" for windows ?

If the POSIX subsystem is "good enough" we might see a shift towards microsoft.

> I used to use a PC not too long ago and nothing would work

Was this before or after the Windows 10 WSL environment was released? I think that has done a lot to change developers' views on doing ＊NIX development on Windows.

For me it was before Windows 10 WSL, but for my colleague it was after. It was very early on right after it was announced, of course. He tried using the Ubuntu on Windows stuff to run a Nodejs app but ran into weird filesystem issues. We didn't have time to be one of the first to figure out why, so it was back to the Mac for him.

why would you do ＊NIX development on anything other than the actual kit the code is going to be running on?

It's important to ensure that the software you're developing runs as expected in the production environment. That does not mean that the development environment and the production environment need to be the same. For example, it's very likely that the development tools you're using will (or should) not be deployed. This extends to anything else about the development environment, as long as you're able to consistently deploy the software to the production environment.

This also assumes that there is only one production environment. Some software is expected to work on different architectures or OSes, some quite dissimilar to each other. For example, some software runs on Linux, macOS, and Windows. A developer (or development team), probably has (and should have) access to all of these environments for testing, but likely does development in the one they're most comfortable with.

Isn't that what I just said? that the development machines os and hard ware should be identical.

I have worked on projects where we brought the dev / test and live from the same production run so the hardware was identical down to the MB rev

why would you do ＊NIX development on anything other than the actual kit the code is going to be running on?

I understand this to mean that you think that the dev environment should be identical to the production environment. Am I misunderstanding?

Assuming I'm understanding you correctly, no, I don't think what you said and what I expressed are the same at all.

A developer (or development team), probably has (and should have) access to all of these environments for testing, but likely does development in the one they're most comfortable with.

If you are saying that development in a different environment is okay, but a dev should do testing in a production-equivalent environment, then we agree. I don't see that distinction in what you've written.

If I'm misunderstanding or misrepresenting what you're saying, please do correct me, as that's not my intent.

I build Node.JS apps and Cordova apps all day long on Windows 10.

What's your problem?

The MAC version of Unix diferers considerably from Linux.

There is plenty of OS software for PC's.

I think your trying to defend Apple when they seem to be disengaging from the "professional" market

Reply on news.ycombinator.com