I know a lot of engineers at a lot of companies who look at porn on their work laptops (which isn't illegal). I don't know a single engineer who would take documents from their previous company to their new company (which is very illegal).
Currently they're unprofitable and their target market is other, unprofitable companies (e.g. turning away Fortune 500s, from the article). If that changes then it looks more sustainable.
I have some friends at AirBnB and I've heard it's much more modest, like $300/yr or something. My experience with these type of "dogfooding" credits is that companies are much more generous when they're smaller, so it could be that older employees get more than newer employees.
That makes sense. $300 is enough to cover Airbnb housing costs for at least a few days in pretty much any location around the world, so they probably still get value out of it.
That's very important in cooking in general, but is definitely not the most important part of baking pizza. Heat transfer is a lot more important, that's why different cooking surfaces (e.g. stone vs. steel) can yield dramatically different pizzas, even at the same temperature. You're going to get a maillard reaction no matter what.
It's interesting to hear him say that npm and node_modules are regrets since lots of complaints about Go packaging from people new to Go ask for something similar...
yarn just seems like a set of incremental improvements over npm? Which is great, we're all for improvements. However, the vehement complaints I've seen about npm [0] make it seem that nothing short of a complete re-architecture could be tolerated. yarn does not seem to be that.
I don't agree with those complaints, but I do agree with you that "some parts" are really good. node really figured out the right search strategy for an unscoped import. (e.g. "require 'foo';" rather than "require './bar/foo';") Just look for a directory with the name "node_modules". If you don't find it, go up one directory and try again. So simple! So predictable! So complete! It works so well, all manner of "left-pad" abominations can be supported. Any other system should think very carefully before using a different import search strategy.
[0] with the exception of those related to path depth: I think those are resolved now? I wouldn't know because I stay on an OS that doesn't go out of its way to frustrate me.
Something seems off here - they mention using 100 workers (a worker for every request). I would expect that to perform way more than 40% faster unless there's a ton of overhead in creating those workers.
Allowing people to put in-law units in their backyard seems like a good move in the short term (to increase supply), but also seems like it might cause problems in the long term: NIMBYs are then _even more_ incentivized to prevent new housing because they're making a killing off the overpriced shipping container in their backyard.
I know a lot of engineers at a lot of companies who look at porn on their work laptops (which isn't illegal). I don't know a single engineer who would take documents from their previous company to their new company (which is very illegal).