kumar303

I think they will co-exist as separate languages for separate problem-solving approaches. Go has first class support for channels and duck-type interfaces, for starters.

Also, nothing on Firefox OS would stop developers from using any payment processor they wish to. It's all just web technology running on a mobile device so there are many payment providers to choose from, especially for US and European users.

Actually you can [theoretically] put a charge on your phone bill from desktop but there are some open bugs around this and it's not a high priority use case for us. The main case for desktop is credit card processing.

The main reason Mozilla built a payments service and offered a custom library for developers vs. recommending Stripe (etc.) is because no one supported the direct operator billing we needed in our Firefox OS launch countries with a developer friendly interface.

The deal is only for the default engine. Firefox users are still free to switch it to Google, Duck Duck Go, or Yandex or anything

I signed up for a dev unit but the "early prototype" part makes me think it won't work all that well ;) We'll see.

I'll admit I'm somewhat conflicted. You can arrive at similar conclusions thinking about it as child pornography. In both cases it does seem like censoring the material is the right thing to do.

However, my conflict comes from the fact that censorship doesn't really solve the root problem. In child molesters, the problem is better treated in psychiatric care and in extremism the problem is better treated through education, peace, and tolerance.

Yes. Firebase. I think Firebase is interesting because they focus on realtime data which is crucial for a lot of apps these days.

It won't be integrated into Android very well though; you can't kill the process, you can't check its resources, it's not in the task switcher, etc, etc