zeotroph

11 ms·

61.
by zeotroph 6y ago
Thank you for the explanations! > In Pijul, conflicts occur between changes (not between commits or states), and are solved by changes. So some channels contains the changeset (Fix, ..), and if adding that change to a channel creates a c
62.
by zeotroph 6y ago
I'd especially be interested in examples regarding multiple channels / branches (one development and several production branches), and then backporting a fix into older versions. In the conflict free use case I expect to just noti
63.
by zeotroph 6y ago
The author makes a distinction between the "drums and trumpets" / "cult of the badass" following and the actual academic discipline, so I think this field is doing fine. It has a similar problem as the "pop sci
64.
by zeotroph 6y ago
Ah yes, the eternal challenge of "Naming things". I just hope the command line tool gets a good 3-letter binary, "pijul record" is a bit awkward, maybe "pjl"? And distribute that by default as well, otherwise e
65.
by zeotroph 6y ago
Using "-march=x86-64-v3" is still a decision which has to be made at compile time. I wonder if the Apple appstore (at least watchOS/tvOS) approach of using bitcode as the one-time artifact and then turning that into concrete
66.
by zeotroph 6y ago
What is it with the simplified Gtk file dialogs? Whenever I use one I am instantly annoyed because I get the impression that some UI-concept from MacOS was badly copied, but is a mismatch for arguably more poweruser-centric Linux user base.
67.
by zeotroph 6y ago
I think this would be a per-thread state which you toggle, defaulting to "off". Then instead of checking and branching after each operation you flip it on/off depending on the type of arithmetic you want. The trick would be t
68.
by zeotroph 6y ago
Yes, quite annoying, and I've been bitten by that before, but you are supposed to check the return of each write(). And I think the motivation is to write platform-agnostic code by default. SIGPIPE is only available on Unix, so you hav
69.
by zeotroph 6y ago
So is Swift effectively adding a jo / jump on overflow instruction after each normal integer operation?
70.
by zeotroph 6y ago
Is there a reason to not add a new instruction to x86-64 which does interrupt the program on an integer operation overflow so no branching happens in the program? And can this instruction be made just as fast as the unchecked ones?
71.
by zeotroph 6y ago
That does not give you destructuring though, so to distinguish different variants of the same type you are left with a classic `if` inside the lambda. Also this has "language support" in the sense that it is (again) implemented vi
72.
by zeotroph 6y ago
> 5.1 / 5.3 -- "don't see any unique selling point" -- "there are a couple of forks" Doesn't that show that the actual users of Lua and the authors have drifted apart, and the former are not willing to
73.
by zeotroph 6y ago
LuaJIT development has effectively halted, and only supports Lua 5.1 (5.3 is current, 5.4 imminent). I get the feeling that Lua is slowly on its way out because the academic nature of it never meant it had to be more than "good enough&
74.
by zeotroph 6y ago
> cool it down If you blocked all incoming sunlight, how long would it take for the surface to cool to human-tolerable temperatures? Or more extreme, how long would it take to cool it down to the freezing point of CO2, then build some so
75.
by zeotroph 7y ago
> affect the way they think That is linguistic relativity / Sapir–Whorf hypothesis[1], and intuitively I think it does hold. On the most simple level, there are groups of people who do not have a name for a certain color and they si
76.
by zeotroph 7y ago
Interesting, thanks for finding that time capsule. With java applets! Maybe Jared will find the time to snail-mail me a hand quilted version of Substrate ;)
77.
by zeotroph 7y ago
The good old xscreensaver has quite a few which I really want(ed) as high quality prints, e.g. "Substrate[1]". I never got around to making it render into a file, and the screens were too far from 4K back then to make screen grabb
78.
by zeotroph 7y ago
Hence most likely . But when you are throwing around shared pointers left and right the program is usually already in the phase of "I don't know... just stick into a shared_ptr to be safe".
79.
by zeotroph 7y ago
Indeed, not linking this discussion to `std::move` which is half the reason to do the copying at the callsite is a big oversight. And not pointing out that a `foo(const std::shared_ptr<Widget>& widget);` should most likely become
80.
by zeotroph 7y ago
...but without a sentence or three about the reasons you think Rust is more suited for parallel workloads you are just giving Rust users a bad name again (see Rust Evangelism Strikeforce).
81.
by zeotroph 7y ago
> htop / 64 threads It sure is fun to see the entire top half of htop being taken up by individual CPU bars, but this is another program whose assumptions have been overtaken by the current silicon: At some point it is not that help
82.
by zeotroph 7y ago
If you can't visit but are interested in the topic and the beginning of the industrial revolution in general, the YouTube channel "Machine Thinking" has a video about this[1][2] and related topics. E.g. in another video he ex
83.
by zeotroph 7y ago
The MPEG group has tried to squeeze too much out of their h264 and h265 codecs, so other interested parties developed the totally free (with a patent-MAD clause) AV1 codec. I guess there will be no widely supported h266.
84.
by zeotroph 7y ago
This is about that ancient EBCDIC (IBM's ASCII "competitor") specific hack called trigraphs, which in modern compilers are opt-in anyhow: "To understand this, I have to admit one thing: I have to pass -trigraphs to a mod
85.
by zeotroph 7y ago
I was a long time Window Maker (not Windowmaker, the world's leading software for... something else) user for a long time as well, but finally jumped ship to boring old KDE. It finally acquired most of the essential window management f
86.
by zeotroph 7y ago
Isn't that stretching "social"? The money I hold is not tied to the yet unknown individual or group with with whom I will exchange it for goods or services, the person might not even be born yet.
87.
by zeotroph 7y ago
Looking at the absurdly long code required to make factorials work makes you wonder what conveniences we are all used to without really appreciating them. And which ones will future programmers take for granted but are too niche now - maybe
88.
by zeotroph 7y ago
The first argument (Long Time Lag Between Planning and Operation) is hard to argue against. To my surprise even in China it takes rather long. And in countries with a nuclear critical public is is a fantasy to think that going with "ju
89.
by zeotroph 7y ago
I actually did this with a debian sid a few years back. I guess I got attached to that trusty system which I moved from PC to PC for years and had a few too many customization. With my latest PC I went with a clean install though.
90.
by zeotroph 7y ago
Or just pair it with iCloud and "cloud heal" the corrupted local data. Then mark the sector as bad and enjoy longer lifetime for the device.

More ›