I think Pentium will still be supported. i486 refers to very old 32 bits CPU (80486). The article is not clear but by default I tend to think that i586 and i686 will still be supported.
> For each option and criterion, you assign a rating (0–10). Each criterion has an importance weight (1–5 stars). Decidit multiplies rating × weight and sums the values – the option with the highest score wins.
Is this really made for people who lack self-discipline or maybe just a website made for a portfolio ?
So eventually that would be used to poison communications, just in case of Iranian would use that old channel, which then would also mean that it's been cracked a while ago.
That's absurd but I like this kind of little stories.
If only that was only about emitting byte code in a file then calling the linker... you also have the problem of debug information, optimizers passes, the amount of tests required to prove the output byte code is valid, etc.
How this was discovered is incredible. An amator satelite was lauched. operators collected data. At some point they had the idea to plot them. That gave a big stain in the south atlantic.
Not into ZIG but for some reasons I monitor new issues that pop in the bug tracker of "new" / "raisins" languages. ZIG has clearly reached the next level, let's say if you compare the issues two years ago (lot of comptime/type system things) VS now.
I cannot reply on the blog but to answer the author about other languages, here is the D version, using a single template:
auto ref T max(T)(auto ref T u, auto ref T v) => u > v ? u : v;
void main()
{
int a = 1;
int b = 0;
int x;
static assert(__traits(compiles, &max(a,b) == &a),
"should have selected the lvalue version");
static assert(__traits(compiles, x = max(1,0)),
"should have selected the rvalue version");
static assert(__traits(compiles, x = max(a,0)),
"should have selected the rvalue version");
static assert(__traits(compiles, x = max(1,0)),
"should have selected the rvalue version");
}
an hygienic way to handle that is often "assert", can be a macro or a built in statement.The main problem with assertions is the side-effects. The verification must be pure...
Bound checks are usually conditionally compiled. That's more a kind of "contract" you'll verify during testing. In the end the software actually used will not check anything.
#ifdef CONTRACTS
if (i >= array_length) panic("index out of bounds")
#endif
What is really mind blowing is that, if understood correctly, bots would be used to check the availability of a product, that sounds so a "hacky" method, like "seriously people are doing that in 2025".