This post contains a brief summary of what I’ve heard on Full Stack Fest 2019.
I’ve been visiting Full Stack Fest from the very first edition back in 2012. I think it’s a remarkable single track conference with topics which are really relevant for modern developers.
Previous years we also wrote blogs about it, these can be found here:
This year the conference is three days and there’s no clear distinguish between frontend and backend days. The location has changed. We’re now in Sitges, a beach place near Barcelona.
We were welcomed by Sara Vieira. She works at codesandbox, which we really like. I also like her humor. She is very direct and I like it very much.
I’ve seen Lee Byron at ReactEurope in Paris and this talk had some of the same elements. I really admire Lee for all his work and in showing everybody how we need to continue to change the abstractions, syntax and mental models. He shows the past in the future. Also liked the Svelte code example.
I’m not sure anymore how the talk was called, but she had an amazing talk on making developers tools. In her work for Rust / WebAssembly she sees that it’s very important to understand how developers use your tool. You don’t make a product, your enriching a developer. There is something like Language Strangeness Budget. When creating tools or clis, this is very important to keep in mind.
Our products are like the Fire Flowers. They turn Mario (a developer) into a Fire Mario! Senior developers should become Fire Mario Enablers.
Nice comparison with Baseball. We’re using a JAMstack for this blog (gatsby). Brian showed what the benefits are of JAMstacks. The static pages can be served everywhere. Github has some good workflows to automatically publish sites. Showing Github Actions, now, netlify and so on. He showed a project Open-sauced. It’s a frontend with github API as backend.
by Yan Cui
Interesting talk on how Yan migrated a monolith to a s8s environment. How it saves a lot of money. How it impacted the lead times for features and how he approached it. He showed a little monolith diagram of the application and a big diagram with the current lambda implementation. The latter looked a lot bigger, but as a matter of fact, was a lot less complex. The first diagram had simple boxes with a lot of functionality in it. The last one had a lot of boxes with isolated functions. He suggested to put all features in separate github repositories and give the task of deployment to each repository. Monorepos were not easy to use.
by Ellen Chisa Ellen complained about how long it takes to build a simple app. She wanted a simple app to register her mood, but months later, she was finally ready with setting up Rails, Heroku, Twillio, and so on. The end result is workable for herself, but can not even be shared, so there is something wrong. Too much accidental complexity.
She’s no co-founder of dark-lang. Dark is a holistic programming language, structured editor, and infrastructure, for building backend web services. It’s for frontend, backend, and mobile engineers.
This is all in Alpha testing, but she did some cool live coding to show the basic of dark-lang. We were all very impressed and kinda speechless.
Very good presentation on the topic of a13y. She showed why it’s so important and how you can improve your apps. Although it was already late, people wanted to hear her complete story and that’s a compliment!
It has a nice contrast with the prior presentation… this feels like a lot of accidental complexity.
by Una Kravets
Una did a great job in showing the possibilities of Houdini and how this can change the way websites will look. Houdini is not available in all brwosers, but it’s getting there. In Chrome you can already use it when you enable a flag;
chrome://flags/#enable-experimental-web-platform-features Once enabled, you can start programming in CSS. See extra-css for more examples.
by Angie Jones
Angie showed how you can miss a lot of things, because people are focussed on only a particular part of the app. She showed a clip Whodunnit? to prove it. By running automated tests, you can improve a lot. You’re testing exactly what text should be on the screen and what buttons to click. This seems all fine, but can still cause problems. Are the texts visible? Are they overlapping? Are the labels located correct? These kind of bugs are not rare. All big websites sometimes suffer from these errors. Angie showed a framework which takes screenshots and uses ML to analyse the differences with a baseline. Not pixel by pixel, because that is very brittle.
by Paul Frazee
Paul explained why P2P on the web deserves another chance. He works on the beaker browser. He showed the history of P2P. Napster, Kazaa, LimeWire, and so on. For some reason P2P was very normal, but for some reason P2P fell off. That’s a pity. Beaker re-introduces P2P nodes with the
dat:// protocol. P2P gives us Decentralization, Data Privacy, Data Ownership, No dev-ops and the code is truely open source. No hidden boxes on a server, just all code on each peer. Personally I’m passionate about P2P. We’re building an Identity Box using IPFS.
by Lin Clark
This was a very advanced talk, with probably the most impact on the world of software. WASI (WebAssambly System Interface) is an initiative to run WebAssembly outside the browser. WebAssembly Interface Types interoperate with all the things; languages, wasm, but also browsers and operating systems. This can have impact on everything we currently know. The slides by @codecartoons were very beautiful. I would definitely recommend watching the presentation in the link below.
Philip Wadler has a lot of energy, especially when he’s excited about something. In this case functional programming and proofing that your program is doing what you claim it does. In a language called Agda, he can write proofs. He uses github to openly write a book, and emphasises how wonderful that is. Functional Programming is becoming more and more accepted in for example banking. Philip uses Haskell and Agda in Blockchain to prove SmartContracts.
Sarah showed us a lot of examples how animations will improve the user experience. She showed a lot of (Vue / Nuxt) code examples how to achieve this.I recommend watching the presentation.
by Cate Huston
A great talk on how you can make teams work. I especially liked the part where she talks about the mismatch between team goals and individual incentives. When they are not aligned, it’s very hard to build a team. I recognized this a lot.
Daniel is part of the TC39. He explained how the stages work in TC39. He’s currently responsible for 3 proposals in Stage 3; BigInt, Class Public Instance Fields & Private Instance Fields and Private instance methods and accessors, and 1 proposal in Stage 2; Decorators. The last one you might already have seen in ember, Angular or MobX. Aligning the implementations is a very hard job. They all seem to have a slight different idea on decorators. It’s up to Daniel (and TC39 which have members of the ember, angular in it) to come up with a solution that doesn’t break the web.
Daniel is the creator of
curl, so he knows a few things about HTTP. HTTP/2 did improve a lot, but Daniel explained how the boxes in between the server and the client are very helpful. They see traffic passing by and they start helping us. This might look useful, but it is not. Especially not when you want to improve the network layer. That’s why HTTP/3 will use UDP instead of TCP. Of course this gives a lot of other interesting problems. Company networks often see UDP as a DDoS attack and blocks it, but in order to improve the speed of the internet, we need to change the protocol. The Head-on-line problem shifted from HTTP level to TCP level when switching to HTTP/2. This causes all streams to be blocked if a package is missing. HTTP/3 with QUIC can resolve the HOL problem on TCP level. This means only one stream is blocked when a package is missing. But it’s a long way… There are a lot of boxes in between..
I love Rust, so I’m not going to talk a lot about this presentation. Steve explains a lot about it and how Rust and the Rust Toolchain can be used for WASM. I recommend everybody to see the presentation. WASM (together with WASI) can be the future of s8s. Currently Docker is the container, but a browser can also be the container with WASM / WASI.
FSF 2019 was again a big success. Thanks codegram for organizing it.