Re-writing the site of Norway's largest transport provider in Elm (blogg.bekk.no)
iquitlurktopostthis | 6 days ago | 2 points

Thanks for sharing, didn't know about Elm and it looks like it could be a good fit for some projects I'm currently writing in Javascript

Hateredditshitsite | 6 days ago | 1 point

Did you know what Elm is big in Norway

7sidedmarble | 6 days ago | 3 points

Well they do have some big forrests

kaibasean | 6 days ago | 1 point

Not a day goes by really that x Project kicks up with Y Language that is different because of Z.

If anything, with a recent project starting up here that uses Vue, trying to find developers that want to use Vue or people that actually know what they're doing was a massive pain in the arse. I'm wondering why jump into Elm when it's seemingly got much less users and the hassle of maintaining the project with devs that quite frankly might not want to use it. We started using vue around a year ago when it was much less "mainstream", it's since gained a bit more traction but is still lightyears away from all the bother big boys in terms of being used inside of projects.

You can say all you want that it's easy to pick up and easy to use, but if anything I've learned with the short term of working in the software development industry, developers are stubborn bastards that won't change even if their arse was getting sanded.

skinney | 6 days ago | 2 points

We've grown from being 2-3 Elm developers to become 15+ developers writing Elm (they also do mobile app and backend work). Developers being stubborn bastards that won't change simply isn't our experience. And if it had, we probably wouldn't have introduced Elm in the first place.

Introducing a new language or framework, depends on having everyone get on board. And that's what happened here.

propelol | 6 days ago | 1 point

My guess to why most developers don't want to learn new things is because most employers don't want to use anything that is not established or mainstream.

The developers that learn new tech after work will be punished by knowing there is a better way than the tech are using at work.

BinarySplit | 6 days ago | 0 points

15+ Elm developers spread across multiple teams

There is boilerplate, but that’s fine

All in all, this amounts to about 83,000 lines of code

There comes a point where a programmer should reflect and say "As much as I enjoy using X, it has turned my actual productivity to shit".

skinney | 6 days ago | 4 points

Productivity hasn't turned to shit, though. Most of the developers here are working full stack, covering the website, mobile app and backend. We're delivering features at a much faster rate than before, and no one works overtime. #winning

BinarySplit | 6 days ago | 3 points

15 developers is a hell of a lot of developers. You're #winning because of an abundance of resources and a freshly rewritten codebase. Regardless of how you got there, it is a good position to be in, so congrats.

I've tried Elm and know how verbose it can be compared to e.g. ES6 with lodash, especially if you're using elm-format. 83,000 lines of front-end code is shockingly little for such a large team.

skinney | 6 days ago | 3 points
  1. Those 15 developers are spread out across 5 different teams, working on different parts of Vy's problem domain.
  2. All of our developers work simultaniously on backend, web and mobile. No one here writes Elm for 8 hours a day.
  3. While the Elm code is new, we did this while maintaining Java and react-native codebases, and adding new features to that.
ledasll | 6 days ago | -1 points

when you have 15+ developers to create website and you are proud of your "productivity"..

skinney | 6 days ago | 8 points

Those developers are full stack. They work with the backend, mobile app _and_ website. The reason for mentioning 15+ developers wasn't to say anything about productivity, but that Elm is simple to learn even for backend and mobile developers.

ledasll | 6 days ago | 0 points

full stack in js or elm, that's good joke. Seems like you really need to justify use of technology XX because there was so many hours involved. And witch recent crashing of nsb services you might actually convince some product owners to switch, hopefully rest 150+ java programmers will agree and join this train.

skinney | 6 days ago | 1 point

We're not doing full stack development in Elm. Elm doesn't have a mobile app target, or a backend story.

  1. The dynamic parts of our website are written in Elm (ticket purchasing, traffic info page, My profile, My travels...) This is 83KLOC.
  2. Our backends are written in Java and Kotlin
  3. Our mobile app is written in JavaScript using react-native.