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

None of my projects want to be SPAs

whatisjasongoldstein.com

Post reply on HN
Print view View original

81–90 of 362 posts

Re: None of my projects want to be SPAs

#81

Post by vertex-four »

seba_dos1 wrote: post #61
masklinn wrote: post #50

Earlier quoted context omitted.

> You can write a lot of that stuff in a dozen lines of JQuery with nicely refreshing content and ajax instead of throwing in large amounts of framework bloat. OTOH jquery is much bigger than you'd expect, there isn't much of a difference between a minimized jquery and vue, or even react once you factored in gzip. And while I've no experience doing so using vue, writing small dynamic react components embedded in larg…

It's 2019, most of the stuff that jQuery used to handle is now included in the browser API. For instance, to have "AJAX", simply try window.fetch instead of $.get.

Then add a polyfill per api call to support anything but the most recent browsers, if you happen to want your site useable by people with old systems or who are at work.

Re: None of my projects want to be SPAs

#82

Post by etnos »

In my last consulting company the CTO decided every single project for now on must be an SPA with a de-coupled back end, that is a mandate (rather idiotic if you ask me).

We had relatively simple projects that could be done in a couple of weeks with a traditional MVC framework, bloated to multi men teams working for months.

But hey I guess over-engineering translates to man hours, man hours translate to revenue.

Re: None of my projects want to be SPAs

#84

Post by totalrobe »

b3b0p wrote: post #80

I feel as if many sites that used to be fine and work well have regressed in usability and features and introduced unexpected behaviors and bugs since the SPA paradigm seems to have taken over. This seems especially true for many corporate, bank, shopping brand sites, etc. An example is the Capital One 360, Chase, and AMEX sites and even Reddit. Even JustWatch.com seems like it's fairly polished, still has it's quirk…

TIL there is a search on HN after more than 6 years of browsing...never noticed it

Re: None of my projects want to be SPAs

#85

Post by k__ »

kerkeslager wrote: post #79

Back when I was doing React, what pulled me in was that it WASN'T a framework for SPAs. What I got from it was the ability to build UI widgets (components, in React terms) that worked within a page, and were composable with other UI widgets. With that approach, you really wanted to keep every component self-contained. That meant a lot of bookkeeping with passing events back and forth between parent and child widgets,…

I don't think Redux is that big of a deal as you describe it.

Many people just use setState.

Since my last Redux project in 2015, I did many React and React-Native projects and not one of them used Redux.

Re: None of my projects want to be SPAs

#86

Post by seba_dos1 »

vertex-four wrote: post #81
seba_dos1 wrote: post #61

Earlier quoted context omitted.

It's 2019, most of the stuff that jQuery used to handle is now included in the browser API. For instance, to have "AJAX", simply try window.fetch instead of $.get.

Then add a polyfill per api call to support anything but the most recent browsers, if you happen to want your site useable by people with old systems or who are at work.

...which you can selectively serve only to the old browsers :)

Re: None of my projects want to be SPAs

#87

Post by WrtCdEvrydy »

kerkeslager wrote: post #79

Back when I was doing React, what pulled me in was that it WASN'T a framework for SPAs. What I got from it was the ability to build UI widgets (components, in React terms) that worked within a page, and were composable with other UI widgets. With that approach, you really wanted to keep every component self-contained. That meant a lot of bookkeeping with passing events back and forth between parent and child widgets,…

Redux was the solution to server side rendering state.

If you don't use redux, then keeping state synced with a server side rendered application because nearly impossible.

Re: None of my projects want to be SPAs

#89

Post by k__ »

gedy wrote: post #55
wickoff wrote: post #28

Personally I was dumbfounded by complexity of doing async things in redux. Libraries like redux-thunk, redux-sage, redux-observable should not exist. The amount of boilerplate required was incredible and meaningful typescript support was very difficult to achieve. Then I tried mobx, I was able to write a small app after 15 minutes of reading the docs and now I love react.

My experience as well, MobX saved React for me, and I did a 180 from hating it to loving it.

For me, there wasn't even an alternative library needed.

I mostly use setState nowadays and it's enough.

Re: None of my projects want to be SPAs

#90

Post by duxup »

Every time I read an article about SPAs... I feel like someone has a new view on what an SPA even IS, what it is good for, and so on. Many articles sound like they're talking about entirely different things.

I get the definition, but I don't see a lot of problems and etc .... necessary a part of SPAs.

Post reply on HN