Why does a user have to email a company to delete their account? How is that consumer friendly, especially after Uber lets your account get hacked/1k stolen!
This happened to me (I never used Uber.. signed up and forgot about it) and in my research I found out they know about the hacks and their PR message is its the user's fault for using a lame password.
What a horrible company.. run by the worst vile, corrupt, arrogant sociopaths ever!
It's an internet service .. I don't need to send an email to Facebook, twitter, etc to have my account canceled. Uber should be no different unless there's a pending charge then tell the user you can cancel after payment has cleared ...not wait until we feel like emailing you to handle your request because WE WANT TO LOCK YOU IN! I was and am still furious that I was unable to cancel my phantom Uber account immediately after my bank account got hacked.
Any web service following this scheme is not doing it for their users but for themselves!!!
Relatedly, I wanted to highlight that Dan Abramov is currently working on a refactor of ReactPerf [1] which will make the performance measurements more accurate.
I don't think any of their sales tactics fell under "misleading, illegal, or dishonest." It was their California pre-certification practices that was blatantly illegal.
Well, that still falls under the "Not behaving in a way that damages the reputation of his/her company or of YC" and "Generally behaving in a professional and upstanding way" rules listed on that page.
Great post! I found Fenwick trees particularly useful when I was implementing layout / view recycling. The problem is that you need to keep track of a large number of vertically stacked elements with dynamic & varying heights, and you need a way to efficiently get the prefix sum. Would be curious if anyone else has real life use cases of these.
Thanks!. I have read that this data structure can be used for range updates and queries. Something that can also be done using Segment Trees. I haven't covered range updates in my article. It only talks about prefix sum and point updates. I will talk about range updates and segment trees in another article soon.
We're still using it on some of our projects, but we've found that no matter how simple we make data-binding it still leads to a mess of event bindings and state management.
The original plan was to make a virtual dom plugin for ripple but it wasn't really possible with the way the worked behind the scenes.
For me, the part of Flux that's difficult to understand is how server data flows into the cycle (left-hand side of the diagram). The Flux docs only recommends that server interactions should be done from the Action Creators. However, things are actually more complicated than that:
- how do you resolve server / client data conflicts?
- how do stores work with a RESTful API?
- how do you handle network failures, retries, etc?
At Quizlet, we designed a hybrid solution [1] with "syncers" that act as the gateway for network I/O. Syncers are responsible for taking view-level data (ViewModels) and exchanging them with the server (ServerModels). It works well with our REST API. Yahoo has also released their own thing called Fetchr [2] which is more tightly integrated to stores.
I'm curious to see how other people are approaching this problem.
https://twitter.com/FamousCeleb/status/834567373214539776/ph...