0xblinq

27 ms·

361.
by 0xblinq 4y ago
The alternative to SPA frameworks is not spaghetti jquery and vanilla js and full page reloads. As mentioned everywhere around this thread, the way to do server side rendered apps has also evolved. Hotwire, htmx, Unpoly, Livewire, etc, etc,
362.
by 0xblinq 4y ago
The new Reddit is the best example of how shitty can get things when you use the fancy tool instead of the tools you need for the job.
363.
by 0xblinq 4y ago
Totally agree with this.
364.
by 0xblinq 4y ago
Yes, that was my initial impression years ago too. But it's very progressive. For example, you can just use Turbo to get the "SPA like" navigation between pages (no full page reloads) and that's for free, just including
365.
by 0xblinq 4y ago
Mostly due to Turbo transitions between pages and being able to persist elements across pages. I know Livewire V3 will solve this but at the time we took the decision it wasn't available. Also something brought up was a conversation re
366.
by 0xblinq 4y ago
It's measured as I get paid a ton of money because of the responsibility I have but then nothing happens when things go to shit because well, nothing happens. BTW when's my next bonus pay day?
367.
by 0xblinq 4y ago
I was replying to @moxplod because it seems they didn't know about these alternatives to pjax. They're mentioning HTMX, etc so I've added Unpoly to the list of similar things. I'm not saying you should replace Hotwire wi
368.
by 0xblinq 4y ago
Found the real senior developer.
369.
by 0xblinq 4y ago
THIS.
370.
by 0xblinq 4y ago
Check out also Unpoly. It’s probably the most “batteries included” of this kind of tools, although not as popular.
371.
by 0xblinq 4y ago
And god protects us if some day you leave the project and somebody else has to come and understand these setups. I bet you know this very well and you’re very productive with this, but just imagine the next person having to pick it up. That
372.
by 0xblinq 4y ago
Most people in this thread are not suggesting a stack for an mvp. They’re just listing their favorite stacks, that’s it. There’s a comment of somebody saying that just Postgres and Go. How on earth is that a good stack for building an mvp??
373.
by 0xblinq 4y ago
None of these are difficult per se. Multiple of them, working seamlessly together, having them tested, documented and battle tested is a bit more difficult. Then you think about all that time doing this could have been spent in actual busin
374.
by 0xblinq 4y ago
No, it’s not, because we’re talking about an mvp and not about building an ultra high performance micro service. And btw, there is no “correct answer” despite how much you like it. There are many “correct answers” and a lot more wrong ones.
375.
by 0xblinq 4y ago
I’m very fluent in JavaScript (I’ve been a js dev for 10 years) and don’t have that much experience with Laravel yet. I totally agree with what you say. Even. It being fluent with pho and the ecosystem I find it incredibly more easy to lear
376.
by 0xblinq 4y ago
None of these frameworks (next.js, remix, redwood, etc, etc, etc) is a even half close to what you need for any non-trivial MVP backend. Such as: - Validations - Translations/localization - Error and request logging and auditing - Secu
377.
by 0xblinq 4y ago
I'm using Laravel with Hotwire and it's fantastic. Now I want to cry every time I see the mess of overengineering I have to deal with in other projects when they're built with Redux, React, etc, etc.
378.
by 0xblinq 4y ago
My issue with Phoenix (or Elixir..) is that there are like 3 people in the world using it. The community and the third party packages available is minimal compared to other ecosystems. And in my opinion, it is already past its best days. I
379.
by 0xblinq 4y ago
This stack is pretty incomplete for most MVPs, as unless you're building something trivial like a landing page, you'll probably at some point also need libraries or a custom implementation for: - Validations - Translations - Error
380.
by 0xblinq 4y ago
1. Laravel. Because: - Battle proven - Secure - Well maintained - Well documented - Fully featured (a lot more than others such as Django or Rails. Jobs, auth, asset manager, etc out of the box) - Doesn't hate JavaScript, embraces it (
381.
by 0xblinq 4y ago
> so its trivial to add that to a project whether its Go or Node or whatever The thing I think you're missing, is that it's trivial TO YOU to do this, and of course you will understand it end to end and be supe productive. What
382.
by 0xblinq 4y ago
Agree. So unless you have a pretty big budget and you're building Google Maps or Figma you shouldn't use React. Sadly, everyone things they have such a big budget and they're building the next Figma. Even if you're build
383.
by 0xblinq 4y ago
Same thing that other people sat about Next.js, about Remix, Nest, Qwik, and the other 10 thousand that "are coming for the crown". In fact, that's the problem.
384.
by 0xblinq 4y ago
> Rails dev for 7 years now but I just don't see it winning over TypeScript/nodejs frameworks I think you're comparing a language/runtime with a framework here. I also prefer Node and JavaScript over Ruby but I get wh
385.
by 0xblinq 4y ago
Next.js is great as long as what you're building is not much more than a landing page, or you're proxying to a real backend system (by another team, etc). Trying to build a "full stack" application with just Next.js is s
386.
by 0xblinq 4y ago
Found the haskell programmer
387.
by 0xblinq 4y ago
So I suppose you also write your own compiler, your own operating system, and built its computer from bare transistors as well? Because all of that looks like magic to me too. At some point you have to accept the foundation you have as some
388.
by 0xblinq 4y ago
What other ecosystems and frameworks are you talking about? I've tried many things across many ecosystems in the last 20+ years and so far, despite any drawbacks it could have Laravel is the best one by a long shot. So I'm curious
389.
by 0xblinq 4y ago
What I mean is that if you enjoy using React, Next.js is your best option in my opinion and from my experience with similar tools (heavy SPA meta-frameworks...). But that's it, it's there for the *frontend* of your application. An
390.
by 0xblinq 4y ago
Using Next.js for writing your backend is pure masochism. You'll only understand why I say this if you've ever used a real batteries included backend web framework.

More ›