Re: Why SPAs are usually a waste of time/money

This article assumes a lot about the problem being solved and the team
solving it. In general it's also dangerous to just categorical assert that
an entire suite of apps in the wild are doing it wrong. It also entirely
disregards several of the benefits of SPAs. Having a CDN deliver your
frontend can save you money, time, and performance. Separating your API
from your frontend can push forward the timeline of opening up your API so
that other companies can integrate with you. Testing on MPAs on the
actually frontend interface tends to be disregarded, whereas with SPAs it's
a first-class citizen.

I'm all for sticking with the monolith and rolling with the Rails blessed
path, but this article comes off more as an uninformed viewpoint about the
quality of frontend development these days than it does a discussion of the
tradeoffs. There is more complexity there for sure, but there are many
benefits not discussed.

Also just saying anything is a bad architectural choice 99% of the time is
wrong. Everything has to come with context.

On Tue, Oct 30, 2018 at 9:53 AM Greg Navis <[email protected]> wrote:

> Hey!
>
> I'd like to share an article with you why SPAs are a bad architectural
> choice from a business perspective 99% of the time.
>
> https://www.gregnavis.com/articles/the-architecture-no-one-needs.html
>
> Thoughts?
>
> Best regards
> Greg Navis
>
> Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
>


-- 
*Kevin D. Deisz*
CTO, CultureHQ <https://www.culturehq.com>


Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>