That’s perfectly fine for some things, but for most people letting their browser choice dictate what sites they use is backwards
That’s perfectly fine for some things, but for most people letting their browser choice dictate what sites they use is backwards
Did you forget the ./s or something? Lemmy itself is developed on GitHub, as are plenty of other “valuable” open source projects. To pretend nothing of value is built there is putting your head in the sand.
If you’re developing software on GitHub you have a chance at getting some useful feedback, bug reports and maybe even PRs. Like it or not, the network effect is real.
Future Idiots.
Patent Pending.
Or maybe the 512kb.club a more reasonable balance between 250 club and the 1mb club.
Also with a view: jankfree.org for a similar focus on performance.
Yes. You can. I have a personal site that is using nuxt static site mode and it renders extremely fast and clean output.
Check out https://250kb.club all performance sites focused on speed and small size.
We need caldev through the bridge app for use in thunderbird and other apps.
Check out Avalonia. It’s like cross platform WPF. Not winforms, but still pretty good and easy to start with.
I mean, I can fix them, but not because I’m a programmer. Makes it hard for normies to understand the difference.
I think if you look at your average “package” from GitHub, that is published to npm, nuget, or the associated language rep, by and large they’re not making any money.
Sure big projects are making money and have paid development teams, but that’s not true at the individual library level in many cases.
Wait, are you seriously overlooking ASP.NET and suggesting c# tes learn typescript and node to build web apps?
I get that it’s a hypothetical, but typescript and node shouldn’t be the first stop on the we need to build a web page train for folks already in the c# wagon.
I felt like I had a good understanding of both htmx and csp, but after this discussion I’m going to have to read up on both because both of you are making a logically sound argument to my mind.
I’m struggling to see how htmx is more vulnerable than say react or vue or angular, because with csp as far as I can tell I can explicitly lock down what htmx can do, despite any maliciously injected html that might try to do otherwise.
Thanks for this discussion 🙂
Can you elaborate on that? I haven’t used it, but just assume if you host it on your own domain you can have it play nicely with csp, there are docs in their site about it. Where did it fall short for your use case?
That sounds awful. Imaging going back and forth requesting changes until it gets it right. It’d be like chatting with openai only it’s trying to merge that crap into your repo.
Win-win.
I see what you did there.
That’s basically how it happened.
While I completely agree with you about electron, I still don’t have to enjoy the fact that companies are outsourcing their lack of development in native tech to my wallet in terms of wasting resources on my device. Now perhaps the cost of the associated services would be higher if they had a native app which is a fair response. I still don’t have to like it.
Written as a user (and occasionally enjoyer) of electron based software.
Is that because of the extension marketplace? Or the fact that the debugger has always been closed source?
That’s exactly what happened to me too. It was in the background until something disrupted my status quo and then there was no looking back.
I’m sure there are projects covering those areas written in JavaScript.