Future Content

Why Marko?

How to spend 5 years making a framework

And why did it take so long?! Michael, a software engineer at eBay and member of the Marko core team will walk through the challenges, design decisions and tradeoffs made while evolving the Marko framework used by hundreds of pages on ebay.com. Lots of interesting learnings and you'll get a look at the newly released Marko 6 which is open source and available to use for your own projects.
Outcomes
- Learn more about optimizing for the web
- Tradeoffs made by various frontend frameworks
"We're getting really close now" - Michael

Solving the Challenges that come with Server-First

The last few years have seen a shift to in focus from UI frameworks to the Server. But there are challenges that come with this shift. While this may be somewhat new to you, the Marko team has been focused on server-first development for a long time now. Come hear what techniques we use to solve common problems - techniques that will be useful to you regardless of your web framework of choice.
The Marko team has been pioneering server-first techniques long before it became a broader industry trend. In this talk, we'll share insights from our experience solving streaming and island architecture challenges. Learn how to mitigate layout shifts, optimize downstream buffering, and resolve over-serialization—techniques that are valuable regardless of your stack. Whether you're using Marko, React, or vanilla JavaScript, this talk will help provide practical strategies for building a more performant web.
Previous Presentation
Streaming
- Out-of-order Layout Shift
- Downstream Buffering
Islands
- Over Serialization
- Donut Islands

How we converted eBayUI to Marko 6

Overview of syntax decisions and how they come together

Copy-paste Refactoring of Frameworks (and Marko)

Hydration & Resumability

Streaming

Typescript & Editor Intellisense

The power of everything being a tag

Testing (End user & developer user, not test user)

Future Articles & Talks