Hacker News new | past | comments | ask | show | jobs | submit login

It's not a good question tbh (http://www.catb.org/~esr/faqs/smart-questions.html)

If your question is about whether to wait for the next iteration see: https://buyersguide.macrumors.com/#mac

As a general purpose machine for development / web dev, then the answer is yes, it's still worth using because it was worth using when it first launched and that didn't change.

Many guides come with instructions specifically for OSX including homebrew install commands etc. https://brew.sh/

The MBP 14' M1 laptop is a powerful, robust machine with great battery life.

If you enjoy that, first class support for all common webdev tool chains, and enjoy OSX, then it's still worth it for web dev.

An overlooked point is many courses and youtubers will be making videos using the same machine as you on OSX so it's good for that purpose as well (i.e. to learn and see the instructor using the same environment as you are.)




> It's not a good question tbh

ESR is mostly wrong about this. He assumes that the person asking the question is not writing in good faith or that they have not considered and dismissed alternatives, without evidence. It's almost always appropriate to assume the person asked what they asked for a good reason ignore the question if you don't know the answer.

SO is plagued with this nonsense, where people answer the question they wish was posted (because it's all they know?) instead of just moving on.


I cannot recommend brew for react development (NPM). Installing NPM packages through brew is not supported by projects that require global packages. NPM installed through brew frequently runs into issues by projects that expect packages via NPM to be in /usr/local but are not symlinked. This is not even mentioning all other flaws of brew, such as owning /opt or /usr/local to your user breaking multi user support, being based on git and subsequently very slow, brew breaking on even point releases of macOS.

I recently started a job that requires react and docker so here's what works for me. Install node.js from their website, use npm to install typescript language server globally, docker binaries like Minikube suggest using `sudo install minikube`, reading the manual for `install` says it simply copies the binary over to /usr/local/bin (already in path! security issue for brew owning this to your user??). You can then use `install` for any CLI tools you need (jq!).

macOS was never designed for package managers, brew does an exceptionally poor job at being a package manager while also fighting against macOS to stay functioning. I highly recommend avoiding brew, it is certainly not a necessity nor supported by packages it hosts.


You don't install npm packages (or any language development packages) with brew. You install nvm with brew and go forward with it.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: