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

Front-end design, React, and a bridge over the great divide

bradfrost.com

Post reply on HN
Print view View original

81–90 of 137 posts

Re: Front-end design, React, and a bridge over the great divide

#81

Post by TomMarius »

jasode wrote: post #80
zbentley wrote: post #34

Earlier quoted context omitted.

I suspect that, in 2-3 years, server-side rendering is going to be rediscovered as a cure for the plague of spaghetti frontend code, just as current template-in-javascript metalanguages are being discovered now as a cure for spaghetti frontend-plus-backend-rendered code.

>I suspect that, in 2-3 years, server-side rendering is going to be rediscovered as a cure for the plague of spaghetti frontend code, Maybe your prediction is informed by different internet usage scenarios but for general mainstream web surfers , I can't see how the industry will migrate back to server-side rendering in 3 years. The unavoidable technical issue is the round-trip latency of the network. The same delays…

I believe in a mix of these two. It's going to be server rendered JS app that will download itself on the background and install itself as a PWA. The best of both worlds.

Re: Front-end design, React, and a bridge over the great divide

#82

Post by medof »

TomMarius wrote: post #81
jasode wrote: post #80

Earlier quoted context omitted.

>I suspect that, in 2-3 years, server-side rendering is going to be rediscovered as a cure for the plague of spaghetti frontend code, Maybe your prediction is informed by different internet usage scenarios but for general mainstream web surfers , I can't see how the industry will migrate back to server-side rendering in 3 years. The unavoidable technical issue is the round-trip latency of the network. The same delays…

I believe in a mix of these two. It's going to be server rendered JS app that will download itself on the background and install itself as a PWA. The best of both worlds.

So you mean universal application? That's how nuxt.js/next.js works

Re: Front-end design, React, and a bridge over the great divide

#83

Post by Kaotique »

In our agency a lot of our backend developers have moved their work on the business logic side of the frontend with React, managing state and routes, interacting with API's. While the traditional frontend developers work more on the visual part of the frontend with styling, JSX, images, animations.

I now call them technical frontend developers and visual frontend developers during interviews. I am not sure what terms will stick in the end.

Our senior frontenders handle both the technical and the visual part.

We have some experienced senior full-stack developers who can work on anything from hosting, server-side code, client-side business logic in React, but they usually stop there and let visual frontenders implement the design.

Observing our junior frontend developers I noticed it is very difficult to be effective in both areas. You really need years of experience before you can grasp the whole thing.

Managing state and business logic is so different from implementing a design. It requires very different skills. I can really sympathize with traditional visual frontender feeling overwhelmed with the whole javascript madness that is going on. Companies who just dumped it on them because "it's frontend", are making a huge mistake.

Re: Front-end design, React, and a bridge over the great divide

#84

Post by TomMarius »

medof wrote: post #82
TomMarius wrote: post #81

Earlier quoted context omitted.

I believe in a mix of these two. It's going to be server rendered JS app that will download itself on the background and install itself as a PWA. The best of both worlds.

So you mean universal application? That's how nuxt.js/next.js works

Yes I am aware of these technologies, and it's basically what I mean, in an abstract way

Re: Front-end design, React, and a bridge over the great divide

#85

Post by efdee »

TomMarius wrote: post #81
jasode wrote: post #80

Earlier quoted context omitted.

>I suspect that, in 2-3 years, server-side rendering is going to be rediscovered as a cure for the plague of spaghetti frontend code, Maybe your prediction is informed by different internet usage scenarios but for general mainstream web surfers , I can't see how the industry will migrate back to server-side rendering in 3 years. The unavoidable technical issue is the round-trip latency of the network. The same delays…

I believe in a mix of these two. It's going to be server rendered JS app that will download itself on the background and install itself as a PWA. The best of both worlds.

That is what we have today.

Re: Front-end design, React, and a bridge over the great divide

#86

Post by arethuza »

recursive wrote: post #65
corebit wrote: post #7

Earlier quoted context omitted.

But seriously why can’t I just do modern webdev with a ?

Wait, is there some other way to load scripts now? Asking for a friend...

I suspect what corebit means is loading a script that has been manually created rather than a file that contains resources bundled by webpack or similar.

Re: Front-end design, React, and a bridge over the great divide

#87

Post by uxcolumbo »

nexuist wrote: post #3
throwaway8879 wrote: post #2

The last time I did a bit of frontend for a side project was in 2004. Then I took a long break from dev and computers in general. Earlier this year I'd decided to brush up on the whole frontend/JS ecosystem. It was weird initially and there was a lot of friction, as I was especially fixated with a "why can't I stick this in a tag, what even is NPM..." mindset. I have the say, after getting the hang of typescript, rea…

I continue to believe that the loudest perpetrators of JavaScript hate are those who overcomplicate simple things or follow other people's advice to overcomplicate simple things. Things like using SPAs for five page sites, throwing Redux into every CRA installation, npm installing useless packages like is-odd or leftpad (lol), etc. You don't need to use ! You don't need JSX! You don't need ! Surely you still don't ne…

What were your reasons for choosing Racket? Why not Clojure / ClojureScript?

Re: Front-end design, React, and a bridge over the great divide

#88

Post by efdee »

pjmlp wrote: post #73
ergothus wrote: post #63

Earlier quoted context omitted.

I keep hearing all of these "Vue just makes more sense than React" converts, and I'm baffled. I recently did some Vue after doing React for a few years, and it felt like a major step backward. It felt very JSP - here was a different syntax that was HTML except when it chose not to be - managing data was done in a custom expression language, and I was left to figure out what scope a given value had. Need to loop somet…

JSX feels like PHP and ASP all over again. Apparently they aren't that bad after all.

How can you say that? PHP and ASP were dumb text template processors. JSX creates object graphs. They are almost nothing alike at all.

Re: Front-end design, React, and a bridge over the great divide

#89

Post by efdee »

fevangelou wrote: post #38

So, if you read between the lines, React was basically built for a better "Like" button according to Dan's blog post here: https://overreacted.io/the-elements-of-ui-engineering/ Hmm...

React was written for Instagram. Nothing to do with Facebook's Like button.

Re: Front-end design, React, and a bridge over the great divide

#90

Post by Marazan »

pjmlp wrote: post #73
ergothus wrote: post #63

Earlier quoted context omitted.

I keep hearing all of these "Vue just makes more sense than React" converts, and I'm baffled. I recently did some Vue after doing React for a few years, and it felt like a major step backward. It felt very JSP - here was a different syntax that was HTML except when it chose not to be - managing data was done in a custom expression language, and I was left to figure out what scope a given value had. Need to loop somet…

JSX feels like PHP and ASP all over again. Apparently they aren't that bad after all.

I hesitate to tell people. They are doing it wrong but if you write JSX like how we all wrote PHP back in the day then you are doing it wrong.
Post reply on HN