Frontend Lightning Talks - Frontend Frameworks

Frontend Lighting Talks - Frontend Frameworks summary:

19:00 - 19:10 👋 Welcome & Introduction
19:10 - 19:30 💬Nuxt, Next… its NestJS - Ankit Raghuvanshi
19:30 - 19:35 🍹Drink break
19:35 - 19:55 💬 Astro your web on a diet - Sander Geraedts
19:55 - 20:15 💬 Learning to love HATEOAS - Sander ten Brinke
20:15 - 20:30 🍻 Leftover question and closing

The last Frontend Lightning Talks of 2021! Feel free to join if you are interested in WebAssembly, Angular, Vue.js or React! There will be three great and short presentations so you'll get the max out of your evening full of inspiration! It will be a remote session, so you can relax and learn in your own chair.

💬Nuxt, Next… its NestJS - Ankit Raghuvanshi
In recent years, we have seen awesome projects like Angular, React or Vue, which improves developer productivity and enable the creation of fast, testable, and extensible frontend applications. However, while plenty of superb libraries, helpers, and tools exist for server-side JavaScript applications, none of them effectively solve the main problem of - Architecture. I came across NestJS and got fascinated to show what all it has to deliver.

💬Astro your web on a diet - Sander Geraedts
"Sander will give a talk about Astro, the latest and (in his opinion) greatest Static Site Generator, meaning every page of the website is prebuilt when the user requests it. Astro aims to remove all Javascript which is not specifically needed to be run by the user to improve pagespeed and put the web on a diet. As a contributor to the project, Sander will take you through the ins and outs of Astro, and explain when to use it, and when it might be best to work on another project that's better fitted for Astro not to use Astro. As Astro is in very early access, it is still in heavy flux. Sander will also talk about his experience building projects on a quickly changing tool."

💬Learning to love HATEOAS - Sander ten Brinke
Have you ever noticed that your web apps often contain code that already exists on the server? For example, you must only render that delete button if the user is the owner of this item AND if the item is allowed to be deleted. But the API already checks this too when you perform that delete action! And if the API changes it's delete logic, you need to manually update all your clients, too! This is boring work that might actually take a lot of time if you need to update a lot of clients like apps and websites and wait for them to deploy... If only there was a better way! In this talk I will show you a solution to this common problem thanks to HATEOAS. You will learn what HATEOAS is, how to pronounce it, and how you can start using it today!

Checkout last meetings recording: https://www.youtube.com/watch?v=8vtdmcjJ8xY