Very nice, perhaps the topic would have needed more time
@João Ferreira thanks for the feedback. I did not say Redux was the first (or only) implementation of the Flux architecture, sorry if that was not clear. I insisted on Redux because around 2015-2016, it became clear that Redux was a good choice for React apps that needed a data management layer other than what React offered.
Webpack is chaos. It's complex software that can be very difficult to use correctly and understand, and this talk perfectly addresses quick and simple wins on getting smaller bundle sizes. I came out with a ton of to-dos.
The speaker was very engaging and spoke clearly.
This is mostly an intro to server side rendering, and a lot of the time is spent discussing the wrong way to do it (double rendering). Some interesting points like performing requests to an API mid-request in the back-end are not addressed.
The author also seemed to think redux was the first implementation of the flux architecture?
Some interesting vulnerabilities but most of them are of the type "if the site is malicious, they can do a bunch of bad stuff", which is nothing new to PWAs. The delivery of the talk could've been more engaging as well.
This talk, like everything and everyone, is AWESOME!
The talk was good as an introduction on the topic, but it did not explain well enough the rationale of some of the choices.
Particularly picking Kafka as a broker... it's not that Kafka is "bad", quite the opposite, but for a *lot* of projects and teams it can definitely be the wrong choice.
One has to know what he is doing, and the talk gave [mostly] good advice but did not explain where they came from.
Insightful, interesting, and with a good pace!
Good talk as an overview to the technology.
I was expecting more details on why one should chose it, or perhaps a comparisons with DAT... but it's just because I already knew the project.
Informative, and well executed.