1. https://www.siidorow.com/master_Siidorow_Mikael_2026.pdf 2. https://aaltodoc.aalto.fi/items/e71b388a-a015-4f01-b7f9-530e...

Overall that's a good point, though, and for this reason I do this with only select few of my students. :)

That said, I see no problem in subsetting or customizing the font especially in personal context. The website even provides tooling for this purpose so it's definitely within the license since you are literally creating your own custom version on the fly.

I hope this clarifies why it seems to be a standard clause for fonts.

In his MSc thesis, my student Mikael Siidorow looked into the space to find out the limits of generalized sync. He did his study through multiple methods including literature review, interviews, and a case study. In the end he came up with a taxonomy showing where generalized sync breaks and what you have to keep in mind when implementing these solutions.

This is not to say sync engines are useless, but that there are clear tradeoffs to consider when introducing them to your codebase especially if you have to deal with an offline requirement.

Comments URL: https://news.ycombinator.com/item?id=48655381

Points: 19

# Comments: 9

Since then we've released a variable v2 (2022) and now we're happy to expand the typeface with a new family called MonoLisa Text. The reasoning was to cover *other* use cases beyond coding with this proportional font.

We hope you give Monolisa a go as there's a free trial to try. We also welcome feedback!

Comments URL: https://news.ycombinator.com/item?id=48630318

Points: 184

# Comments: 86

For the next paper, I plan to have a look at a couple of disappearing frameworks in detail. Let me know if you have special requests on what to research. :)

Today, we're launching a new monospaced font called MonoLisa (https://monolisa.dev) to the public.

After Marcus saw me (Juho) and Andrey working, he was curious about the fonts we use. In programming, we're stuck with the monospaced format as code has to align to a grid in order to be readable. For a font designer, that's an interesting constraint as you'll have to make compromises to fit the format.

Roughly two months after our initial chat, Marcus came back to us with a font he called MonoLisa. It was a starting point for a collaboration results of which you see here.

To deal with the size constraint, Marcus did something interesting. Instead of going with the regular character width you see in monospaced fonts, he went 7% wider. The small change has implications for the design because now you can:

* Design characters such as m and w to be more readable.

* Be more careful with the space. Marcus went for a balanced design so both dark and light part of the font is roughly equal per character.

* Put more emphasis on terminals (the ends of a glyph) to make sure they are both distinct and they flow to each other.

Although the font is a little bit wider than what you might have been used to, in practice it's not a big deal as these days displays are wider as well. I feel Marcus did a good choice there and it shaped the font and it stands as something unique compared to the others.

Now, after a year of effort and collaboration we're happy to launch MonoLisa after private testing and rounds of feedback. You can test the font online and learn more about it at https://monolisa.dev.

Feedback is welcome (comment below or send us mail, info@monolisa.dev)- I hope you enjoy using the new typeface!

Comments URL: https://news.ycombinator.com/item?id=22535174

Points: 12

# Comments: 2

Comments URL: https://news.ycombinator.com/item?id=13985332

Points: 2

# Comments: 0

In short, it's definitely possible to earn a living out of technical writing. Getting started is the hardest part. If you don't have a reputation, you will need to build one. Growing audience will take time, but it will pay dividends.

To keep this comment short, I'll just link to a series of articles (and presentation slides) I've written about my experiences. Hopefully these help! Here we go:

* http://agile.fi/survivejs-writing-a-book-in-a-lean-way/

* http://survivejs.com/blog/succeed-at-technical-books/

* http://survivejs.com/blog/survivejs-interview/

* https://survivejs.github.io/how-to-write-a-book-and-survivej... (Chrome works the best)

Best of luck!

Comments URL: https://news.ycombinator.com/item?id=11152535

Points: 3

# Comments: 0

I just published a new version of SurviveJS. Feel free to ask anything about the effort. :)

Comments URL: https://news.ycombinator.com/item?id=10651576

Points: 11

# Comments: 0

I feel adding vocabulary like this to a system can help with understandability. That's the point I made with a "feature". It's something that could fit between views and components.

Atomic design (http://patternlab.io/) is close to this idea.

Comments URL: https://news.ycombinator.com/item?id=10253973

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=10216606

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=10031265

Points: 1

# Comments: 0