Instead of one big code pile, activities will gently enforce a clean, standardized way for organizing code.

They are an abstraction that will save code and bugs, and introduce strong conventions.

The office door is locked at 5pm. We work hard, but at 5 it's time to go home!

On the other hand, we could impose restrictions to the feature in order to avoid these hard paths.

Instead, my purpose is to illustrate why an alternative approach — based on Single File Components with real CSS — is so damn delightful.

By enforcing this practice, Svelte can make some assumptions that simplify your code.