1) People hate car dealerships
2) The cars/trucks are really innovative
3) People hate car dealerships
2,379 karma · joined April 6, 2016
1) People hate car dealerships
2) The cars/trucks are really innovative
3) People hate car dealerships
It's a cool post but it has nothing to do with censorship. Am I the only one who was misled?
> Tons of breaches documented here [1], at least 14 000 trips with unlicensed (uninsured) drivers. Drivers with suspended licences were allowed to re-register with Uber, drivers were allowed to drive without insurance on their vehicle.
I genuinely wonder if Uber could keep enough drivers if they stopped allowing uninsured or suspended drivers.
[1]: https://tfl.gov.uk/info-for/media/press-releases/2019/novemb...
[0]: Couldn't find a quick source on this
[1]: https://theintercept.com/2019/03/04/google-ongoing-project-d...
All said I don't like the name because it puts Postman in a tough situation, keep the gender pronoun if you want just don't make it near identical to them.
Bronn then answers "Without question? No. I'd ask how much."
Handling large arbitrary JSON objects where I need to operate on their keys but don't need to work with their values by unmarshaling to map[string]interface{}. The alternative would likely be code generation of struct definitions with JSON bindings, which is likely preferable if you already have code generation in your project, but can be an overhead in smaller ones.
It can also be used to create your own syntactic wrappers around API's which consume interface{} such as encoding/json and database/sql:
Unmarshal(r *http.Response, dst interface{}) ([]byte, error)
and BulkInsert(tableName string, columns []string, values [][]interface{}) (time.Duration, error)Something enterprise customers love hearing. Ooof imagine being assigned to sunsetting the service and explaining to what enterprise customers it still has.
The current negative sentiment as seen on HN is about Google dropping products. But I think the negative sentiment outside of our bubble is due to Google blundering into this with dishonest marketing. Google tried to force this into a viral success on day 1 and that's not going to happen. This strategy also eroded trust that it will be fixed to the point it was originally promised either.
Finally, it didn't help that they didn't vertically integrate the games themselves and are charging full price for the game on top of the service. Microsoft is a good example of how it may have been done, by investing heavily in studios and exclusives to get the people going. To be fair though, Microsoft has decades of experience with this with xbox alone.
EDIT:
Because of a sibling comment I just want to mention how I think this may end. I think Google is now between a rock and a hard place, they either dump immense resources to get it right, or they dump the product and face even worse consumer reputation decline (this time in an entirely new market segment!). I suppose there may be a third alternative of putting it on life support. Either way there is no clear win here, I do empathize with the team which probably has a lot of passionate members who just want to do a good job. It'll be a good PM lesson to watch how it shakes out.
First, is it possible to develop software without inconveniencing business users with temporary (let's assume the ultimate products are better then the linux/vim/emacs they are superseding) regressions and inconveniences? And what is the cost in terms of time to route around such pitfalls? Would we still be able to have startups at all if products required thousands of hours of QA or perfect test suites in order to launch?
Second, if we were to set a hard rule 20 years ago that all software was to avoid this phenomenon during its development, what valuable tools and services would never have been developed at all? Would we still have Twitter? Reddit? Steam? Whatsapp? I don't have to dig far into the history of any of those tools to find near revolutions by their userbases over braindead UI or adversarial practices in the name of "vision".
I don't know, these are open questions. I just think avoiding all such frustrations you mentioned is wishful thinking and at some point it is just part of the process of experimentation and iteration. Or perhaps this process is entirely different in a small corp. versus a big corp. environment.
I agree with your overall point, that things are worth trying even if they don't inherently scream success. But that doesn't mean we need to try everything and abandon common sense at the door. In this case I don't think Stadia defies common sense, I think it defies consumer benefit: gamers should own the games they buy, freemium services powered by ads are dubious, and products which need to be advertised dishonestly to sell well probably shouldn't be sold at all.
If the answer is yes to these questions Google may have a clear competitive reason to lobby for pro data selling/buying legislation to the detriment of users which may signal that these privacy advocacy groups may not actually be privacy advocacy groups as the article alludes to.