{"id":3120,"date":"2017-09-22T17:19:13","date_gmt":"2017-09-22T15:19:13","guid":{"rendered":"https:\/\/vizZzion.org\/blog\/?p=3120"},"modified":"2017-11-28T20:30:35","modified_gmt":"2017-11-28T19:30:35","slug":"the-evolution-of-plasma-mobile","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2017\/09\/the-evolution-of-plasma-mobile\/","title":{"rendered":"The Evolution of Plasma Mobile"},"content":{"rendered":"
\"Plasma<\/a>
Plasma Mobile<\/figcaption><\/figure>\n

Back around 2006, when the Plasma project was started by Aaron Seigo and a group of brave hackers (among which, yours truly) we wanted to create a user interface that is future-proof. We didn’t want to create something that would only run on desktop devices (or laptops), but a code-base that grows with us into whatever the future would bring. Mobile devices were already getting more powerful, but would usually run entirely different software than desktop devices. We wondered why. The Linux kernel served as a wonderful example. Linux runs on a wide range of devices, from super computers to embedded systems, you would set it up for the target system and it would run largely without code changes. Linux architecture is in fact convergent<\/em>. Could we do something similar at the user interface level?<\/p>\n

Plasma Netbook<\/h2>\n

In 2007, Asus introduced the Eee PC<\/a>, a small, inexpensive laptop. Netbooks proved to be all the rage at that point, so around 2009, we created Plasma Netbook<\/a>, proving for the first time that we could actually serve different device user interfaces from the same code-base. There was a decent amount of code-sharing, but Plasma Netbook also helped us identifying areas in which we wanted to do better.<\/p>\n