Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We fell out of love with Next.js and back in love with Ruby on Rails

hardcover.app

Post reply on HN
Print view View original

431–440 of 533 posts

Re: We fell out of love with Next.js and back in love with Ruby on Rails

#431

Post by TranquilMarmot »

DangitBobby wrote: post #311
esperent wrote: post #261

Earlier quoted context omitted.

> There’s no one go-to I thought Prisma.js was the most popular by far? It's the one I've always seen used in docs and examples.

Yes it's pretty good though it falls short of my golden standard (Django) by missing good automatic migrations and transactions in migrations.

We had to write a migration layer on top of Prisma that can run arbitrary code to do things like transactions in migrations. Kind of a bummer that something like that's not built-in to the system but it was also trivial to put together.

Re: We fell out of love with Next.js and back in love with Ruby on Rails

#432

Post by TranquilMarmot »

austin-cheney wrote: post #27

When I see articles and discussions about web + stack I can’t but ask “What problem are they actually solving” ? The answer is always: put text on screen . When your business goal is put text on screen the next logical step is to ask how much time and money does the tech stack really save? I have never found a developer that answer that question with a number. That’s a really big problem.

I don't think any business goal of anywhere I've worked for the past 10 years has been "put text on a screen". It's usually more like, "interactive application that can view and manage complex data representations in intuitive ways". Charts, forms, graphs, error validation, nested tables, consistent styling, nice animations are all vital components that are much much easier with a modern web tech stack.

Re: We fell out of love with Next.js and back in love with Ruby on Rails

#433

Post by twodave »

TranquilMarmot wrote: post #428
twodave wrote: post #275

Earlier quoted context omitted.

We have some other projects that are Angular, and NextJS was sort of a proof of concept for us. The goal is to just have one front-end framework for our devs to work with (and keep up to date, ugh!), so we’re folding those deploys back into our Angular family of features.

Have you checked out https://astro.build/ yet? You can drop in any framework where you need it, so if you need to bring along those Angular components you can but you can also lean on React if you need it.

No, and on a cursory look it doesn’t seem very aligned with our goals anyhow.

Re: We fell out of love with Next.js and back in love with Ruby on Rails

#434

Post by mike_hearn »

torben-friis wrote: post #240
waprin wrote: post #233

Earlier quoted context omitted.

It's one of those things that's like "write one HTML file with zero styling, then you can have multiple different CSS files style the same content completely differently! Separation of Concern!" Sounds perfect in theory but just doesn't always work. Having one API for web and mobile sounds good but in practice often the different apps have different concerns. And SEO and page speed were always reasons the server neve…

>In fact, the trend is the opposite direction - the server sending the mobile apps their UIs. That way you can roll out new updates, features, and experiments without even deploying a new version Is that allowed by app stores? Doesn’t it negate the walled gardens if you can effectively treat the app as a mini browser that executes arbitrary code ?

It's not really allowed but they aren't policing it, so, the technique ("code push") continuously grows.

Re: We fell out of love with Next.js and back in love with Ruby on Rails

#435

Post by Version467 »

dyogenez wrote: post #405
Version467 wrote: post #355

Earlier quoted context omitted.

I stumbled upon hardcover when I was looking for a book info api and saw that goodreads discontinued theirs. Although it's pretty rough around the edges I've been using it extensively since then. As far as I understand hardcover was really created because goodreads discontinued their api and the team at hardcover saw how many people relied on it for a myriad of different niche projects. If hardcover was just a replac…

Thanks for the comments! You hit on a lot of why our app is structured the way it is. I agree too, we could've put those investments into Next.js rather than migrating to Rails. The difference was with Rails I could envision what the endpoint looked like (codebase, costs, caching, dev env, deployment, hosting options, etc). If we were to invest that time Next.js, some of those answers were (and still are) unclear. Ag…

That's a fair argument. And to be clear (because my original comment might read as negative), I do like hardcover a lot. It might not work sometimes, but I still use it to track all my reading, because the ui is charming, because it has a good, open api and because it's very clearly made by people who really like reading. Wishing you all the success you can get!

Re: We fell out of love with Next.js and back in love with Ruby on Rails

#436

Post by chagel »

Exploring web programming from the frontend view (e.g., Island Architecture) is always intriguing. I'd love to see how JS/SPAs surpass the SSR/HTTP paradigm with LLM/AI. Until then, focus on mastering infrastructure, protocols, databases, and APIs — engineering over designing.

Re: We fell out of love with Next.js and back in love with Ruby on Rails

#437

Post by switch007 »

TranquilMarmot wrote: post #430
welder wrote: post #344

Earlier quoted context omitted.

The go-to is Drizzle

That's funny, I would say the go-to is Prisma. We use it heavily and have not had any issues.

Very lucky to not have encountered one of the 500 open and confirmed bugs!

Re: We fell out of love with Next.js and back in love with Ruby on Rails

#438

Post by switch007 »

welder wrote: post #345
esperent wrote: post #261

Earlier quoted context omitted.

> There’s no one go-to I thought Prisma.js was the most popular by far? It's the one I've always seen used in docs and examples.

Not anymore, now it's Drizzle

lol and next year it'll be something else. Drizzle isn't even 1.x

Re: We fell out of love with Next.js and back in love with Ruby on Rails

#439

Post by freeone3000 »

baq wrote: post #332
CuriouslyC wrote: post #235

Earlier quoted context omitted.

I've been a professional programmer for ~20 years and worked in a variety of languages on a variety of different types of projects, and Typescript with Bun is mostly just fine. It lacks some low level primitives I'd like to have available for certain projects (e.g. Go channels), and the FFI interface isn't as nice as I'd like, but it's basically serviceable for for a very broad range of problems. You should still kno…

I agree, nowadays working on mostly TS backend with some parts in JS written before async/await was introduced and I’m inclined to say TS is better than Python at most things bakcendy. I’m missing sqlalchemy and a sane numerical tower pretty much.

Python suffers from the same problems: its type system has many escapes and implicit conversions, making soundness opt-in and impossible to statically verify. Any language with an implicit cast from its bottom type to an upper type is unsuitable for use.

Re: We fell out of love with Next.js and back in love with Ruby on Rails

#440

Post by switch007 »

welder wrote: post #344
mattgreenrocks wrote: post #170

Earlier quoted context omitted.

Yep. The ORM situation in JS is not great. There’s no one go-to, and it seems like the question often prompts a patronizing response about how ORMs aren't really necessary. Kysely is really great, but it’s not an ORM. My take: the JS ecosystem tends to avoid abstraction for whatever reason. Example: they don’t believe that their web framework should transparently validate that the form submission has the correct shap…

The go-to is Drizzle

When not even 1.x?
Post reply on HN