Re:New React docs pretend SPAs don't exist anymore
by leerob on Saturday March 18, 2023 @10:07AM
(#35209245)
There are similarities to PHP – and I think that's a great thing! I like to think of Next.js as the best parts of PHP / Rails with the powerful UI engine of React. Especially with the new App Router, where you can fetch code inside components like `await db.query()` and soon easily insert/update/delete from the same file as well.
Re:New React docs pretend SPAs don't exist anymore
by matijash on Saturday March 18, 2023 @10:17AM
(#35209321)
that's one thing I've been thinking about a lot lately and I think it is confusing for many - that both Next/Nuxt/Remix and Rails have a title of a "full stack" framework while they are pretty different in reality.
Next/Nuxt are coming from the frontend origins and are strongest there, while Rails/Django are coming from the backend and focus on db ORM / data model story via ActiveRecord etc.
I understand the etymology of terminology, but I think we'll probably come up with better names in the future. E.g. Remix briefly called themselves "center-stack" which I found interesting and think makes sense.
I'll keep investigating and probably whip up a blog post about it.
Re:New React docs pretend SPAs don't exist anymore
by robertlagrant on Monday March 20, 2023 @09:22AM
(#35231104)
I enjoy interviewing people who have full-stack engineer on their resume, as it means I can ask them about anything from HTML tags to CPU microcode, or from relational algebra to networking stacks, and they'll be able to give a good answer.
Re:New React docs pretend SPAs don't exist anymore
by lawkwok on Saturday March 18, 2023 @02:26PM
(#35211738)
It’s funny to think there was a time when using JS vs JQuery was the biggest division among devs. Now just using JS is considered the baseline and React is the new framework that people jump to when it isn’t always necessary.
Re:New React docs pretend SPAs don't exist anymore
by Dylan16807 on Saturday March 18, 2023 @04:47PM
(#35212941)
Well, when I hear people complain about PHP it's not about the routing or the idea of server-side rendering.
Re:New React docs pretend SPAs don't exist anymore
by mmis1000 on Sunday March 19, 2023 @09:44AM
(#35218831)
The ancient php idea of mix data fetching and rendering instead of wait until everything done for least `TTFB`(Time to first byte) is still hard to do for a lot of js framework today. You generally need to add tons of hack to the framework so you can print your site header before fetch and print the article body completely. (Which a phper will ask you "why you don't just print it?").
React and vue has add limited streaming rendering support recently, but they are still very limited and you need to met some constraint to actually use it.
It's really something `old is new today`.
Re:New React docs pretend SPAs don't exist anymore
by Dylan16807 on Sunday March 19, 2023 @10:54AM
(#35219561)
"You can't do this old thing, except barely and with great difficulty" sounds like it's close to the opposite of "old is new" to me?
Re:New React docs pretend SPAs don't exist anymore
by robertoandred on Saturday March 18, 2023 @06:56PM
(#35214028)
Php doesn’t equal file system routing. Look at Wordpress.
Re:New React docs pretend SPAs don't exist anymore
by bobbylarrybobby on Monday March 20, 2023 @02:41PM
(#35236497)
Noob here. What's wrong with file system routing?
Re:New React docs pretend SPAs don't exist anymore
by psnehanshu on Monday March 20, 2023 @03:20PM
(#35237157)
There's nothing wrong. But the commentator perhaps isn't aware that PHP isn't enough to write complex and interactive apps.
Re:New React docs pretend SPAs don't exist anymore
by psnehanshu on Monday March 20, 2023 @03:18PM
(#35237131)
Here's your answer: https://news.ycombinator.com/reply?id=35220064&goto=item%3Fi...
I have been in software for about a decade and I think I’m experiencing my first complete cycle of “what’s new is old”.