Progressive React

#1

Post by brandonhall » Fri, Dec 20, 2019, 8:19 PM UTC

Re: Progressive React

#2

Post by seph-reed » Fri, Dec 20, 2019, 11:59 PM UTC

I know this is a low quality comment, but given I was once the guy at my last company who's job it was to make React do things it didn't want to, I really dislike React. It's a dead end for interactive UIs, and the closer you can stay to native html elements with encapsulation, the better off you'll be later down the road.

Re: Progressive React

#3

Post by singlow » Sat, Dec 21, 2019, 12:01 AM UTC

Start by making your blog not crash android chrome.

Re: Progressive React

#4

Post by foota » Sat, Dec 21, 2019, 12:03 AM UTC

seph-reed wrote: post #2

I know this is a low quality comment, but given I was once the guy at my last company who's job it was to make React do things it didn't want to, I really dislike React. It's a dead end for interactive UIs, and the closer you can stay to native html elements with encapsulation, the better off you'll be later down the road.

How do you figure?

Re: Progressive React

#5

Post by ahartmetz » Sat, Dec 21, 2019, 12:04 AM UTC

It's funny because scrolling in this article is a stuttery mess (Firefox on Linux).

Re: Progressive React

#6

Post by maverick2007 » Sat, Dec 21, 2019, 12:05 AM UTC

singlow wrote: post #3

Start by making your blog not crash android chrome.

Crashes mobile Firefox too. Very ironic given the small portion of the article I read before it crashed.

Re: Progressive React

#7

Post by WrtCdEvrydy » Sat, Dec 21, 2019, 12:06 AM UTC

foota wrote: post #4

seph-reed wrote: post #2

I know this is a low quality comment, but given I was once the guy at my last company who's job it was to make React do things it didn't want to, I really dislike React. It's a dead end for interactive UIs, and the closer you can stay to native html elements with encapsulation, the better off you'll be later down the road.

How do you figure?

I call this the 'Rails Paradox'... a lot of people invested into Rails and wrote a lot of software that powers small businesses.

As people exited Rails, the cost of maintenance has gone up... since you have to pay a lot to get someone writing Rails now.

Re: Progressive React

#8

Post by friedman23 » Sat, Dec 21, 2019, 12:08 AM UTC

seph-reed wrote: post #2

I know this is a low quality comment, but given I was once the guy at my last company who's job it was to make React do things it didn't want to, I really dislike React. It's a dead end for interactive UIs, and the closer you can stay to native html elements with encapsulation, the better off you'll be later down the road.

You can use native html elements with react. I'm curious what it is you were trying to do since I'm sure you could do anything native html supports with react.

Re: Progressive React

#9

Post by foota » Sat, Dec 21, 2019, 12:10 AM UTC

WrtCdEvrydy wrote: post #7

foota wrote: post #4

Earlier quoted context omitted.

How do you figure?

I call this the 'Rails Paradox'... a lot of people invested into Rails and wrote a lot of software that powers small businesses. As people exited Rails, the cost of maintenance has gone up... since you have to pay a lot to get someone writing Rails now.

Wrong thread?

Re: Progressive React

#10

Post by rriepe » Sat, Dec 21, 2019, 12:17 AM UTC

WrtCdEvrydy wrote: post #7

foota wrote: post #4

Earlier quoted context omitted.

How do you figure?

I call this the 'Rails Paradox'... a lot of people invested into Rails and wrote a lot of software that powers small businesses. As people exited Rails, the cost of maintenance has gone up... since you have to pay a lot to get someone writing Rails now.

Bigger parade, bigger cleanup.