Top all-time · #7522
Aseprite Devblog
Company blog · dev.aseprite.orgprogrammingdesign
Aseprite Devblog is the company blog at dev.aseprite.org, writing about programming and design. Since 2016, 11 different Hacker News readers have linked it 12 times, most often “Aseprite's source code license change from GPLv2 to EULA (2016)”. The last post was in 2018, but the archive is still widely read.
Too few sampled comments (9) to say how often HN recommends it.?
Why HN links it
Commenters link the Aseprite devblog's 2016 post announcing its new source-code license, cited to explain that Aseprite is source-available rather than open source. One commenter calls it recommended reading.
Summarised by Claude from a sample of 9 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Animated sprite editor & pixel art tool
Most-linked posts?
- /2016/09/01/new-source-code-license/8 people · 8 mentions · first linked 2018-06-19
- Aseprite's source code license change from GPLv2 to EULA (2016)2 people · 3 mentions · first linked 2018-06-19
What Hacker News says?
They switched from GPL in 2016: https://dev.aseprite.org/2016/09/01/new-source-code-license/
Comment linking /2016/09/01/new-source-code-license/
on “Mindustry: Open-source automation tower defense game”Submitted Aseprite's source code license change from GPLv2 to EULA (2016) as a story · 3 points
HN discussionAs of version 1.1.8, Aseprite is source-available proprietary software, not open source: https://dev.aseprite.org/2016/09/01/new-source-code-license/
Comment linking /2016/09/01/new-source-code-license/
on “Richard Stallman – The state of the Free Software movement”Submitted Aseprite development: new source code license as a story · 1 points
HN discussionMore fully explained here : https://dev.aseprite.org/2016/09/01/new-source-code-license/ The license and FAQ are somewhat confusing as to if you need to pay for a license even if you compile from source.
Comment linking /2016/09/01/new-source-code-license/
on “How to pay your rent with your open source project”Asesprite is is shared source, not open source. https://dev.aseprite.org/2016/09/01/new-source-code-license/ https://bugs.debian.org/864990 https://github.com/aseprite/aseprite/blob/main/EULA.txt https://opensource.org/osd
Comment linking /2016/09/01/new-source-code-license/
on “How to pay your rent with your open source project (2020)”Nobody "turned free software into proprietary software". He released some free software, then later he released other non-free software. He also explained his reasoning[0] - that developing the project as FOSS wasn't working out, for specific reasons he goes into, so he needed to try something else. Honestly, this kind of thing is the ugly side of FOSS culture. I get why you were hoping he'd continue under the old l…
Comment linking /2016/09/01/new-source-code-license/
on “LibreSprite – fork of last open-source release of Aseprite pixel art editor”Yeah, that usually happens. However, the sway creator (SirCmpwn) is doing surprisingly well; having received $5,480 for his sway crowdfund[1] and getting over $500 per month in donations if my math is correct.[2] That's not really that much, but it is surprisingly much for a single open source dev. I'm not sure if it's the community or the fact that he works on a bunch of different projects, but given that Krita was…
Comment linking /2016/09/01/new-source-code-license/
on “LibreSprite – fork of last open-source release of Aseprite pixel art editor”EDIT: The author's post from 2016.09 outlining the background of his decision: http://dev.aseprite.org/2016/09/01/new-source-code-license/ Super recommended reading! --------- It's not clear to me if you're aware, but aseprite's author actually had a very interesting approach to monetization already live for some time, AFAIK. Namely, code was GPL, but official Windows binary builds were paid-only. I found it ingenio…
Comment linking /2016/09/01/new-source-code-license/
on “LibreSprite – fork of last open-source release of Aseprite pixel art editor”Sorry, this doesn't really help people who have no idea what Aesprite is or why it's suddenly an issue https://www.aseprite.org/ , looks like a really nice pixel art editor / sprite editor. The author needs to eat, therefore relicense (I think). It seems like this is the crux of the matter: https://dev.aseprite.org/2016/09/01/new-source-code-license/ and https://github.com/aseprite/aseprite/issues/1666 https://githu…
Comment linking /2016/09/01/new-source-code-license/
on “LibreSprite – fork of last open-source release of Aseprite pixel art editor”https://dev.aseprite.org/2016/09/01/new-source-code-license/ Here is the actual information. and a quote from it "Aseprite is non-free software from now on"
Comment linking /2016/09/01/new-source-code-license/
on “Creating Pixel Art (2010)”Usually when people use the term "open source", they'll be referring to an OSI-approved definition. I do distinguish between open source (lowercase) and Open Source (uppercase) but I'm in a minority on that point, most of your readers won't. In general, "source available" or "shared source" are terms that will lead to less confusion in situations like this. In terms of proprietary licenses, Aseprite is very good. It…
Comment linking /2016/09/01/new-source-code-license/
on “LibreSprite is an open source program for creating and animating your sprites”
