Riot vs Svelte: What are the differences?

## Introduction
Riot and Svelte are both popular frontend JavaScript frameworks that aim to simplify web development. However, there are key differences between the two that set them apart.

1. **Compilation Process**: Riot uses a runtime compiler, which means that it compiles the code in the user's browser at runtime. On the other hand, Svelte uses a compiler that converts the code during the build process, outputting highly optimized vanilla JavaScript code.

2. **Reactivity**: In Riot, reactivity is not built-in and developers need to manage reactivity through manual DOM manipulation or additional libraries. In contrast, Svelte has reactive declarations that automatically update the DOM when the data changes, making it more efficient and developer-friendly.

3. **Bundle Size**: Riot is known for its small bundle size, making it ideal for projects where minimizing code footprint is crucial. Svelte, however, produces even smaller bundle sizes by eliminating the need for a virtual DOM at runtime and optimizing the generated code.

4. **Component Architecture**: Riot follows a component-based architecture where each component manages its state independently without a centralized store. Svelte, on the other hand, promotes a centralized app state management using stores, allowing for easier data sharing between components.

5. **Lifecycle Methods**: Riot provides specific lifecycle methods such as `onMounted` and `onUpdated` for handling component initialization and updates. Svelte, on the other hand, has a single `onMount` lifecycle method for both initialization and update logic, simplifying the component lifecycle process.

6. **Code Reusability**: While both Riot and Svelte support code reusability through components, Svelte's reusability is enhanced by its reactive nature, allowing components to easily share and respond to changes in data without manual intervention.

In Summary, Riot and Svelte differ in their compilation process, reactivity handling, bundle size optimization, component architecture, lifecycle methods, and code reusability strategies.