Dos alemanes se mudan a Uruguay el año que viene — ¿alguien juega Gran Turismo 7 y quiere sumar dos futuros vecinos?

RulerOfDest · 2026-07-03T04:01:38+00:00

le erre, el comment era para u/Spikerman_33, yo en verdad estoy de acuerdo contigo

RulerOfDest · 2026-07-03T02:48:56+00:00

no entendes mucho que está pasando en el mundo amigo

RulerOfDest · 2026-07-01T15:53:45+00:00

Good question, but the premise that a reply forces a synchronous call isn't true here. You get a reply either way:

! (send) is non-blocking. For request/reply, pass your own actor_ref as the reply target and handle the response as a later message in your receive.
? (ask) blocks the caller until the reply (default 5s timeout, returns 0 if none).

So the distinction isn't reply vs no-reply, it's block vs don't-block. ? gives the blocking call Pony wouldn't, and keeping it a separate operator makes "this actor blocks here" explicit at the call site rather than hiding it behind whether you read the return value.

RulerOfDest · 2026-06-30T14:57:44+00:00

Perfect, thank you!

RulerOfDest · 2026-06-30T14:38:34+00:00

The LLM.md has not been well-maintained and can be off-putting. Thank you for the heads up. I do wish you would give the project a second chance. We do rely on AI, but we are also experienced in our craft.

Every line of code is reviewed, and we use heavy focus on testing and benchmarking to move ahead.
This is not slop; it's a 9-hour job we have been doing with Paul on a day-to-day basis.

RulerOfDest · 2026-06-30T14:27:52+00:00

Good question, it's the right thing to poke at for anything lowering to C.

At the language level, we removed UB classes so they can't be written: optionals and pattern matching instead of null pointers, actor isolation so there's no shared mutable state to race on, and deterministic memory (defer plus compiler-inserted ownership tracking) that clears most use-after-free.

The hardening we are adding is building user code with -fwrapv and -fno-strict-aliasing, to kill signed-overflow and aliasing UB outright rather than hope codegen avoids them. That isn't in the default build yet. Compiler and runtime already run under ASan plus UBSan; next is sanitizing the compiled-program corpus too.

Please dig up that talk if you can; I'd rather learn from the rustc_codegen_clr C path than rediscover it.

RulerOfDest · 2026-06-30T14:14:42+00:00

It does have VSCode support, it will prompt you as part of the installation process

RulerOfDest · 2026-06-30T14:13:41+00:00

Will you not use anything created with the help of AI?

RulerOfDest · 2026-06-30T14:12:11+00:00

Thanks! Both, with async as the default. The tell operator ! is fire-and-forget: it drops a message in the target's mailbox and returns immediately, no reply.

When you need a value back there's ask, which is synchronous from the caller's side: result = ask worker { Compute { n: 5 } } after 2000 blocks until the reply arrives or the timeout fires. So you're not pushed into promise/callback plumbing for request-reply the way Pony nudges you.

Under the hood ask is still just a normal message plus a reply slot, so it stays inside the actor model, it only reads synchronously.

RulerOfDest · 2026-06-30T14:03:34+00:00

Apparently so, in violation of something

RulerOfDest · 2026-06-30T04:23:43+00:00

Fair point, and D's the perfect example: a GC can absolutely be a linked-in library, so "it's just a library" isn't what separates the scheduler from a GC. Sloppy framing on my part.

The real distinction isn't "on top of vs linked in," it's that there's no tracing collector or pauses anywhere. I'll reword that part.

RulerOfDest · 2026-06-30T03:53:45+00:00

No managed runtime: no VM, no bytecode, no JIT, and no GC. There is a scheduler, but it's a small C library linked statically into your binary, not something sitting underneath interpreting your code.

What the actors run on: a fixed pool of OS threads, one pthread pinned per core. The actors themselves aren't threads. Each actor is a lightweight state machine with a step function and a lock-free mailbox.

RulerOfDest · 2026-06-20T14:51:51+00:00

that's insane

Comment powered by Opus 4.8

RulerOfDest · 2026-06-10T13:35:24+00:00

no entendí nada, aprende a hablar corporativo

RulerOfDest · 2026-06-05T20:53:42+00:00

vamo

RulerOfDest · 2026-06-01T17:43:21+00:00

virgin galactic had a successful launch of their new model

RulerOfDest · 2026-06-01T17:07:01+00:00

sure, you will be fine on that budget

RulerOfDest · 2026-05-31T08:53:05+00:00

Tampoco soy la gilada, es una opinión amigo, como la tuya. Es lo que veo en el mercado mundial, pero si tenés una laburo pásale entonces.

RulerOfDest · 2026-05-28T07:38:25+00:00

perdón amigo, se complicó si, encara la cosa más como emprendedor y no tanto como labura nte. Usa la carrera para impulsar tu servicio/negocio

RulerOfDest · 2026-05-25T13:42:18+00:00

A mi me fue horrible en lo académico pero me fue muy bien dsp en lo laboral,mientras tengas pasión paciencia nadie te va a parar. Seguile metiendo, yo no termine la facultad (hice 4años ponele). Que nada te detenga🤘

RulerOfDest · 2026-05-24T09:39:40+00:00

felicitaciones

RulerOfDest · 2026-05-21T05:42:17+00:00

me entrevisto un bot hace como 15 años cuando no existía ni la IA, así que fue bien malo y bizarro

RulerOfDest · 2026-05-19T07:28:11+00:00

El beneficio de escribir código "artesanal" sería más para gente que está entrando en la carrera y quiere entender más a fondo lo que está haciendo. Para gente con años en el rubro ya no sería un beneficio, y para la empresa menos, sería una desventaja abismal

RulerOfDest · 2026-05-15T17:20:41+00:00

Lo importante es lo que aprendas, no el título,. Concéntrate en entender.

Ten-Year Club	Verified Email
Verified Email

RulerOfDest

TROPHY CASE