Closed Spice-Z closed 5 months ago
hey there @Spice-Z thank you for opening an issue with us! Your talk proposal sounds super interesting, I'll put you down for June! Please use code SPEAKER
to secure your ticket and let me know if you have any questions! :) https://lu.ma/vanjs-june-2024
by the way, usually we use the Mini-bio to introduce the speaker, make sure you add anything else there that might be relevant!
@bibschan
Thank you! I updated the Mini-bio!
@Spice-Z perfect! would you be able to also send me a picture that I can use for our introduction slides?
@bibschan Sure! Can I use this picture? https://photos.app.goo.gl/AGCpDXGr7oA5K79y8
Before SPAs became popular, MPAs were the norm. Web servers ran on PHP, Ruby, or other languages, and used tools like templates, jQuery, and Gulp. However, SPA libraries such as React, Angular, and Vue brought SPAs as the new standard. Concurrently, TypeScript and Node.js were developed, enhancing the capabilities of developers. Numerous modern JavaScript frameworks like Next.js, Nuxt.js, and Gatsby now offer full-stack TypeScript development with options for SSR or SSG. Currently, Astro advocates for a return to the MPA approach. Why does Astro want to go back to MPAs? I believe Astro's MPA approach is much more advanced than its predecessors. I want to discuss why I favor Astro, contextualized by this history of web development.
Speaker Bio