mattste

Joined 13 years ago

Karma

Submissions

Member since

Feb 1

Recent submissions

This is the beauty of Elixir's macros. For a lot of libraries, they are usually just calls to an underlying function with the same name. Because of Elixir's functional style and immutability, it makes it much easier to read through the magic compared to macros in other languages.

That being said, I don't have any hands-on experience with Ash so I can't speak for its approach to macros. I do think Zach's work in the community with Ash/Igniter is something to be applauded for. I'm currently working in a Python codebase that lacks conventions and would kill for something like Ash that provides consistent design patterns.

Comment · 3 years ago

It's great to see this publicly launch! Congrats to the team on making a great product. The Earthfile + Earthly CI approach is so much better than GHA or CircleCI. I feel like the only piece missing is distributed builds. Maybe one day?

And the pricing scheme is awesome, especially for smaller teams.

Comment · 3 years ago

I've been a very happy user of Earthly and this is one of the final pieces of the puzzle that I've been waiting on[1]. I've found Earthly to be the perfect balance between declarative, repeatable, flexible yet easily understandable.

While I've been fortunate to have early access to Earthly CI, the cool thing is that the Earthly primitives it uses are available for everyone to see in the latest launched version [2]. The only puzzle piece missing is distributing the compute amongst different machines but that appears to be on the team's mind.

And the zero-margin compute pricing is a breath of fresh air.

[1] https://news.ycombinator.com/item?id=30869904

[2] https://github.com/earthly/earthly/releases/tag/v0.7.0

Comment · 3 years ago

I came here to echo the pricing sentiment. I just encountered this problem and documented my company's architecture using Whimsical. I felt it was lacking.

We're a <10 person start-up. $40/mo seems too much relative to how often we'd use the tool. I would use this tool if there was a cheaper option ($10/mo/editor) for a team of our size.

Comment · 4 years ago

As someone in the ecosystem, I've found a noticeable uptick in job postings the past few years. I haven't applied for such jobs so I can't personally attest to it.

After gaining some recent experience in Go, I'd still choose Elixir for any web project. Phoenix/Ecto/Absinthe/LiveView are all extremely productive libraries for web projects. Tooling/infrastructure work may be another discussion.

Comment · 4 years ago

I agree heavily with this assessment.

I think there is room for a framework similar to Phoenix LiveView but also allows compiling certain interactivity to the client. Next.js and Remix are kind-of fulfilling this but they have downsides.

In the BEAM ecosystem, I think there is room for [Gleam](https://gleam.run) to be used to compile to both Javascript and the BEAM.

Comment · 4 years ago

I'm curious if anyone can comment on their experience using the HTML renderer.

Comment · 4 years ago

I recently converted my company's build process to Earthly. I find its syntax to be much easier to grok than CUE. They've also extended/added Docker commands that shore up some of the pain points of working with Dockerfiles.

>Dagger has a wider scope: build, test, deployment, any part of a CI/CD pipeline really

I don't see any reason this can't go into an Earthfile. We have all of these parts in our Earthfiles.

The one common pain point that both Dagger and Earthly haven't solved for me is unifying the machine parallelization with the DAG parallelization. According to this comment[1], it seems like Dagger doesn't have that goal.

For example, we only run our +deploy target if +build, +test and +lint pass. We parallelize each of those targets across workers in Github Actions. I don't know what the solution is to this problem but I know this was annoying to have to handle with Github Action's workflow syntax and horrible to debug locally.

[1] https://news.ycombinator.com/item?id=30859864

Comment · 4 years ago

How does this compare to Doppler[1]?

Is there a way to handle the configuration in Terraform?

[1] https://www.doppler.com/

Comment · 4 years ago

This was wonderfully written. As a Nix beginner, I found it super helpful and wish there was more documentation that explained the major aspects of Nix this clearly.

Comment · 5 years ago

Agreed. My gaming persona is different than IRL persona. I personally love the way Slack handles accounts.

Comment · 5 years ago

My team has had success training experienced devs in Elixir that were coming from other backgrounds. I would caveat this with the fact that we just have a Phoenix app with hardly any code that leverages OTP.

Comment · 5 years ago

Considering that the impacted region has a lot of forestry, there are environmental concerns with how they will protect the land in their new state's regulatory system.

Comment · 6 years ago

This was a pain point for me when I was first evaluating them too. I had to manually email support for them to inform me they run in GCP US West

EDIT: see sibling comment from anurag. It appears they now list the regions they support in their documentation.

Comment · 6 years ago

I 100% agree about Elixir and its surrounding ecosystem being almost perfect. It's insane how simple the building blocks are and how easy the code is to read and write.

Here are a few pain points I've ran into: 1. Typespecs leave something to be desired compared to other type systems 2. Maps vs structs and easily using one in place of the other

Things that my team would like to see: 1. Components in addition to templates as a first-class citizen in Phoenix. My team loves React because of the component model even though we hardly use an insane amount of interactivity.