borromakot

7 ms·

31.
Tidewave: Beyond Code Intelligence(dashbit.co)
8 points by borromakot 1y ago|1 comments
32.
by borromakot 1y ago
High information density is good for LLMs. https://ash-hq.org benefits from this, but hurts due to being fairly new. https://hexdocs.pm/usage_rules is helping.
33.
by borromakot 1y ago
You are probably right
34.
by borromakot 1y ago
https://github.com/burrito-elixir/burrito
35.
by borromakot 1y ago
> Well-designed Erlang systems can fail gracefully and self-heal locally...but they’re only as fault-tolerant as their distributed architecture and ops discipline allows Correct. > you went for an ad hominem Not my intention. I asked
36.
by borromakot 1y ago
What I mean is that, you can write CLIs in Elixir. I have. You can write games in Elixir (others have, I haven't). They come with pros & cons. The Elixir community advances on many of those fronts regularly. I could write a w
37.
by borromakot 1y ago
1. Yes 2. You didn't answer my question? Your answer ""Practically never crash" ignores software bugs, resource exhaustion, or bad architecture" indicates I think ignorance of actually deploying BEAM applications, a
38.
by borromakot 1y ago
It having strengths and weaknesses doesn't make it not general purpose language.
39.
by borromakot 1y ago
Have you written/deployed Elixir before?
40.
by borromakot 1y ago
Elixir has been quite easy to set up, configure and deploy, at least for the last 5-6 years. I can't speak for Erlang though.
41.
by borromakot 1y ago
LMK when you get the awful errors and we'll fix them
42.
by borromakot 1y ago
I don't think this links to where you intended to link to.
43.
by borromakot 1y ago
We just launched an api key strategy `mix ash_authentication.add_strategy api_key`
44.
by borromakot 1y ago
FWIW I regret introducing that term into this conversation. I've used it in some cases to try to bring people close to an understanding when we have like...no middle ground. But its nothing close to an ORM.
45.
by borromakot 1y ago
Would love to have some conversations about specific bad error messages and indirection that causes problems. Please open issues or reach out, I'm happy to help.
46.
by borromakot 1y ago
I appreciate the perspective. Honestly for us it was just something that our whole user base was mega excited about, and so we made a big deal about it. It seemed like a positive that there was a book available (especially given that young-
47.
by borromakot 1y ago
...do you think the book is like a money grab or something? We put it big on the site because a bunch of our users were excited about it and found value from it. The book doesn't even remotely pay for itself.
48.
by borromakot 1y ago
I will go in and add another section that expands a bit more on what Ash is after ElixirConf EU is over. Thanks for the feedback!
49.
by borromakot 1y ago
We've always had trouble with this. The closest thing to Ash I've seen elsewhere is an ORM. It's not an ORM though. Ash is a declarative application framework. You define your application logic using Ash.Resource, which model
50.
by borromakot 1y ago
Do these help at all? https://hexdocs.pm/ash/what-is-ash.html https://youtu.be/vjnPjrCF4rs?si=sGlfZeEpPrfp1J0K
51.
by borromakot 2y ago
Author of Ash/Igniter here, curious how it doesn't speak to your personal values. Are we doing something that you find problematic at a non-technical level?
52.
Ash Framework: Build Declarative Elixir Web Apps(pragprog.com)
11 points by borromakot 2y ago|1 comments
53.
by borromakot 2y ago
Also launched: New homepage and installer builder - https://ash-hq.org Ash Weekly newsletter - https://ashweekly.substack.com
54.
Oban Web is now free and open source(oban.pro)
5 points by borromakot 2y ago|1 comments
55.
by borromakot 2y ago
Oban is a background job system packed with enterprise grade features, real-time monitoring with Oban Web, and complex workflow management with Oban Pro.
56.
by borromakot 2y ago
Ash isn’t an alternative to Phoenix, they are typically used side by side :)
57.
by borromakot 2y ago
There is a guarantee that you have when rebinding is the only option. with rebinding: def thing() do x = 10 do_something(x) # x is 10, non negotiably, it is never not 10 end with mutability def thing() d
58.
by borromakot 2y ago
I didn't mean you "must be inside of a function". If you call `Process.put(:something, 10)`, any references you have to whatever was already in the process dictionary will not have changed, and the only way to "observe&q
59.
by borromakot 2y ago
Gross :) But I will update my example in that case. Someone else mentioned this but I was waiting to hear back. I will alter the example to `await doSomethingElse`.
60.
by borromakot 2y ago
The point wasn’t to encourage shadowing bindings from a parent scope, only to illustrate that it is not the same thing as mutable references. Whether to, and when to, use rebinding is a different conversation, but in some cases it can lead

More ›