0xblinq

9 ms·

151.
by 0xblinq 2y ago
Wow. FoxPro. Good times! I’ve never found anything as productive since Visual FoxPro.
152.
by 0xblinq 2y ago
+1 for Unpoly.
153.
by 0xblinq 2y ago
Hey! But those sweet download stats! Now it’s bigger than next and that’s the only thing that matters.
154.
by 0xblinq 2y ago
> It means the old versions are pretty good and people are still using them That's a very optimistic view of the situation.
155.
by 0xblinq 2y ago
yes https://remix.run/blog/remixing-shopify
156.
by 0xblinq 2y ago
You do have to upgrade. At some point incompatibilities between libraries arise, and if neglected for too long at some point it becomes impossible to update everything. Keeping dependencies up to date is an important part of software mainte
157.
by 0xblinq 2y ago
Take one more sir.
158.
by 0xblinq 2y ago
This is all about download counts and who's more popular. That's it.
159.
by 0xblinq 2y ago
Yet another mess, once again. All of this just so that they can brag that their framework has more stars/downloads than Next.js, because there's no other reason to do this than to "show" who's more popular. And whil
160.
by 0xblinq 2y ago
oh noes!
161.
by 0xblinq 2y ago
It’s going to take some time but it’s going to take over. Next really fucked up with the app router, and people are realizing everything is just a trap to get more customers on vercel.
162.
by 0xblinq 2y ago
+1 I’ve been using remix for the last 6 months and I’m super happy with it.
163.
by 0xblinq 3y ago
LOL
164.
by 0xblinq 3y ago
I've worked with both, Laravel and Django, for many many years. Laravel is miles ahead of Django, in every single aspect. The template system is incredible while the django one is stuck in the 90s. The integrated job queues, scheduling
165.
by 0xblinq 3y ago
And what prevents these aggregator apps from having different settings for each network?
166.
by 0xblinq 3y ago
Author's code is vulnerable to timing attacks and probably others as well. This is why people should use established backend frameworks such as Laravel/Django/Rails if they really want to focus on their product and not on rei
167.
by 0xblinq 3y ago
> before going straight to the Next.js or Remix behemoths where we'll have 45min builds pulling in thousands of NPM dependencies over half a million files in node_modules. You sound unhappy as well, and you also sound like you'
168.
by 0xblinq 3y ago
From what I can see from the demo that's a super simple application. It might make sense to use a tool such as htmx/unpoly/hotwire/etc. What I don't get is people just blindly "following the hype" (as with
169.
by 0xblinq 3y ago
If all you have to do is render a form you don't even need HTMX. IF your project is just about rendering forms then fine.
170.
by 0xblinq 3y ago
That won't happen. That's not a priority for them and goes against their business interests. In fact, there are already many intentional limitations that makes Next a very bad choice if you're self hosting. proof: https:&#x2
171.
by 0xblinq 3y ago
Agree with this. Remix is a thousand times better than Next. We migrated our main application to Remix and couldn't be happier. The app router stuff is such a mess.
172.
by 0xblinq 3y ago
LOL. The HTMX hype is worse than every other fashionable framework. Only backend developers like it. As soon as you have to do anything minimally complex it's just terrible.
173.
by 0xblinq 3y ago
This is the "Hyped" stack, not the "Right" stack. From all of this, the worst decision is to use Next. Vendor lock in, developed by one of the most shady companies right now, and full of problems.
174.
by 0xblinq 3y ago
As a full time JavaScript developer for the last ~8 years (with some previous Django experience), getting into Laravel has been one of the best things that have happened to me in my professional life. It's so refreshing to have such a
175.
by 0xblinq 3y ago
People should be more careful when picking names. I know it’s its difficult, but still. This sounds extremely bad in Spanish, to the point I wouldn’t be able to use something like this at my company just because of how it sounds and the con
176.
by 0xblinq 3y ago
And in practical real life terms (where teams and long term projects and people coming and leaving the team over years and different skill levels, etc) is how CSS becomes a write-only mess. Tailwind is primarily a way to do "css-in-js&
177.
by 0xblinq 3y ago
They're different things IMHO. Bootstrap gives you a pre-made look and feel that you can use despite knowing CSS or not and maybe you can customize a bit, make a theme, etc. Bootstrap is more like "Tailwind UI" which is diffe
178.
by 0xblinq 3y ago
I think it's been the same situation with React. Everyone hated JSX when it first came out, then people realized the benefits outweigh the drawbacks.
179.
by 0xblinq 3y ago
+1. I’m also using it and it’s truly refreshing after so many unnecessary SPAs. The latest generation of js meta frameworks made me switch and I’m so much happier with Livewire.
180.
by 0xblinq 3y ago
+1 The ecosystem is unmatched.

More ›