Nobody forces you to use unchecked build! And some people want maximum performances, I've read that bound checking can hurt SIMDification..
Or that reasonable people may disagree on when to make signed/unsigned overflow undefined: Zig didn't only make it an UB on unchecked build they also trigger an "abort on overflow" in checked build.
Zig disagree with you: they even made unsigned OV undefined (in unchecked mode)
> The same goes for its "Code Density" argument: nope, code density is very important. Sure, but ARM's thumb has shown that you can get a RISC which has the same code density as current CISCs. Of course, it's because…
> Unfortunately that's somewhat expected - regardless of implementation Yes, that's expected and no the GC implementation may be improved. See this: >> I remember a research paper about swap and GC, where the GC…
It isn't a toy for sure, but I doubt that it has good scalability stories when using SMP.. I'd love to be wrong given that even phones are multicores, so feel free to correct me.
'data oriented' doesn't mean 'just use SoA' it means use data structures which correspond to your data access pattern. Which is quite difficult to know in complex applications and which can change..
> hands are wrung that communication will become rife with error and misunderstanding because unlike the telegraph, the newfangled telephone leaves no written record! Well let's not forget that early phone communication…
> If you have a read-only variable and exclusive access to it, then you can rely on immutability as well. The problem is the "exclusive access to it", most language aren't Rust.. Some Ada-implementation has the problem…
Why do you say this? The post is quite clear that marking the memory region as NX fix the issue caused by speculative execution.
> the OS _writes_ unused memory pages to the swap file The OS write unused memory pages to the swap file by default. But the 'constant memory' design is usually done with locking in memory both the executable and memory…
Read about the AF447 Rio-Paris crash. Input stick averaging?? That's a huge design mistake which contributed to the crash and AFAIK is still here..
You're phrasing this as if using an IDE was always an advantage, but unfortunately this isn't always the case: -IDEs are more resources hungry, I remember when trying to use CLion on a big C++ codebase, until increasing…
> It's a difficult coordination problem. Well, it depends on the language: language which "capabilities" (both for the source code and for the building* ) could in theory really reduce a lot of the burden to identify…
One thing I noticed with your clever encoding is that you can avoid some nops: instead of having 2 15 bits instructions followed by two nops, you could have two 30 bits instructions, saving maybe a little decoding…
So a VLIW, interesting but usually compressed instructions are at most two-registers..
If the language is Java which puts the GC in nearly everything you're f..., other languages have GCs and nonGC'd data so you go to the wonderfull world of manually managed objects with its use-after-free..
> Do you really think current LLMs can implement a large application in C as securely as they can in e.g. Go? That's not my experience: I've seen an LLM generate a C++ use-after-free (1.5 month ago).
Congratulations your language is trying to solve an hard problem. But .. your language mostly hide when you're doing an 'inside' function call or an 'external' function call. I'm not sure I like this; 1) the latency of…
> The car industry is constantly innovating trying to prevent accidents and make them less damaging to occupants And at the same time, they make bigger and bigger cars which make more serious accidents for pedestrian,…
This part is very bad, 99% of the time if you overflow a 64 bit variable it is because you did the wrong computation, not because you need BigInts..
Not the only one though: I remember what happened when we 'invaded' Lybia: not one criticism in the French news anywhere, total censorship, even though our media had widely and correctly criticised the US for the Irak…
> In France, there has been some ban on advertising alcohol, cigarettes. So technically, it's possible but of course politician's corruption is a big issue..
> And, on the other end, C's warts, footguns and ancient quirks also matter less if you have an LLM plow through it. 'plow through it's?? An LLM can definitedly fall into these traps! Happened to me a few months ago, I…
> Human beings are rational animals as such Really? Explain the success of advertising, superstitions (including religion) then.
Nobody forces you to use unchecked build! And some people want maximum performances, I've read that bound checking can hurt SIMDification..
Or that reasonable people may disagree on when to make signed/unsigned overflow undefined: Zig didn't only make it an UB on unchecked build they also trigger an "abort on overflow" in checked build.
Zig disagree with you: they even made unsigned OV undefined (in unchecked mode)
> The same goes for its "Code Density" argument: nope, code density is very important. Sure, but ARM's thumb has shown that you can get a RISC which has the same code density as current CISCs. Of course, it's because…
> Unfortunately that's somewhat expected - regardless of implementation Yes, that's expected and no the GC implementation may be improved. See this: >> I remember a research paper about swap and GC, where the GC…
It isn't a toy for sure, but I doubt that it has good scalability stories when using SMP.. I'd love to be wrong given that even phones are multicores, so feel free to correct me.
'data oriented' doesn't mean 'just use SoA' it means use data structures which correspond to your data access pattern. Which is quite difficult to know in complex applications and which can change..
> hands are wrung that communication will become rife with error and misunderstanding because unlike the telegraph, the newfangled telephone leaves no written record! Well let's not forget that early phone communication…
> If you have a read-only variable and exclusive access to it, then you can rely on immutability as well. The problem is the "exclusive access to it", most language aren't Rust.. Some Ada-implementation has the problem…
Why do you say this? The post is quite clear that marking the memory region as NX fix the issue caused by speculative execution.
> the OS _writes_ unused memory pages to the swap file The OS write unused memory pages to the swap file by default. But the 'constant memory' design is usually done with locking in memory both the executable and memory…
Read about the AF447 Rio-Paris crash. Input stick averaging?? That's a huge design mistake which contributed to the crash and AFAIK is still here..
You're phrasing this as if using an IDE was always an advantage, but unfortunately this isn't always the case: -IDEs are more resources hungry, I remember when trying to use CLion on a big C++ codebase, until increasing…
> It's a difficult coordination problem. Well, it depends on the language: language which "capabilities" (both for the source code and for the building* ) could in theory really reduce a lot of the burden to identify…
One thing I noticed with your clever encoding is that you can avoid some nops: instead of having 2 15 bits instructions followed by two nops, you could have two 30 bits instructions, saving maybe a little decoding…
So a VLIW, interesting but usually compressed instructions are at most two-registers..
If the language is Java which puts the GC in nearly everything you're f..., other languages have GCs and nonGC'd data so you go to the wonderfull world of manually managed objects with its use-after-free..
> Do you really think current LLMs can implement a large application in C as securely as they can in e.g. Go? That's not my experience: I've seen an LLM generate a C++ use-after-free (1.5 month ago).
Congratulations your language is trying to solve an hard problem. But .. your language mostly hide when you're doing an 'inside' function call or an 'external' function call. I'm not sure I like this; 1) the latency of…
> The car industry is constantly innovating trying to prevent accidents and make them less damaging to occupants And at the same time, they make bigger and bigger cars which make more serious accidents for pedestrian,…
This part is very bad, 99% of the time if you overflow a 64 bit variable it is because you did the wrong computation, not because you need BigInts..
Not the only one though: I remember what happened when we 'invaded' Lybia: not one criticism in the French news anywhere, total censorship, even though our media had widely and correctly criticised the US for the Irak…
> In France, there has been some ban on advertising alcohol, cigarettes. So technically, it's possible but of course politician's corruption is a big issue..
> And, on the other end, C's warts, footguns and ancient quirks also matter less if you have an LLM plow through it. 'plow through it's?? An LLM can definitedly fall into these traps! Happened to me a few months ago, I…
> Human beings are rational animals as such Really? Explain the success of advertising, superstitions (including religion) then.