Meet Orca: Deterministic, AI-driven development flows.
Orca Flow scripts orchestrate coding agents. No need to try to convince the LLM that reviewing code until all review comments are fixed is a good idea - the script will ensure that's the way it will be done. No need to spend tokens on calling a code formatter, switch branches or creating PRs.
Orca Flow scripts are written in Scala, and executable using scala-cli. That's the only component you'll need to install - everything else will be downloaded on-the-fly.
Orca Flow scripts read like Python, but are type-safe, so you can know that your script will execute just fine.
Orca works with Claude & Codex (now), but the plans are much wider than that!
@Krever01 Save some energy for the old stuff too 😉 I’m just polishing two MRs for workflows4s, so you’ll have something to review in a sec. Two features.
OpenCode, a popular project, is using #Effect (#TypeScript library). They adopted it as it makes code safer in age of LLMs.
Originally inspired by #Scala's ZIO, Effect getting popular is a big deal as it's pushing FP to the masses.
https://t.co/UwpAdaHvSG
@adamwarski@ghostdogpr@adamhearn It's not about taste; it's about how fragile code can be in IDEs, like when you're refactoring or merging conflicts, which happens a lot in real-world, big industry projects. That's why braceless syntax is risky.
Scala Native 0.5.12 has been published today!
If you're up to the new goodies, there's a support for experimental Virtual Threads (Scala 3 and Unix only, no Windows yet)
If you prefer stability, issues with GC deadlock under release mode is now fixed
https://t.co/0tWF6V1JKu
Scala has long been a magnet for innovation and, although that's actually desirable, the consequent fragmentation of the ecosystem is a major issue for library authors. And yes, Kyo worsens it.
It's time for a proper solution! Forget F[_], meet kyo-compat: write your library once, support ZIO, Cats Effect, Future, Ox, Twitter Future, and Kyo 🪄
✅ Zero overhead: every method is inline and lowers to the backend's own primitive. No typeclass dispatch
✅ No degraded features: capabilities like tracing work as if using the underlying libraries directly
✅ Fully isolated: each artifact depends only on its target library. No Kyo runtime, zero dependencies
✅ SBT plugin: cross-publishes every backend from one source tree
One source. Every stack.
Kyo 1.0.0-RC2 is out so why not - refactoring my whole project to use it. Let's see how it goes in the wild ✌️
PS: Will need to introduce workflows4s-kyo :) @Krever01 should be easy with recently added effect polymorphism I guess :)
https://t.co/r45xrRxFMk
After a long search for a new projector, it came down to three models: XGIMI Aura 2, JMGO O2S Ultra, and Epson EH-LS800W. In the end, I chose the XGIMI.
Its real brightness is lower than advertised, and modest on paper to begin with, but its power consumption is also lower than expected and impressively low for this class. With a UST ALR screen, brightness should be just right.
Built-in speakers do not matter to me, because I will be using external audio anyway.
It also has great design and an automatic cover, a feature the competition lacks.
This review was especially helpful: https://t.co/9qJ3kgwS9n.
Thought I was getting old as modern metal stopped clicking, turns out I’m just very picky. I’ve never managed to sit through a full Kreator or Sadus album, yet Abuser (PL) - "Blood Marks" really hits me hard. Thrash on paper, though I’m surprised they don’t call it Thrash-Death. Also, if you’re into Slayer or early Sepultura (Beneath the Remains), you should check this, but Abuser feels even wilder. The energy just explodes out of the speakers.
https://t.co/M7WPfMStWc
https://t.co/OG6NpEyG37