I find that I still need one physical machine per task when doing perf sensitive work, because the agent needs a quiet environment where benchmarks reflect how things perform on real dev machines. Running two sessions in parallel they already start to cause benchmark noise to each other.
Going to do a for real post on this soon, but late last night we shipped @AkkaDotNET v1.6-beta1
This includes:
- Full AOT support for core Akka, Hosting, Streams
- Source-generated serialization + System.Memory-powered primitives for it + all I/O
- Artery.Tcp - need to re-benchmark it since Iast posted about it but TL;DR; it can do 1.6m msg/s over a single connection, and these are REAL message payloads, not byte arrays or strings.
I've already validated the AOT support in a live application that consumes Akka + Akka.Streams - works great so far. Going to deploy that later today.
great post from @exedev team - the same thing that has always been true of software engineering is still true:
Do fewer things in parallel, do them very well, optimize for getting incremental value out to users, FOCUS
It's been 30 years since the XP and Lean folks said "limit work in progress (50+ if you count the eli goldratt thing) - its still true
https://t.co/eyMSiF0fX7
i feel like people do not grok how important celld is.
it's scalable applications of arbitrary complexity. the only dependency is s3.
once you see it, you'll realize there's no point to traditional javascript runtimes in serving applications - only for build processes (eg bundling) and scripting.
the networking and scaleability are deeply rooted not only in the distributed runtime (celld), but in the programming model itself (largely kenton's design)
I wasn't quite sure when I started celld how well this could be made to work, but we've been running it in bigger capacities and getting user reports over the last months. Actually handles load surprisingly well. (any experience in the comments to share?)
because the programming model does not expose the underlying linux system, you can actually think of celld as a distributed operating system - running in user space of linux. it only runs one program / doesn't support multi-tenant, but it has system services like an operating system. it's all about networking - i like to think of it as the practical modern version of plan9 or even erlang beam.
So the fastest JSON serializer for .NET now is developed by CAPCOM as part of their game engine that powers Resident Evil / Biohazard
I did not see that coming lol
https://t.co/oaAarJRfmQ
Today weโre introducing Gemini 4 Argon.
It delivers frontier performance in complex workflows across real-world software engineering, knowledge work, and cybersecurity defense with an industry-leading 1M token output limit.
โLos SaaS van a morir, ahora cualquier persona puede hacer su propia Appโ
Cualquier persona puede hacer ejercicio 1 hora al dรญa para tener buena salud y aun asรญ la mayorรญa decide no hacerlo.
Lynx 4.0 is here! ๐
๐ฑ Foldables & CSS media queriesโจโจ Liquid Glass & Blur with <blur-view>โจ๐ Open-source <webview>โจ๐ค OpenUI & Agent Skillsโจโ๏ธ ReactLynx improvements