4 ms·
From seeing others dealing with bleeding edge node.js stuff - installing modules and following tutorials become confusing. Sometimes you get weird error and onl
by hippich 13y ago
From seeing others dealing with bleeding edge node.js stuff - installing modules and following tutorials become confusing. Sometimes you get weird error and only after couple hours googling you find out that it is because on Mac it is a bit different and you would avoid it if you start with Ubuntu in first place.
Yes, Ubuntu, since it is most used OSS desktop right now and most tutorials, docs, etc focus on it from my experience.
So it boils down to what you do. If you do mostly client-side html/js/css you probably will be ok with Mac. If you do more server stuff - it might make sense to switch to Ubuntu to make your life easier. Start with Virtualbox with Ubuntu in VM to keep your workflow the same in the beginning.
- ryan-allen 13y agoExactly this! If you are deploying to Ubuntu, it is so much easier on you if you have your dev environment running the same thing. On OS X I found it not to be too different an experience as well, I would run Ubuntu server, open terminal, SSH into the local server, and in the browser just hit the VMs IP, as opposed to open terminal, and hit localhost.
- kayoone 13y agoYou shouldnt pollute your local system with all the dev libs you need anyway. With things like vagrant its very easy to put your projects into containers which run identical enviroments to your target. For these containers it also doesnt reallt matter if you run them from an osx, linux oder even windows host. Another option would be to get some remote Server and do your development there, which has the benefit of being available from anywhere. In that case you will have to use some form of remote editor like vim/emacs though since syncing from local is painful for bigger projects, especially if you work with different branches.