Re:A single-page app is almost always worse than a multi-pag...
by rpeden on Tuesday October 30, 2018 @01:38PM
(#18339268)
Using SOAP from JS is doable if you really want to. :)
But if we're comparing to crufty tech, I'd say what I was talking about in that sentence was more like DCOM or CORBA. Both of which were nice in concept but a bit of a PITA in practice.
Re:A single-page app is almost always worse than a multi-pag...
by jrochkind1 on Tuesday October 30, 2018 @01:45PM
(#18339343)
Thanks, you're right, that's what I meant. I have thankfully forgotten most of what I ever knew about these technologies.
Re:A single-page app is almost always worse than a multi-pag...
by scroot on Tuesday October 30, 2018 @01:54PM
(#18339452)
Check out Lively4 [1] and see what you think. It's the fourth incarnation of dan ingalls' LivelyWeb concept.
[1] https://lively-kernel.org/lively4/lively4-core/start.html [2] https://github.com/LivelyKernel/lively4-core
It sounds to me like "what if Javascript had SOAP", heh.
We can envision lots of things. The beauty of software engineering/architecture is you can envision almost anything.
The trick is that the more complex the thing is, the harder it is to pull of _well_, and the easier it is to end up with a monster.
The complicated things take more expertise/skill/experience to design, and _also_ take more development time to produce -- and on an ongoing basis to maintain. And it's not always clear where development resources come from on 'shared commons' like platforms (unless they are proprietary and only available for a fee). The current front-end JS environment is already _pretty darn complex_ of course. How well it's pulling it off, well, is a matter of debate central to the OP.
On, and then there's getting different actors to coordinate in thing that require that (like browser's supporting something).
I can envision it too. But I wouldn't wager much on it happening in a way that actually results in an improved development environment (instead of a monster).