Please login or sign up to post and edit reviews.
You still have to build two apps
Podcast |
Frontend First
Media Type |
audio
Categories Via RSS |
Technology
Publication Date |
Feb 27, 2019
Episode Duration |
01:01:05

Topics include:

  • 0:00 - Refreshing an Ember app when a new version is deployed

  • 11:05 - When SPAs become too difficult

    • 14:50 - Building an SPA never got as quick as we'd hoped
    • 19:20 - You're now responsible for two applications
    • 28:00 - Integration costs
    • 32:00 - Architecture is easier within a single monolith
  • 40:20 - Beginners should use the same tools as experts

    • 40:50 - Rolling advanced solutions back into the framework
    • 47:41 - Services that are used by both beginners and experts
    • 52:32 - Can you start an SPA without making an API server decision?

Links:

Sam and Ryan chat about the integration costs that make developing an SPA so difficult. They also talk about different ways to reload an Ember application while people are actively using it, as well as why it's important for beginners to use the same tools as experts.

Topics include:

  • 0:00 - Refreshing an Ember app when a new version is deployed

  • 11:05 - When SPAs become too difficult

    • 14:50 - Building an SPA never got as quick as we'd hoped
    • 19:20 - You're now responsible for two applications
    • 28:00 - Integration costs
    • 32:00 - Architecture is easier within a single monolith
  • 40:20 - Beginners should use the same tools as experts

    • 40:50 - Rolling advanced solutions back into the framework
    • 47:41 - Services that are used by both beginners and experts
    • 52:32 - Can you start an SPA without making an API server decision?

Links:

This episode currently has no reviews.

Submit Review
This episode could use a review!

This episode could use a review! Have anything to say about it? Share your thoughts using the button below.

Submit Review