liyanage

Joined 16 years ago

Karma
927
Submissions
104
Member since
Dec 26
https://twitter.com/liyanage

my public key: https://keybase.io/liyanage; my proof: https://keybase.io/liyanage/sigs/VVA1UdmCKuSmCtF0IKLdO0Jp3V7eOikcokc538yV41g

View on Hacker News

Recent submissions

Comment · 4 years ago
Comment · 5 years ago
Comment · 5 years ago
Things like "not sure" and "I think" and "even if I'm wrong" suggests that it is not very clear what is covered and what isn't. A lawyer would probably have to sort that out.

The practical problem is that some organizations simply discourage or don't allow the use of GPLv3 or AGPL software. I don't want to learn one tool for personal projects and another for potential work projects, in case the opportunity comes up.

The easiest way to deal with that is to just switch to a tool that has a license that is more widely accepted.

Comment · 5 years ago
For me it was the license that made me not pick it: https://github.com/getpelican/pelican/issues/1397.

A while ago I was picking a new SSG and I would have preferred something written in Python so I can hack on it more easily. I ended up moving on because of the license.

I am now very happily using Hugo.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton