3 ms·

I couldn't agree more. It is a spectrum. <-- Fully MPA ... MPA with mini SPAs ... Fully SPA. --> Many don't venture in the middle. Not sure why. Do not stay o

I couldn't agree more. It is a spectrum. <-- Fully MPA ... MPA with mini SPAs ... Fully SPA. --> Many don't venture in the middle. Not sure why. Do not stay on either end. It will bite you!

zerkten 5y ago
People don't venture in the middle because it's complicated and scary for many people due to the skill requirements. It only starts to feel safe to play there when you have experience with development at both ends of the spectrum because you likely won't have the support of tools which are intended to run there. Further, it's a compromise that is difficult to explain and justify to management. If they are risk averse then they won't want to move far from the safety of the frameworks at either end of the spectrum. If you are a developer of frameworks, it also seems advantageous to go to one end of the spectrum because it's easier to reason about the problem space. When you target the middle there starts to be more variations in how to handle it best. It's really the only place to go though, if folks really want to innovate and provide better experiences for all.
- martin_drapeau 5y ago
  Laravel encourages the middle ground. Sprinkle Vue.js. I've worked in both MPA and SPA. The middle ground is much faster. You can pre-load objects in the page and then use AJAX to finalize loading. The user experience is snappier. The bundle size also remains smaller. Divide and conquer. Yes, it does require being comfortable navigating back and front end. Over time, a good developer will get there.
  - nightski 5y ago
    This trope of "if you were just skilled enough" needs to die. Things cost money. They cost money to maintain and evolve. If a solution requires exceptionally high skill that means it is very expensive and pushes employees to their limits. Meaning it is not a healthy technological solution. It's funny how the article goes on about "If managers were just good enough". But the problem is managers face real world constraints. They can't just give us unlimited resources to live out our complex ego-driven tech fantasies.
    - zerkten 5y ago
      >> This trope of "if you were just skilled enough" needs to die. Things cost money. They cost money to maintain and evolve. I don't disagree terribly with the trope aspect, but people are hurting from the cost to evolve and maintain projects using approaches that sit at the extremes. There needs to be some understanding, and possible embrace, of elements of the middle ground in order to be truly maintainable in a lot of cases. My call to action would be more for the innovators and framework developers to think more about this. Companies can try to solve it for themselves, but forces like staff turnover prevent meaningful progress for most.

I couldn't agree more. It is a spectrum. <-- Fully MPA ... MPA with mini SPAs ... Fully SPA. --> Many don't venture in the middle. Not sure why. Do not stay on either end. It will bite you!

zerkten 5y ago

People don't venture in the middle because it's complicated and scary for many people due to the skill requirements. It only starts to feel safe to play there when you have experience with development at both ends of the spectrum because you likely won't have the support of tools which are intended to run there. Further, it's a compromise that is difficult to explain and justify to management. If they are risk averse then they won't want to move far from the safety of the frameworks at either end of the spectrum. If you are a developer of frameworks, it also seems advantageous to go to one end of the spectrum because it's easier to reason about the problem space. When you target the middle there starts to be more variations in how to handle it best. It's really the only place to go though, if folks really want to innovate and provide better experiences for all.

martin_drapeau 5y ago
Laravel encourages the middle ground. Sprinkle Vue.js. I've worked in both MPA and SPA. The middle ground is much faster. You can pre-load objects in the page and then use AJAX to finalize loading. The user experience is snappier. The bundle size also remains smaller. Divide and conquer. Yes, it does require being comfortable navigating back and front end. Over time, a good developer will get there.
- nightski 5y ago
  This trope of "if you were just skilled enough" needs to die. Things cost money. They cost money to maintain and evolve. If a solution requires exceptionally high skill that means it is very expensive and pushes employees to their limits. Meaning it is not a healthy technological solution. It's funny how the article goes on about "If managers were just good enough". But the problem is managers face real world constraints. They can't just give us unlimited resources to live out our complex ego-driven tech fantasies.
  - zerkten 5y ago
    >> This trope of "if you were just skilled enough" needs to die. Things cost money. They cost money to maintain and evolve. I don't disagree terribly with the trope aspect, but people are hurting from the cost to evolve and maintain projects using approaches that sit at the extremes. There needs to be some understanding, and possible embrace, of elements of the middle ground in order to be truly maintainable in a lot of cases. My call to action would be more for the innovators and framework developers to think more about this. Companies can try to solve it for themselves, but forces like staff turnover prevent meaningful progress for most.