> when Google does the same thing, it is an example of "locking everything down while still calling itself open."
Well, Mozilla have a proven track record of providing a self-host alternative for their cloud platform (the main reason I'm using Firefox sync -- with Mozilla servers -- is that I could set up a proof-of-concept sync server[1] on my own hw, see that, yes it does work fine. Contrast that with what Google does ("We have a magic database, here's some of the ideas behind it; sorry you can't host your own, so all our service tech will remain proprietary").
I use Chromium from time to time, but I don't use Chrome -- and I avoid logging in to Google services when I can.
I've been waiting for a Cyanogen-mod for my current phone, because I don't like running stock Android in it's sort-a-open, mostly-closed state -- not to mention the amount of spyware that ships with the platform (it doesn't help that Samsung ships its own software too -- which I'm assuming contains its share of bugs).
Try building a working phone kernel+userland with whatever Google+partner have released and try and convince me that they're good at doing "open".
I hope they will keep the dev-mode for all chromebooks -- and that they'll make it easier to boot into custom kernels without a boot-up delay etc -- but I'm not holding my breath.
[1] I actually ran the previous one, but I'll be setting up an updated one, as soon as I move "into" my new server.
Well, Mozilla have a proven track record of providing a self-host alternative for their cloud platform (the main reason I'm using Firefox sync -- with Mozilla servers -- is that I could set up a proof-of-concept sync server[1] on my own hw, see that, yes it does work fine. Contrast that with what Google does ("We have a magic database, here's some of the ideas behind it; sorry you can't host your own, so all our service tech will remain proprietary").
I use Chromium from time to time, but I don't use Chrome -- and I avoid logging in to Google services when I can.
I've been waiting for a Cyanogen-mod for my current phone, because I don't like running stock Android in it's sort-a-open, mostly-closed state -- not to mention the amount of spyware that ships with the platform (it doesn't help that Samsung ships its own software too -- which I'm assuming contains its share of bugs).
Try building a working phone kernel+userland with whatever Google+partner have released and try and convince me that they're good at doing "open".
I hope they will keep the dev-mode for all chromebooks -- and that they'll make it easier to boot into custom kernels without a boot-up delay etc -- but I'm not holding my breath.
[1] I actually ran the previous one, but I'll be setting up an updated one, as soon as I move "into" my new server.