beders (u/beders) - Readit News

beders commented on Clojure Async Flow Guide clojure.github.io/core.as... · Posted by u/simonpure

kasajian · 8 days ago

Funny. I was just thinking about dismissing Clojure for a project I'm going to work on because I was concerned about it's lack of ability to work with async calls. I'm too used to how async in JavaScript and C#, and I'm not sure I'd want to work in an environment that doesn't have a simple way to structure async calls. It doesn't necessarily have to be async / await. Just some attention to the issue rather than completely ignoring it.

beders · 8 days ago

You can get basically all variations of async coding with Clojure a la carte.

beders commented on Training language models to be warm and empathetic makes them less reliable arxiv.org/abs/2507.21919... · Posted by u/Cynddl

beders · 14 days ago

They are hallucinating word finding algorithms.

They are not "empathetic". There isn't even a "they".

We need to do better educating people about what a chatbot is and isn't and what data was used to train it.

The real danger of LLMs is not that they secretly take over the world.

The danger is that people think they are conscious beings.

beders commented on Use Your Type System dzombak.com/blog/2025/07/... · Posted by u/ingve

beders · a month ago

It is tempting, maybe a good first step, but often not expressive enough.

Especially and particularly attributes/fields/properties in an enterprise solution.

You want to associate various metadata - including at runtime - with a _value_ and use that as attribute/field/property in a container.

You want to be able to transport and combine these values in different ways, especially if your business domain is subject to many changes.

If you are tempted to use "classes" for this, you will sign up for significant pain later down the road.

beders commented on The jank programming language jank-lang.org/... · Posted by u/akkad33

dzonga · 2 months ago

beautiful work. clojure is very nice. one of the most impactful talks I have ever seen was from Rich Hickey - simple made easy.

however my only gripe with clojure while it's easy to write and comprehend at first - it's difficult to read. & yet most our time we read code not write it. but then again it might be my lack of brain power.

beders · 2 months ago

You need a REPL to truly read Clojure code. Could be a weakness or could be a strength. In my day to day work I consider a strength since I’m working at the REPL the whole day anyways

beders commented on Most RESTful APIs aren't really RESTful florian-kraemer.net//soft... · Posted by u/BerislavLopac

beders · 2 months ago

I always urge software architects (are they still around?) and senior engineers in charge of APIs to think very carefully about the consumers of the API.

If the only consumer is your own UI, you should use a much more integrated RPC style that helps you be fast. Forget about OpenAPI etc: Use a tool or library that makes it dead simple to provide data the UI needs.

If you have a consumer outside your organization: a RESTish API it is.

If your consumer is supposed to be generic and can "discover" your API, RESTful is the way to go.

But no one writes generic ones anymore. We already have the ultimate one: the browser.

beders commented on Mercury: Ultra-fast language models based on diffusion arxiv.org/abs/2506.17298... · Posted by u/PaulHoule

true_blue · 2 months ago

I tried the playground and got a strange response. I asked for a regex pattern, and the model gave itself a little game-plan, then it wrote the pattern and started to write tests for it. But it never stopped writing tests. It continued to write tests of increasing size until I guess it reached a context limit and the answer was canceled. Also, for each test it wrote, it added a comment about if the test should pass or fail, but after about the 30th test, it started giving the wrong answer for those too, saying that a test should fail when actually it should pass if the pattern is correct. And after about the 120th test, the tests started to not even make sense anymore. They were just nonsense characters until the answer got cut off.

The pattern it made was also wrong, but I think the first issue is more interesting.

beders · 2 months ago

I think that's a prime example showing that token prediction simply isn't good enough for correctness. It never will be. LLMs are not designed to reason about code.

beders commented on A Rust-TypeScript integration github.com/beeeeep54/rust... · Posted by u/wreedtyt

beders · 2 months ago

I wish people would be a little bit more precise.

There is no type safety.

There must be data validation on the endpoint but anyone can send anything and if you rely on your front-end to send you the right data shapes and valid values without checking, you are in deep trouble.

beders commented on Zig breaking change – Initial Writergate github.com/ziglang/zig/pu... · Posted by u/Retro_Dev

thayne · 2 months ago

This is why I'm surprised when production projects, like bun, choose to use zig. I don't think the language itself is a bad choice (although I do disagree qith some of the design decisions), but having to make substantial changes when there are breaking changes like this because the language is pre-1.0 every so often in a large code base isn't something I would want to deal with.

beders · 2 months ago

Zig just caught up with the practice that runs rampant in JavaScript land ;)

beders commented on React Still Feels Insane and No One Is Talking About It mbrizic.com/blog/react-is... · Posted by u/mbrizic

beders · 2 months ago

This is what happens when a V also wants to do the M and the C.

But I would say most front-end libraries are insane: Their job is to manipulate a tree structure which is kinda slow (still?).

Who would have thought that this problem has such a crazy solution space!

From jQuery to Knockout.js to Angular to Vue to React to Svelte and many many others.

Only a couple of those understand that V = f(state) is only half the equation.