yladiz

At least body language has some studies put into understanding it.

I have a similar disdain to high levels of unnecessary cursing in something written, like the trend of "The Fucking Weather" style things, but I think this wasn't particularly noticeable. I would stick with it to the end.

Without getting into the territory of if the tax should exist at all, in general I think the way it works in Germany is the optimal way to approach a tax of this kind: tax each household (not individuals), with few exceptions. This gets rid of the whole trouble of people checking if you should pay the tax, because you have to, and so it dramatically simplifies the system.

Define worse/better.

So, you started by making a pointed comment about that the language has no string interpolation when it's ostensibly for building UIs, so I'm not sure why you're surprised you're getting responses like mine or the one from lpil. Gleam is not ostensibly meant for building UIs just because it targets JS, and while you don't get string interpolation in the way you might get in other languages you can go pretty far with the <> syntax.

To answer your question about why you would use Gleam when you're running code in a JS engine, it's the same about any language that compiles down to another, such as Clojure, and you can take your pick of those reasons: preference, syntax, pragmatism, etc. I'm not sure what kind of answer you're looking for beyond that.

You can do a lot more with JavaScript than building UIs.

> Arabs themselves understand and respect what Israel is doing in Gaza and why.

Any sources that aren’t just anecdotes? I’d love to see some details about “Arabs” understanding and respecting the atrocities in Gaza, because many news organizations including English available ones like Al-Jazeera don’t seem to.

Understanding technology and doing something like drinking are not equivalent, what are you on about?

Software maintenance is not free, especially for a project the size of Homebrew, and it's perfectly reasonable for software to not be supported on older computers due to maintenance burden, with a good example being 32 bit processors. If you had a 32 bit processor would you expect all of your software that was supported now to be supported forever, just because it supports it now?

How long do you expect them to support Intel processors though? It’s been like 6 years since the last MacBook release had any Intel processor, and Apple doesn’t make OS updates anymore, so it doesn’t surprise me that Homebrew stopped too.

It’s not perfect but I’ve just tested and reader mode does work for this website.

Torpedoing how?

Great, number go up. Have the features led to actual customer growth, or just increased productivity?

Yeah, with all the AI needs we’ll just have to transition to fusion energy.

Is this assuming or studying human maintenance?

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.

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.

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

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).

> 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.

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`.

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.

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?

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.

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.

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.

Speak for yourself.

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.

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

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.