tmountain

Gleam has potential to fill the niche and has an active and growing community.

Elm.

Came here to say this. Excellent content there if it’s your sort of thing.

I read the book and loved it (about 15 years ago). There’s no royal road to becoming an artist but lots of joy along the way. Whatever the path, enjoy it!

I have been practicing art a lot lately. You can draw just about anything using spheres, cubes, cylinders, and cones. You start off with the 2d versions.

I watched Kiss Kiss Bang Bang recently and really appreciated his performance in that movie. He’s one of the original “indie stars” of my generation. Sorry to see him go.

I guess the first sentence could be restated as, “the reason avocados have exploded in the U.S. is that Mexican avocados are much more affordable”; although, the author goes on to state that the price isn’t a driver, and touches on the necessity of getting them from Mexico for year round availability.

Oh boy, here we go…

Still waiting on real pattern matching in TyoeScript.

For anyone struggling to manage their PL/pgSQL codebase via migration files. This is a game changer.

https://github.com/t1mmen/srtd

I’ve recently ported some legacy code to Golang with AI assistance, and the process was painless. The compiler caught a few issues along the way, which were easily fixed. I did a 1:1 port module by module and gave context on intention. Of course, I had to test and audit the code, but I had a pretty good integration test that was easily reused. I wouldn’t have felt nearly as confident without the compiler.

Very common in eastern storytelling. Ghibli films are some of my favorite for many reasons, but I particularly love how they contrast ideas.

You’re asking the wrong questions. Query complexity and patterns matter. Nobody can answer this for you. You have to do the analysis based on your workload.

Systems tend to ossify over time. Thoughtful solutions to problems usually stand the test of time better than rapid fire solutions. On my team, we often take an extra day to verify and validate design decisions before binding ourselves to them. Yes, some may deliver faster, but developing with intention is the road to sanity in my book.

> Who is choosing anything but Kotlin for new projects on the JVM?

I dunno... Scala, Clojure, and Groovy users? Small user bases, but the languages are not dead.

There are TONS of JVM languages and nobody is complaining about that. BEAM is much smaller and a very nice target IMO. I learned Erlang but found it too weird for my tastes. Elixir lacked a type system when I evaluated it, and that steered me away from it. Gleam feels kind of like Elm felt. Small, simple, and safe. It feels very intentional and designed for a particular purpose and audience. I did their online tutorial and felt comfortable with the language in one sitting. Can’t say that for many other languages.

Gleam is about as simple as Go but with a more expressive type system and Elm style guarantees that your app won’t crash if you stay in its ecosystem.

You can greatly improve DX with something like this and get the best of both worlds.

https://github.com/t1mmen/srtd

Feels like Gleam is gaining a lot of steam and getting a lot of attention recently. It’s the language that I am most excited about right now. It’s hitting all the right notes.

100% depends on how it’s written. It gives a ton of flexibility regarding incorporating “magic variables” which can lead to incredibly abstruse code. The language motto is “there’s more than one way to do it”, and that’s implemented to a fault.

It will result in a loss of power. Isolation is not a strengthening posture. You need allies to succeed over the long term. This looks like the beginning of the downfall of the United States from every measure.

I dunno how to compare stable to stable but I ran Win2k for so long that I got bored with it (something like 5-7 years) and never experienced a single crash. This is coming from a Linux guy btw… so I’m no Microsoft fanboy, just saying, it was as stable as any other stable OS.

The Democrats follow the rules if that's what you are saying...

Wow, thanks for the reply, and correction! I look forward to learning more about Gleam, as I've just started with it, and I'm really enjoying it so far.

I'm still learning Gleam, but I do not believe that "use" has anything to do with async. It seems to be a direct riff on Haskell's "do notation" syntax sugar (<-), which is used for unwrapping monads, but Gleam seems keen on insulating users from these details at the surface level.

The author of the article has an intuition that "use" is helpful for error handling, and it definitely is because one of the core benefits of monads is chaining certain categories with a guarantee that nothing will blow up in the process; however, use cases are broader, as you can chain all sorts of things.

Looking at it now, it's actually akin to clojure's threading operator, which basically just simplifies syntax when making successive function calls (argument threading). Whatever the case, it's not just for errors/async, but more so for chaining without causing a bunch of unnecessary indents to occur.

I’ve been eyeing gleam as my next language to learn. Lots to like about it for sure, and I have always like the idea of OTO but never had an opportunity to tinker with it.

I’m glad you found something that works for you, but it’s barely a text format from my vantage point. Parsing it is downright user hostile.

For what?

Just tried it out. This is exactly what I was looking for. Very nice work!

Will take a look, thank you!