171–180 of 298 posts
Earlier quoted context omitted.
So your answers is no, you cannot provide any arguments.
The poster provided an example of poor abstraction. HTML for display, JS for client side logic. Combining them is part of the problem with other popular frameworks.
Which is weird, because this is (was?) the predominant way to make websites for decades.
Earlier quoted context omitted.
> 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.
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…
Earlier quoted context omitted.
i went looking for pricing info and it's the last item in the last menu on the website... it's not exactly up front. i was looking for a "pricing" top-level menu item first, which is pretty standard nowadays.
As ive said in many other comments - YOU DO NOT NEED PRO. The devs are very adamant about this - even aggressively so. 99% of apps will work just fine with the free library. Pro is for some bells and whistles, or just to support people who have invested many thousands of hours into making a genuinely innovative framework, and given it away
Earlier quoted context omitted.
I appreciated it. If I'm going to consider a framework I want to know if some of it costs money. Especially like 299usd. Frankly your response seems very hostile and makes me wants to avoid them more.
What a world we're living in - I point out that a hostile comment is hostile, and I'm labeled hostile. Once again, they aren't charging anything. Pay them if you want some largely-unnecessary features, or if you just want to support years of hard work and innovation. That's what I did. But you do you.
Earlier quoted context omitted.
If you're amenable to feedback, the impression I got from your initial comment was "a hostile comment pointing out another hostile comment". It assumed a negative motivation on OOP based on vibes and you ran with it. Even this comment's parting line: > But you do you. - seems like a truism. I get the feeling it's meant to be read as "I give up. You can keep whatever wrong viewpoint you have".
Finally a good-faith reply! I concede that my original comment here was somewhat hostile, but only really the first line. And it wasn't even all that hostile - especially when the rest of the comment was really just informative and positive about datastar. And, moreover, is standing up to poor behaviour - even if done in a somewhat hostile/confrontational way - really such a bad thing? It seems quite clear to me that…
Plenty of other open source projects make money without attracting this kind of negative feedback. It's curious to me that you suggest everyone is intentionally being negative or malicious here, instead of looking at why the project caused such a response.
Earlier quoted context omitted.
And yet, most frontend frameworks barely on even the simplest of sites. This is not only well documented, but most of them have now moved towards some sort of SSR hybrid - at great complexity cost.
>This is not only well documented Please, I'm begging you to share this "well documented" fact that most frontend frameworks barely "handle" on the simplest of sites.
https://infrequently.org/2024/11/if-not-react-then-what/ (there's MUCH more at this site as well)
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…
Earlier quoted context omitted.
Which feature are you referring to?
not the OP, but a lot of the referenced functionality looks like I might use it. The problem is I'm not going to bother trying this and investing any effort with even the looming possibility I'll need to pay to keep going. I don't think too many people approach this space with a purchase evaluation mindset like say, "I'm going to test out this grid to see if we should buy it". In that case pay-for advanced functional…