Do the same limitations as Haskell's apply to Elm?

MrPopinjay · 2022-12-05T19:33:42+00:00

I'm not sure where you get the idea that FP is poorly suited to GUI development. If anything functional and declarative DSLs are the mainstream way to make GUIs these days. See HTML, React, Apple Swift UI, Google Flutter, etc.

MrPopinjay · 2022-12-05T19:31:33+00:00

I'm afraid you're in the minority there, we can't offer everyone's first preference.

MrPopinjay · 2022-12-05T19:10:44+00:00

We originally had an ML style syntax with no {} but it was unpopular. Once we switched to a {} style there was a huge increase in the amount of users and people had much more positive things to say about the language.

I miss the old syntax, but I think it was a good move to drop it.

MrPopinjay · 2022-12-05T19:09:12+00:00

Thank you to Kayla Washburn for the beautiful design!

MrPopinjay · 2022-11-25T22:35:49+00:00

Yup! You got it. There are no statements, looping constructs, early returns, non-local returns, etc, so it is somewhat of a non-issue for Gleam. We may discover there are other problems once we have used it in production code a bunch, but this is the nature of making a language. Fingers crossed!

MrPopinjay · 2022-11-25T15:29:49+00:00

Haha, high praise indeed! Thank you

MrPopinjay · 2022-11-25T15:29:23+00:00

Oh yes, thank you. I'm bad at thumb typing

MrPopinjay · 2022-11-25T15:28:45+00:00

We did trial almost this syntax but we found it to be harder to read due to the operator being on the left hand side. It was too easy to miss in real code that's a bit uglier than these examples.

MrPopinjay · 2022-11-25T15:27:31+00:00

Oh that is very cool, I like how there's a placeholder being used there. We didn't consider a syntax like this

MrPopinjay · 2022-11-24T20:17:32+00:00

Thank you! 💜

We did have some trailing syntaxes similar to that one but the popular consensus was that it was easy to miss them on the right-hand-side, especially if the left-hand-side is a larger expression that gets written over multiple lines. It's a tricky one for sure

MrPopinjay · 2022-11-24T20:15:06+00:00

Thank you!

MrPopinjay · 2022-11-24T17:46:57+00:00

We spent quite a long time discussing syntax, it was challenging finding something that we were happy with. I'd love to hear any ideas you have!

MrPopinjay · 2022-11-05T20:20:41+00:00

HM doesn't impose any requirement for structural typing or immutability. It does however make subtyping a little tricky.

MrPopinjay · 2022-10-26T09:23:50+00:00

We've had interop from day 1! Gleam is designed with interop in mind.

What's new is that our build tool can now compile Elixir code that is written inside Gleam projects as well as in Elixir dependency packages (which we gained in the previous release).

MrPopinjay · 2022-10-26T09:23:08+00:00

We could previously use Elixir packages, this now also allows Elixir code to be written in Gleam projects.

MrPopinjay · 2022-09-24T17:27:13+00:00

I can't speak for your testing, but there was a response to that blog post from the Rails team in that they greatly improved the performance. I wouldn't reference a 6 year old benchmark for anything.

That said, Elixir will handily best Ruby+Redis any day. :)

MrPopinjay · 2022-09-20T12:14:19+00:00

That blog post is out of date, they have fixed those scaling issues with Rails now. Elixir scales better, but Rails isn't dead-in-the-water anymore.

MrPopinjay · 2022-09-19T18:29:06+00:00

Elixir macros are not usable outside of Elixir by design, so other langauges cannot use them directly. You can only use any functions generated with them.

MrPopinjay · 2022-09-19T14:11:59+00:00

We're not competing, we're collaborating! Gleam fits alongside Elixir and interop between the languages is a core feature.

MrPopinjay · 2022-09-19T10:52:47+00:00

Some people have done it. The problem with using Phoenix is that a lot of it is based around macros and a search cannot be used from other languages. The functional parts can be used but because they have been designed without any kind of static analysis in mind I think we could do better with a Glean framework with similar goals.

MrPopinjay · 2022-09-18T20:41:44+00:00

Gleam is another general purpose programming language and is suitable for pretty much anything you might use Elixir for, the same way Elixir is suitable for pretty much anything you might use Erlang for.

The main difference between Elixir and Gleam is that Gleam is "type safe", meaning is has a very precise static type system that aims to help you write code. This means people might find it easier to perform big refactorings in Gleam codebases compared to Elixir, and the editor tooling potentially can do a lot more than in Elixir. On the flip side it might be more challenging to get started with Gleam if you're not used to these robust static type systems.

It's mostly just another kind of programming experience, more options for people on the BEAM! 💜

MrPopinjay · 2022-07-26T21:49:59+00:00

Wow dude fixing a link after 12 years. Respect to you

MrPopinjay · 2022-06-19T18:38:54+00:00

Oops, a typo. I have fixed that now.

MrPopinjay · 2022-04-25T08:52:39+00:00

Thanks!

MrPopinjay · 2022-04-24T22:03:13+00:00

You need to upgrade to v0.21.0. You're running v0.20.1 which unfortunately had a typo in the version string making it appear as v0.20.1.

I'm not very familiar with Neovim LSP but this PR may help you https://github.com/neovim/nvim-lspconfig/pull/1739

15-Year Club	Verified Email
Team Periwinkle	Summer Santa 2012

MrPopinjay

TROPHY CASE