3 ms·

Mithril author here. Curious what version you were using. There have been some notable internal changes to the engine over the years. The 1.0 release was a com

by lhorie 6y ago

Mithril author here. Curious what version you were using. There have been some notable internal changes to the engine over the years. The 1.0 release was a complete rewrite of the previous codebase, and included a very aggressive optimization inspired by inferno.js (called node recycling) that turned out to cause issues in some edge cases and didn't materialize significant enough performance benefits given the added internal complexity. I suspect that this is what was causing you grief. This optimization has since been removed.

aetherspawn 6y ago
Hey Leo, Yeah we reported a few bugs over the years and many of them got fixed. We were using Mithril 0.x. We did get the product to a point where it was very stable, but there were patterns that we had to avoid (for example, at the time IIRC we had spooky bugs with children cycling between an element, a list of elements, or an empty array []). In the end, the reason that we moved away from Mithril.js was that as a 300-person company, we just didn't have the resources to give it the attention that we felt we needed to give it (i.e. contribute) vs. the timeline that we needed for isolation and resolution. Before we built our app in Mithril, I built a MVP prototype in Angular and the performance was so bad that the product was marked as "not plausible". Discovering Mithril.js was the only reason we decided to go through with the project. In some respects, the company owes its market-leading position to Mithril.js whilst its competitors are still crawling out of the dark ages of TTY and desktop thin clients
- lhorie 6y ago
  > We were using Mithril 0.x Ah, yeah things have improved a lot since the 0.x days. > I built a MVP prototype in Angular and the performance was so bad I hear you. Having issues with Angular.js performance at work was the reason I started Mithril.js. It's always interesting to hear war stories :)

by lhorie 6y ago

aetherspawn 6y ago

Hey Leo, Yeah we reported a few bugs over the years and many of them got fixed. We were using Mithril 0.x. We did get the product to a point where it was very stable, but there were patterns that we had to avoid (for example, at the time IIRC we had spooky bugs with children cycling between an element, a list of elements, or an empty array []). In the end, the reason that we moved away from Mithril.js was that as a 300-person company, we just didn't have the resources to give it the attention that we felt we needed to give it (i.e. contribute) vs. the timeline that we needed for isolation and resolution. Before we built our app in Mithril, I built a MVP prototype in Angular and the performance was so bad that the product was marked as "not plausible". Discovering Mithril.js was the only reason we decided to go through with the project. In some respects, the company owes its market-leading position to Mithril.js whilst its competitors are still crawling out of the dark ages of TTY and desktop thin clients

lhorie 6y ago
> We were using Mithril 0.x Ah, yeah things have improved a lot since the 0.x days. > I built a MVP prototype in Angular and the performance was so bad I hear you. Having issues with Angular.js performance at work was the reason I started Mithril.js. It's always interesting to hear war stories :)