Slashdot Mirror
Mozilla Is Working On a Firefox OS-powered Streaming Stick
SmartAboutThings writes: Mozilla took the world by surprise when it announced that it was developing a Firefox operating system that would be used for mobile phones, particularly in developing markets. Such devices have already arrived, but they aren't the only targets for the new operating. According to a report from GigaOM, Mozilla is currently working on a secretive project to develop a Chromecast-like media streaming stick powered by Firefox-OS.
Mozilla's Christian Heilmann shared a picture of a prototype.
Mozilla doesn't build hardware. We make software, including Firefox OS. Firefox OS is a completely open platform freely available for any company to build on top of without restriction. There are dozens of companies building Firefox OS-based products today and there will be more tomorrow, covering mobile phones, tablets, TVs, set top boxes, game consoles, streaming dongles, wearables, and more. Some of those companies are working directly with Mozilla and others are taking the code and running with it on their own.
Mozilla should go back to doing what they have always done best - annoying the shit out of Microsoft in the browser wars.
thunderbird still around and just going to community development model. or you're going to pay mozilla for the expense of keeping it purely in house? no? you've never contributed to anything? then shut the fuck up.
Firefox already is 64-bit and has been for quite a while.
Just, not on Windows. I think their excuse was something to do with third party plugins not being 64-bit. (Although I'm pretty sure they have a 32-bit plugin shim that works on Linux and Mac OS X, so whatever.)
I don't really care, though, since Firefox 30 entirely broke Firefox with the proxy where I work. Now I can't access outside sites at all due to OCSP errors and I can't access internal sites since they removed NTLMv1 support as a "security hole."
You are in a maze of twisty little relative jumps, all alike.
I think the answer is obvious from the parent post. Without a dedicated receiver to route signals, hdmi all goes to one place, and many people prefer other speakers than their display has. I should also point out that the digital pcm streams in hdmi are easy to rip if hdcp is not active on the link, so your assumption is off. On the other hand I believe drm schemes only hurt the customer and the artist, only serving to enrich the content distribution cartels.
How has Thunderbird been killed? It is a stable mature piece of software. There are very few features that they could add to it without making a bloated piece of software.
Because those other browsers didn't have a huge extension ecosystem to contend with. Are you going to go and tell every extension author, big or small, new or old, maintained or not, that they need to rewrite their add on to work with electrolysis? No, you have to make e10s seamlessly compatible with the legacy, single-threaded APIs that those extensions use. That's hard.
I'm going to the casino. Don't gamble.
You've done the same as google did with Android - take Linux, write a few hardware specific drivers and shove a roll-your-own graphics interface on top. Its a pity you and Google don't give credit where its due frankly but oddly enough the word linux never seems to mentioned in any of your or their presentations. As if the effort of the thousands of people who helped develop linux counts for sweet FA in your marketing.
TB has some architectural problems and the withdrawal of paid developers by Mozilla makes it unlikely they will be fixed. The problem I ran into is that attachments cannot easily be stored separately from messages. That column showing the attachment count is actually just a guess. The db does not have real info on the MIME situation in messages. All that work is done on the fly whenever you open the message. You can detach the attachments from messages and store them separately, but only by clicking on messages one-by-one. There is an extension that attempts to automate detachment through filters, but it will crash if it encounters too many messages with attachments at one time, since the task is asynch. I confirmed all this with the extension developer - not the crashes, but the architecture and the fact that the db only guesses at the attachment count when you view the message list. Of the 12,000 current extensions, I found two or three that attempted to deal with detachment.
HOLY FUCK SON! YOU'RE REPLYING TO ASA DOTZLER!
YOU CAN'T FUCKING SAYING WHAT YOU JUST SAID TO HIM, SON!
Look, Asa is more than just a God. He is the God Almight of the Almighty Gods. He is The Master, The Creator, The Founder and The Omnipotent Being.
When Asa writes something, you don't just read it. You revere every single character it contains. You revere the whitespace between those characters. You revere the entire message, because it represents The All-knowing All-powerful Nature of Asa.
Asa, PLEASE FORGIVE THIS POOR SOUL! He knows not what he is saying! Please, Asa, please don't hold it against him! He's just a Rubyist! We beg you to spare his rotten soul! PLEASE! WE BEG YOU!