Hacker News new | past | comments | ask | show | jobs | submit login

Really? This seems like one Chrome extension away...



so that someone else gets your data?

Chrome extension is a no go.


Who says it can't save it to a local database?


It can, until the extension developer receives a tempting offer for it, as has happened countless times


Fork the extension and use your own then.


And you’re going to spend the time reviewing every single commit to make sure the dev didn’t sell out without telling anyone? Or risk running a potentially outdated and vulnerable extension?


And then you’ve gotta wake up in the morning and put your shoes on!

What’s with the argumentative tone? Do you think that the replier doesn’t know this?


The obvious point being that the “fork your own code and write your own kernel” attitude is simply unworkable for 99.999% of the population.

If we had to waste that much time re-inventing the loaf of bread, and then making sure that my neighbors didn’t decide to throw some raisins in my loaf, that we never get around to figuring out the next best thing: slicing it.


The argument you're making (you can't trust software whose you code you haven't studied) applies to every software package ever made.


Exactly. So we have to choose: trust everything reasonably mainstream with the hope that someone is watching it, or stop functioning.


...which is a lot more work than "one Chrome extension away".




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

Search: