0xblinq

13 ms·

211.
by 0xblinq 3y ago
We are using Remix at work. We are super happy with it. None of the nonsense artificial limitations of Next, great integration with express, and a really simple model which, if you ever used a traditional “MVC” framework, will make you feel
212.
by 0xblinq 3y ago
“Your data is safe, because we’ve never written it to disk.”
213.
by 0xblinq 3y ago
Yes, this is true for any js framework (and most libraries) to be honest. If you want something “safe”, nowadays the only option is to use one of the big MVC frameworks (django, laravel, rails, etc...) with inertia.js, if you want to use Re
214.
by 0xblinq 3y ago
> Just, why? Next.js is marketed as a super cool framework you can just install and run anywhere, and while that's mostly true... it has a lot of limitations and architectural decisions which make sens only on their hosting platform
215.
by 0xblinq 3y ago
> Unfortunately This is not unfortunate. I've done this recently and I'm so glad I did. Remix is much, much, much simpler and pragmatic. And doesn't have all these artificial limitations Next.js has when you're runnin
216.
by 0xblinq 3y ago
Which is just yet another js framework which might disappear next month. That's the problem.
217.
by 0xblinq 3y ago
+1 We're also using Inertia in a pretty large project and we're super happy with it.
218.
by 0xblinq 3y ago
I think you're actually agreeing with me :-). Just extending my take to all of Rails, which I think it makes sense too. Yeah, Inertia is great. We're supper happy with it. It simplified a lot of things and makes us feel we're
219.
by 0xblinq 3y ago
+1
220.
by 0xblinq 3y ago
Backend devs doing "just simple rails views" only works when those views are really simple, and mostly for internal tools. Otherwise it becomes a total nightmare to maintain. I agree the "popular" JavaScript solutions ar
221.
Migrated a smallish project from Next to Remix(old.reddit.com)
2 points by 0xblinq 3y ago|0 comments
222.
by 0xblinq 3y ago
horrible
223.
by 0xblinq 3y ago
I find the combination of a component framework such as React with a fully fledged backend such as Laravel or Rails with Inertia.js is perfect. The best of both worlds. All this server side components is just over engineering no one needs,
224.
by 0xblinq 3y ago
This.
225.
by 0xblinq 3y ago
HTMX is in NO way a replacement for frontend libraries. If you can achieve what you wanted to do with HTMX you didn’t need any frontend framework to start with. Also, repeating this again… the hype and the marketing from HTMX is something I
226.
by 0xblinq 3y ago
The “just use js and HTML” doesn’t work for anything but trivial projects. Not using a framework leads to either spaghetti code, or reinventing your own undocumented, untested, unproven framework.
227.
by 0xblinq 3y ago
I think all this RSC is a big fuck up. A feature nobody needed that breaks the ecosystem and introduces huge amounts of complexity. It hurts to see.
228.
by 0xblinq 3y ago
I think you are confusing a productive language with a productive ecosystem. Using typescript and next maybe you are super productive writing code, but in the big scheme of things you are not productive if you have to reinvent the wheel and
229.
by 0xblinq 3y ago
To make it worse, there are like 10 half assed frameworks claiming to be the “rails” of node. Not a single one of those provide even a way to do translations, run a background job and most don’t even provide an ORM or a way to validate inpu
230.
by 0xblinq 3y ago
Laravel + Hotwire if working alone or with a small team. Laravel + Inertia if working on a large team or with dedicated backend and frontend teams.
231.
by 0xblinq 3y ago
I’ve moved to use Laravel + Inertia (with react) and I’m so glad I did.
232.
by 0xblinq 3y ago
In those cases you use alpine, and do the interactivity on the client side.
233.
by 0xblinq 3y ago
> Every interaction in a livewire type system requires a round trip You’re wrong on this. You’d use Alpine and do the interactivity client side. If you don’t miss use the tool, Livewire is supposed to reach to the server in the same situ
234.
by 0xblinq 3y ago
Nothing is great for everything.
235.
by 0xblinq 3y ago
What would be the engineers doing otherwise? You get bored if you don’t.
236.
by 0xblinq 3y ago
This. I love php, and especially Laravel. But the Wordpress community continues in the Stone Age of the development practices.
237.
by 0xblinq 3y ago
People just look for ways to justify their already taken decisions.
238.
by 0xblinq 3y ago
> fronted dev can work with their favourite patterns and frameworks And this is a big problem in my opinion. We should decide the stack that better solves the problem, and then hire people that are happy to work with that, not the other
239.
by 0xblinq 3y ago
Another day another JavaScript framework. Also, to me at least, just because it’s able to execute code on the browser and on the server doesn’t mean “full stack”. Let me know when it supports all the real stuff you need to build actual “ful
240.
by 0xblinq 3y ago
Sorry, I don’t know anything about Asp.net. My comment definitely applies to the other two options you listed.

More ›