With no disrespect intended to the authors, the website doesn't seem to be quite right as-is. Whenever I click any of the big buttons, I get a flash of white across the whole screen. This is off-putting, especially when navigating between pages doesn't incur this on a "normal" static HTML website. I normally wouldn't bring this up but the article is very specifically talking about the benefits of using this web frame…
The blog website isn't written in Elm. We're using Elm for the product application, not for the blog or for https://www.humio.com/ . I'll transfer the remarks though :)
Why we chose Elm for Humio’s web UI
11–20 of 137 posts
Re: Why we chose Elm for Humio’s web UI
#12Happy Humio user here. Love the product. I think there were some recent changes to the front-end too that makes it feel snappier than before. Great job on that too. However, at the risk of sounding like insensitive clod who makes critical comments on a post talking about its front-end, if I can offer one criticism of the web interface it's that it doesn't responsively adapt to mobile resolutions nicely. I get that th…
Re: Why we chose Elm for Humio’s web UI
#13Earlier quoted context omitted.
Yeah it even renders weird, like the page is completely rebuilt on every navigation... even when moving back through the history in chrome on a desktop. ̛It's definitely a little off putting. Stepping through with the debugger it actually seems to be rebuilding the whole page every time you navigate... Anyone more familiar with the whole Gatsby javascript framework/library/stack/thing able to chime in on what is goin…
The website is also mostly broken with JS disabled. But as you noticed, they are using Gatsby, not Elm, so it's not directly related to the subject of the article.
Re: Why we chose Elm for Humio’s web UI
#14Earlier quoted context omitted.
The blog website isn't written in Elm. We're using Elm for the product application, not for the blog or for https://www.humio.com/ . I'll transfer the remarks though :)
Nice. Have you folks run into any limitations of elm and its ecosystem? Are there any js/ts integrated with the website?
Re: Why we chose Elm for Humio’s web UI
#15Earlier quoted context omitted.
The blog website isn't written in Elm. We're using Elm for the product application, not for the blog or for https://www.humio.com/ . I'll transfer the remarks though :)
Is there is a public (working not video) demo of the product somewhere?
Re: Why we chose Elm for Humio’s web UI
#16The points this article makes like strong typing pull me towards Elm, but people talk about understanding Lisps as a nirvana-like state of enlightenment, which pulls me towards Cljs
Re: Why we chose Elm for Humio’s web UI
#17Interop with JS is mostly fine. Just integrated Adyen, and it went without an issue (except their js bundle being 10x the size of our elm app..). Same with our map provider. We can call their APIs, and they can render/take over certain divs inside our elm app without issue. The only JS issue I'm having is for smaller synchronous stuff. Like calling small utils imported from JS is burdensome, as it becomes an async flow and the response can only be handled in our update function. But day-to-day mostly a non-issue.
No real changes for the last two years. But that's fine. No breaking changes (like from 0.18 to 0.19) and not really any big features I'm missing.
I'm very fan of elm-css. There are some minor annoyances, but having the css just be plain elm-code (with type safety even, cannot write invalid css) with functions and logic and stuff is very powerful.
Re: Why we chose Elm for Humio’s web UI
#18It's not just a fledgling project, it's a project that's being carried by one person for a very broad scope, and it's been going for a very long time now. Contrast that with something like vue, where Evan You has a fair amount of corporate sponsorship, has a much smaller scope (i.e. not an entire new language), big following, and has other frameworks to develop in tandem with (i.e. get inspired by react). Not to mention that it's very similar to other frameworks, so it's easy to pick up, so easy to hire for.
I would shitting bricks if I had 200k lines of code in a completely different language with a heavily different paradigm, that's not really battle tested.
Re: Why we chose Elm for Humio’s web UI
#19Apologies if this is too off-topic, but I'm currently trying to decide between Elm and ClojureScript to get started with FP. Can anyone weigh in with recommendations? The points this article makes like strong typing pull me towards Elm, but people talk about understanding Lisps as a nirvana-like state of enlightenment, which pulls me towards Cljs
Re: Why we chose Elm for Humio’s web UI
#20Ok, exaggerations about elm's safety aside, there's the huge issue of it's readiness for production. It's not just a fledgling project, it's a project that's being carried by one person for a very broad scope, and it's been going for a very long time now. Contrast that with something like vue, where Evan You has a fair amount of corporate sponsorship, has a much smaller scope (i.e. not an entire new language), big fo…
Elm may not be a good fit for every project out there, like when you need tight integrations with specific JS projects, but it will work well for most projects.
At this point, I'd personally be more interested in hearing about cases where Elm was NOT a good fit (and why) rather than where it is.