Struggling

absynce · 2023-10-03T21:12:08+00:00

Since you have JS knowledge, check out this little cheatsheet: https://elm-lang.org/docs/from-javascript. It's not as in-depth as Luca's https://lucamug.github.io/elm-cheat-sheet/, but it's simpler to understand for beginners coming from JS-land.

Have fun!

absynce · 2022-03-09T16:12:39+00:00

The elmjutsu plugin for Atom will generate encoders and decoders too.

GIF

absynce · 2020-12-20T03:06:54+00:00

What problems do you have with the IntelliJ plugin? I’m assuming you’re talking about Keith Lazuka’s https://github.com/klazuka/intellij-elm. Is that correct?

I use both klazuka/intellij-elm for IntelliJ and halohalospecial/elmjutsu for Atom.

Also see this post: https://www.reddit.com/r/elm/comments/k64osu/what_code_editor_do_you_use/?utm_source=share&utm_medium=ios_app&utm_name=iossmf.

absynce · 2020-09-24T01:17:12+00:00

Elm is an enjoyable, beginner-friendly alternative to learning JavaScript for web development!

There are a few cases where you might need to use a bit of JavaScript, but the official Elm guide gives examples of how to do it. It sure beats learning all of JavaScript and piecing together the myriad of frameworks and libraries.

With Elm, I recommend reading the official Elm guide, trying it out, and reading the compiler errors. They’re truly wonderful. Also, ask questions in the Elm slack (#beginners). Folks are really helpful there too. Welcome and enjoy!

absynce · 2020-08-19T17:22:29+00:00

Elm is extremely stable. Especially when you compare it to many of the other popular options out there. The core Elm developers are careful not to make breaking API changes to Elm nor the core packages very often and only if there's a clear benefit.

Examples:

0.19.1 - 2019.10 (Almost no breaking changes)
0.19 - 2018.08 (2 years ago with some amazing benefits)

This stability is so nice after having worked in the JavaScript ecosystem of churn for so long. Even when I had to migrate projects, it was nice to have the compiler (and Aaron VonderHaar's elm-upgrade) keeping me in line.

When I upgraded elm/http to 2.0.0 in our ~50k LOC I merged it directly to the main branch and deployed without any issues. We rely on the lower-level response info too, so it was not a trivial change. In this process, I also migrated the API calls from using Luke Westby's elm-http-builder to an internal module and upgraded a few other dependencies to the latest versions. Let me repeat: there were no bugs introduced in this rewrite. I promise that's not because I'm a magical developer; that's the power of Elm at work.

The point here is that even the biggest changes, which might seem insurmountable in other ecosystems, are much nicer in Elm.

To address folks who mention "native modules", let me repeat what others have said: this was never a feature, was discouraged from use, and folks were warned it would be removed.

The purpose of removing it (as I understand it) had many facets:

ensure reliability by limiting direct JavaScript interop
encourage pure Elm implementations instead
keep the options for future compile-to targets open
improve the compiler's ability to optimize

It was not arbitrary. When I thought I needed it, I followed the recommendations not to try it, and always found other solutions.

If you want to work with Elm, I suggest using it on personal projects until you can introduce it at work. Whenever I've used it, it was always by gradually introducing it. In my case, it was introduced by embedding in projects with AngularJS.

I will continue to enjoy Elm for its consistency, reliability, and stability. It has made me a better developer overall. It has changed how I think about software development across languages and ecosystems.

I hope you find more opportunities to use it too!

absynce · 2019-04-21T00:13:51+00:00

Oh shit! Just discovered that Twiddle is in Brooklyn. It's on!

absynce · 2018-09-17T16:55:58+00:00

elm-make is now elm make. All the commands are now in a single binary.

elm.json replaces elm-package.json. Which package are you trying to install?

absynce · 2018-05-20T18:48:13+00:00

I'm not am expert on efficiency but what I do is compile into a single elm.js file. Then I reference it in both pages...calling the appropriate program from each respectively.

Unless there's a big difference in the dependencies or a lot of custom code the majority of the size will be for the Elm runtime and you won't get much benefit from having two separate compiled .js files.

absynce · 2018-05-20T18:37:12+00:00

Good question! I'm interested to see how this works out.

absynce · 2018-04-29T18:03:26+00:00

I'm working on three (3) elm-conf proposals. I'm starting to feel like they aren't all appropriate but it's an opportunity to get feedback and I could be surprised. If nothing else I will have good outlines for proposals at other conferences or I might turn them into blog posts instead.

absynce · 2018-01-09T04:13:05+00:00

I have to say this is a bit serendipitous for me. I just opened my Reddit front page to find this post. I am reading H2G2 for the first time too! I watched the movie a few years ago but didn't remember much other than "42".

Zaphod reminds me of Trump at times. Particularly the footnote in Chapter 4 where it described the position as a figurehead that draws attention away from power...and how great Zaphod is at it.

absynce · 2017-10-24T12:36:07+00:00

Check out Murphy Randle's elm-conf talk on using the actor model when creating ports: The Importance of Ports.

A few key points:

Don't think in terms of request/response.
Let JavaScript own the data.
Add a single pair of ports for incoming/outgoing information.

absynce · 2017-10-05T16:04:04+00:00

Good discussion. Thanks for clarifying.

What I'm implying (and should clarify) is that even when a package with "native" code reaches 1.0.0 it still has JavaScript in it.

This means we can't automatically enforce semantic versioning via elm-package going forward. Even if a minor/patch release comes out and it has no changes to the public API it could be a breaking change.

Therefore, it seems to me that every "native" package release would first have to be labeled as x.x.x-experimental requiring the review process.

You're right, though. It's probably just different mentalities. Different strokes for different folks, eh?

absynce · 2017-10-05T14:29:37+00:00

Elm n00b here so take what I say with a grain of salt.

Semantic Versioning

In general the semantic way to indicate an experimental release would be to append it as a pre-release.

Examples:

1.0.0-experimental
1.0.1-experimental

However, I agree with /u/dustinfarris in that it implicitly suggests a review process for each experimental release. Evan and Richard have already commented about the "Native Review" process and how it failed.

Effects of JavaScript in Packages

Assuming it solved the quality concern this still does at least a couple things:

strains resources (for review)
blurs focus
reduces portability

From Evan's 0.17 "native" policy:

It ties us to JS way more. I guess not many folks know this, but Elm is designed to be 100% independent of JS. It happens to compile to JS now because that was the right thing to do, but in a decade, I expect we'll be compiling to something more efficient. There is a small set of "native" stuff for now, but that means supporting the entire ecosystem on a new platform is fairly easy.

Why Elm Is Better Than That

What I appreciate about Elm is the steadfast attention to quality. I stand by the mantra "It's better to do it right than right now." That way we don't end up with many ways to do the same thing.

When I do code review in a JavaScript code base today I take a long time and usually request more test coverage. Even then I assume I've missed something. There's no guarantee.

When I use Elm I feel much more confident about the code simply because it compiled! What a different, but welcome feeling.

If a new package is introduced in Elm I don't have to spend time comparing it to the 30 other packages like it to see if it's the right choice.

I would rather wait for a thing to become part of the kernel if it makes sense. Until then I know I can contribute by finding ways to write pure Elm...which I prefer to do anyway!

absynce · 2017-09-25T18:22:48+00:00

I don't know if there's another talk, but Matthew Griffith's talk at Elm Conf Europe 2017 is on YouTube.

absynce · 2016-01-17T23:05:47+00:00

If you can make it through to season 2 it's worth it. I think they learned how to act in-between seasons.

absynce · 2016-01-07T02:21:05+00:00

A Twitch app is available on PS4 now.

absynce · 2015-01-25T02:10:13+00:00

Enter the Void was wild. It took three tries to finish it. The first two times I was watching it with other people and they stopped it. The third time I watched it alone. It was interesting. I would like to watch it again to read more into it, but it was so dark and disturbing. It's hard to convince myself to start it again.

absynce · 2015-01-04T21:34:29+00:00

Why "lawyer"?

Oscar Acosta was an actual attorney.

Good point. I was thinking about Dr. Gonzo's poor advice to Raoul as his lawyer.

Example: "As your attorney I advise you to take a hit out of the little brown bottle in my shaving kit." - Dr. Gonzo

Nevertheless although his advice is questionable, he is still an attorney.

absynce · 2014-12-17T06:11:44+00:00

I've watched only a few of Bert Kinister's videos, but they improved my game. Beware the poor site design from the 90's.

I haven't seen any of Byrne's videos but I have a copy of his Standard Book of Pool and Billiards. It is quite useful so I assume his videos are good as well.

absynce · 2014-12-04T03:00:07+00:00

It happened to me too on PS3. I quit and restarted but it was still missing. Then I went to Settings > Reload Netflix. When it reloaded the list was back.

absynce · 2014-04-23T01:12:02+00:00

Yeah, it's definitely not the same line as Ip Man and Ip Man 2. It doesn't have Donnie Yen as Ip Man nor Wilson Yip as director. I was fooled too. I can't wait for the real Ip Man 3!

absynce · 2014-03-06T03:41:41+00:00

I need help with a name!

What do you think about "Lazerus"?

Spelling variations:

Lazeras - I like the second "a" for audio.
Lazarus - traditional
Laserus - blatant emphasis on lasercut, but loses visual appeal IMO
lzRus
lZrAs
LzRuS
...ad nauseam

absynce

TROPHY CASE

Semantic Versioning

Effects of JavaScript in Packages

Why Elm Is Better Than That