2021-05-25
1411
#js libraries
Hussain Arif
49240
May 25, 2021 ⋅ 5 min read

Intro to Clio lang: Ship performance-critical JS with ease

Hussain Arif Hussain is a CS student in Pakistan whose biggest interest is learning and teaching programming to make the world a better place.

Recent posts:

master state management hydration Nuxt usestate

Nuxt state management and hydration with useState

useState can effectively replace ref in many scenarios and prevent Nuxt hydration mismatches that can lead to unexpected behavior and errors.

Yan Sun
Jan 20, 2025 ⋅ 8 min read
React Native List Components: FlashList, FlatList, And More

React Native list components: FlashList, FlatList, and more

Explore the evolution of list components in React Native, from `ScrollView`, `FlatList`, `SectionList`, to the recent `FlashList`.

Chimezie Innocent
Jan 16, 2025 ⋅ 4 min read
Building An AI Agent For Your Frontend Project

Building an AI agent for your frontend project

Explore the benefits of building your own AI agent from scratch using Langbase, BaseUI, and Open AI, in a demo Next.js project.

Ivaylo Gerchev
Jan 15, 2025 ⋅ 12 min read
building UI sixty seconds shadcn framer ai

Building a UI in 60 seconds with Shadcn and Framer AI

Demand for faster UI development is skyrocketing. Explore how to use Shadcn and Framer AI to quickly create UI components.

Peter Aideloje
Jan 14, 2025 ⋅ 6 min read
View all posts

4 Replies to "Intro to Clio lang: Ship performance-critical JS with ease"

    1. All `console.log` calls are redirected to the DOM, and they’re costly, that’s why the playground appears to be slow. You can check out my latest article here:

      https://medium.com/geekculture/clio-extremely-fast-multi-threaded-code-on-the-browser-e78b4ad77220

      or check the benchmark here:

      https://github.com/clio-lang/benchmark

      Clio is always faster than JavaScript, and sometimes extremely faster, if you check the benchmark the fib function’s performance is close to C. In addition to that, you can do multi-threading to speed up your code.

  1. Thanks for the great article and for featuring us Hussain! I really enjoyed the article and I’m going to add a link to it in our documentation, if it’s alright by you! By the way, the installer issue you reported is fixed in the latest release, give it a try 😉

    Reading your article, I noticed some of the code samples don’t compile, they throw a syntax error. First one is the comparisons where you used = instead of ==, this is changed in the recent versions. Other issues are in the mapping section, I will share a few links with the corrected code here.

    Comparisons: https://tinyurl.com/ttw4x58j
    Mapping: https://tinyurl.com/djfb9hta
    Mapping (with anonymous functions): https://tinyurl.com/sfk7sy9h
    Pipes: https://tinyurl.com/378we5vj

    Thanks again for the great article!

  2. Thank you so much for your feedback, Pouya! Yes, you can include this article in your documentation.
    As for your question, I wrote this article when Clio was in version 0.35(back in April), however it got published just now.
    Other than that, Clio really is a great programming language. Can’t wait to play with it in the future.

Leave a Reply