3,917 karma · joined April 13, 2015
GitLab: https://gitlab.com/golddranks/ GitHub: https://github.com/golddranks/ Twitter: https://twitter.com/golddranks
meet.hn/city/jp-Tokyo
Socials: - github.com/golddranks
Interests: Programming, AI/ML, Data Science, DevOps, Education, Hacking, Hardware, Open Source, Networking, Philosophy, Science, Web Development, Japanese Language
---
E-mail: pyry.kontio@drasa.eu
1) Writing a high-performance memory allocator for a game engine in Rust: https://github.com/golddranks/bang/tree/main/libs/arena/src (Still work in progress, so it's in a bit messy state.) Didn't seem to understand the design I had in mind, and/or the requirements and goes on tangents and starts changing the design. In the end, coded the main code myself and used LLM for writing tests with some success. Had to remove tons of inane comments that didn't provide any explanatory value.
2) Trying to fix a Django ORM expression that generates unoptimal and incorrect SQL. Constantly changes opinion whether something is even possible or supported by Django, apologizes when pointing out mistakes / bugs / hallucinations, but then proceeds to not internalize the implications of the said mistakes.
I used the Zed editor with its recently published agentic features. I tried to prompt it with a chat style discussion, but it often did bigger edits I would have liked, and failed to share a high-level plan in advance, something I often requested.
My biggest frustrations were not coding problems per se, but just general inability to follow instructions and see implications, and lacking the awareness to step back and ask for confirmations or better directions if there are "hold on, something's not right" kind of moments. Also, generally following through with "thanks for pointing that out, you are absolutely right!" even if you are NOT right. That yes-man style seriously erodes trust in the output.
What I meant was purely from the capabilities perspective. There's no way a current AI model would outperform an average junior dev in job performance over... let's say, a year to be charitable. Even if they'd outperform junior devs during the first week, no way for a longer period.
However, that doesn't mean that the business people won't try to pre-empt potential savings. Some think that AI is already good enough, and others don't, but they count it to be good enough in the future. Whether that happens remains to be seen, but the effects are already here.
However, as a debugging companion, it's slightly better than a rubber duck, because at least there's some suspension of disbelief so I tend to explain things to it earnestly and because of that, process them better by myself.
That said, it's remarkable and interesting how quickly these models are getting better. Can't say anything about version 4, not having tested it yet, but in a five years time, the things are not looking good for junior developers for sure, and a few years more, for everybody.
These days I can in all truthfulness say that I don't only enjoy writing Rust –something that was true already 10 years back, despite frequent frustrations – but I am also productive and feel that the language provides what it set out to provide. That's something that certainly _wasn't_ true 10 years back. A decade of iterative improvement is nothing to sneeze at.
I hope stability without stagnation will continue in the coming decades. May Rust 1.174 in year 2035 be a thing of beauty!
Maybe to you. For some of us, it's also a form of self-expression, a hobby or a lifestyle.
In my experience coding for money and coding for fun is a very different experience. I know my worth, but I am also free to do whatever I want out of my working hours.
I also think that Svelte, having a compiler, seems like that it would have an edge in theory.
I'm interested in fine-graned reactivity so Svelte and SolidJS have been on my radar, but the HTMX-style approach appeals to me.
Here's something to munch on:
https://dev.to/ryansolid/marko-compiling-fine-grained-reacti...
https://dev.to/this-is-learning/marko-for-sites-solid-for-ap...
(Just throwing ideas here, but there could be `#[never_panic]` for simple cases where the compiler can clearly see that panic is not possible, or error otherwise, and `#[unsafe(never_panic)]` for more involved cases, that could be proven with 3rd party tools or by reasoning by the developer like normal unsafe blocks.)
For more complicated guarantees, it's harder to see if there's enough common ground for these tools to have some kind of common ground.
> A primordial black hole with an initial mass of around 10^12 kg would be completing its evaporation today
And according to this:
https://www.omnicalculator.com/physics/schwarzschild-radius
Mass: 10e12 kg → Schwarzschild radius of 1.5e-14 m which is smaller than a hydrogen atom (5.3e−11 m).
I wonder what would be the mass that'd keep a black hole in thermal equilibrium with the current background radiation...
(Edit. whoops, minus sign in a wrong place made the calculations haywire, fixed now.)
Also, the site seems to have abysmal performance.
Why would that be, because it's too "political" for tech news? Or are there actual DOGE sympathies within the HN population?
If you want to write a function that takes a linked list of a specific type as a parameter, you just take in a value of that type. The linked list is baked in, so you can get to the other nodes, and because the type is known, you can get back to the parent type from the linked nodes with fieldParentPtr. How to do that _safely_? I don't think that Zig embraces any Rust-like safe/unsafe dichotomy, so you don't.
> Btw. wouldn't it be possible in modern pipelines to remap or "disfigure" the texture when converting to triangles, so that it counters the bias accordingly? Ah, but that bakes in the shape of the quad, so it can't be modified runtime or it will get distorted again, right.
How does that work with animated meshes?