Axino vs Vue, React, Angular.

Image for post
Image for post
Axino vs Vue, React, Angular.

Link: Getting started with Axino (A quick introduction to Axino)

Unlike frameworks like Vue.js, React.js, Angular.js. Axino strives to:

  1. Using a “clean” easy to learn / easy to debug language: it uses Typescript instead of JavaScript, because:
  • Typed languages are less error prone than dynamically typed languages.
  • Typescript is more standardized than JavaScript.
  • Typescript has a sane class model which is familiar to Java or C++ or Python developers.

2. Avoiding outlandish pseudo-html constructs, such as JSX used in React or in Angular.

// JSX:const element = (
<h1 className="greeting">
Hello, world!
</h1>
);
// HTML:<h1 class="greeting">
Hello, world!
</h1>

Which is problematic, because it looks like HTML, but it is not quite HTML (for instance, “class” has to be renamed “className” in order to distinguish it from the “class” reserved keyword from JavaScript).

3. Avoiding pseudo-JavaScript constructs such as e.g. the v-for predicates used in Vue.js:

<div id="app-4">
<ol>
<li v-for="todo in todos">
{{ todo.text }}
</li>
</ol>
</div>

4. Sticking to:

  • Typescript.
  • HTML5.
  • Simple development tools: “npm”.
  • Using a simple component-based approach to develop UI (user interfaces).
  • Using a simple “channel” approach (inspired by Google Go aka Golang) to tackle concurrency (asynchronous events inherent to web apps).

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store