151–160 of 298 posts
Seems pretty elegant if you are willing to give up on the type safety of TSX. I wonder if this can be combined with it somehow. An example using Fresh would be great.
Earlier quoted context omitted.
I understand it sincerely. Is there some middle way that I could use these datastar attributes/paid offerings via lets say 5$ but I wouldn't get support from the team itself. I think that they might have a discord server as well and so I am more than okay to take support from the community itself if I can be honest... Simply because like me and others, we simply can't pay 299$ when we don't require support. Could ano…
There are so many issues with doing something like this that it's almost never going to be financially viable for small companies. - Some jurisdictions require some level of warranty, extended refund periods, or limit your ability to avoid liability for product defects. - You need to spend time doing research to set prices for each country or region. - You need to combat fraud from people trying to buy your product u…
Now, regarding 5-10$ payment, suppose we do a 20$ payment one time donation, they are a non profit so they can definitely do fiscal foundation but I can get it why you might not want to do that
I was discovering more about chargeback and other things like taxation as well
I found polar.sh could be a decent approach to a lot of these problems, just create a polar.sh set account and they have a github thing as well where you can allow access to any git private repo to anyone who pays and even a discord integration so you could have support through there out of the box
I think the same can be done through patreon or the likes as well from what I know
all I was trying to say was that yes I agree with your comment and I thought about it and the other comments regarding how 5-20$ wouldn't cover support but what if I don't need support, I just want the code and I can take the support through their discord server/like minded people?
I understand, I truly do, currently I read more about datastar, I have come to the conclusion that they are somewhat not necessary in the sense that I can have sse.ExecuteScript(`console.log("Hello from server!")`) and I think that it could be integrated with something like gsap if someone wants to hack through a animation thing without modifying datastar library itself as well
I still believe though that they should atleast give another optional method imo where someone can pay 20$ as an example to get the template of sorts but no support and using something like polar.sh or patreon or stripe with MOR, it should be pretty easy and well they have to realize that there might be people who genuinely can't afford this as well I suppose y'know?
I am genuinely curious what your thoughts are on why/if they can add a 10-20$ tier which just gives access to the code and no (official) support through github sponsors/patreon/polar.sh and the likes?
And maybe if someone needs support but can't afford it, maybe optionally they could ask it into their server so that like minded people could volunteer to help as well in the process?
What are your thoughts?
Earlier quoted context omitted.
Like I said, it's crucial for the developer to be fair about it. Running a sustainable business built on open source is entrepreneurship on hard mode. Some companies do a better job at this than others, and, unfortunately, open source has been abused as a marketing strategy on many occasions. No matter how you look at it, though, any business model that enables users to use open source software is a much better optio…
They're not even running a business on this - its literally registered as a 501c3 nonprofit. Its a labour of love that theyve shared with the world, and they actively tell people that the pro features are unnecessary for most projects. If you want those features or just want to support the project, the cost is quite fair, and just goes to things like traveling to do conference talks etc... They are not getting rich o…
Earlier quoted context omitted.
Both Datastar and HTMX have the same issue: they want to pretend to be HTML. So they force themselves into writing several DSLs like this to pretend that this is still "just HTML". Since they have a full "Datastar expression" language, I'd just expand that. Then you wouldn't need these weird constructs:
Well they are both "just HTML", Datastar being better about being spec compliant using the dataset attributes and all. By expanding the "Datastar expression" language, do you mean a compiled language or moving all the expressions into JS files or something else?
Doesn't matter. They literally already have a Javascript-like DSL: https://data-star.dev/guide/datastar_expressions
- this would mostly work if the sole consumer of your API is the frontend, since it returns HTML, rather than, eg JSON that would be consumed by a CLI, some streaming tools, clients, etc
- this would not really be suited to some Capacitor app?
Earlier quoted context omitted.
> exploring models This model of using deception to hide costs isn't exactly "exploring". It's tried and tested.
you're stretching the definition of deception here my guy-what do you want them to do? plaster a big sign on the landing page stating that this framework ALSO contains pro features that you have to pay for?
The common thing to do today is put a "pricing" menu item at the top right. That'd be fine.
Earlier quoted context omitted.
[flagged]
I just think you are wrong. It mostly takes mindshare from rookie developers that are insecure and need to cover all their bases lest they be called bad at being a developer. Many grow out of this insecurity and see things for what they are. TS is OKAY, but it's not worth my time.
As for productivity, maybe it doesn't matter on tiny projects or short-lived one-man projects, but for anything else I don't see how you can argue it. You basically can't refactor reliably without static types, you can't navigate the codebase quickly without static types, and it makes it more difficult to understand other people's code without static types. Sure it might take slightly longer to write in the first place but that is easily outweighed by all those other benefits. Like, by an order of magnitude.
It sounds like you are one of those "well I don't make mistakes" developers.
Earlier quoted context omitted.
This is exactly what is done here. They're emphatic that most will/should never need the pro features.
Looking at https://data-star.dev/reference/datastar_pro#pro-features the features that stood out for me as things I would want to to use (and that don't feel particularly "pro" to me) are the animation features, data-replace-url, data-on-resize, data-scroll-into-view, the @clipboard() mechanism and, most importantly, the debugging tool. My problem with this business model is that it has a chilling effect on open sour…
Earlier quoted context omitted.
not sure i think this is a good way to fund their work BUT exploring models to make open-source sustainable for the developers does seem like a good thing, no?
I have no problem with anyone charging what they would like, but I do think it should be mentioned on the homepage. It feels intentionally left off which makes me think the developers themselves aren't 100% comfortable with the model.
Earlier quoted context omitted.
I just think you are wrong. It mostly takes mindshare from rookie developers that are insecure and need to cover all their bases lest they be called bad at being a developer. Many grow out of this insecurity and see things for what they are. TS is OKAY, but it's not worth my time.
Well I'm objectively correct about it preventing bugs. This is one of the few things that has been fairly conclusively shown by studies. As for productivity, maybe it doesn't matter on tiny projects or short-lived one-man projects, but for anything else I don't see how you can argue it. You basically can't refactor reliably without static types, you can't navigate the codebase quickly without static types, and it mak…
What a great interview test. I’d absolutely not hire someone that can’t do that. It also doesn’t make any sense. That’s like saying entire codebases without types can’t be worked on. Huh? Those are basic things you can do in any language.
This Typescript anointing has got to die. It’s lame, and most of you overuse it even when it’s appropriate.