0xblinq

6 ms·

61.
by 0xblinq 1y ago
Exactly. I remember that at the time, the alternative was the nightmare of setting up tomcat, Jboss, etc and dealing with all that bullshit. Thanks God most of us didn’t have to deal with that enterprise crap for long, and in my case it was
62.
by 0xblinq 1y ago
Facebook entered the chat
63.
by 0xblinq 1y ago
I agree with your opinion on vercel and next. But if HTMX is enough for your project, then your problem was picking the wrong tools from the get go. You didn’t even need react. They’re very different tools for very different kinds of UIs an
64.
by 0xblinq 1y ago
Don’t bet on it. Nobody can resist a big pile of money. Everyone has a price.
65.
by 0xblinq 1y ago
This would be true if you also provided an adapter-node, which would work on most traditional servers, and most non-serverless platforms. The fact that you prioritize the vercel one and not the node native one proves what OP implies in my o
66.
by 0xblinq 1y ago
It’s a mess because there’s no first party, properly thought out and working solution. So every year we get a new “new way” to do it. Like that xkcd… this time this is the standard that will work!
67.
by 0xblinq 1y ago
2025 and python packaging and dependencies management is still a mess.
68.
by 0xblinq 1y ago
Hooks were introduced in 2018. We're in 2025. It's not 10 years yet, but we're pretty close to that. Yes, time flies.
69.
by 0xblinq 2y ago
That's a great project! I'm definitely going to give it a try.
70.
by 0xblinq 2y ago
It’s major version 2. Compare that to the amount of major (and really breaking, like Vue) for all other frameworks. LOL
71.
by 0xblinq 2y ago
Solid is so underrated. The simplicity and the power it brings is so good. I’ve also used SolidStart for a project and it’s by far the best meta framework I’ve tried so far. Again, simplicity, power and extensibility.
72.
by 0xblinq 2y ago
I don’t get why anyone would use Svelte to be honest (other than because of the hype/marketing). If you like template like syntax and single file components the. Vue provides the same benefits, with a bigger ecosystem and better team b
73.
by 0xblinq 2y ago
Totally agree. We used it for a customer's medium size project and we ended up regretting it. We're now using Solid for another project, and so far we're very happy with it.
74.
by 0xblinq 2y ago
> I don't know why they're so resistant to do treat SPAs as a completely valid way to use React in 2025 Many React of the core devs work for Vercel, so they have to promote Next and anything that leads people towards their plat
75.
by 0xblinq 2y ago
For example, when the translation is shit and you prefer to use the English one because the one in your language is impossible to understand.
76.
by 0xblinq 2y ago
Thanks a lot for your effort and all the work you did to get this done. May I ask about the feedback you provided and they didn't include?
77.
by 0xblinq 2y ago
Not much to see here. Just backend developers hating on JavaScript and looking for workarounds to avoid it that will come back and bite in the neck the poor souls that will have to pick up the project after the current Go devs leave.
78.
by 0xblinq 2y ago
> I’m not against Tailwind, but I didn't used it yet because I struggle to see why it's a better approach compared to other options like Web Components or React Styled Components. > The biggest issue I have with Tailwind is
79.
by 0xblinq 2y ago
There's a clear pattern in every "Tailwind or not tailwind" conversation (which happens everytime Tailwind is mentioned). There's those that never used it for more than 30 minutes, that just tried it out or just skimmed
80.
by 0xblinq 2y ago
Well, something I do like about Inertia is that it's not tied to any specific framework, neither backend nor frontend ones. That's a big advantage in my opinion.
81.
by 0xblinq 2y ago
I think a big part of your bad experience is probably due to the django adapter which seems to be the less well maintained out of all of them. Even more, maybe it's not even the django adapter but the overal "assets" and fron
82.
by 0xblinq 2y ago
> the lack of hot-reloading is painful This works perfectly fine for me, both in the Rails and the Adonis projects. In both cases using Vite. Sounds to me like a misconfiguration somewhere. >Having to add custom code to for flash, the
83.
by 0xblinq 2y ago
I have the exact opposite experience, but context is everything here I guess. > React Router is excellent. When you compare it to Next, etc... yes, I agree. The issue I have is the constant change of mind their devs have regarding how to
84.
by 0xblinq 2y ago
Check out https://inertiajs.com/ . I've never used it with Django (there's an adapter here https://github.com/inertiajs/inertia-django ) but I did use it a lot with AdonisJS and Rails. It'
85.
by 0xblinq 2y ago
I will never understand how is it possible that htmx has become more popular than Unpoly, when Unpoly exists since a long time ago, has been very stable, has a lot more features, it has a nicer API, better docs, etc. I just don’t get it.
86.
by 0xblinq 2y ago
Inertia is a godsend. We are using it at work and it’s such an amazing combination of the best of both worlds without all the craziness going on with the more popular meta frameworks.
87.
by 0xblinq 2y ago
> Then you can hydrate with React and manipulate as needed. This is what NextJS does. :facepalm: Tell me you're a backend developer with little to no experience on this stuff without telling me you're a backend developer.
88.
Inertia 2.0 Released(blog.laravel.com)
1 points by 0xblinq 2y ago|0 comments
89.
by 0xblinq 2y ago
> or you need to do SSR. This approach doesn't work if you need to SSR any of the content of those components. This is also a terrible solution UX wise. Your users will see some content and after some time (more or less noticeable,
90.
by 0xblinq 2y ago
+1 I’ve used it in a largeish project and I liked it a lot. I rally hope I never have to deal again with redux or sagas

More ›