# Marko 6 introduction comic

Like [the Google Chrome announcement/explainer comic](https://www.google.com/googlebooks/chrome/)

Polo Bear & Marco Racha

## What should it cover?

1. Marko 6 was created to solve problems:

- Client devices today are lumpier than they've ever been.
- Automatic sub-component hydration and "Resumability???"
- No more VDOM: goodbye triple copies of DOM trees and GC pauses
- Streaming, partial hydration and other features that React is finally supporting. Maybe you'd be interested in the OG who's been battle-testing these features for almost a decade?
- Developers have also gotten pickier
- Nicer authoring experience with Tags; you might even use Marko just for that, even if you can't leverage the server! (That copy/paste migration that sold me, ask what other things are uniquely good about Tags)
- Oh yeah. And TypeScript.

2. WTF is Marko anyway?
- The problems/story behind eBay making it (No SSR regressions, ecommerce thrives on perf, "if employees were recognized for making websites fast… well, you'd know. there'd be no slow websites")
- Frameworks can only make certain things easier, so what does Marko make easier? Can that be transformative for what you make?
- Marko 6 keeps Marko’s good parts; Render HTML like you mean it!
- Best-in-industry streaming support
- Fast-as-hell server rendering
- Minified HTML output
- Easy automatic server-only code
- Why do things on the server-side?
- Better backbone connections
- More reliable performance and better tradeoffs
- Progressive enhancement and progressive performance
- Note what PHP and other server frameworks got right:
- Fast HTML generation (serving dish with HTML instant ramen)
- Streaming (spouting from trunk)
- And the easiest way in web dev to go from HTML knowledge to dynamic pages (trunk becomes stairshaped):
1. Rename `.html` to `.php`
2. `&copy; <?php echo date("Y"); ?>`

3. What could you create with what Marko 6 makes easy?
- eCommerce that's fast on cheap phones and iffy cell data?
- Government or nonprofit services/resources to serve everyone, including those who rely on Lifeline phones?
- (other ideas sorely welcomed)