readability

Do you mean the readability of the generated assembly code?

Most of my technical books are in PDF form, converting them to any other format ruins the readability, and the PDF on the kindle is terrible to navigate.

It follows the same philosophy: emphasis on readability, familiarity and maintainability, with PL research and new paradigms being non-goals.

I don't think the readability is bad at all...

It's not uncommon for form fields to be illegible on one or more of them, layout is different, readability is different.

Sure, much better build times and less problems with code readability when using Akka, Play, Spark with Kotlin instead of Scala.

The only function sacrificing some level of readability (and wich i still find quite easy to read) is the new split function.

However, while the lighter weight font is acceptable for the UI widgets, it isn't nearly as acceptable for readability of document text.

The classic Windows font renderer sacrifices accuracy for readability on low DPI displays.

You might want to use both approaches and combine them for best performance/readability.

All of that stuff about improved development time and readability and support for whatever browsers misses the mark (no pun intended) as well.

Looks like working a bit more on the font readability could be a good start as it's something that came up several times.