Bit like Pydantic. It's a JSON parsing library at the end of the day, and now suddenly that's got a corporate backer and they've built a new thing
Polars is similar. It's a faster Pandas and now suddenly it's no longer the same prospect.
FastAPI the same. That one I find even more egregious since it's effectively Starlette + Pydantic.
Edit: Add Plotly/Dash, SQLAlchemy, Streamlit to that list.
SQLAlchemy just has paid for support, I shouldn't have included it with the others, I must have confused it with something else.
Interestingly, this article pops up first page if you search "htmx vs datastar".
For such reasons, The Economist style guide advises against using fancy language when simpler language will suffice.
I don't really have much of a response beyond this.
You're of course free to do it, just as I'm free continue to use other products which do not do this.
Seems to fit in with your world view better and then I can just leave those people high and dry with much less concern!
You're not owed these people's time.
If the point is good stewardship of the product, deleting features that users clearly need only to replace with a for-pay version stinks possibly only slightly less than deprecating features users clearly need and then replacing with nothing. Both of these things mean your product sucks.
For a proper way this would work, you the user would contribute your time for those features so you don't overburden the maintainer, but people like you won't and so this is where we're at.
I'd rather avoid burnout (which will kill a project entirely) and lose a few folks like you.
Sure, if you're up front and honest from the beginning then some users will do that, the majority are likely to go for other offerings which don't suffer this problem. Vanishingly few users are going to be cool with features disappearing and then reappearing later on with a price tag attached, which is the scenario we're talking about.
In reality, 99.9% of the users are going to be using whatever free thing is available and your project will live for just about as long as you personally care about it. Rightly or wrongly, the maintainer's work/life balance isn't on the forefront of your mind when you're looking at npm packages, no amount of grandstanding will change that.
I dont know what world you live in where you can be entitled to something you dont pay or contribute to.
They can do whatever they want to ensure their project works and frankly once again the projects dont need people like you. You’re not that important or special at all, certainly less so than the people building things. Like I get that you really think you are it’s dripping from your comments, but you’re not.
And to be clear this was a discussion among their community it wasnt a sudden thing so your entire premise is wrong.
I don't have a problem, on principle, with paywalling new features. I don't like it, but I don't think it's bad behaviour.
Putting up a paywall around features that were previously free, however, I do take issue with. It's deceptive and it's not common practice. It tricks people into becoming invested and then holds hostage the features that they've become invested in using. Frankly, fuck that.
Fuck me buddy, no fuck you GUY. I'm not your guy pal.
That said, the attitude of the guy in the article is really messed up. Saying "fuck you" to someone who gave you something amazing for free, because he's not giving you as much as you want for free -- it's entitled to a toxic degree, and poisons the well for anyone else who may want to do something open-source.