4 ms·

React the client side rendering by attaching dom element to create the html front end tool is really cool idea! Terrible idea in practice. graceful degradation

React the client side rendering by attaching dom element to create the html front end tool is really cool idea! Terrible idea in practice. graceful degradation goes out of window. Why are you rewriting the browser rendering implantation in a JS engine? It is clever, and dumb. For visual consistence just stick with templating model and SSR. Also most tech people mostly turn off JS when they browse the web any way. React people, yes I'm looking at your! In addition, as React/Redux type of projects gets big, it is a nightmare to maintain. Yes I know it is all about the coder. However, most front end developer (transitioning from jquery css/html) do not have the needed programming skills to develop something like React. I would say React is more computer science ppl who wants to do front end approach. If that is the case, just go with mithril (they have JSX). Stop this insanity of using React just because hipster sillicon valley ppl are using it cause it is trendy and get high paying jobs.

0df8dkdf 6y ago
The only exception to use React type of front end framework is when one need a SPA like cordovva. Before you do that, be dame sure you need a SPA. Developer and CS people you are not in the fashion industry. Stop it!!!!! Stop chasing the trend.
dagi3d 6y ago
> Also most tech people mostly turn off JS when they browse the web any way any public stats that confirms this?
- ajkjk 6y ago
  Yeah I really can't imagine that's true at all. I bet the rate of tech people turning off JS is like -- 1 in 100,000. But they _talk_ about it a lot, so it seems more like 1 in 100.
austincheney 6y ago
> Why are you rewriting the browser rendering implantation in a JS engine? Tree models. Many developers have trouble understanding implicit relationships present in tree models. That is a cognitive barrier acting as a breaking force that eliminates any development. To solve for that frameworks provide an abstraction layer so that developers can envision the DOM more as a graph to be searched. There are all kinds of performance penalties for superficially reinventing a technology like this, but the bigger limitation is lost creative potential. Instead of operating according to the capabilities of the language or API the developer is operating according to the limitations and most common approaches of the framework. For example templating is mostly easy. State management is ridiculously easy. But, the frameworks would have you think these are massive accomplishments requiring the titanic efforts of a super genius.
bluedevil2k 6y ago
What Trump would sound like as a tech lead. Seriously, there’s so many fake outlandish claims in this. Most tech people do not turn off JS because they know most of the web will break. They also know React projects scale really well and React is not a trendy project.
- Natsu 6y ago
  I think a lot of people here are running NoScript, more than you may realize. Yes, it breaks a ton of stuff. I give temporary whitelists to sites I actually want to run JS for and permanent whitelists are quite rare. Case in point: google only gets temporary whitelisting.
  - 0df8dkdf 6y ago
    or ppl uses lynx2 also. Personally web site for informational purposes should always work on lynx2. JS is not needed for web page. Now if you are making SPA or an application on the web then that is something else.

0df8dkdf 6y ago

The only exception to use React type of front end framework is when one need a SPA like cordovva. Before you do that, be dame sure you need a SPA. Developer and CS people you are not in the fashion industry. Stop it!!!!! Stop chasing the trend.

dagi3d 6y ago

> Also most tech people mostly turn off JS when they browse the web any way any public stats that confirms this?

ajkjk 6y ago
Yeah I really can't imagine that's true at all. I bet the rate of tech people turning off JS is like -- 1 in 100,000. But they _talk_ about it a lot, so it seems more like 1 in 100.

austincheney 6y ago

> Why are you rewriting the browser rendering implantation in a JS engine? Tree models. Many developers have trouble understanding implicit relationships present in tree models. That is a cognitive barrier acting as a breaking force that eliminates any development. To solve for that frameworks provide an abstraction layer so that developers can envision the DOM more as a graph to be searched. There are all kinds of performance penalties for superficially reinventing a technology like this, but the bigger limitation is lost creative potential. Instead of operating according to the capabilities of the language or API the developer is operating according to the limitations and most common approaches of the framework. For example templating is mostly easy. State management is ridiculously easy. But, the frameworks would have you think these are massive accomplishments requiring the titanic efforts of a super genius.

bluedevil2k 6y ago

What Trump would sound like as a tech lead. Seriously, there’s so many fake outlandish claims in this. Most tech people do not turn off JS because they know most of the web will break. They also know React projects scale really well and React is not a trendy project.

Natsu 6y ago
I think a lot of people here are running NoScript, more than you may realize. Yes, it breaks a ton of stuff. I give temporary whitelists to sites I actually want to run JS for and permanent whitelists are quite rare. Case in point: google only gets temporary whitelisting.
- 0df8dkdf 6y ago
  or ppl uses lynx2 also. Personally web site for informational purposes should always work on lynx2. JS is not needed for web page. Now if you are making SPA or an application on the web then that is something else.