SPAs are harder and always will be (2013)

Re:SPAs are harder and always will be (2013) by mthamil on Wednesday January 17, 2018 @01:16PM (#16170261)

I don't mean to be rude, but you clearly aren't talking about the same kind of application. I have worked on a SPA before that used knockout and jquery with an ASP.NET MVC backend and Razor-rendered 'templates'. It was a much different beast than an angular or react app.

[ Parent | on HN ]

Re:SPAs are harder and always will be (2013) by jorgeleo on Wednesday January 17, 2018 @03:33PM (#16171527)

I am observing that you are right, there is no definition globally accepted by the community on what an SPA is.

For me, a better definition is the one that it is independent of the technology used to implement it. An SPa is a way to structure an app, is not a vendor feature or a tool.

While is true about nowadays angular et all are the tools commonly used to create SPA, the tool shouldn't have the power to change the definition, so your knockout MVC is still an SPA.

If the OT chose a complicated set of tools to develop an SPA, then is his decision and the difficulty lies in his decision of the tools chosen, not on the SPA type of app.

[ Parent | on HN ]

Re:SPAs are harder and always will be (2013) by neosavvy on Wednesday January 17, 2018 @03:05PM (#16171287)

I agree we aren't talking about the same apps.

I don't know if folks much consider vanilla JS / JQuery apps Single Page Applications.

I think (but am not sure) that all SPAs are built these days with Angular, React, Ember, Elm, Vue, or some other framework I haven't paid attention to.

Usually tied into Restful webservices that don't do any templating server side unless it's via Isomorphic JS. Maybe I got it all wrong though.

[ Parent | on HN ]