jordskott

The same way you can build anything you want on your own, I also can say it's crap and I don't want it. And that's fine, you don't need my permission and I don't need to be your public target.

But it's a bit odd that once you realize that you can't build your own vision without asking for my opinion, you start throwing a tantrum saying I'm a negativist and that I don't embrace the community spirit.

No one forced Mark to shut down the project, he made the decision on his own.

Also, community and open source is all about contributions and public discussions, not _just_ code dumps.

The problem with Mir, Unity and all the convergence ideas was that they were poorly communicated.

They didn't really engage with the community and kept all the discussions and development behind closed doors, releasing dumps of code once in a while once they reached a milestone that they were satisfied with.

That's what Google does with Android, for example, and that would be okay... but only if they were able to take on such ambitious plans.

You can't expect the community to welcome you when you blindly follow your ideas and you can't even produce anything in quality. And when I mean in quality, I mean something that justifies going your own way, not just another "GNOME clone" without any added features.

I'm pretty sure they had amazing ideias in mind and that they had reasons on why they avoided going to Wayland but... is anyone able to point out any public mailing list, or public blog discussions, where they discuss all of this? I really tried to follow all Ubuntu/Mir/Unity/Phone/Convergence project but all the information I found was poor and outdated. Even working Ubuntu Phone images for the Nexus 5 was hard to find.

But ARM cannot, and won't, officially support the OEM's devices and start releasing updates for them. The process is a bit more complex than you might be imagining.

If there is a reason on why ARM's GPU drivers are not updated on your device, it's hardly ARM's fault. ARM doesn't ship the SoC or the device directly to you, it ships it to the OEM. And it's the OEM who states the agreements.

If you want to blame someone, starting by blaming the OEM.

Open sourcing commercial products like hardware architecture and algorithms to the public is not exactly an easy thing to do.

There are millions of registered patents and the chances that your clean-slate ideas were already invented and patented are really high.

Open sourcing means exposing patent infringements to the public (even if you are not really aware that you are infringing anything), which means that you need to invest on a strong legal team in order to go through all possible patents and to deal with all possible litigations you might face.

In order words, open source requires much more than ideals, it also requires butt loads of money.

I already made a comment about Apple's GPU here: https://news.ycombinator.com/item?id=14021814

Apple actually has its own mobile GPU, built from scratch.

The Tile-Based Deferred Rendering GPU is an advantage from the GPU sharing the same memory with the GPU. On a normal desktop GPU you need to transfer huge amounts of data from the main CPU RAM to the Video Ram but on a mobile device, the CPU and the GPU sit both on the same memory system. This allows you to architecture your GPU in a different way.

Both ARM's Mali and Qualcomm's Adreno use Tile-Based Deferred Rendering.

No, I can say with certainty that they are working on their own mobile GPU.

They have been hiring a lot of graphics people and putting a team together.

And another thing that most people are not really aware: Apple had a lot of saying in the architectural and design decisions of Imagination's GPUs that ended up on their iPhones. A good part of the development actually happened at Apple's offices with Imagination people flying over.

So they know what they are doing, they are very well familiar with Imagination's GPU and they are more than capable of developing their own thing from scratch.

The beauty of orgmode is that you don't need to learn everything to start using it, actually, you can just start with your typical workflow and look for stuff as you need.

To be honest, Yubikey was never really open source. Sure, they open sourced _some_ compomnents before but you coulnd't do anything with the source.

I guess it mostly boils down to Moxie and his ridiculous claims of how much more secure Signal is when compared to other solutions (like XMPP and anything based on PGP).

Don't get me wrong, I understand the design and user experience decisions of making Signal depending on GCM but Moxie just loves to bash on XMPP and federated protocols and putting Signal on a pedestal of exemplary security.

I admire the dedication on putting together the Axolotl protocol but I hate when he mixes his business interests with secure crypto solutions, because by the end of the day that is what he wants, to sell Axolotl to companies like Google and WhatsApp. And of course, bashing on XMPP is just a business pitch to those companies.

I have some reservations towards Open-V, I would be careful before backing it:

https://www.reddit.com/r/linux/comments/5ekuck/openv_the_wor...

https://www.reddit.com/r/cpudesign/comments/5eep88/the_world...