0xblinq

14 ms·

181.
by 0xblinq 3y ago
It’s the framework of the week because now it’s when it’s getting popular, gaining traction and everyone is trying it out. Not because of how long has been in the make.
182.
by 0xblinq 3y ago
While I like and use Remix I do agree with your prediction about its future. Sadly.
183.
by 0xblinq 3y ago
I’m one of those using remix and I do like it a lot, but I don’t have much hope. I wish I’m wrong but probably in a couple years we’ll be all hating it. I also liked next a lot in the early days. Somehow they always manage to fuck yo and no
184.
by 0xblinq 3y ago
Everyone thinks their preferred stack is the best in the world and should be used by everyone for everything and everything else is wrong. It’s so funny.
185.
by 0xblinq 3y ago
At work we are using Inertia.js as an interface between React and Rails (inertia is just a tiny library/protocol that lets you use React or Vue replacing your mvc framework templates) Check it out, it’s really nice.
186.
by 0xblinq 3y ago
LOL. One best a replies I’ve read in HN in a long time.
187.
by 0xblinq 3y ago
Stable as jelly. As everything in the js ecosystem, sadly.
188.
by 0xblinq 3y ago
I like remix and I have big hopes for it, but the devs do have a horrible trajectory of breaking things and leaving everyone behind. But sadly this is so common in the js ecosystem. There’s no stable option.
189.
by 0xblinq 3y ago
This is done so that you never use it (even in your own servers) because otherwise you won’t be able to move to their cloud. This is why you don’t use VC backed dependencies that are not easy to move away from.
190.
by 0xblinq 3y ago
This is done so that you never use it (even in your own servers) because otherwise you won’t be able to move to their cloud. This is why you don’t use VC backed dependencies that are not easy to move away from.
191.
by 0xblinq 3y ago
It’s a pretty big fuck up actually
192.
by 0xblinq 3y ago
> I would say if you know that you are going to use Vercel, use Next.js but otherwise I would always argue for Remix. Exactly. It makes absolute no sense to deal with all of Next's artificially imposed limitations if you're run
193.
Remix Vite Is Now Stable(remix.run)
138 points by 0xblinq 3y ago|98 comments
194.
by 0xblinq 3y ago
This is amazing. Great work.
195.
by 0xblinq 3y ago
This. So much this.
196.
by 0xblinq 3y ago
Unpoly is great. I've used it for several projects and I love it.
197.
by 0xblinq 3y ago
Yeah, that sounds good to me. I think that when working with Node the "trick" is to pick libraries/dependencies/frameworks that are either 1) Well know, supported, big community, well maintained, many users, etc or 2) Th
198.
by 0xblinq 3y ago
Too new, too focused on TypeScript (which I don't use), mostly developed by a single dev that already abandoned other similar projects (objection) and nobody knows what its future is. This is exactly what I mean. Compare that to using
199.
by 0xblinq 3y ago
Remix is my favorite as well from this category. But I’m super conflicted regarding ORMs and data access libraries. All of them are either too new, too unstable, too unmaintained, too VC backed, too little devs/community, etc.
200.
by 0xblinq 3y ago
Remix is so much better than Next. I’m just crossing my fingers they won’t f**k up.
201.
by 0xblinq 3y ago
So you’re either: 1) writting a super basic application, 2) Creating your own abstractions so inventing your own undocumented untested unproven framework or 3) creating a mess no one will be able to maintain. Which one is it? Or please, des
202.
by 0xblinq 3y ago
I’d say use a “real” full stack (or batteries included) framework such as Laravel, Rails or Django. If you do need to use React, Vue, etc, then glue them with Inertia.js which is just a super thin layer that basically just replaces those fr
203.
by 0xblinq 3y ago
So far I’ve found some shelter in Remix. But I’m skeptical they won’t fuck up as well. They have a reputation of breaking everything with react router.
204.
by 0xblinq 3y ago
In my experience the sweet spot nowadays is to use a traditional batteries included framework such as Django/laravel/rails with Inertia, which basically just replaces the template part of those frameworks by a modern components fr
205.
by 0xblinq 3y ago
Remix is so much better than Next. We moved a project at work and it’s been night and day for us. Not going back.
206.
by 0xblinq 3y ago
You see unnecessary bloat, I see wheel reinventions. Unpoly gives me almost everything I need for any non trivial app. Same thinking about using Django/Rails/Laravel vs bare bone routers like express, Sinatra or flask. Once you ge
207.
by 0xblinq 3y ago
I’ve had a Xiaomi phone and it was the worst crap I’ve ever had. I can understand somebody compares a pixel to an iPhone… but the only advantage of a cheap/low tier android phone is that…. They’re cheap.
208.
by 0xblinq 3y ago
Both are small enough for this to not matter. Unpoly also has many more features you’d have to add code for.
209.
by 0xblinq 3y ago
iPhones are expensive for a reason. Moving from android was the best decision I’ve made tech-wise. If you can afford it, it’s totally worth its value.
210.
by 0xblinq 3y ago
And I still don’t get all the hype and marketing around it. Unpoly is so much better in every way you look at it. Most people seem to be using it just because “it’s popular” which ironically is the reason most people use React as well.

More ›