Hacker Newsnew | past | comments | ask | show | jobs | submit | Fennhella's commentslogin

I think you're reading too much into it (If you're being serious).

Doubt it had any other meaning other than the team just having fun making a quip at the Boaty Mcboatface poll for a ship's name.


Yes, I was being playful with language, rather than straight serious. But this topic invites that.


Especially when that makes it sound neck on neck when in reality Uber is trailing Didi Chuxing (formerly Didi Kuaidi) by a wide margin.

Didi Chuxing has 87.2% of the market according to research from the China Internet Network Information Center.

http://news.xinhuanet.com/english/2016-01/11/c_134998758.htm


I feel like that is expected. Uber can't win China if they don't want it too. The Chinese state and people naturally want to produce this service (and others, i.e. search engine) themselves, they don't need or want foreign companies taking their market.


Disagree. Uber is not winning in China for one reason only - Didi is better than Uber. It has nothing to do with Chinese government or people. Chinese people love foreign brands, which are seen as being better and higher quality. They buy iPhones, go to Startbucks etc.


I see you, with a new account, post a lot of protective comments about the Chinese government, do you work there?


Why is Didi better?


Im curious, what do you use/recommend for monitoring and tracing?


Others mentioned Observer. That is very cool.

When without a GUI I use the built-in dbg module. Sometimes via the recon_trace wrapper to get the tracing to be rate limited (if on a production cluster).

ttb built-in modules used for tracing on multiple nodes, capture more data and then save to a file and inspect later.

eflame or eep (not the Erlang Proposal, the profiling tool) + kcachegrind to view results.


Erlang has Observer, a built in tool that lets you monitor and trace things as well as well see your process hierarchy.


I'm often not much of a GUI tool guy, but Observer is really cool - the GUI really does give you a nice view of how the supervision tree of a more complex Erlang system is put together.


Yep. Not only that, but I find it to just be insanely fun to go double-clicking with wanton abandon throughout Observer, digging in to everything just because I can. That it's all there, with no setup and effort required, makes it feel almost magical.


Seems like a test to see how the practice goes.

Really don't know what the hypothesis or plan is that would lead to good conclusions though.


I have no doubt about uber being around in 20 years, they're just too well established and understand where the industry is heading to become irrelevant.

Though what I do think will happen is an erosion of their lead where they go from the sole 800lb gorrilla in the west to being one of many with automakers coming into their own offering self driven taxi style service on what will probably be a subscription model (like how we have monthly payments for cars today).


There was a time, less than 20 years ago, when people would have said the same thing about Nokia.


>>Though what I do think will happen is an erosion of their lead where they go from the sole 800lb gorrilla in the west to being one of many with automakers coming into their own offering self driven taxi style service on what will probably be a subscription model (like how we have monthly payments for cars today).

Either this, or I could easily seeing aggregator apps, similar to the many that have popped up to manage multiple social media accounts, appearing to help drivers and riders manage both Uber and Lyft accounts.


They already kinda are. Look at, say, Drive Now (https://uk.drive-now.com/) - they're owned by Sixt, and they operate Drive Now jointly with BMW (BMW cars being the only type you can have with DN). I imagine automakers have relationships with other "car-sharing" firms (e.g. Zip Car) as well.

You might already know that, but for everyone who doesn't live in a city where they're available... :)


Thanks for all the work thus far, isn't a day goes by where I don't use a YC company's service.

hope there's plenty quality time in this sabbatical!


You could proxy using nginx to allow read only access to specific endpoints, there's a few good posts about it going into better detail than me, for example:

http://blog.eagerelk.com/securing-elasticsearch-using-nginx-...


Very similar instantsearch.js (which is also react components) for Algolia search.

Having this for elasticsearch is very useful indeed, get products out there with a consistent search UI.


Yes, instantsearch.js is built on top of React. But it's not a React component yet.

See https://github.com/algolia/instantsearch.js/issues/920


Indeed we are working to provide it as React components also. Thanks for the mention :)


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

Search: