kodablah

5 ms·

31.
by kodablah 7mo ago
Duralade - a programming language for durable execution (but has many neat aspects) Most of the work as of today is in a branch, can see the language spec at https://github.com/cretz/duralade/blob/initial-runt
32.
by kodablah 7mo ago
> People who are saying they're not seeing productivity boost, can you please share where is it failing? At review time. There are simply too many software industries that can't delegate both authorship _and_ review to non-huma
33.
by kodablah 8mo ago
> that's the only way they "learn" anything I think skills and other things have shown that a good bit of learning can be done on-demand, assuming good programming fundamentals and no surprise behavior. But agreed, having
34.
by kodablah 8mo ago
I'm of the mind that it will be better to construct more strict/structured languages for AI use than to reuse existing ones. My reasoning is 1) AIs can comprehend specs easily, especially if simple, 2) it is only valuable to &quot
35.
by kodablah 10mo ago
> The thing is, if you want people to understand durability but you also hide it from them, it will actually be much more complicated to understand and work with a framework. > The real golden ticket I think is to make readable intuit
36.
by kodablah 10mo ago
> that your entire workflow still needs to be idempotent If just meaning workflow logic, as the article mentions it has to be deterministic, which implies idempotency but that is fine because workflow logic doesn't have side effects
37.
by kodablah 11mo ago
At Temporal, for Java we did a hybrid approach of what you have. Specifically, we do the java.lang.reflect.Proxy approach, but the user has to make a call instantiating it from the implementation. This allows users to provide those options
38.
by kodablah 11mo ago
> The author's point about the friction from explicit step wrappers is fair, as we don't use bytecode generation today, but we're actively exploring it to improve DX. There is value in such a wrapper/call at invocatio
39.
by kodablah 11mo ago
> is it the dev ergonomics that's cool here? Yup. Being able to write imperative code that automatically resumes where it left off is very valuable. It's best to represent durable turing completeness using modern approaches of
40.
by kodablah 11mo ago
Yes, maybe the causation assumption here is inaccurate.
41.
by kodablah 11mo ago
I think correlating "pushes per repository" to certain languages is interesting. The top "pushes per repository" are C++, TeX, Rust, C, and CSS. I guess it's no surprise many would also consider those the most guess
42.
by kodablah 1y ago
Deterministic output is needed when LLMs are used for validations. This can be anything from input validation at runtime to a CI check leveraging LLMs. It can be argued this is not an acceptable use of AI, but it will become increasingly co
43.
by kodablah 1y ago
As someone that has had to build libraries for the nuances of coroutine vs thread async in several languages (Python, .NET, Java, Ruby, etc), I believe how Ruby did fibers to be the best. Ruby's standard library was not littered with t
44.
by kodablah 1y ago
I use RBS/steep with great success to catch plenty of nil issues early, but it's similarly not great from a dev POV to have to maintain a completely separate set of rbs files (or special comments with rbs-inline). Also in my exper
45.
by kodablah 1y ago
> Agents, on the other hand, are often given a set of tools and a prompt. They are much more free-form. This defines how workflows are used with modern systems in my experience. Workflows are often not predictable, they often execute one
46.
by kodablah 1y ago
Right, I am saying I don't think their definition is an accurate one with the modern use of the term. It's an artificially limited definition to fit a narrative. An agent is nothing more than a very limited workflow.
47.
by kodablah 1y ago
I believe the definition of workflows in this article is inaccurate. Workflows in modern engines do not take predefined code paths, and agents are effectively the same as workflows in these cases. The redefinition of workflows seems to be a
48.
by kodablah 1y ago
> I hate this idea that Ruby needs to be more like Python or Typescript It's not be more like those, it's be more like helpful, author-friendly programming which is very much Ruby's ethos. Every time I think about ripping
49.
by kodablah 1y ago
Fingers crossed this is/becomes extensible. Pyright and MyPy both suffer from lack of extensibility IMO (Pyright doesn't consider the use case and MyPy plugins come across as an afterthought with limited capabilities). There are m
50.
by kodablah 1y ago
Not true, you can compete with the quality of the deployed service _separate_ from the development of the software. The quality of the service can include internal, at-scale optimizations that don't affect user-facing parity with the o
51.
by kodablah 1y ago
Sibling quoted the proper part. It's to help people keep code deterministic by helping prevent shared state and prevent non-deterministic standard library calls.
52.
by kodablah 1y ago
There just aren't good Python sandboxing approaches. There are subinterpreters but they can slow to start from scratch. There are higher-level sandboxing approaches like microvms, but they have setup overhead and are not easy to use fr
53.
by kodablah 2y ago
> Workflows are systems where LLMs and tools are orchestrated through predefined code paths This definition keeps coming up, but the definition isn't accurate for workflows. Modern workflow systems are very dynamic in nature and di
54.
Temporal Raises $146M Series C to Power the Future of Durable Applications(temporal.io)
18 points by kodablah 2y ago|1 comments
55.
by kodablah 2y ago
TC: https://techcrunch.com/2025/03/31/temporal-lands-146-million... , press release: https://www.businesswire.com/news/home/20250330487137/en/Tem...
56.
by kodablah 2y ago
We wanted to use Ractors in our latest Ruby project (which is Rust based using rb-sys/magnus for some parts), but since our users use Google Protobuf inside the code that may run in Ractors, we could not because the library is not Ract
57.
by kodablah 2y ago
My biased answer, because I work at Temporal[0], is to use an existing workflow solution that solves all of these problems instead of reaching for a solution that doesn't help with any of these but happens to be AI specific. Most agent
58.
by kodablah 2y ago
I think Anthropic's definition of workflows is inaccurate for modern definitions of the term. Temporal for instance (disclaimer, my employer) allows completely dynamic logic in agentic workflows to let the LLM choose what to do next. I
59.
by kodablah 2y ago
The problem with this definition is that modern workflow systems are not through predefined code paths, they do dynamically direct their own processes and tool usage.
60.
by kodablah 2y ago
> Just like the external-distribution model, arbitrary-location architectures often come with a performance cost. Durable execution systems typically snapshot their state to a persistent store between every step. This is not true by most

More ›