C on the other hand puts an implicit `return 0` at the end, but only on the main function for some reason. Very weird.

C++ also special-cases the `main` function. Probably because `main` is the interface to the OS so it gets special language treatment.

In C++ you're not allowed to call main yourself, so that the compiler can call the global constructors at the start of main.

Which also exist as C extensions, in some compilers.

frp is nice. I have the tiniest Amazon Lightsail instance running a tunnel to a Minecraft server in my basement. It’s cheaper than getting a fixed IP from my ISP, at sufficiently low traffic.

That is the point. They stop you from memorizing it “just in case” and reusing it, and they force you to use a password manager.

For the average user, which doesn’t use a password manager, this is great. It means they can’t get phished. And it’s also great for the average password manager user, who keeps dozens of insecure and reused passwords in their vault because they manually thought of a password when signing up instead of randomly generating one.

If you’re already using a password manager and random passwords, the UX is designed to be the same. It’s just a way to get regular people to do this.

> If you’re already using a password manager and random passwords, the UX is designed to be the same.

In that case, they've completely and utterly failed.

Z.ai are temporarily offering unlimited usage during off-peak hours with their harness, which is a pretty good deal if your project is public even with this news.

All fun and game until it also silently uploads your other things.

You could always sandbox it or run it in a container

Shouldn't do that, either.

Mind and marketshare are currency in this space. Either these people are honest and deserve your trust and business, or they don't. They've been mischaracterizing the way they've been handling your data. Shut them off accordingly until they make things right.

I mean, it's just basic access control. You don't need to trust every program you run with 100% of all your personal/private information, just confine it to a specific domain accordingly.

I'm fine with certain codebases and configs being shared, but not others, hence the sandbox/container recommendation. I suspect many others are the same way.

It's less about access control and more about corporate behavior control. When you ask a contractor to come fix something about your home, you don't have to clarify to them that they shouldn't also be snooping around the bedroom drawers and taking pictures to be stored somewhere.

You shouldn't have to go and create zero-trust environments for things to operate in because tech companies can't be trusted to be honest and transparent about how they handle your data. It should be a given that they're up-front about what they do with it within the various terms and licenses, and easy to enforce those terms.

Those that cannot behave in such a way should get exactly zero of your business, even if the product is free and you can set up ways to block any sort of intrusions.

I could not agree more. The rise of sandboxing reflects a decrease in trust. Not just in AI. You just don’t download stuff from the internet anymore. It does not matter who created it, or whether it is open source. There is too great a possibility that the package has been blessed with either incompetence or malice by its creators or contributors.

I hope nobody thinks that software produced by these obviously immoral sociopathic corporations should be exempt from such suspicion, when history shows time and time again with news stories like this that they do not deserve such trust.

You should use a sandbox. It is dumb to run any proprietary software without a sandbox, especially LLM-powered.

Create a few terra repo

In practice, if you’re using both Anthropic and OpenAI models, how can you configure Pi (or any other harness) to use these native tools?

I’ve seen this before and the conclusion ends up being “use the native harness”, which I don’t think is an acceptable solution.

OpenCode checks model name and registers the appropriate tools.

const usePatch = model.modelID.includes("gpt-") && !model.modelID.includes("oss") && !model.modelID.includes("gpt-4")

Pi uses its own tools, like Armin wrote in the linked article.

That’s insane. Windows does not have a stable syscall ABI. The way you’re supposed to interact with the kernel is through the userspace library. Of course the kernel team refuses to cooperate.

Do you want to keep reverse engineering the syscall ABI for every Windows edition and update ever? Do you want to ask your users to disable Windows Update?

Regardless, I don’t even understand how that’s relevant, since you’re still introducing a dependency on a proprietary ABI.

All you could tell from this snippet is that .NET 11 eliminated 2 instructions, one of which is a branch.

You should learn assembly anyway, but it won't make this part any more insightful.

To me it’s the fact that if you try to do it in real life (sorting a collection of objects in the real world), you just end up doing merge sort by accident.

It feels like an optimization of merge sort for computers, rather than a different approach.

This is also reflected in the way that it’s usually taught. Normally merge sort is presented first, and quick sort follows from observations about what would happen if you picked different partition points instead of dividing them in half, and how you can reduce the additional space requirements.

These days I was surprised to see, on my personal computer, information from PRs in private repos from my work’s org on GitHub. These are usually secured behind SSO flows which I don’t/can’t do on personal devices. So now I also don’t trust them to keep our code private anymore either. Nice.

It used to be that you could have a single GitHub account and join multiple orgs, some of which have enterprise plans with GitHub. They completely fumbled this during the pressure to ship AI features. Some enterprise controls that are supposed to affect only my work at a specific GitHub org affects me account-wide. I’m part of quite a few orgs on GitHub for OSS projects, and I never consented for that one org’s policies to basically take over my account.

I thought of going through the process of creating another account specifically for my work at this company, but GitHub is itself solving the problem in a very unique way: by being a place I don’t want to be in after I clock out.

My guess (not involved with PS2 emulation specifically at all) is that this will improve low-level emulation.

So things like making a clone of the hardware with an FPGA, making emulators cycle-accurate, removing game-specific hacks that are no longer needed due to more accurate emulation, and achieving 100% bug-for-bug compatibility with original hardware.