HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
MithrilJS
mithril.js
JavaScript2014–2025
MithrilJS / mithril.js

mithril.js

A JavaScript Framework for Building Brilliant Applications

25Distinct people
34Mentions
0Explicit recommenders
14.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A JavaScript Framework for Building Brilliant Applications

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:01:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year34 dated mentions

Observed mentions: 2014-03-24 17:00:10 UTC to 2025-05-12 00:10:30 UTC.

0123452014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC505
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC404
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC514
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC505
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC413
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC404
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC220
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC211

What Hacker News says

5 sources
- I use Browserify(1) because it allows me to use CommonJS(2) modules and bundle my JavaScript painlessly. - Beyond the pretty standard debowerify(3) and hintify(4) transforms I use babelify(5) to help me sprinkle fancy ES6 features here and there. - Node-based watchers and the npm client itself are all broken in many ways and very bad Unix citizens so I've stopped using npm for anything beyond actual package management and I will almost certainly replace the npm client with Yarn(6) very soon. The venerable make(7) or the much much younger but very dependable modd(8) are infinitely better than all that Node-based crap on _every_ front. - I use tape(9) for tests (works like node-tap(10) with a little fewer dependencies) but I _love_ the look of ospec(11) even if it's not TAP(12)-compliant. - Some JS libraries I've used recently: route-pars
Read the rest
In Ask HN: What languages and technologies/tools are you using right now?
No, we're working on a v1.0 release You can see the latest code here: https://github.com/lhorie/mithril.js/tree/rewrite The main highlights are improved performance, modularity and API design. The `render` module - which is analogous to React/Preact - is about 3kb min+gzip and has support for fragments, lifecycle hooks for animations among other things. Other additions to the framework include new utilities for testing, bundling, and optional reactive streams. It's currently in release candidate status, but there are already some applications in the wild using this new version. I'm just finishing up writing documentation before the official release
In React 15.4

We found a JavaScript UI library that performs great on Android mobile web

Our company reviewed many of the options available based of suggestions from our Reddit posts. In the end we made a constructive attempt at trying all the libraries/frameworks that our team could attempt in a single sprint. In the end, we tried React, Ember, Angular 2, Vue, Mithril, Cycle, Preact and Inferno. We tried the latest Vue 2.0 (https://github.com/vuejs/vue/tree/next) and Mithril 1.0 (https://github.com/lhorie/mithril.js) betas and we had some great results from both. We also tried Preact but we had issues with some SVG namespaces not properly being rendered so we gave up. Vue and Mithril enabled us to finally use our example app on our legacy Android testing devices. The experience with Cycle and Angular 2 was about the same as React (unusable) and the latest Ember was better but the initial page load times were still terrible.
Read the rest
We thought we found our library (Vue 2) until someone found a benchmark recently that showed that there was a library out there like Preact and React called Inferno. I highly recommend reading their readme (https://github.com/trueadm/inferno). It makes sense. We ran all our benchmarks and it not only came up quite a bit faster than both Vue 2 and Mithril 1.0, it also had a much more modular breakdown that allowed us to use our own state and router library without being tied to a framework – which was a massive win for the team. I have to say though, the amount of choices out there is insane. We're just lucky we found the right library for us and our needs. We highly recommend checking out Vue 2 though for ex-Angular codebases (which some of our team came from). I hope this helped!
4 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.