HackerLangs
トップ新着トレンドコメント過去質問紹介求人

sixthDot

no profile record

投稿

Has GitLab Felt into the Enshittification?

gitlab.com
4 ポイント·投稿者 sixthDot·3 か月前·1 コメント

South Atlantic Anomaly

en.wikipedia.org
3 ポイント·投稿者 sixthDot·7 か月前·2 コメント

What is the sense of agency and why does it matter?

frontiersin.org
3 ポイント·投稿者 sixthDot·7 か月前·2 コメント

Git for Music – Using Version Control for Music Production (2023)

grechin.org
81 ポイント·投稿者 sixthDot·10 か月前·57 コメント

コメント

sixthDot
·2 か月前·議論
That is funny, somewhat works but there's a bias toward the victorian era. https://halupedia.com/the-x128-cpu-architecture. Otherwise I feel sorry for the creator's tokens.
sixthDot
·3 か月前·議論
https://github.com/vlang/v
sixthDot
·3 か月前·議論
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.
sixthDot
·3 か月前·議論
When a team is so much into its own littke bubble, it does not realize anymore the shit they are doing
sixthDot
·4 か月前·議論
This work on system of weight:

> 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 ?
sixthDot
·4 か月前·議論
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.
sixthDot
·5 か月前·議論
> When a wealthy artist bought the island [...]

Not an artist. British businessman and Winter Olympian. See https://en.wikipedia.org/wiki/Keith_Schellenberg.
sixthDot
·6 か月前·議論
Also the C API is a bit the poor child. Plenty of useful options (or even opt passes !) are not available.
sixthDot
·6 か月前·議論
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.
sixthDot
·6 か月前·議論
Another one bites the dust
sixthDot
·6 か月前·議論
The bigest anoyance nowadays (in the EU at least) is rather the cookie policy agreement. "View the list of our 258 partners", etc.
sixthDot
·7 か月前·議論
That remind me of The Ax [0]

[0] https://www.imdb.com/title/tt0422015/
sixthDot
·7 か月前·議論
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.
sixthDot
·7 か月前·議論
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.
sixthDot
·7 か月前·議論
I've wrote a lot of `xor al,al` in my youth.
sixthDot
·7 か月前·議論
related researches

- https://pmc.ncbi.nlm.nih.gov/articles/PMC7264682/

- https://psycnet.apa.org/record/2014-51129-001
sixthDot
·9 か月前·議論
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");
    }
sixthDot
·9 か月前·議論
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...
sixthDot
·9 か月前·議論
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
sixthDot
·9 か月前·議論
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".