678 karma · joined September 10, 2013
Question about pricing: are "users" just developers, or anyone that should be able to view the app?
While I find the pricing of $16 just fine if it is for developers / designers, it is very common to need to show / share a feature with a few customers / QA people / friends to get feedback, and if that kind of users are also priced at $16, that adds up quickly.
This is just the way the world works. If you are opposed to something, you need to complain and make a buzz to get change over time. Even if in the moment it is both obvious and will make no difference.
This is a major performance factor, since it means all layout can be done in one pass. If the proposed selector were added. CSS layout would have unbounded complexity.
http://en-gb.topographic-map.com/places/Oslo-1311779/
http://en-gb.topographic-map.com/places/San-Francisco-353207...
New bike paths are around the periphery of the center. In the city center, there are close to zero bike parking spots. Everyone who wants to take the bike to work, must have parking in the workplace. In addition the tram tracks on many streets are a hazard to taking the bike. But things are improving here slowly
Public transport though is probably the best in the world per capita, with subway, buses or trams going every couple of minutes. So this compensates (as the article states). Overall the reduction of cars is a great improvement overall.
In addition; it would require quite a lot of labor to auction and send all these sets around, as well as paying for storage space. Something which is not accounted for in the 10-20% return figure.
However, development of a new web server in Rust is an interesting project, and could certainly compete with nginx over time if enough effort was put into it.
For the same reason, I print all important photos for posterity. Who knows if apple / google cloud photo library will be around in 50 years when I grow old? I can make sure my printed material remains much more easily.
If you had a React based web app already, and a bunch of React devs, the case for React Native is obviously stronger. And would make more sense.
However workers who represent the union are often unpaid. Or paid very little for their efforts.
For example: If my mother "cleared her history", I really doubt she would notice the worse quality of Facebook and regret deleting her data, as the top-level comment implied. So my point is it's not a move to show how effective the algorithms are, but a privacy-conscious one from Facebook.
There probably will be a difference, but I think in actual use, for most people, it will be very small.
You decide on a timeframe for deletion of backups (ie. X days). You keep a record of deletion requests you receive for X days. If you need to restore to a backup, you delete data again for the users that requested it.
Then you delete the backups and records of deletion (or the tables in it that contain personally-identified information) after X days.