Is there a license that requires (or encourages) contributing back the modifications, _but only if the upstream project is open source/non-commercial_?
Htmx changes license to Zero-Clause BSD
51–60 of 120 posts
Re: Htmx changes license to Zero-Clause BSD
#52background: - over the weekend I started making the @htmx_org twitter account increasingly corporate looking - started talking a lot about MSFT, implying they were interested in htmx - someone asked if MSFT was going to buy htmx: https://fxtwitter.com/htmx_org/status/1746656784088228204 - i then put up a post about changing the htmx license, implying i was going to restrict it due to MSFT interest: https://fxtwitter.…
> the reason i did all this is for the lols Do the lols while you still can, the Trust and Safety departments at major social media companies want to extinguish funny. Everyone who does even a smidgen of memeing on the internet knows what happens when you post images of large spiders. People start talking about burning things down, like the entire building its inside of, etc. Someone posted a video where a little gir…
All reports denied. It was glaringly obvious she was a paid misinfo troll.
Re: Htmx changes license to Zero-Clause BSD
#53Earlier quoted context omitted.
Presuming that 'MIT' was a typo: most BSD-licensed software doesn't use the original (4-clause) BSD license, most are under variants: https://en.wikipedia.org/wiki/BSD_licenses
No, it wasn't a typo; the 0-clause BSD looks pretty similar to the MIT license, and from a cursory reading, it appears that the clauses are what makes the BSD license different from the MIT license. I was wondering if my reading is correct or if I've missed something.
Re: Htmx changes license to Zero-Clause BSD
#54Earlier 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?
Re: Htmx changes license to Zero-Clause BSD
#55Re: Htmx changes license to Zero-Clause BSD
#56Earlier quoted context omitted.
Yes there used to be issues with mongo (and Postgres around serializable for the matter). What are the issues in 2024?
Breaks causal consistency and a bunch of other assumptions: https://jepsen.io/analyses/mongodb-4.2.6
Re: Htmx changes license to Zero-Clause BSD
#57background: - over the weekend I started making the @htmx_org twitter account increasingly corporate looking - started talking a lot about MSFT, implying they were interested in htmx - someone asked if MSFT was going to buy htmx: https://fxtwitter.com/htmx_org/status/1746656784088228204 - i then put up a post about changing the htmx license, implying i was going to restrict it due to MSFT interest: https://fxtwitter.…
Re: Htmx changes license to Zero-Clause BSD
#58Re: Htmx changes license to Zero-Clause BSD
#59Earlier quoted context omitted.
Your lack of professional seriousness is truly astounding. One of the primary reasons we've gone with React/NextJS coupled with MongoDB and Kubernetes over HTMX
Talks about lack of professional seriousness. Goes with MongoDB. Sometimes reality writes the best jokes.
Re: Htmx changes license to Zero-Clause BSD
#60I'm curious, what exactly would a VC or MSFT want with htmx? Just talent? or the actual product/tech?
MSFT might want it because it's gotten a lot of attention lately (finished #2 in https://risingstars.js.org/2023/en#section-framework for 2023) and would give them a front-end library in the game w/ React, Vue, Svelte, etc. On the other hand, i've made the social media account pretty toxic/funny (same thing) for a big tech company and now the library is 0BSD, and htmx's agnosticism towards back end tech doesn't really dovetail w/ the Microsoft ethos.