TEA Ebook – A Modern Ebook App for Stylish Readers

We have reviewed a good number of ebook apps in the past, most of which have been in development for a long time. Today, we bring you a relatively new app to the application market and it goes by the name of TEA Ebook. TEA Ebook is a free and cross-platform EPUB and PDF reader with which you can browse and read through your entire digital library wherever you are, and without an internet connection.

Akiee – A Markdown-Based Task Manager for Developers

Akiee is a cross-platform, AGILE-inspired task manager that helps you to concentrate on your most important tasks by making use of ranks instead of priorities. It features a simple UI with three main tabs, Todo, Doing, and Done. A "+" button for adding new tasks, an “Editor” button for editing tasks directly, and an “All” button to list all your tasks.

Discover, the KDE Software Center App, is Improving Nicely

Many KDE fans –maybe even you– consider the app to be too limited, preferring instead to use an alternative tool like Synaptic or the Muon Software Center to handle package management. So popular is Muon that Kubuntu 17.10 even re-added it to its install image! But Discover shouldn’t be forgotten about. It’s important that Plasma desktop has a vibrant, easy to use, “one-stop-shop” for users to discover, install, update and remove software on their desktops.

Polishing Discover Software Center

KDE Discover Software Center is a key element of our Usability and Productivity initiative because it encompasses the basic experience of discovering, installing, and removing software. Most regular people don’t want to use the command line to do this, and for them, we have Discover.

Breaking apart massive bosses in the Breakout-like 'Puppet Kings', some thoughts

I have fond memories of Breakout as a child, my son even has a rather low quality version on his 'kids camera' and Puppet Kings [Steam] is an interesting take on it.

Need to relax? Guppy is a simple game about trying to survive as a fish

Since releases are always light at the start of a year, I've been able to look over some more titles sent to our Steam Curator. Guppy [Steam, Official Site] is one such game, that sees you become a fish.

On using Github and a PR based workflow

Linux size Command Tutorial for Beginners (6 Examples)

How to Retrain Your Google Assistant Voice Model

Analyze Song Lyrics with a Shell Script, Part II

How to hibernate Fedora

How to use syslog-ng to collect logs from remote Linux machines

xsos : a tool to read sosreport in RHEL/CentOS

Rocking the docs: improving Mycroft's documentation

Getting started with automation: 6 tips

Mozilla Marketing Engineering & Ops Blog: Kuma Report, December 2017

We have a lot of things we have to do in Q1 2018, such as the CDN and Django 1.11 update. We postponed a detailed plan for 2018, and instead will spend some of Q1 discussing goals and priorities. During our discussions in December, a few themes came up. For the MDN Web Docs product, the 2018 theme is Reach. We want to reach more web developers with MDN Web Docs data, and earn a key place in developers’ workflows. Sometimes this means making developer.mozilla.org the best place to find the information, and sometimes it means delivering the data where the developer works. We’re using interviews and surveys to learn more and design the best experience for web developers. For the technology side, the 2018 theme is Simplicity. There are many seldom-used Kuma features that require a history lesson to explain. These make it more complicated to maintain and improve the web site. We’d like to retire some of these features, simplify others, and make it easier to work on the code and data. We have ideas around zone redirects, asset pipelines, and translations, and we hope to implement these in 2018. One thing that has gotten more complex in 2017 is code contribution. We’re implementing new features like browser-compat-data and interactive-examples as their own projects. Kuma is usually not the best place to contribute, and it can be challenging to discover where to contribute. We’re thinking through ways to improve this in 2018, and to steer contributor’s effort and enthusiasm where it will have the biggest impact.

Retained Display Lists

As part of the lead up to Firefox Quantum, we added new telemetry to Firefox to help us measure painting performance, and to let us make more informed decisions as to where to direct our efforts. One of these measurements defined a minimum threshold for a ‘slow’ paint (16ms), and recorded percentages of time spent in various paint stages when it occurred. We expected display list building to be significant, but were still surprised with the results: On average, display list building was consuming more than 40% of the total paint time, for work that was largely identical to the previous frame. We’d long been planning on an overhaul of how we built and managed display lists, but with this new data we decided that it needed to be a top priority for our Painting team.

Multilingual Gecko in 2017

In January 2017, we set the course to get a new localization framework named Fluent into Firefox. Below is a story of the work performed on the Firefox engine – Gecko – over the last year to make Fluent in Firefox possible. This has been a collaborative effort involving a lot of people from different teams. It’s impossible to document all the work, so keep in mind that the following is just the story of the Gecko refactor, while many other critical pieces were being tackled outside of that range. Also, the nature of the project does make the following blog post long, text heavy and light on pictures. I apologize for that and hope that the value of the content will offset this inconvenience and make it worth reading.

Mozilla Marketing Engineering & Ops Blog: Kuma Report, December 2017

We have a lot of things we have to do in Q1 2018, such as the CDN and Django 1.11 update. We postponed a detailed plan for 2018, and instead will spend some of Q1 discussing goals and priorities. During our discussions in December, a few themes came up. For the MDN Web Docs product, the 2018 theme is Reach. We want to reach more web developers with MDN Web Docs data, and earn a key place in developers’ workflows. Sometimes this means making developer.mozilla.org the best place to find the information, and sometimes it means delivering the data where the developer works. We’re using interviews and surveys to learn more and design the best experience for web developers. For the technology side, the 2018 theme is Simplicity. There are many seldom-used Kuma features that require a history lesson to explain. These make it more complicated to maintain and improve the web site. We’d like to retire some of these features, simplify others, and make it easier to work on the code and data. We have ideas around zone redirects, asset pipelines, and translations, and we hope to implement these in 2018. One thing that has gotten more complex in 2017 is code contribution. We’re implementing new features like browser-compat-data and interactive-examples as their own projects. Kuma is usually not the best place to contribute, and it can be challenging to discover where to contribute. We’re thinking through ways to improve this in 2018, and to steer contributor’s effort and enthusiasm where it will have the biggest impact.

Retained Display Lists

As part of the lead up to Firefox Quantum, we added new telemetry to Firefox to help us measure painting performance, and to let us make more informed decisions as to where to direct our efforts. One of these measurements defined a minimum threshold for a ‘slow’ paint (16ms), and recorded percentages of time spent in various paint stages when it occurred. We expected display list building to be significant, but were still surprised with the results: On average, display list building was consuming more than 40% of the total paint time, for work that was largely identical to the previous frame. We’d long been planning on an overhaul of how we built and managed display lists, but with this new data we decided that it needed to be a top priority for our Painting team.

Multilingual Gecko in 2017

In January 2017, we set the course to get a new localization framework named Fluent into Firefox. Below is a story of the work performed on the Firefox engine – Gecko – over the last year to make Fluent in Firefox possible. This has been a collaborative effort involving a lot of people from different teams. It’s impossible to document all the work, so keep in mind that the following is just the story of the Gecko refactor, while many other critical pieces were being tackled outside of that range. Also, the nature of the project does make the following blog post long, text heavy and light on pictures. I apologize for that and hope that the value of the content will offset this inconvenience and make it worth reading.