News for hackers. Stuff that matters.
Re:React is becoming a black box by pier25 on Thursday September 03, 2020 @09:59AM (#24364099)
I love Mithril but I find hs to be noisy to read and tedious to write.

It's probably because I've been reading and writing HTML for +20 years though.

Re:React is becoming a black box by lhorie on Thursday September 03, 2020 @02:18PM (#24366990)
(mithril author here)

hyperscript is about as close to a middle ground as we can get. It's compatible with JSX for the folks that really really want to see angled brackets, while still being uniform javascript like other API variations (div(), html`<div></div>`, etc). The lit-html syntax is not bad either, but template strings did not have as widespread support back when mithril originally came out.

Re:React is becoming a black box by avtar on Thursday September 03, 2020 @02:56PM (#24367429)
Is there a roadmap for mithril? As in, what are the current pain points, where development is headed, etc.
Re:React is becoming a black box by lhorie on Thursday September 03, 2020 @04:45PM (#24368689)
I've given stewardship of the project to the community. At this point, it's largely in maintenance mode. Most changes are tightening up loose semantics and the like. IIRC the last major was only a major by technicalities; it didn't really break anyone unless they were relying in weird obscure behaviors.

Since the framework isn't interested in chasing trends and since it provides extension points via lifecycle methods, there's really nothing novel that needs to come from the framework itself.

I know some of the more popular frameworks make it seem that webdev is constantly in churn/evolving, but if you look at React for example, other than the hooks paradigm shift etc, it hasn't really changed all that much in scope over the years either (the same can be said about other libraries as well).

For example, Mithril could easily be used w/ coffeescript when that was still a thing, and people use it with typescript these days too without much fuss since TS is also a project that decouples well. And this is with zero changes to the framework. You can integrate dragula or plupload or google maps or whatever via lifecycle methods as you always could too.

So, TL;DR: I think the focus still remains on making it as stable and robust as possible

Re:React is becoming a black box by nextaccountic on Thursday September 03, 2020 @07:27PM (#24370009)
Does mithril provides typescript function signatures for its API?
Re:React is becoming a black box by lhorie on Friday September 04, 2020 @12:38PM (#24376510)
Re:React is becoming a black box by avtar on Thursday September 03, 2020 @05:35PM (#24369147)
This was helpful. Thanks!
Re:React is becoming a black box by engineeringwoke on Thursday September 03, 2020 @02:52PM (#24367385)
Yeah but why isn't it just HTML?
Re:React is becoming a black box by simplify on Thursday September 03, 2020 @04:01PM (#24368221)
Why isn't what just HTML?
Re:React is becoming a black box by rapind on Thursday September 03, 2020 @12:59PM (#24366070)
Yes, probably. I started using haml (then slim) a very long time ago and the hyperscript / elm type syntax is fairly intuitive to me.
Re:React is becoming a black box by engineeringwoke on Thursday September 03, 2020 @02:59PM (#24367467)
What is the point of templating HTML? I really don't understand it. Just write HTML or HTML-like APIs like JSX. Is there some theoretical reason why this is wrong?
Re:React is becoming a black box by rapind on Thursday September 03, 2020 @11:22PM (#24371414)
Subjective I guess. For me it’s just a reduction in noise and I prefer to read code with significant white space. Perfectly ok writing HTML, but given the option, and if it doesn’t screw with others, I prefer not too.
Re:React is becoming a black box by jschrf on Friday September 04, 2020 @04:16PM (#24378484)
JSX is HTML templating