asveikau

Part of the reason we're seeing objectionable government action now is because we militarized law enforcement tasks and equipment in the post-9/11 era.

I don't think the article is saying don't build a payload-agnostic telemetry engine. The specific examples cited are that it's probably legitimate to have a vehicle registration database (with the caveat that even that could be abused), but not a database of sexual orientations or religious affiliations.

> system C/C++ ABI

C++ abi should not be included in this. It is independent from the other pieces and historically a source of incompatibility on its own.

Saying "C/C++ abi" as if they are the same is looney tunes, the former is very simple and stable and the latter is very complex.

It didn't write a driver. It used a linux driver. You don't need an LLM.

But the dominant print daemon on Linux, CUPS, was literally acquired by apple to form the basis of their printer architecture.

I'm pretty sure I've used that exact printer on Linux without issue. Long ago, deep into the pre ai era.

Edit: no, I was thinking of the older p1008.

I am an old man yelling at cloud, but why is a library that does something this simple something that needs maintenance? Like if your jaw is dropping because an environment variable parser hasn't seen commits since 2023 ... ... How old is /usr/bin/env ? Lots of code churn on that one?

The github release pages for this project have me wondering who it is for. There are multiple releases per day. Also the Linux release binaries do not compile for CUDA.

It's more reasonable for a lot of people to just follow master and build from source.

I'm hoping when the shit hits the fan, you can get a sick GPU for cheap.

Ah ok. So the Bulgarian printed lowercase looks similar to Russian cursive.

> OCR all the business copy of receipts from the till,

I would not do this at all. OCR is still very bad. If you want incorrect dollar figures be my guest.

I don't think it's NIH so much as the glibc ABI is a broad surface of implementation specific choices outside the C standard, and a moving target. It's an emergent property of many small implementation choices that another libc project would find too difficult to replicate.

I had a recent experience fighting this sort of thing when I wanted to cross-compile from a distro using glibc to a distro using musl.

Glibc is also kind of bloated and it's reasonable that android or a similar embedded project would not want to pull the whole thing in. Especially when you consider the original goal of bionic was just to bootstrap Java code, which was meant to be the primary platform interface rather than C, they would want a very minimalist libc for that purpose.

Is that true? Other than things like not seeing a Ы, Э or Ё in Bulgarian, the modern printed fonts look the same to me, though I am not from either country.

I know it's not the same, but you can "kind of" name them by using them as a template parameter, then, scoped to the template, you can reference them under the template parameter name.

Anyway, I don't see it mentioned anywhere in this discussion, but imo the area where c++ lambdas shine is the way they interact with copy constructors and move constructors.

> Can't you just repeat it?

I wouldn't assume you could. I guess that's why people study these things.

> SQLite corruption is possible, but it’s highly unusual and not something you should encounter in normal operation

If there's a hardware failure, for example a flaky SD card, it's not out of the question. A mobile app with a lot of usage will see it.

(Yes, I know this appears to be a server use case.)

This subheading popped out at me:

> The new AI economy

I don't know if this phrasing is intentional, but it gives me a chuckle. The dotcom boom was called "the new economy" about 26-28 years ago.

I was playing with ollama because of name recognition. I was finding pretty quickly that the selection of models on the "ollama store" was pretty stale, and gguf models on huggingface are technically downloadable but don't work as well.

The "friends don't let friends use ollama" article linked in another comment convinced me to try llama-swap. I find it easier to directly deal with gguf files. Hard to quantify, but the outputs of the LLM seem better too. Asking the same gguf the same question with the same chat harness, I subjectively find llama.cpp does better. Might be some different defaults. I haven't dug deeply.

Have you met cops? They are not able to sit still or write things down. You expect too much of them.

If they disagreed about something so fundamental as the attribution of copyright, it would be a serious schism, from my outside perspective it seems along the lines of something that would lead to a fork or separation between the projects.

I also just read more context on the thread and it seems like Damien Miller is in there saying much the same thing as Theo. He wrote:

> ... use of AI-written code now [will] expose us to legal risk.

These policies seem to be often evolving lately in many projects, but I believe OpenBSD (the project OpenSSH is contained inside) is currently skeptical of AI generated code contributions at this point in time.

For example, I found this on a Google search, here is a thread from Theo, the project leader, about LLM output and copyright, where he says they can't accept it into the tree on copyright grounds. https://marc.info/?l=openbsd-tech&m=177425035627562&w=2

Elsewhere in the thread he implies using it for a code review tool is ok

If you've seen Zuckerberg for long enough you'll see he doesn't hold any position for all that long. Remember they renamed the entire company for a product idea he basically abandoned. So if he does "the right thing" you can just wait, he'll give up on it pretty soon.

That's one reason I phrased it as density rather than weight or a raw count of calories. For density we would have the weight as a denominator.

It's conceivable that if they've removed better quality ingredients, calories per gram of weight could go up.

I'd be curious to know, with the reduction in size, if calorie density went up.

Because that would fit a lot of people's perception of how food is going: you get less, but what you do get is worse for you.

> For example, under what constraint regime should the calculator app bundled with an OS be written? It's just a little bundled toy app. Until someone under pressure uses it to calculate a medicine dose, expecting it to be a calculator like it says.

This captures a sentiment I have often felt when people don't take bugs seriously. Or don't take it seriously that they introduced regressions. You should feel personal responsibility for your bugs. When your shit doesn't work, and people are trying to use it, you are basically hurting them, personally.

But it seems with the increase of AI coding, the industry is going the other direction. Nobody seems to care about bugs introduced by slop coding. Except perhaps the users.

GCC and VC++ supported anonymous structs and unions long before C11.

You never know what's going on in the mind of another person, they could have something going on that makes them feel negatively about qemu. We can project our stress into all kinds of strange places.

The other thing is that qemu is so many things. It can be a CPU emulator, a full system emulator, and a frontend to a virtualization engine. And all of this for so many different systems. It's kind of remarkable that all of this is called by the same name.

The M dash stands out, as does "no bindings, ..." but I feel like the LLM would have gotten the correct use of the question mark when they rhetorically ask "why?"

Sounds like quite an ordeal, hope things are going well now.