Skip to content

Taon vs Others

Taon’s isomorphic architecture with code splitting makes it unique
in the world of TypeScript frameworks.

Taon vs NestJS

NestJS Taon.dev
Approach More General (REST API, GraphQL – everything) More Focused (on seamless, elegant REST API)
Code splitting and shipping separate versions of the same file to client (browser) and backend No Yes
Node_Modules Normal npm approach Taon Containers with base/core packages
Dependency Injection Similar to Angular DI Each class is a singleton inside its context
Class Names The framework does not use class names for any specific purpose Context names and TypeScript class names are used to build automatic API paths and to identify/replace classes during inheritance
Inheritance Similar to Angular DI Everything can be easily inherited/extended from Contexts, Controllers, Repositories, etc. – everything is a singleton in its context and has a unique name
Controllers Class methods with decorators can be used as a way to access APIs Automatically generated REST API calls based on contexts, inheritance, controllers, class method names, and decorators
Databases Supports all databases SQL.js for development, MariaDB for production

Taon Vs ExpressJS

ExpressJS Taon.dev
Controllers for rest api Inside functions Inside classes
Inheritance of controllers No Yes
Isomorphic middlewares No (only backend middlewares) Yes
Auto generated rest api endpoint No Yes
Can be started inside browser? No Yes (in websql mode)

Taon CLI Vs Angular CLI

Angular CLI Taon CLI
All nice third party packages already included No Yes
Building packages that can shared assets ? No Yes
Building packages that can shared SCSS files (index.scss) ? No Yes
Normal "npm install" just works Yes No (different approach -> stable packages base + you are putting your taon projects (each taon project is a library also) inside "organization" parent project. By building and updating organization you have strict control over third party packages)

Taon Vs NextJS

NextJS Taon.dev
Frontend Framework React Angular
Isomorphic TypeScript capability Yes Yes
Cutting backend code from isomorphic TypeScript files (so the rest can go to frontend) No Yes