Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sorentwo
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
1.
▲
by
sorentwo
14d ago
Glad somebody noticed and appreciated that! Human written long form content is extremely important (to us, but I think for the world). Every single email and issue reply is also 100% human authored. People deserve to interact with humans on
2.
▲
by
sorentwo
19d ago
Had to go through the exact same process of linking Partner Central with Marketplace. The console suggested following multiple video tutorials and linked to docs that may be outdated. They have this AI tool on every page that links to the s
3.
▲
A failed project could help solve the biggest energy need
(washingtonpost.com)
2 points
by
sorentwo
27d ago
|
0 comments
4.
▲
by
sorentwo
2mo ago
They certainly do, and I don't think it's a controversial take at this point. Shameless link to an older article about throughput with Oban ( https://oban.pro/articles/one-million-jobs-a-minute-with-oba... ), a
5.
▲
What is the most sophisticated piece of software ever written?
(quora.com)
1 points
by
sorentwo
3mo ago
|
0 comments
6.
▲
by
sorentwo
4mo ago
As a library maintainer, skill and taste are almost equally important. If I can’t recognize inefficiencies, difficult to maintain code, or generally unpleasant code smells, then people lose trust in my libraries/products and it’s no be
7.
▲
by
sorentwo
4mo ago
The efforts we've undergone to make Oban (and Pro) work with CRDB have been ridiculous. Feature detection all over because of a lack of common operators and functions that can't be used in indexes. The worst is the rampant "s
8.
▲
Digger engines drive JCB's attempt on hydrogen-powered land speed record
(thetimes.com)
3 points
by
sorentwo
4mo ago
|
0 comments
9.
▲
by
sorentwo
6mo ago
The moment that OpenCode, after helping fix a Dockerfile issue, decided it was time to deploy to prod without asking for consent , I was out.
10.
▲
Iran's Sea Mines Are One of Its Most Powerful Weapons
(wsj.com)
3 points
by
sorentwo
6mo ago
|
0 comments
11.
▲
Bridging Elixir and Python with Oban
(oban.pro)
137 points
by
sorentwo
7mo ago
|
54 comments
12.
▲
by
sorentwo
7mo ago
Nearly this, but using ghostty instead of tmux. You don’t get the remote connection aspect of tmux, but for splitting/zooming/preserving windows it is fantastic. The best part is you can configure natural shortcuts rather than usi
13.
▲
by
sorentwo
8mo ago
There is one for elixir that is _mostly_ compatible with oban-py. Full compatibility, and potentially native hosting, are goals before 1.0 https://github.com/oban-bg/oban_web
14.
▲
by
sorentwo
8mo ago
With a typical Redis or RabbitMQ backed durable queue you’re not guaranteed to get the job back at all after an unexpected shutdown. That quote is also a little incorrect—producer liveness is tracked the same way, it’s purely how “orphaned”
15.
▲
by
sorentwo
8mo ago
You can have jobs that run as long as you like. The difference is purely in how quickly they are restored after a crash or a shutdown that doesn’t wait long enough.
16.
▲
by
sorentwo
8mo ago
This is absolutely true (except we went OSS + Web initially, Pro came later). You were an inspiration, always helpful in discussion, and definitely paved the way for this business model.
17.
▲
by
sorentwo
8mo ago
> The vast, vast majority of Python libraries are not async-friendly and most still rely on the GIL. On the other hand, Celery has absolutely no asyncio support at all, which sets the pro feature apart. That's great advice. Wish we&
18.
▲
by
sorentwo
8mo ago
Transactions around fetching/updating aren't trivial, that's true. However, the work that you're doing _is_ regular activity because it's part of your application logic. That's data about the state of your over
19.
▲
by
sorentwo
8mo ago
There are other projects that implement the ideas in OSS, but that's the same in Elixir. Not that we necessarily invented DAGs/workflows, but our durable implementation on the Elixir side predates DBOS by several years. We've
20.
▲
by
sorentwo
8mo ago
> It supports workflows, rate limiting, unique jobs, bulk operations, transactional enqueuing, etc. Why not move these things to the OSS version to be competitive with existing options, and focus on dedicated support and more traditional
21.
▲
by
sorentwo
8mo ago
> Oban has been a lifesaver for me and it is the tool I miss the most from the Elixir ecosystem when doing work in Python That's wonderful to hear! Hopefully you can make use of Oban in both places now =) > I have one question: a
22.
▲
Show HN: Oban for Python (Job Orchestration Framework)
(github.com)
2 points
by
sorentwo
8mo ago
|
0 comments
23.
▲
by
sorentwo
8mo ago
Pleased to see this posted! A lot of design time and effort behind this project (something we'll be speaking about this year). Happy to answer any questions people may have.
24.
▲
by
sorentwo
9mo ago
Seconded. I was going to say the exact same thing. Brilliant thought exercise that I still think about on a weekly basis 20 years later.
25.
▲
by
sorentwo
9mo ago
Before looking at the zoo I figured there would be a dozen or so engines compared. Seeing the actual comparison is astounding! The amount of work just to aggregate and compare is admirable, let alone the effort behind the engines themselves
26.
▲
Are Pop Lyrics Getting More Repetitive? (2017)
(pudding.cool)
4 points
by
sorentwo
11mo ago
|
0 comments
27.
▲
by
sorentwo
11mo ago
It is an old US military term that means “F*ked Up Beyond All Recognition”
28.
▲
by
sorentwo
11mo ago
> Just as a whole the Erlang and Elixir primitives allow oban to be built truly in the most retarded, obvious way and get away with it. Maybe it is obvious in retrospect…
29.
▲
by
sorentwo
1y ago
This is absolutely true. I can confirm, from firsthand knowledge, that Elixir is used at dozens of Fortune 500 companies in the US.
30.
▲
by
sorentwo
1y ago
The roadmap is purely about AI, and reads like it was written by AI. It’s purely trendy and myopic.
More ›