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

131–137 of 137 posts

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

#131

Post by digitaltrees »

rhizome wrote: post #130
digitaltrees wrote: post #113

Earlier quoted context omitted.

Same with TechCrunch, every time I visit I am reminded how frustrating react sites can be compared to server rendered pages with all the flicker, slow page reveal, and odd navigation it introduced.

Late loading artifacts is all the fault of JS, not server-side rendering. Not sure what you mean by "odd navigation."

To close an article there is a x button and back swipe is disabled. I agree that flicker is introduced by Javascript. That is what I was saying. Might be ok for an app, but a content driven site seems like it should stick to the concept of pages where navigation is like turning a page. Just seems like server rendering fits that mental model better. Not sure why react even makes sense for a blog.

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

#132

Post by efdee »

pjmlp wrote: post #106
efdee wrote: post #88

Earlier quoted context omitted.

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

Mixed content on the same file, looks pretty much the same, regardless how it is implemented.

The problem with ASP/PHP (or at least, the one we are addressing here) always mixing presentational logic with business logic. Something you still shouldn't do, and React doesn't advocate doing so at all.

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

#133

Post by ngrilly »

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.

JSX let's us define components, usable with the usual HTML syntax. PHP does not. That's why Facebook developed XHP (XML fragments in PHP), which inspired JSX.

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

#134

Post by ng12 »

digitaltrees wrote: post #131
rhizome wrote: post #130

Earlier quoted context omitted.

Late loading artifacts is all the fault of JS, not server-side rendering. Not sure what you mean by "odd navigation."

To close an article there is a x button and back swipe is disabled. I agree that flicker is introduced by Javascript. That is what I was saying. Might be ok for an app, but a content driven site seems like it should stick to the concept of pages where navigation is like turning a page. Just seems like server rendering fits that mental model better. Not sure why react even makes sense for a blog.

It doesn't, but blogs aren't built to present content they're built to sell advertisements and collect data. That's much easier with an SPA than a SSR app.

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

#135

Post by rhizome »

ng12 wrote: post #134
digitaltrees wrote: post #131

Earlier quoted context omitted.

To close an article there is a x button and back swipe is disabled. I agree that flicker is introduced by Javascript. That is what I was saying. Might be ok for an app, but a content driven site seems like it should stick to the concept of pages where navigation is like turning a page. Just seems like server rendering fits that mental model better. Not sure why react even makes sense for a blog.

It doesn't, but blogs aren't built to present content they're built to sell advertisements and collect data. That's much easier with an SPA than a SSR app.

they're built to sell advertisements and collect data. That's much easier with an SPA than a SSR app

How easier? By dint of additional JS that an SSR doesn't have/need? Not sure how pulling a header nav (or any cell/element) from a server on pageload plays into that, but even today I've watched sites (plural) loading, pushing loaded parts all over the page for 30sec until everything settles down. Maybe blogs aren't quite so affected by this set of popular dark- and anti-patterns, but even so the post is almost always the last thing to load. Presumably, the monetization and data collection takes precedence over all else.

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

#136

Post by metsong »

Hi dude,are you a hacker? Can you do me a favor to break into a illegal web in china(it's a web of bitcoin trade,but it's forbidden by Chinese government). It's a very simple job to a professional man. Contact me: xuechs@gmail.com. I wish your reply , and get money together.

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

#137

Post by TomMarius »

pjmlp wrote: post #120
arvinsim wrote: post #118

Earlier quoted context omitted.

I totally disagree. VueJS and AngularJS feel like PHP/ASP but I never got that feeling from JSX.

I fail to see how proper component based frameworks, with clean separation of concerns, provide such experience. JSX is the one mixing echo like statements with proper JavaScript.

That is pretty impossible since JSX is just JavaScript, including all of its scope separation. It might be that you're not well versed in using it.
Post reply on HN