Hacker News: yladiz

New comment by yladiz in "Go 1.27 Interactive Tour"

yladiz — Sun, 02 Aug 2026 15:05:00 +0000

Please. I’m sorry, but you kind of can’t avoid needing to think about types unless you use a language like JavaScript which is super loose with its type conversions, and you especially can’t avoid in a language like Go. With generics in Go you don’t even need to prefill the types like you go with a lot of other cases, so I’m dubious about the cognitive overhead.

New comment by yladiz in "Go 1.27 Interactive Tour"

yladiz — Sun, 02 Aug 2026 12:07:48 +0000

The percentage of people that use LLMs so much that their language would change based on its responses is small enough that I’d doubt it would happen. Maybe for technical groups that use it more, but not for the general population.

New comment by yladiz in "On the non-use of AI in my writing process"

yladiz — Sat, 01 Aug 2026 23:10:38 +0000

Define “direct”, “access”, and “reality”.

New comment by yladiz in "Software for One"

yladiz — Sat, 01 Aug 2026 19:31:09 +0000

I could also recommend SQLite with OPFS, if you’re comfortable with adding a web worker. I personally find it a lot easier to reason about than IndexedDB (even with a wrapper, it’s still a bit tricky to work with, and you get the power of SQL with SQLite).

New comment by yladiz in "SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers"

yladiz — Wed, 29 Jul 2026 10:03:49 +0000

> Why is that the ideal? With SQLite your database is 1:1 connected to your application

I don't think this solves the issue though. To be fair, I was a bit loose with my wording and the principle is actually "don't make backwards breaking changes to your database schema" rather than "do your migrations separately", but if you do them separately it is a good way to enforce it. The issue you want to prevent is your application having bugs/issues in production necessitating a rollback, and your now rolled back application doing things that are incompatible with the current database version (or in a concurrent setting, that some applications may not be updated).

There's still the issue where you're copying over all of the migrations to your server too when you do it in the application, which is in my opinion something you are ideally able to avoid, but it's not a problem in practice until you have 1000s of migrations.

New comment by yladiz in "SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers"

yladiz — Wed, 29 Jul 2026 09:59:35 +0000

I’m a bit confused. That’s not a column definition change, because the original column is the same, you’re doing a data migration. That is one way you would solve this class of problems in SQLite, but it’s a bit annoying compared to a something like `alter column`.

New comment by yladiz in "SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers"

yladiz — Wed, 29 Jul 2026 09:22:36 +0000

I'm fairly confident this is AI generated, but it makes me think regardless: Whenever I see these kind of articles, I'm left wondering if they've actually used SQLite in production because I always see points about how to optimize performance, like using the WAL, but never about annoyances/issues you'd run into before even needing to worry about that. I guess it's the zeitgeist to use it in a production setting, and I think it's great that it's getting hyped because it truly is a capable database, but after trying myself I think I'd never reach for it in production because it lacks a lot of power that a database like Postgres has, and some of that power is actually relevant to a real production setting:

- Column definitions aren't able to be changed with something like `alter column` after creation. To change a column definition you have to manually update the underlying schema using the `writable_schema` pragma. If you mess this up you can be left with a corrupt database.

- Column types are pretty limited. This isn't too much of an issue in practice since you can handle this somewhat in application code, but it can still be a bit annoying at times.

- You have limited options for dealing with schema migrations. You basically either copy the migrations to the server and run it there (manually or with something like Ansible), or you run the migrations in your application on startup. Ideally you'd perform your schema migrations separately from your application, and having to somehow copy/get the migrations to your server to then run the migration is a bit clunky.

All 3 of these are handled in a more powerful (and not local-only) database, and so I don't get why someone would choose SQLite except for prototyping (or places like the browser or phone apps) where performance concerns aren't really relevant.

New comment by yladiz in "PyPI Blog: Releases now reject new files after 14 days"

yladiz — Sat, 25 Jul 2026 12:21:54 +0000

I’m a bit surprised this is possible in the first place. I get that you might not be able to upload everything in one go, but it feels like you should “start” and “finish” a release in that case, and once it’s finished you can’t modify it.

I guess the use case is that you might want to build a wheel for an older release for a newer version of Python?

New comment by yladiz in "ARC-AGI Leaderboard"

yladiz — Sat, 25 Jul 2026 09:53:49 +0000

You could argue that if you allowed a harness, and that harness was specific for ARC, then you don’t have AGI, you have something that is definitely not general.

New comment by yladiz in "The startup's Postgres survival guide"

yladiz — Wed, 22 Jul 2026 16:47:46 +0000

Stored procedures and SQL injection are orthogonal concerns. You can have a parameterized query using PREPARE without needing to resort to stored procedures, and many database drivers or wrappers help you with this by making you provide a string with something like $1 and then the values which are sanitized.

Stored procedures are useful in cases such as annoying data type conversions (for example, before the newer ltree versions, its path couldn't accept hyphens and so if you were using UUIDs you needed a way to convert the UUID to a ltree compatible representation) or when you want to write a function that is used by a constraint, but it's not something I would generally reach for and certainly not for SQL injection reasons.

New comment by yladiz in "GitHub suddenly rejected my SSH key (the fix was a .pub file?)"

yladiz — Tue, 21 Jul 2026 12:48:18 +0000

This isn't about an academic issue though, and who would actually state their RSA key is mathematically sound except in the case that they're performing some research in the field? The point the parent was making was that it was obviously written by AI.

New comment by yladiz in "Sony Deletes a Bunch More Movies from the Accounts of People Who 'Bought' Them"

yladiz — Thu, 16 Jul 2026 15:32:35 +0000

Speak for yourself.

New comment by yladiz in "Control the Ideas, Not the Code"

yladiz — Tue, 14 Jul 2026 09:53:04 +0000

You do not need to understand an entire program to get the benefit of reading a chunk of source code that is part of that program.

New comment by yladiz in "EU Parliament greenlights Chat Control 1.0"

yladiz — Thu, 09 Jul 2026 12:06:10 +0000

Sure, it's not a fallacy, but it does erode nuanced conversations and so it shouldn't be used without caution.

Nocode: Way to write secure and reliable applications

yladiz — Sat, 04 Jul 2026 09:38:11 +0000

Article URL: https://github.com/kelseyhightower/nocode

Comments URL: https://news.ycombinator.com/item?id=48784114

Points: 1

# Comments: 0

New comment by yladiz in "Weave Robotics launches Isaac 1, a $7,999 home robot with Fall 2026 deliveries"

yladiz — Wed, 01 Jul 2026 23:12:02 +0000

At what point is it actually cheaper? Laundry isn't that expensive to do yourself, or to outsource if you really don't want to do it yourself.

New comment by yladiz in "Should European housing politics be Americanized?"

yladiz — Sat, 27 Jun 2026 22:55:50 +0000

That's a fair point, maybe "city center" isn't the best term here. What I mean are areas still in the city close to where a lot of the cafes, bars, restaurants, nightlife - third places in general - are, which is where people that want to live in a city generally prefer to live in if possible.

New comment by yladiz in "Should European housing politics be Americanized?"

yladiz — Sat, 27 Jun 2026 22:46:58 +0000

What?

New comment by yladiz in "Should European housing politics be Americanized?"

yladiz — Sat, 27 Jun 2026 22:38:47 +0000

Many cities and areas close to major European cities have good transit infrastructure, yet people don't want to live there, they want to live in the city. So making more housing outside of the city, again, doesn't solve the actual problem facing major European cities.

New comment by yladiz in "Should European housing politics be Americanized?"

yladiz — Sat, 27 Jun 2026 22:29:13 +0000

No, but they are don't rise nearly as much as real estate prices in city centers, and it's mostly irrelevant to the point I was making, because it doesn't matter how the prices are outside of the city center if you want to live in the city center.