HNHacker News
TopNewBestAskShowJobs

BlackFingolfin

624 karma · joined February 21, 2014

submissionscomments
BlackFingolfin··on Apple App Store Principles and Practices
Five years? Citation needed? Also, do "people" other than nerds really complain about this?
BlackFingolfin··on Show HN: ZFS Implementation in Python
And reference counting is a form of GC
BlackFingolfin··on GNU Awk 5.0
Actually, Chet Ramey maintains GNU Bash, and Jim Meyering maintains GNU Grep. As far as I can tell, Arnold Robbins "just" maintains GNU awk. Don't get me wrong, I don't want to trivialize this at all, just correct the record.
BlackFingolfin··on Measuring the overhead of WebAssembly using libsodium
They do not translate to a fully native experience. At least on macOS, they stick out like a sore thumb.

And honestly, I think in the end, virtually any such tool will, because to really get the fine nuances and details right, the programmer simply must be aware of them, no automation will do this for you. On macOS, even Apple's own attempt on this ("Marzipan", which allows to generate iOS and macOS apps from a single codebase) suffers from this, although admittedly one may hope that at least in principle this framework could eventually really provide a 100% native experience, provided the people using it are aware if the idiosyncrasies of macOS (and conversely, iOS).

And that's for a tool trying to provide a common API for two UIs, with all three products developed by the same company. It gets much tougher once you also try to get Linux and Windows supported...

I've tried many frameworks that promised to this in the past 20 years, both as developer and user. All overpromised and underdelivered. Qt and wxWindows included. I actually prefer Atom (electron based) over any wxWindows or Qt software I ever tried - though this probably is primarily because somebody tried hard to polish its UI. While (I am guessing) most people who are content with what Qt and Wx deliver won't even notice the need to polish (those who do care eventually realize it is hopeless, and move on).

BlackFingolfin··on A Julia Interpreter and Debugger
Yes, the language was (intentionally) stabilized with 1.0. So version 1.1 (the current one) is fully compatible with that, and this will remain so for the whole 1.x series. And I expect that even 2.x won't be as bad (if at all) as the major changes that were made during the early evolution of the language.
BlackFingolfin··on So Long, Macbook. Hello Again, Linux
Interesting, I don't know a single program on OS X which supports Ctrl+C/V for copy&paste but does not support Command+C/V (indeed, I know only a tiny set of programs that support Ctrl-C/V at all, mostly cross platform software that is badly adapted to OS X).

Out of curiosity, could you name an example or two?

BlackFingolfin··on 50 CVEs in 50 Days: Fuzzing Adobe Reader
Just because something is XML doesn't mean it is "well-defined".
BlackFingolfin··on Proof That iOS Still Hasn’t Gotten Undo Right
Out of curiosity (I haven't used Android in quite some time, and even then only cursory): does Android (resp. Google) have a good solution for uniform Undo in phone apps? How does it work?
BlackFingolfin··on Proof That iOS Still Hasn’t Gotten Undo Right
But that usually only helps for text editing (it's even in the article ;-)
BlackFingolfin··on Proof That iOS Still Hasn’t Gotten Undo Right
That's where a menu bar shines: it allows you to browse for and discover new functions. Sure, most people still won't use most of those. But at least you have a realistic chance of finding them.

Of course this is not unique to menu bars, they just happen to be one established way to squeeze a lot of functions into a tight places. For a touch interface, we may want different ways to do that; but I'd argue that it's still crucial to provide non-hidden, discoverable ways to access all functions of your app.

BlackFingolfin··on Proof That iOS Still Hasn’t Gotten Undo Right
I'd say there is nothing bad about having additional shortcuts for often used functions, as long as the standard ones still work (and of course as long as there is a standard...)
BlackFingolfin··on Proof That iOS Still Hasn’t Gotten Undo Right
Actually, he never says that he does not think iOS needs a menu bar. He just says "I’m not arguing that iOS should have a Mac-style menu bar." which makes sense, because doing so would distract from the core of his criticism -- adding a menu bar is only one possible way to address it. And there is a footnote on that sentence, too, which suggests that in a sense, Apple is already having a (bad) fake menu in their iWorks apps...
BlackFingolfin··on Questions
PDFs might still work - but will the storage devices they are on? There are good reasons to doubt this: tapes, CDs and DVDs age and degrade over time; plus devices to read them only last so long, and may not be produced anymore at some point. Classic "spinning" hard drives degrade, too; and even ignoring this, will there still be conputers supporting, say, SATA, in 50 years?

And then there is a trend to switch to onboard soldered flash in new devices which adds further problems.

Not saying this is impossible to overcome, but "PDF might still work" is at best solving a part of the problem, for only a part of all data (PDF is great - but only for some types of data) one might want to preserve.

BlackFingolfin··on Future Directions for Optimizing Compilers
Am I missing something, or is their example at the start of section 3 (bottom of page 7) plain wrong? If x is an uint32_t, then ((x << 31) >> 31) + 1 returns either 1 or 2; while the "optimized" version ~x&1 reutrns 1 or 0 (which matches the semantics they describe, while the initial code does not).
BlackFingolfin··on A Retiree Discovers an Elusive Math Proof (2017)
This is from 2017, previous discussion here: https://news.ycombinator.com/item?id=13977554
BlackFingolfin··on iTerm2 has a new drawing engine that uses Metal 2
Things I love in iTerm include the following: * cmd-click on URLs or filenames to open them in my browser resp. editor -- even recognizes "FILENAME:LINE" to jump to the right line in my editor, which is super useful for errors printed by a compiler * changing the theme when using SSH and/or root, so I don't accidentally issue commands on the wrong machine or as root * split views * lots of other, often "small" features, which I can't think of right now but which I usually notice quickly if forced to use Terminal.app
BlackFingolfin··on The libkern C++ Runtime
Plenty: classes (including constructors/destructors, virtual methods, etc.), operator overloading, patterns like RAII, ...
BlackFingolfin··on GCC 8.1 Released
I'd love to see that reference, as I've not yet seen an example where this was true in practicd, but know several examples where it is definitely false (e.g. we use a modification of the Julia GC which uses consevative stack scanning to allow interop with another system, and it seems to perform very well).
BlackFingolfin··on Linux 4.17-rc1: “We removed more lines than we added”
The problem is that often enough it is not "known working good code", because nobody has been compiling and/or running and/or stress testing this code for a long time. Given that constant churn in the kernel, refactoring of APIs etc., it's quite likely that subtle (or not so subtle) breakages creep into that code over time. (Even if people who perform this refactoring try to update these archs, too; or perhaps I should say: "especially if", because usually you can't test them, after all).

Leaving it in gives the wrong impression that this is "known working good code", which is one reason to remove it. Another is that removing them makes it easier to be agile and refactor things, because you don't have to worry about these archs anymore.

BlackFingolfin··on Jupyter, Mathematica, and the Future of the Research Paper
I am not sure that there are/were "high profile failures", but serious bugs for sure, not just in Mathmetica but also in the calculators you mention; ser eg here: https://mathoverflow.net/questions/11517/computer-algebra-er...

Now being open source does not prevent such errors. What I think is far more important here is open issue tracking: companies like Wolfram may not be exactly eager to let you know that there are serious bugs in their products (and what they are) unless they must. Being able to fix the bug yourself can of course be a real perk for some user's, but realistically, it's out if question for most.

BlackFingolfin··on Internal Facebook posts of employees discussing leaked memo
Innovated? More like blatantly lied and committed fraud, I'd say
BlackFingolfin··on 100 days with Rust: a series of brick walls
Reference counting can also lead to big cascades of objects being freed, which can make it impractical in realtime context as well. This makes RC useless for systems which have hard constraints here (e.g. automotive).

And of course, once you are multi-threaded, you can more or less forget about "predictable and deterministic" with RC, too.

In contrast, there are real time capable garbage collectors.

BlackFingolfin··on Project Gutenberg blocks access from Germany
You mirror sage, but your site still links to sage.org, which seems to be defunct AFAICT, current is http://www.sagemath.org
BlackFingolfin··on Project Gutenberg blocks access from Germany
It also appears for the URL they give in the FAQ for donations :-(
BlackFingolfin··on DEC64: Decimal Floating Point
Re 1: it is true that there is a single paragraph "discussing" rounding in https://github.com/douglascrockford/DEC64/blob/master/dec64.... -- which is not much. If there is more, I did not find it, and would genuinely appreciate a pointer! In the meantime, though, alternative rounding methods are missing, and those can be quite important for both scientific and business computations. I guess they could be added. But, a lot of things "could be done". Fact is, they were done so far. In so far, DEC64 is mostly a proposal for people to sit down and work out an actual standard. Perhaps this will happen one day, but it seems so far not so many people are convinced it's worth investing efforts into that (I am also not sure if the author is interested in feedback and collaboration? I see no indication for that anywhere)

Re 2: these are at best toy implementations, at worst dangerous (in the sense that they may provide wildly inaccurate results, due to convergence

Re 3: agreed. Though there is still a gargantuan number of values which have 2 or more representations, and that makes all kinds of comparisons more complicated. Dealing with that efficiently in SW is difficult, and more so in HW. It might be worth it if the advantages outweigh it, but at least I personally don't see it.

Re 4: if it can be "undoubtedly improved with effort", why hasn't it been done in several years? Sure, it may be possible, but I will keep my doubts for the time being :-)

I agree with you on 5, 6 and 7.

BlackFingolfin··on DEC64: Decimal Floating Point
I see no contradiction here, as long as the period is >= 16...
BlackFingolfin··on Feature comparison of ack, ag, git-grep, GNU grep and ripgrep
Unfortunately that page does not say when the comparison was made, and which version of each tool was tested. Also, which "grep" is that? I assume GNU grep? There are others, though...

All in all, it'd still be nice to have a more comprehensive performance comparison page, which gets regularly updated. Bonus points if it shows how speed changes over time, similar to http://speed.pypy.org (the code for that is available, by the way).

Wishful thinking, I know, but hey, who knows... :-)

BlackFingolfin··on High-Level Problems with Git and How to Fix Them
And it has been for some time (years, I think)
BlackFingolfin··on How I implemented my own crypto
While I actually mostly agree with you, I feel I need to point this out... You write: > I will point out that a network protocol is not designed to be error-proof in an intentionally antagonistic environment, which is a difficulty unique to cryptographic software.

But that's actually not true, at least not anymore. People attack protocols on the internet all the time, and it's a difficult task to harden them against that.

That said, it doesn't really take aware from your point, I think; but rather confirms it: Think twice before rolling your own network protocols (at least if they are meant to be used in large scale on the open internet), be aware of all the complicated pitfalls.

BlackFingolfin··on PyPy v5.8 released
The benchmark showing a factor 100x compares a pure python implementation of "pidigits" running in PyPy3 vs one that uses GMP (via gmpy2) in python. I am actually impressed it's only a factor 100. And with progress made by cffi, I'd hopeful that a GMP-using PyPy version could be written rhat matches the speed of the code using gmpy2.

The next benchmark "only" runs 6x slower in PyPy ; still bad, but that paints quite a differen picture.

← PreviousPage 4 of 6Next →