pyrolistical

Why can’t user request be spicy numbers so prompt injection is impossible

You’re using a straw man of a bad designer

Perforce was fine. It just had a terrible ui and didn’t allow me to code on the beach.

If I were still manually merging conflicts the p4merge tool was GOAT

I used it in git

Why not just just have most of it in wasm? There are wasm runtimes that don’t require js, and I’m sure Google can adapt their engine. Then they could integrate the other side with rust

I was enticed by the promise of it being barebones but I still found it too bloated

So I cut out a lot of functionality in my own fork

https://github.com/Pyrolistical/mi

I took “expected to customize basically everything” to heart

But you kind of do.

For a untype language like js array, since it can be empty, you have to either always check the length, the item returned, or have a precondition to know the array is not empty.

All three of those cases is either code or context you’re holding in your head.

All that stuff is equivalent to a type system

Funny, I solved this problem by having Claude write a pi extension

https://github.com/Pyrolistical/pi-notify

Now my pi agent setups its own trigger to notify itself when a background process is done

Until there is a machine that is natively functional, there is always going to an incentive to go lower level for more performance.

Even hardware (GPUs) that functional language could trivially exploit, it’s still higher performance to write low level code and manages all the memory imperatively

Ask for analogy in terms of a thing you are an expert in.

ie. i am an expert at zig, explain this c++ in terms of zig

Soooo anytime now to bring it back right??

No way you can get that much each without extremely quants

For a single r9700 you have 637 GB/s and for qwen 3.8 27b q4_k_xl the maximum tg/s is 33 before mtp

Now if you meant 4xr9700 tensor parallelism with mtp, 80 tg/s starts to make sense

I run it locally at q4_k_xl on a r9700 with kv cache bf16 and while it thinks a lot, it’s still fast enough to do the task.

This model had its knowledge replaced with reasoning ability. The chain of thought what makes this reasoning effective.

So this is why you need to let it think and don’t quantize the kv cache.

Nic needs pcie5 x16 slot, so on am5, take out your gpu

It’s like next.js but for backend.

Personally not for me. These are very productive once you learn the shape they expect.

But the wheel needs to be reinvented on how to do everything.

I ran have straight forward verbose code with no hidden control flow

Give it agent instructions in the major breaking api changes. I force around Io stuff. Then point it to the zig source code.

Sure it wastes a bit of time always figure it out when it fails to compile.

This is why I’m excited to see qwen3.8 27b removed a bunch of knowledge for more reasoning. Baked in old zig api is worthless

Umm I have an extra 35, do you have layer 6?

Then fix it using the llm

I like putting the stdin before the command

< file grep abc

Except Claude remembers in it memories. You need to clear that too

It’s open source. You take ownership of it for your deployment and stop relying on continued free work.

You can use llm to pull in updates as they are released. It’s not gpl, so you don’t need to publish your port

Yeah but they turned it into something unreadable. Call it a skill issue if you wish.

I just haven’t found another language that just makes sense. Zig doesn’t hide anything from you

I predict we may be heading back to self implementations based off of papers since it is now cheaper to do so with AI coding agents.

Yeah they kinda suck and make mistakes right now, but tech only gets better.

It’s no different than 3D printing. Instead of cutting and joining a bunch of stock parts, you just print the desired part.

In the same way printing with plastic kinda sucks, the tech will improve. Now you can print in metal or in resin without supports.

The future will be take all the ideas from various off the shelf products but tightly integrate them together for my specific use case

That would require someone who knows what they are doing, hence this service

Within an order of magnitude. I would call this awash

And then you can get AI do a nicer port of SDL.zig and you get way better decls.

Proper enums, proper tagged unions, and often reading the docs can allow the AI to distinguish T * to one of

1. [*]T

2. [:0]T

3. ?T

4. *T

And these are just the most common ones. If you know it’s a read only pointer/array then you can add the const modifier

What do you mean? By the time you have kernel access like that you’ve already won.

I’ve been yak shaving the interfaces not the implementation.

I used ai to convert c headers into in nice zig code. Then I link to the library.

It’s cheap to use zig translate-c to convert c headers but the output isn’t nice.

You can give ai c++ source which usually has more documentation than the compromised flat c header. It allows you to do a better zig port. Zig greatly cuts down the noise in c headers as everything needs to have long prefix for namespacing. But in zig we can just nest things properly.

We can introduce intermediate layers to use proper tagged unions and distinguish ?T, *T, [*]T

Expose the sync queue to end user and train them to understand if they attempt to close the tab with a pending queue they will get the ugly prompt warning them

The prefix cache is working properly 100k doesn’t prefill more than once

We should port the zig std lib as a c lib