HNHacker News
TopNewBestAskShowJobs

zeotroph

508 karma · joined August 2, 2012

submissionscomments
zeotroph··on Pijul – The Mathematically Sound Version Control System Written in Rust
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 notify Pijul that this fix now belongs to not only to the dev-master, but also and rel.22, rel.21 etc. - in contrast to switching to every release branch and cherry-picking it with git.

How is the workflow if this applies cleanly to rel.22, but not rel.21 anymore? What if the same conflict happens in rel.20, rel.19 and rel.18?

If I (in git speak) "--amend" the original fix, could I automatically include this in the release branches?

What if the conflict resolution changes every single line, but I still want to record that, "Yes, this fix is also in rel.17, even though it does not look like it".

zeotroph··on Why Military History?
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" fluff resulting from badly copied university press releases which were inaccurate in the first place. The enthusiasts which then pick up from there are just a lot more, because to them war is just too interesting and emotionally satisfying. This then has an effect on the society as a whole, something for maybe military sociologists to research? But nothing the field itself can be blamed for, if anything without it the situation might be a lot worse.

I found this quote fitting: "[..] military historians study conflict in the same way that doctors study disease; no one assumes that doctors like diseases, quite the opposite."

Edit: Also thought provoking and reflecting on the fascination of war, in the comments the user TomBombadil quotes musings of a sentient machine from Iain M. Banks Culture novel Excession:

"It was a warship, after all. It was built, designed to glory in destruction, when it was considered appropriate. It found, as it was rightly and properly supposed to, an awful beauty in both the weaponry of war and the violence and devastation which that weaponry was capable of inflicting, and yet it knew that attractiveness stemmed from a kind of insecurity, a sort of childishness. It could see that—by some criteria—a warship, just by the perfectly articulated purity of its purpose, was the most beautiful single artifact the Culture was capable of producing, and at the same time understand the paucity of moral vision such a judgment implied. To fully appreciate the beauty of the weapon was to admit to a kind of shortsightedness close to blindness, to confess to a sort of stupidity. The weapon was not itself; nothing was solely itself. The weapon, like anything else, could only finally be judged by the effect it had on others, by the consequences it produced in some outside context, by its place in the rest of the universe. By this measure the love, or just the appreciation, of weapons was a kind of tragedy."

zeotroph··on Pijul: Towards 1.0
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 everyone defines their own mutually incompatible aliases.

Oh and provide an official way to pronounce it!

zeotroph··on LLVM Clang 12 Merges Support For x86_64 Microarchitecture Levels
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 instructions later would be possible for an entire Linux distribution (Gentoo II). The Mill CPU team wants to use something like that OS-wide to hide/emulate entire missing functionality on lower-tier CPU models.

Or the other possibility of compiling for all architecture and then selecting this or that function depending on what the current CPU is, or even hotpatching if the security model allows it. I remember either gcc or glibc having some support for one of these.

zeotroph··on Gimp 2.99.2 – GTK3 user interface toolkit
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. Once I discovered that Ctrl-L can bring up the url/file path I found it at least usable, but still not pleasant.

Am I using it wrong? Can I change the default system wide somehow? Is there a design document which can finally convince me that this is generally a good idea, just not for me?

Also, some Gtk apps had/have tearable menus, a shame these went out of fashion. Is there something fundamentally wrong with that, too, or can this be enable globally for Gtk, and maybe even Qt apps?

zeotroph··on How expensive is integer-overflow trapping in C++?
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 to get to the minimal number of toggles and not do the "safe" thing and set it to on/off for each operation.
zeotroph··on How expensive is integer-overflow trapping in C++?
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 have to explicitly opt-in.

zeotroph··on How expensive is integer-overflow trapping in C++?
So is Swift effectively adding a jo / jump on overflow instruction after each normal integer operation?
zeotroph··on How expensive is integer-overflow trapping in C++?
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?
zeotroph··on Functional Language Features: Iterators and Closures
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 via template meta programming, i.e. the compile time is impacted quite heavily.

See "std::visit is everything wrong with modern C++": https://bitbashing.io/std-visit.html

This standards proposal would add proper match (named, of course, inspect) support: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p009...

zeotroph··on Gravity: An embeddable programming language without any external dependencies
> 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 commit to a hard fork or taking over development? Or both sides could come together to form a much-beloved committee. The curse of "good enough".

> quirks / fastest

I think you misunderstood: Yes, it is fast even without LuaJIT, and super easy to embed and integrate - which is why this slow fading away into the embedded only realm would be quite a shame.

But it is also "quirky", and adding some (optional, possibly slower) syntax sugar over it could make it more appealing. Sure, Lua-fans will argue that tables are better than anything, but for those who just want to transfer existing language knowledge are hard to convince, and setmetatable makes everything even weirder.

zeotroph··on Gravity: An embeddable programming language without any external dependencies
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" outside it's core strengths.

I think they should have kept a super-light "classic" Lua where ~= still means !=, there are only tables, and all the other quirks (but also speed). Then add official, optional support for classes, lists, dicts, sets. This probably can all be built on top of setmetatable, so be pure lua, but at least it comes as one consistent standard library and not in the form of a fractured ecosystem.

All the mentioned compiles-to-lua Projects tried something similar, but never gained significant traction, probably because of the lack of an official blessing.

zeotroph··on How Long Was Venus Habitable?
> 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 sort of maglev launch system and lob solid CO2 to... Mars maybe, that planet could use more atmosphere.

And how much stuff would you need to launch to spin up Venus? Months long nights are not fun. Can you launch stuff to yield more spin, then have it sling around Earth or Mercury, and then have it hit Venus again, resulting in more spin up, i.e. getting twice the rotational acceleration from a launch?

zeotroph··on Mongolia to restore traditional alphabet
> 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 simply can not distinguish them from a related color which may be very obvious to us. And in fiction there is of course Newspeak from 1984.

So yes, I think killing off all other languages apart from English / Mandarin / Esperanto is a bad way to go, I'd rather go for early bi- or triligualism.

1: https://en.wikipedia.org/wiki/Linguistic_relativity

zeotroph··on Show HN: Write generative fine art in Rust
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 ;)
zeotroph··on Show HN: Write generative fine art in Rust
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 grabbing useful. Plus I was too afraid to bug jwz himself :).

1: Crystalline lines grow on a computational substrate. A simple perpendicular growth rule creates intricate city-like structures.

https://duckduckgo.com/?q=xscreensaver+substrate&iax=images&...

zeotroph··on Pass-by-value vs. pass-by-reference-to-const in C++
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".
zeotroph··on Pass-by-value vs. pass-by-reference-to-const in C++
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 a plain `foo(const Widget& widget);` with a `*widget_ptr` dereference at the callsite.

zeotroph··on 64 Core Threadripper 3990X CPU Review
...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).
zeotroph··on 64 Core Threadripper 3990X CPU Review
> 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 helpful anymore and makes looking at the processes themselves harder.

Sadly the development of htop seems to have stalled, patches/PRs for that and many other issues remain unmerged and unanswered.

zeotroph··on The Museum of Arts and Crafts in Paris is a trove of cunning inventions
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 explains how to get a perfectly plan surface from scratch: Rubbing two somewhat flat surfaces together until they are smooth enough does not work, you might end up with a subtly concave/convex combination. But do that with three surfaces and the result can only be perfectly flat, though it will take quite some time.

[1]: https://www.youtube.com/watch?v=waEqmfH7z2Y - Paris' Temple To Science - Part I

[2]: https://www.youtube.com/watch?v=djB9oK6pkbA - The 1751 Machine that Made Everything

zeotroph··on FFmpeg libav tutorial – from basic to transmuxing, transcoding and more
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.
zeotroph··on C, what the fuck??!
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 modern version of gcc before this actually works. "

C++17 actually removed support for these.

zeotroph··on Comparison of X Window Managers
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 features of WMaker, such as Meta-R/L-Mouse to move or resize the window by clicking anywhere into it or shading windows.

However I still miss selecting multiple windows with a rubber band and then moving them to a different virtual desktop together, or the dock apps. I still can't find a proper widget which displays the network activity or something like wmforkplop to show the general system load.

zeotroph··on The Invention of Money
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.
zeotroph··on Cobol Still Powers the Global Economy
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 async/await or the borrow checker concepts, or is programming mostly "done"?

http://rosettacode.org/wiki/Factorial#COBOL

or also http://rosettacode.org/wiki/FizzBuzz#COBOL

Is there a code example where Cobol shines in comparison to, say, Python?

zeotroph··on Why nuclear energy is not the answer to solve climate change
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 "just the facts" for a year or two will sway enough opponents, and then go all-in with nuclear (as would be the case in an Ideal World).

The Cost argument [$151 (112 to 189)/MWh vs $43 (29 to 56)/MWh / $41 (36 to 46)/MWh for wind / solar PV] is also convincing, assuming the numbers are correct. If it is really a factor of > 2 then this would even be enough to bridge shortfalls of renewable energy due to lack of wind or sun, i.e. building rather inefficient (40%?) long term thermal or battery storage.

Weapons Proliferation Risk, Meltdown Risk, Mining Lung Cancer Risk, Waste Risk are tolerable when the alternative is a catastrophically warmer planet.

The "Carbon-Equivalent Emissions and Air Pollution" point counts the time it takes for a nuclear plant to come online?

So ideally going full nuclear would have started 10 years or so ago, but in the muddy real world this pure nuclear fantasy does not work. Time to bury it and stop wasting time and energy fighting for it, just get solar panels and build a wind farm already.

zeotroph··on i386 architecture will be dropped starting with Ubuntu 19.10
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.

zeotroph··on What’s New in Apple Filesystems [pdf]
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.
zeotroph··on What’s New in Apple Filesystems [pdf]
SLES (Suse) is going all in with btrfs, it is no ZFS but better than the equivalent RH solution of offering an LVM or other blocklevel layer of checksums.

Not to mention all the ..BSD or ZfsOnLinux based storage solutions.

I am not denying that APFS is a good FS, but not even having the option of checksums given its contemporaries was clearly a political and financial decision to benefit Apple and not its users. Pointing to an opaque mix of raid (and indeed, raid10 is not even enough), super-reliable SSDs and the full stack control doesn't make the lack of checksums any better.

← PreviousPage 3 of 6Next →