80 karma · joined May 17, 2013
No need to worry about explaining it kindly and plainly to me :)
I work on a platform team developing many different libraries used by many different teams throughout the company. If we didn't leverage semver (or some versioning scheme that at least differentiates between breaking and non-breaking changes) I don't know how we would do it. We either a) wouldn't be able to release 'patch' updates to a particular library without consumers getting it for free/automatically without changing anything or b) wouldn't be able to release breaking changes without it automatically breaking consumers builds.
Semver may not be useful for the final build or end product that you end up shipping. But it is a very useful tool for all the parts (dependencies) that make up that final product.
I almost always have both my Macbook Pro an iPhone connected. The switch from listening to music from the laptop to the iPhone (such as when I leave the office and get on the bus) is seamless. Simply stop playing music on the laptop and start playing music on the phone. I highly recommend them.
No innovative features? What do you call a ribbon display that no one has ever done before?
No expansion - nothing new to the MBP line.
The post comes off a little more abrasive than I'd like. I think writing it as an "email" to a hypothetical new team member makes it worse.
The point is: we take our code reviews seriously and we may point out things that seem silly or nitpicky, we may question your approach, we may make many suggestions for improvement, but at the end of the day it is nothing personal. It is for the common goal of high code quality.
You must be confused. Node.js is used to run JavaScript on the server, not in a browser (the client).