News for hackers. Stuff that matters.
Re:From Node to Ruby on Rails by recursivedoubts on Thursday December 16, 2021 @09:19AM (#29578331)
Prediction: the big move in the next few years is going to be "back to hypermedia"

People are realizing that you can accomplish quite a bit more with hypermedia than you could in the past, and that the complexity of javascript stacks isn't worth it in many cases.

Older, mature hypermedia-based technologies like rails, django, and even PHP, will experience a resurgence and a lot of older lessons and techniques in web development (caching, SQL tuning, etc.) will be rediscovered.

I have a dog in this fight, w/ htmx, but I think we are increasingly seeing evidence for this move.

Re:From Node to Ruby on Rails by allendoerfer on Thursday December 16, 2021 @09:29AM (#29578444)
We might see a combination of both.

The biggest CMS of one of the biggest languages is moving away from the approach you call hypermedia by implementing a JS-based editor and REST apis. Effectively they are building a headless version on top of their legacy platform, which can be used like a JavaScript stack.

This can be used as an argument for the hypermedia approach: "Let's just use this thing for now, we can always implement our SPA inside it later, if we need to."

Re:From Node to Ruby on Rails by recursivedoubts on Thursday December 16, 2021 @10:41AM (#29579282)
I think that's a trailing indicator, a reaction by Wordpress to the current "right way" to build web software.
Re:From Node to Ruby on Rails by ethanpil on Thursday December 16, 2021 @11:00AM (#29579504)
I don't think this transition has been very well received by the WordPress community...
Re:From Node to Ruby on Rails by gwright on Thursday December 16, 2021 @10:00AM (#29578791)
> The biggest CMS of one of the biggest languages

Which CMS is this?

Re:From Node to Ruby on Rails by ankit70 on Thursday December 16, 2021 @10:05AM (#29578836)
WordPress
Re:From Node to Ruby on Rails by coldtea on Thursday December 16, 2021 @11:10AM (#29579679)
>Older, mature hypermedia-based technologies like rails, django, and even PHP

Not sure what you refer to as hypermedia.

In the first part of your comment I assumed something like a new version of Flash. Here you seem to simply imply http/hypertext.

But then again, those technologies where never lost (to need to be rediscovered). They're as popular as ever, people just add more stuff on top, at the client JS layer.

Re:From Node to Ruby on Rails by regularfry on Thursday December 16, 2021 @12:31PM (#29580947)
Anywhere you see graphql, you see someone who's rejected hypermedia.
Re:From Node to Ruby on Rails by coldtea on Friday December 17, 2021 @01:52AM (#29588792)
Not sure I follow. GraphQL is a way to ask for data from the backend. What does it have to do with the client layer?
Re:From Node to Ruby on Rails by regularfry on Friday December 17, 2021 @06:51AM (#29590972)
It's generally used as a replacement for REST, which, if done properly, uses hypermedia.
Re:From Node to Ruby on Rails by CuriouslyC on Thursday December 16, 2021 @11:29AM (#29579987)
If we see a return to "hypermedia" it won't be wholesale, but rather in the form of a static site generator that does the 80% work and is easy to extend the rest of the way. Something somewhere between Svelte and Gatsby. The react component model and JSX style bracketed DSLs both have a lot of traction, the main issue is the amount of groundwork and glue needed to do simple things with them.
Re:From Node to Ruby on Rails by recursivedoubts on Thursday December 16, 2021 @11:34AM (#29580090)
i don't agree at all

i think it will rather be in non-javascript technologies with strong existing hypermedia infrastructure again, like rails, django, etc

the front-end component model is anti-RESTful and is really a mechanism for handling the complexity of the current client-server approach, it becomes significantly less important as hypermedia is re-embraced

Re:From Node to Ruby on Rails by CuriouslyC on Thursday December 16, 2021 @02:19PM (#29582540)
I think RESTful APIs will die before component based interfaces do. Component based UI has been a thing for like 30 years outside the web dev space, and GraphQL/post-based RPC APIs solve a lot of problems and can be derived cleanly from a database schema or functional modules.

Hypermedia also doesn't play well with offline-capable applications, which limits its use cases.

Re:From Node to Ruby on Rails by recursivedoubts on Thursday December 16, 2021 @03:11PM (#29583237)
the component problem, in as much as it is one that can't be dealt with via just standard template includes, can be solved server side and offline-capable isn't a huge percentage of web apps

we just disagree, the future will tell us who's right

Re:From Node to Ruby on Rails by BuckRogers on Saturday December 18, 2021 @12:51AM (#29602073)
I think you’re both wrong and the future belongs to platforms that compile to web assembly.
Re:From Node to Ruby on Rails by recursivedoubts on Saturday December 18, 2021 @02:40PM (#29607826)
could be!
Re:From Node to Ruby on Rails by zerocount on Saturday December 18, 2021 @05:35AM (#29603452)
Hypermedia is just the addition of graphics, sound, etc... to your web page. I don't understand the context you're using it in here.
Re:From Node to Ruby on Rails by stevefan1999 on Thursday December 16, 2021 @09:25AM (#29578401)
It already happened with SSR
Re:From Node to Ruby on Rails by tosihakkeri on Thursday December 16, 2021 @02:25PM (#29582627)
I think requirements have generally shifted quite bit from what plain html can do, if that's what you mean with "hypermedia". Though true, there's probably a growing understanding that one doesn't need React on every website. So maybe it'll rather be more refined understanding of when to use certain technologies.
Re:From Node to Ruby on Rails by recursivedoubts on Thursday December 16, 2021 @03:56PM (#29583793)
Re:From Node to Ruby on Rails by tosihakkeri on Friday December 17, 2021 @02:31AM (#29589035)
Certainly interesting but I fail to understand what's the big benefit? Also I would be afraid to have some corner cases that would need to be covered with JS, and that could get really ugly.
Re:From Node to Ruby on Rails by recursivedoubts on Friday December 17, 2021 @09:07AM (#29592306)
the big benefits are the simplicity of the model and returning to the hypermedia network architecture (with its attendant benefits)

don't worry! If you need to kick out to some front end scripting we have a solution for that as well:

https://hyperscript.org

So no ugly javascript! ;)

Re:From Node to Ruby on Rails by smm11 on Thursday December 16, 2021 @02:43PM (#29582862)
Exactly. This "stuff" is maturing, and a lot of people realize we've been headed the wrong direction for a long time.

At some point, stuff needs to be maintained. You can still start and drive that 1967 car, after all.

Re:From Node to Ruby on Rails by qudat on Thursday December 16, 2021 @01:04PM (#29581484)
The react team are developing "server components" that will bring the js ecosystem even closer to your prediction.