DuckDuckGo donates $25k to the Perl and Raku Foundation • Hacker News Board

Re: DuckDuckGo donates $25k to the Perl and Raku Foundation

#211

Post by raiph » Mon, Dec 09, 2024, 10:24 PM UTC

sneak wrote: post #185

graemep wrote: post #102

Earlier quoted context omitted.

You can also do things like dual licensing. GPL or Affero GPL plus proprietary license. Of course this puts off outside contributors so not if you want a "bazaar" development mode—but people complaining about this are usually not doing so.

First off, the AGPL license is nonfree (and also nonsensical, it is a EULA pretending to be a license), but more importantly, dual licensing means that you don’t actually believe in software freedoms. If you think users have basic and fundamental rights to the software that they run on their computer, you would never release software under proprietary licenses. It’s like Microsoft’s VS Code nonsense where all the imp…

> dual licensing means that you don’t actually believe in software freedoms

If both licenses are accepted by essentially everyone as inherently fully free software licenses, and they don't contradict each other, then what's not to like?

Consider the appropriate example here, which isn't anything to do with AGPL (which many people do NOT accept as a free software license), but rather the AL2 / GPL pairing which was the evolution of the original pairing created by the inventor of dual licensing (Larry Wall).

What's your beef with Artistic License 2.0 / GPL dual licensing?

Re: DuckDuckGo donates $25k to the Perl and Raku Foundation

#212

Post by shagie » Tue, Dec 10, 2024, 5:54 PM UTC

kazinator wrote: post #209

shagie wrote: post #114

Earlier quoted context omitted.

https://news.ycombinator.com/item?id=6959326 > Scala feels like the Perl of the modern era: there is more than one way to do it. There is value in that mode of thinking, and Perl is a better language than people give it credit for. https://news.ycombinator.com/item?id=2603425 > This actually is one of my frustrations with Scala, too many right ways to do the same thing. Makes it easier to write but harder to read esp…

> people talking about having to learn a new LISP (or Scheme) each time they switch to a different company. Which people, where? Do you have a URL to a discussion? I've not seen heard or read such talk almost 25 years of being involved in open source Lisp. Needless to say, I've often seen such narrative repeated by programmers not working in Lisp, who heard it from such others. Someone talking about any industry work…

It's a browsing about https://wiki.c2.com/?WhyWeHateLisp

And that does get into the "25 years ago" area. Really neat place to browse and see as a historical record of discussion from back then.

The issue is that languages that allow/encourage writing domain specific languages within the environment leads to people doing exactly that - writing a DSL that is then used in that company.

Lisp, Ruby, Groovy, Raku (possible in perl 5 as demonstrated by https://metacpan.org/dist/Lingua-Romana-Perligata/view/lib/L... )...

These languages (and Scala too) allow for writing a dialect of the language that differs substantially from the main language.

I've seen it in ruby. I've personally done it in groovy (wrote categories to make certain reports easier to write)... twice (also wrote a DSL in groovy that matches the script used as input for powershell doing ftp so that instead of `ftp.ps1 script` it looked like "add this import to the top of the script and do `groovy script`")... for that matter gradle is a groovy script that has gone well beyond groovy as a DSL.

Just as the problem existed with "having to learn a new LISP dialect" 25 years ago, many times going from languages that allow for such flexibility in how its written from one shop to another have the "having to learn a new {language} dialect" today.

For code that I have to work on with someone else, I believe it is better/easier to work in a language that doesn't allow you to rewrite the language so that when I have to work with yet another person, they don't need to learn a completely different way of doing it from what they knew previously.

Re: DuckDuckGo donates $25k to the Perl and Raku Foundation

#213

Post by renewiltord » Wed, Dec 18, 2024, 7:02 PM UTC

samus wrote: post #208

renewiltord wrote: post #146

Earlier quoted context omitted.

Bug reports are other people doing work for me. I’m fine with that. These are free interactions between people. If you want to charge for bug reports then you can put that in your repo text and just auto-close any issue from non-approved authors. If you want to bountysource a solution do that. If you don’t want to fix an issue don’t.

Filing a bug report is only half of the work. The bug then has to be reproduced, fixed, tested, documented, and rolled out. Sometimes with a deadline. If that sounds fun to you, I really cannot argue against it. Usually, that is part of a support contract, and therefore hobbyist open source developers basically supply free labor to for-profit companies.

You don't have to fix bugs. They can remain bugs. Deadlines are other people's problems.