
Rosario De Chiara discusses why small language models (SLMs) may outperform giants in specific real-world AI systems.

Vibe coding isn’t just AI-assisted chaos. Here’s how to avoid insecure, unreadable code and turn your “vibes” into real developer productivity.

GitHub SpecKit brings structure to AI-assisted coding with a spec-driven workflow. Learn how to build a consistent, React-based project guided by clear specs and plans.

:has(), with examplesThe CSS :has() pseudo-class is a powerful new feature that lets you style parents, siblings, and more – writing cleaner, more dynamic CSS with less JavaScript.
Would you be interested in joining LogRocket's developer community?
Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.
Sign up now
4 Replies to "Intro to Clio lang: Ship performance-critical JS with ease"
Performance?! Why is it measured in ms? That’s slow
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.
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!
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.