Live data from Hacker News

Htmx changes license to Zero-Clause BSD

github.com

111–120 of 120 posts

Re: Htmx changes license to Zero-Clause BSD

#111

Earlier quoted context omitted.

It was mainly as a joke, but I wanted to remove the attribution clauses, they just seemed dumb for a single-file javascript library that was probably going to be minimized anyway, where are you supposed to stick the license?

Some companies are careful to include all the libraries' licenses when minimizing JavaScript code. There are tools to do it. But it seems wasteful, so it's great that you removed the requirement.

I'll bet $10 that the compressed size shows no discernible difference.

Re: Htmx changes license to Zero-Clause BSD

#112
post #19

Earlier quoted context omitted.

it eschews attribution, making it just about the closest thing to a public-domain dedication that still retains the appropriate verbiage to hold up to legal scrutiny

In the US, simply saying "I hereby dedicate this work to the public domain." is as an effective, if not more effective, way to do that as any license. These licenses are just for countries like Germany that basically make it illegal to sell, gift, or release a copyright at all.

It's great feature that we don't need consider where authors locate

Re: Htmx changes license to Zero-Clause BSD

#113
post #6

This made me wonder what the shortest open source license is, and it seems to be the Fair License: https://en.wikipedia.org/wiki/Fair_License > > > Usage of the works is permitted provided that this instrument is retained with the works, so that any entity that uses the works is notified of this instrument. > > DISCLAIMER: THE WORKS ARE WITHOUT WARRANTY. EDIT: I would not use this license. I'm not sure how this got a…

If you want statistics about license texts, many years ago I had published a peer-reviewed article:

Zavras, Alexios. Twenty-five years of school? Analysis of Free and Open Source software license texts. Journal of Open Law, Technology & Society, [S.l.], v. 8, n. 1, p. 29-44, nov. 2016. ISSN 2666-8106. Available at: https://www.jolts.world/index.php/jolts/article/view/111>.

Re: Htmx changes license to Zero-Clause BSD

#114
post #37

I hadn't seen Zero-Clause BSD before: https://opensource.org/license/0bsd/ > Note: Despite its name, Zero-Clause BSD is an alteration of the ISC license, and is not textually derived from licenses in the BSD family. Zero-Clause BSD was originally approved under the name “Free Public License 1.0.0”. Anyone seen a good write-up of the tradeoffs for this license? I like how short and simple it is.

It's a nice license when you don't want to burden users of your software with providing attribution. A typical use case is for stuff that will be included in many different projects, while not being a crucial part of it.

For example, all the code snippets in the Intel Software Developer Manuals (https://www.intel.com/content/www/us/en/developer/articles/t...) are licensed under 0BSD, so that people can easily re-use them (with or without adapting them).

Re: Htmx changes license to Zero-Clause BSD

#115

I use the zero clause licence for my all my work because it just removes all the overhead of using my code. I think (please correct my understanding) zero clause BSD can be embedded in a GPL project too, it just becomes one-way included, subsumed into the GPL project and then under the GPL licence. (Relicenced) Could the author of HTMX explain their reasoning for changing the licence? I am curious?

It was mainly as a joke, but I wanted to remove the attribution clauses, they just seemed dumb for a single-file javascript library that was probably going to be minimized anyway, where are you supposed to stick the license?

Thank you for this!

It lifts a significant burden for people/projects/organizations who want to release software while complying with all license obligations.

Re: Htmx changes license to Zero-Clause BSD

#116
post #18

Earlier quoted context omitted.

what does the fx in fxtwitter.com mean?

since the WHOIS states it's DNS servers are hosted by cloudflare (twitter is hosted by twtrdns.net) it seems to be a "fuck x - twitter.com" forwarding domain. Maybe also with some tracking to see how many people clicked the link but that's just speculation

[deleted]

Re: Htmx changes license to Zero-Clause BSD

#117
post #37

I hadn't seen Zero-Clause BSD before: https://opensource.org/license/0bsd/ > Note: Despite its name, Zero-Clause BSD is an alteration of the ISC license, and is not textually derived from licenses in the BSD family. Zero-Clause BSD was originally approved under the name “Free Public License 1.0.0”. Anyone seen a good write-up of the tradeoffs for this license? I like how short and simple it is.

This is handy but might not classify as a "write-up".

https://www.tldrlegal.com/

Re: Htmx changes license to Zero-Clause BSD

#119

Earlier quoted context omitted.

Mongodb was/is for a long time inconsistent. You had to worry loosing data when using mongo. And everything mongodb brought us, was either implemented by someone else better or already existed. If you use mongodb today, just go with postgres and forget about mongo

Yes there used to be issues with mongo (and Postgres around serializable for the matter). What are the issues in 2024?

Why giving something a chance when you can just use postgres?

Re: Htmx changes license to Zero-Clause BSD

#120

Earlier quoted context omitted.

I thought "I can't speak to its current state" explained that I could not, in fact, speak to its current state. But when it comes to databases, which are often the single most important part of an architecture, you'll find that many people are less forgiving of old sins, especially when Postgres now has native JSON support. Much like I won't trust Uber with my location, or Google with my email, I won't trust Mongo wi…

Why even reply if you don’t know what you’re talking about in terms of current mongo? Not sure what Postgres or Uber or Google even has to do with this. FYI using mongo is more than simply wanting a json interface.

Does this proverb sound familiar?

"Fool me once, shame on you; fool me twice, shame on me."

Maybe MongoDB is great now. That doesn't change the fact that many people have been burned by MongoDB.

But, perhaps we can let maybe we can let bygones be bygones if we can determine that MongoDB is solid and dependable now. How do we make that determination?

If we decide that MongoDB is now robust based on present popularity and general satisfaction, that's fallacious reasoning:

https://yourlogicalfallacyis.com/bandwagon

After all, there was tons of stoke about MongoDB early on, only for people to realize later that their data was being silently nuked, which is why there is such a grudge against MongoDB in the first place. If an appeal to popular belief is proof, then we have a paradox.

Not everyone has the time and skill to thoroughly analyze MongoDB like Kyle Kingsbury / Jepsen:

https://jepsen.io/analyses/mongodb-4.2.6

And even then, there are so many other databases that have a better track record, so it would be hard to argue that the effort would be worthwhile.

I don't see how you're struggling with the notion of reputation here.

Maybe bias in favor of MongoDB is too strong? If that's the case, one last ditch effort:

If your friend's dog has gruesomely bit you 10 out of the last 10 times you've visited him, but he swears the dog is now rehabilitated, do you just shrug off being bit over and over again, and visit your friend without even the slightest apprehension? Or do you, at the very least, remain hypervigilant, given you're history with the dog?

Now replace "dog" with "MongoDB", and replace "bite" with "invaluable production data being absolutely eviscerated, resulting in your customer's lost trust and also immeasurable financial harm being done to you and your family".

Post reply on HN