Datastar's ideas look wonderful, and I've thought of adopting it myself, but hobbling the open source version to not compete with pro this early on sounds like a fast ticket to a hard fork. It's not like they command a vast ecosystem that would be reluctant to switch.
[edit: Seems like the model with an open core and some closed plugins could work out fine. If not, everyone's got options. Wishing success for both the D* developers and the users.]
> sounds like a fast ticket to a hard fork.
Indeed! Could you do us all a favour and fork the pre-pro plugins and make them compatible with the current iteration of d* pro? They're all like 50 LOC, after all, so should be simple.
Were I so inclined, I'd make them compatible with non-pro. And more likely just take my fork in whatever direction I cared to, just keeping the wire format compatible (and likely negotiable). But it's a project best left for people actually using Datastar, not curious onlookers like me.
Given the simplicity of doing such a fork, and that no one has done it yet, perhaps this is a non-issue?
Same as my other comment, it seems like you are involved in the project. Stop responding like this is facebook or reddit. Here we offer our expertise with all good intentions. They haven't said it is a simple task, you are assuming that they said that.
If you can't take constructive criticism or even respond to opinions you disagree, then it is better to not respond at all, because it is bad PR.
I understand that maintaining a project like this is hard, that you need to be compensated and that open source corporate usage tends to be disgraceful. But that's not what they are telling you. They are just shating their opinion, which is part of your potential customer opinions.
Share the rationale behind paywalling common features. Give us, if you have to respond, why you hide the pro features off the homepage, etc. Instead of this kind of childish reaction that adds nothing
I'm a user of datastar, nothing more. And I'm defending the developers against all of the baseless slander here.
And now Im forced to defend myself against your baseless slander. If you cared to read, you'd see that I said it was a simple task to update the pre-pro versions of the tiny plugins to be compatible with the current api, because it would be. And they replied on that basis.
The rationale has been shared many times - here and elsewhere. And the pro features are not "hidden" - they're right there in the header. And it's not for any nefarious reason - precisely the opposite, in fact. They don't want to appear to be flogging something. Similarly, they don't advertise any of the pro features as being free, anywhere.
But, I brought this all up with the devs earlier and suggested they add a small link or banner or something to the pro license and they said they would. But not because it's a good or necessary idea, but instead just so all the trolls won't have even the wobbliest leg to stand on in the future on this topic.
Please take some constructive criticism - you have no idea what you're talking about here, in any regard. It is childish. Please inform yourself in the future, especially when you want to try to correct someone.
"Hobbling" is too strong a word. There's a handful of attributes and events that are only available in Pro and none look fundamental to the operation of most sites [1]. In fact they could all probably be replaced with a bit of custom JS sent up from the server.
[1] https://data-star.dev/reference/datastar_pro
Please do! I highly recommend doing that, PLEASE FORK
I have already seen a few of your responses to criticism coming up toxic like this. They don't need to fork it, but some of your potential customers could. They are explaining to you their opinions, and in HN, this is very valuable.
Most of us have some decision at companies, which are your real customers, and criticism like I've seen you respond boldly and badly, is the criticism I think you should review and take into account.
Personally, I like everything of the pro, except the features that you decided to exclude. Doesn't seem pro features, but features you ramdomly decided not to open source them, and that could be ok. But instead of doing it like this, maybe put a restrictive license so that companies with more than 5 people have to pay.
But I think you should focus on premium/pro features that are really a plus, like your debugger, the bundler, etc. And find features that aren't common and give a plus.
And it is an opinion which you may disagree with, but if you respond to me, don't do it like that, because to me, it is not professional and I'll tend to avoid doing business with people that respond like that