Show thread[email protected]1h ago

@rradczewski I have no real idea of elixir programming but if this does what I think I’d expect a solution based on something like an ordered set for comparison or transformation to integers.
Does this make sense in #elixir?

(No snark intended, it’s just curiosity. Im not a dev and especially when programming ruby in the past I spent too many hours on figuring out the one true beautiful way to do something.)

Lobsters10h ago
Concurrency - Understanding the BEAM Limits https://lobste.rs/s/khtcsy #video #elixir #erlang #gleam
https://www.youtube.com/watch?v=mJRhFo3QnHY
Concurrency - Understanding the BEAM Limits

0 comments

Lobsters
Lars Wikman15h ago

Some databases are built different. Teresa Lopes joins us from the Postgres community to share her experiences scaling, running and maintaining a big ol' Postgres database. 100TB is non-trivial it turns out.

https://www.goatmire.com/talk/operational-hazards-of-managing-postgresql-dbs-over-100tb
#elixir #goatmire

Operational hazards of managing PostgreSQL DBs over 100TB by Teresa Lopes

sayzard21h ago

Req Is All You Need

이 글은 AI 제공자 API를 통합하는 복잡한 라이브러리 대신, 각 제공자의 HTTP API를 직접 간단히 래핑하는 방식을 제안한다. Elixir의 Req 라이브러리를 활용해 Anthropic API를 1:1 매핑하는 간단한 클라이언트 래퍼를 구현하고, 서버 전송 이벤트(SSE) 기반 스트리밍 응답 처리 및 중간 취소 기능도 소개한다. 복잡한 멀티 제공자 통합은 별도의 얇은 추상화 계층에서 관리하되, 에이전트 구축은 여전히 개별 프로젝트별 맞춤형 문제로 남아있음을 강조한다. 이는 AI 개발자가 불필요한 추상화 없이 API를 직접 다루며, 스트리밍과 취소 기능까지 효율적으로 구현하는 실용적 접근법이다.

https://benreinhart.com/blog/req-is-all-you-need/

#api #httpclient #streaming #elixir #aidevelopment

Req Is All You Need

Req and ServerSentEvents cover all your Elixir AI needs.

Lobsters1d ago
How do I write Elixir tests? by @hauleth https://lobste.rs/s/4xgljh #elixir #testing
https://hauleth.dev/post/writing-tests/
How do I write Elixir tests?

0 comments

Lobsters
Lobsters1d ago

How do I write Elixir tests?

https://hauleth.dev/post/writing-tests/

#Elixir #Testing #Programming

Hauleth's blog - How do I write Elixir tests?

Personal guides for writing tests that are readable and maintainable. Stuff to use, stuff to avoid, and how to organize stuff. Furthermore, I think that mocking must be destroyed.

Lars Wikman1d ago

Stockholm BEAM folk assemble! Day after Code BEAM Stockholm we will be hosting a little community Unconference. Bring your rejected talk ideas, your curiosity, your interests and lets make up a day of learning and sharing. The Erlang Ecosystem Foundation invites you to come hang.

https://luma.com/n71am1d6
#elixir #erlang

BEAM Unconference, Stockholm · Luma

Let’s unconference together in the land of erlang. We have been generously provided the space to meet by local security company Entryfy. Conveniently…

Lars Wikman1d ago

Getty Orawo is slated to be joining us at Goatmire. We are very happy that we'll be able to hear her story of lazines and Elixir.

https://www.goatmire.com/talk/elixir-made-me-lazy-and-thats-a-good-thing
#elixir #goatmire

Elixir Made Me Lazy (And That’s a Good Thing) by Getty Orawo

hauleth 🇵🇱❤️🇺🇦2d ago

https://hauleth.dev/post/writing-tests/

Furthermore, I think that mocking must be destroyed.

#elixir

Hauleth's blog - How do I write Elixir tests?

Personal guides for writing tests that are readable and maintainable. Stuff to use, stuff to avoid, and how to organize stuff. Furthermore, I think that mocking must be destroyed.

Show threadپویان Pouyan 2d ago
@reiver I've been using #Akkoma for a while now. It has separated front and back ends and it's really lightweight. But it's written in #Elixir and not easy for me to debug.

You're project sounds very promising. Is it ready for productive use?