HNHacker News
TopNewBestAskShowJobs

nasretdinov

1,318 karma · joined May 25, 2020

submissionscomments
nasretdinov··on Go 1.27
I still believe that SIMD support is one of the most underrated new features in Go.

It's relatively straightforward to read and to write code using Go's SIMD package (the caveat being that you have to convert your data to SoA manually), and it gives comparable performance to other languages, since there's little in the way of GC overhead, bounds checking, etc, in this case.

So SIMD not only increases performance on its own, but it also closes the performance gap between Go and C++ / Rust, which has been a major cause for rewrites in the past. The memory usage overhead due to GC doesn't go anywhere of course, so there are still performance reasons to "Rewrite in Rust", but it's now become much easier to just optimise the hell out of Go code instead.

nasretdinov··on pg_clickhouse v0.10: Subquery pushdown and 1000x faster TPC-H queries
As someone who tried doing things like condition pushdown, transpiling from one language to another, etc, this is really impressive. Correctly pushing subqueries while preserving the semantics of the original database is something I can't imagine I could've ever achieved
nasretdinov··on Go is an ideal language for AI-assisted software engineering
Correct concurrent code is mind-bogglingly hard even for seasoned veteran humans (and don't get me started on distributed programming...), so it's hardly surprising that LLMs with their limited context windows into the code have a hard time writing correct concurrent code
nasretdinov··on Achieved Full Desktop in GeForce Now
You know, clouds in general let you run arbitrary code and that's not really considered an exploit :)
nasretdinov··on As a Windows user, it's a surreal way to install a program
I've once made a disk image backup of the running system (and it warn that it might be a good idea) and then wiped the laptop clean and installed a new macOS. The disk image (predictably) failed to mount and there wasn't much I could do to fix it.

Since then I also read dmg as damage :)

nasretdinov··on Go 1.27 Interactive Tour
Now I have full understanding
nasretdinov··on Golang proposal: container/: generic collection types
Why isn't it a good fit? The design prioritises readability of code that uses generics vs writing generic code (which is in line with the overall language philosophy). It also does it in a way that doesn't impact compilation speed or add too much complexity, which is also in line with the language philosophy.

If you don't like the fact that not all of standard library has been refactored to support the new language features -- I think it'll come over time. Once these features land into the standard library they can't be taken away, so the language authors take their time to make sure it's designed well.

I don't see anything going obviously wrong here.

nasretdinov··on Golang proposal: container/: generic collection types
Also having stuff like a concurrency limiter (instead of doing weird var limiter chan struct{} and using it as `limiter <- struct{}{}` and `defer <-limiter`) as a library function in `sync` package would be great too.
nasretdinov··on Golang proposal: container/: generic collection types
Well, better late than never. Stuff like sets or a typed heap is long overdue. Maybe they'll even add iterator API for database/sql results this decade too (something like my pull request for sqlx https://github.com/jmoiron/sqlx/pull/990 but maybe more polished)
nasretdinov··on 2x, not 10x: coding with LLMs in 2026
> the main issue is that they’re completely undebbugable now

Well, that means the quality actually dropped then :). Looking impressive isn't equal to quality, understandability and reliability is

nasretdinov··on Htmx 4.0, the first JavaScript library to release exclusively on the Game Boy
Well, no, I don't think you should be doing that :)
nasretdinov··on Htmx 4.0, the first JavaScript library to release exclusively on the Game Boy
Yes, but on the other hand what I'm implying is that you might not actually need it :)
nasretdinov··on Htmx 4.0, the first JavaScript library to release exclusively on the Game Boy
Sorry can you please clarify what you mean by having two databases? You can share the same SQLite between applications if you really want
nasretdinov··on Htmx 4.0, the first JavaScript library to release exclusively on the Game Boy
Well if you already have Postgres then yes, sounds fine. I don't really agree that SQLite needs tons of tweaking -- setting journal_mode to WAL/WAL2 is the only real thing worth doing, everything else I would consider optional.

Version upgrades for SQLite are basically a no-op though, that's kinda one of the reasons why it's so great to run in production (and deployment a maintenance being mostly a no-op as well, apart from setting up backups I guess).

I don't actually suggest that everyone should run their production on SQLite, but it's genuinely worth considering especially for small-ish projects.

nasretdinov··on Htmx 4.0, the first JavaScript library to release exclusively on the Game Boy
<please don't take this too seriously>

That's great but I believe it's still over-engineered. Unless it's a web site that can tolerate no downtime at all during schema updates, SQLite in WAL2 mode is more than enough. Moreover, in Postgres version upgrades can't be done without significant downtime (or setting up replication and performing a complex dance), so even that isn't so cut and dry.

</ ... >

nasretdinov··on Codeberg Bans Cryptocurrency Projects
I think the real issue is that lots of people somehow got convinced that Codeberg is a somehow better version of GitHub that won't ever be susceptible to the same issues GitHub had, which is mainly too much centralisation and all the risks associated with it.

Codeberg and others setting their own rules (especially if it's done via a community vote and not a decision by some random exec who's just heard a buzzword and now forces everyone to immediately adopt it) is actually a desirable outcome -- given that Forgejo or any other GitLab is open source, so you can (and somebody probably will) create more "hubs". This avoids lock-in by a single "hub" and hopefully will lead to more standartisation and cooperation instead of what we have now with a single largest hub like GitHub.

nasretdinov··on Everyone should know SIMD
It actually works really well in the last couple Go versions with GOEXPERIMENT=simd. You do get a similar speedup (if not higher, since SIMD also eliminates the penalty for bounds checking and other things Go runtime does.
nasretdinov··on Intel Starts Shipping High-NA EUV Silicon
IMO it's competition that makes better products in the end. If either party becomes a full monopolist the progress will stall (as already happened with Intel I guess)
nasretdinov··on AI makes programming differently difficult
Depending on what you're working on, moving slowly and thoughtfully might be a feature. Just saying
nasretdinov··on AI makes programming differently difficult
Definitely not my experience. No matter the model, if I'm working on something important (and there is little reason on working on something not important) I do care about correctness and understandability. While LLMs are great for throwaway one-time code (although that's also debatable), they cannot compete with code written by a seasoned professional. No matter how many times I've tried delegating writing code to LLMs I've always regretted it in a few months' time, because it is more buggy and I don't really know what is happening there.

The future is using LLMs for what they are good for. What that is still being found out. I've had great experience with LLMs reviewing the code (matches with Primagean's ~50% accuracy at finding bugs, which is really good) and for explaining unfamiliar concepts to me.

I firmly believe that the code itself needs to be 100% organic, and if it's not and you're relying on LLMs to generate tons of code, you haven't built enough abstraction to make it unnecessary.

nasretdinov··on GC shape stenciling in Go generics
That is true. Moreover, in general the performance of generic code in Go isn't any better than interface-driven one. Generics are there in Go just for better type safety, and IMO that's sufficient already :)
nasretdinov··on Nul Characters in Strings in SQLite
The only really confusing part to me is that SQLite has separate STRING and BLOB type.ls. I always thought SQLite only really supports INTEGER, REAL and TEXT (aka BLOB) types. And even then the types aren't enforced. So it's really interesting to see that you still somehow can distinguish TEXT from BLOB for example.

P.S. I meant default settings -- I know that strict mode, etc, exists, but it's not the default, so few people change it

nasretdinov··on Using Go for Mobile Apps
> if you have some complex config instead of a simple default

Yup, exactly that. You don't always control the environment in which your software is going to run...

nasretdinov··on Using Go for Mobile Apps
Given that even on Linux DNS resolution in Go can be quite... interesting without CGO being enabled, honestly it's hardly surprising that on iOS it would also be quite challenging.

I imagine that one more interesting thing to consider is that on iOS you can't fork() or spawn sub-processes, so your Go mobile app is indeed running simultaneously as a Go binary and the UI, and there probably can exist countless interactions between the two being unaware of each other that might cause issues

nasretdinov··on Postgres locks do not scale
As others have already pointed out, the issue is too high concurrency — IMO that should be the main outcome of the analysis. E.g. InnoDB has innodb_thread_concurrency setting that applies for internal operations to prevent exactly kinds of issues like these. Yet MySQL isn't perfect in any regard either, it's also very much possible to hit lock (or latch as they're called in DB world) contention if you hit the same rows in a table too hard from too many different threads. It's a fundamental limitation of the CPUs that they can't do too much of parallel read-modify-write, and it starts to break down very quickly with the number of cores
nasretdinov··on Postgres rewritten in Rust, now passing 100% of the Postgres regression tests
I can trivially copy any code even without an LLM though with a simple tool called rsync!
nasretdinov··on WAL-RUS: a Rust Rewrite of WAL-G for PostgreSQL Backups
Value types do indeed reduce the GC pressure, however large Virtual Memory usage (in my understanding) is mostly due to large thread count by default (one per core), and some unavoidable GC overhead in general.
nasretdinov··on Agentic coding notes from Galapagos Island
I can agree with Dan on two things: LLMs do often produce incorrect results and that it's still useful for productivity when used in moderation. For me the wrong results actually cause some kind of ragebait response so I become much more motivated to learn more about the subject to actually generate correct response. After I've learnt the subject area enough I find I'm better off having LLM review my code instead of writing it.

I haven't even begun to try to comprehend how to use fuzzing testing to improve the ability to find bugs, but it sounds really interesting. I've seen mutation testing to be very useful for finding gaps in tests, so I can only imagine that fuzzing + LLMs might produce insane results.

nasretdinov··on WAL-RUS: a Rust Rewrite of WAL-G for PostgreSQL Backups
You probably could limit the bloating of Go programs by setting GOMAXPROCS to something like 1 or 2 on smaller machines, but then again you wouldn't get the best performance. So IMO good call here to rewrite it in a language without GC.
nasretdinov··on Codeberg Is Down
Codeberg is smaller than GitHub and, you know, Go is slightly more efficient than Ruby :)
← PreviousPage 2 of 17Next →