Has anyone tried to extend the C Preprocessor to be a fully turing complete language (perhaps something like Snobol) to allow for Terra like meta-programming?
(I am not talking about metalang99 or Cello like stuff, which exploits the Turing tarpit of the currently specified preprocessor but rather tasteful additions to the preprocessor itself).
> You might ask “why not have two stack allocators instead of a double headed one?” The main benefit is when you are memory constrained and know that the size of one stack allocator is enough to serve two systems, but the proportion of memory that goes to one side vs the other is flexible.
This doesn't make a lot of sense. Solving `x <= X, y <= Y` is much easier than solving `x + y <= Z`. If you put a limit on both the size of in-core level data (perhaps using a Cell based system) and on character data in the asset pipeline itself, that is much better than to ensure that all the various combinations of level sizes and character sizes are compatible and won't end up trampling over each other.
Sure, but how do you prove that you won't end up with `x' + y' > Z` for some value of x' and y'? In practice, it's always easier to prove `x < X, y < Y`.
Free Pascal or Delphi? I tried FP a while back and felt that the language had really stagnated (e.g., variables can only be declared at the top of scope like C89).
We mostly use Free Pascal (works fine on Linux and cross-compiling for Windows). But during development we also sometimes use and test Delphi builds on Windows.
This is a good idea, we should start a blacklist of open-source projects that are known to have used LLMs. There should be two universes of code, one for hand-typed code used by people who care about quality and one for slop used by those making trash.
Eh, not really. It just lowers the barrier for lazy people who never would have tried contributing before.
I’ve read a lot of code hand-written by programmers. By smart and hard working people. And I know from experience that the code the average programmer writes is not great either.
Yeah but that's just bad code in general, no? You can make good code with LLMs, you just have to actually engineer it and give up some of the velocity; which is just a bigger version of the same problem we've always had (yes, I get that code review can't scale).
This is just really silly.
The more I think about this the more I think it's like self-driving cars. We have this expectation that self-driving cars MUST be 101% safe and never get into any accidents, ever, before the technology is worth adopting. LLMs are the same -- it's like we think if you can't one-shot a prompt and get perfect software out of it, it's failed. You can choose to spend time getting the LLM to refine the code it's written, review the architecture, come up with an actual engineering process around the LLM. Yes that means you'll be producing less code per time spent -- which is a good thing.
Anyone know when Rust's std::autodiff will become stable? Assuming this Rust support expands to other GPU vendors, autograd will probably be the only reason to use Slang instead of Rust anymore.
I was told in the 2025 LLVM dev meeting that it will always stay in nightly because it's not practical for them to provide long-term stability guarantees that is expected of stable Rust.
Probably because living in PNG sucks and they would rather risk their lives at a chance of improving their condition. Same reason immigrants came from Germany to the US to live in mud dugout houses in the plains. Or immigrants go anywhere really.
I learnt that I must be good at computers when in 4th grade, despite never having touched a PC before, I not only managed to ace my Logo class but was asked by my teacher to help out other struggling students (I am just realising that essentially made me a TA in our class). I still remember trying to understand the Pen Up and Pen Down commands from a book with no immediate access to a PC to try them on.
Maybe that's why they include some sort of screen protector with the device? At least they did with the X4 Pro, did you get that with the X3 as well, and were you using it while it cracked if so?
I've been having mine in a beach bag I'm not too careful with, for about two months, which goes out with me when I swim in the sea, without using the included screen protector, and still no scratches or cracks in mine.
reply