Leif Åstrand (@leifastrand) profile picture

Leading research for Vaadin's frameworks: Flow and Hilla

Joined July 2013
Photo by Leif Åstrand (@leifastrand)Photo by Leif Åstrand (@leifastrand)Photo by Leif Åstrand (@leifastrand)Photo by Leif Åstrand (@leifastrand)Photo by Leif Åstrand (@leifastrand)
Maybe spec-driven development got it backwards? Instead of treating specs as authoritative input for generating throw-away code, what if we'd instead have the code as authoritative and generate throw-away specs relevant for the change we want to make?
1
91
Leif Åstrand retweeted
What if you could build a reactive web app using only #Java? Join Leif Åstrand at the upcoming LJC meetup to see how to build a modern app with #springboot, #Redis, and #Vaadin – no JavaScript required. 📍 London, May 28 🔗 Register at: meetup.com/londonjavacommuni…
4
6
478
This will be a great show also if you already know Vaadin since I will show how to use the new reactive UI state management functionality, Signals, that we launched in Vaadin 25.2. It feels like a new framework in my opinion!
Today at 18:00 CET, Leif Åstrand will build a reactive web app with Spring Boot and Vaadin using only Java. Real-time updates, external services, and UI, with no JavaScript, HTML, or CSS in the stack. Save your spot: bell-sw.com/webinars/reactiv…
1
2
83
Leif Åstrand retweeted
On April 28, @leifastrand will show how to build a reactive web app with @springboot and @vaadin using only #Java, covering real-time updates, external services, and UI without dropping into JavaScript, HTML, or CSS. 📅 Apr 28, 18:00 CET bell-sw.com/webinars/reactiv…
3
7
442
Exciting new feature in Vaadin 25.1.0 rc1. View state values in signals are preserved when hotswapping. You stay where you were before but with new logic applied. Feels like using a completely new framework!
1
2
7
479
See how you can make it easier to reason about collaborative UI by sharing UI state over the network!
🍃 Beyond REST: Using Full-Stack Signals for Real-Time Reactive UIs by @leifastrand @ Spring I/O 2025 ▶️ Video: youtu.be/WLF_RSYXKz8 🔗 Slides: 2025.springio.net/slides/bey… #springio25
1
8
2,589
This is also the most impactful Vaadin webinar so far this year based on the number of sign-ups. You still have a chance to join and get the opportunity to get live answers to your questions!
I think this will be the most impactful framework-level change for Vaadin since going from GWT to web components. Even better is that we can preserve full backwards compatiblity! The preview API in Vaadin 24.8 is just the beginning, but let's start from those fundamentals!
1
4
114
I think this will be the most impactful framework-level change for Vaadin since going from GWT to web components. Even better is that we can preserve full backwards compatiblity! The preview API in Vaadin 24.8 is just the beginning, but let's start from those fundamentals!
Reactive frameworks changed front-end dev: update state, the UI just works. Now, #VaadinFlow does the same for #Java devs with Signals in 24.8. See what’s possible in our live webinar + demo with @leifastrand. 📆 July 9th @ 15:00 CEST Save your spot: bit.ly/4ez5nRx
2
4
249
Leif Åstrand retweeted
Introducing: The most over-engineered way to find a component name. Built with AI, a bit of randomness, and confetti. Because nothing says “enterprise-grade” like a spinning wheel and JSON. 😉 Try it out today! 👉 bit.ly/4lcs29e
3
12
520
Is there any public info on how the jOOQ code base is managed so that the paid editions support older Java versions while the open source version doesn't? Or is that a corporate secret?
1
2
126
Seems like the open source code uses new Java features which makes me suspect one of these options: * Full internal fork of the open source version * An ever growing set of patches that are applied for every build * Automatic transformation using something like OpenRewrite
1
79
Replying to @springcentral
@springcentral enterprise.spring.io/project… and spring.io/projects/spring-bo… show different info on how long the support overlap was between the 3.0 release and the end of OSS support for 2.x. Either 12 months or around 7 months. What should be expected for the Spring Boot 4 release?
1
83
And today, the dates on those two pages are more aligned but there's still roughly a month difference between 2023-05-19 and 2023-06-30 as the end of OSS support for 2.7. The enterprise page is also missing the recently announced 5 years enterprise support.
51
What do you call an AI that uses a different kind of neural network? Neurondivergent!
48
Leif Åstrand retweeted
SPA vs. Full-Stack – What’s the better approach? SPAs can deliver great #UX—but at the cost of complexity. At @Jfokus 2025, @leifastrand explores the shift toward full-stack solutions for simpler, faster development. 🎥 Watch the full talk: bit.ly/4b0t7fJ
2
4
320
You might have good reasons to not do full-stack development. But if you suggest one of separation of concerns, skill overload, or 3rd party clients, then I might accuse you of missing the point. vaadin.com/blog/objections-a…
2
8
369
If you had a voice AI assistant working alongside you in applications, what would you like it to do for you? For example, would it be useful for it to be able to interact with the UI like here? github.com/marcushellberg/vo…
2
6
1
16
1,449
Just took JEP 450 from @java 24 ea for a spin. A simple Hello World UI in @vaadin Flow goes from 17.9 kB to 15.2 kB, thus supporting 17% more users with the same memory. Not bad for toggling a command line parameter.
1
10
436
Goes from 136 kB to 117 kB with the "Grid With Filters" view from start.vaadin.com so it seems to be in the same ballpark also for non-trivial examples. Measured using gist.github.com/Legioth/2515…
1
59
Leif Åstrand retweeted
Vaadin 24.6 is here! 🎉 Highlights in this release include: ✨ New Card & Dashboard components 📦 Enhanced drag-and-drop API 🤖 Smarter #VaadinCopilot 🛠️ Upgraded @gradle & @springboot support 💻 Easier installation with Control Center See what’s new: bit.ly/41EE9EU
1
12
1
33
2,544
Do I count right about using LLMs for writing code? AI handles the first 80% well but struggles with the rest. And as we know from software engineering in general, the remaining 20% will take 80% of the effort. That's lots of buzz for getting the costs down from 100 to 80.
1
65