HNHacker News
TopNewBestAskShowJobs

msbarnett

12,236 karma · joined April 12, 2010

submissionscomments
msbarnett··on Ligatures in programming fonts: hell no (2019)
> Humanity advances when it can hide complexity. Tools help with that. To argue against tooling because it makes you dependent on the tooling is like telling the construction worker to put away the jackhammer and pick up the pickaxe.

Calling replacing ">=" with a ligature for "≥" "hiding complexity" strikes me as more than a bit of a stretch. They're two different visual presentations of the same thing, neither more or less complex in-and-of-themselves.

The ligature has some external complexity, though, in that for certain things I have to remember that that's "really" 2 characters in the file, and backspacing directly in front of ≥ will net me > instead of deleting the entire thing.

So if anything, ligatures are introducing a small bit of complexity that otherwise isn't there. Any relation to Socrates' quote seems forced.

msbarnett··on Why Not Rust? (2020)
> Saying that Rust can't do it now because the C standard doesn't sufficiently specify bitfield semantics isn't a good answer.

I don't think anybody is saying that? Particularly given that Rust is working on precisely that.

The argument is merely that not currently having a good bitfield solution is hardly a showstopper for systems development, given that C is already far more popular in that area than Ada despite its deeply deficient version of bitfields which leads to them being banned in a great many codebases.

msbarnett··on Why Not Rust? (2020)
> Hint: nobody uses "new" in C++ anymore

"nobody"

    ~/chromium (main)$ rg --stats -t cpp "[=\(][ ]*new "    
    ...
   
    17639 matches
    17536 matched lines
    7162 files contained matches
    96561 files searched
    1539692 bytes printed
    763109193 bytes searched
    1.119265 seconds spent searching
    1.428974 seconds
That's surely a lot of non-usage. Maybe it's just Chrome, though?

    ~/llvm-project (main)$ rg --stats -t cpp "[=\(][ ]*new "
    ...
    7447 matches
    7394 matched lines
    2245 files contained matches
    35148 files searched
    541938 bytes printed
    385115019 bytes searched
    0.425689 seconds spent searching
    0.485431 seconds
Hmmmm.
msbarnett··on Why Not Rust? (2020)
> I've used Ada extensively in this area, and I just don't see what Rust has to offer that Ada didn't already address.

Memory safety guarantees that don't go out the window if you ever need to free a dynamic allocation, for starters.

Bitfields are an underspecified minefield in C, I don't think it's as clear of a loss as you're making it sound.

msbarnett··on I can read C++ and Java but I can’t read Smalltalk (2000) [pdf]
Because those are names the caller decided upon, so they can just as easily misinform the reader as correctly educate them. The caller could have mistyped the call as

     t.rotate(around, rotateBy)
and the error in the effect might seem very mysterious indeed. The beauty of keyword args is that the mapping of caller's name to function argument name is explicit, and therefore reads correctly or incorrectly immediately at the callsite

     t rotateBy: point around:degrees
is obviously an error, without sending the reader to look up the definition.

Compiler-enforced clarity rather than relying on every individual piece of client code to always name things well & never make a mistake.

msbarnett··on Tuxedo Stellaris: A Powerful Linux Laptop
> I wish the touchpad weren’t too large though or improve the palm detection. If macOS have the feature, then it is not on par as other trackpad manufacture which their palm detection/rejection is superior to Apple's.

Man, this is just not my experience at all. Apple's palm rejection feels best-in-class to me -- I literally never have any issue with it on a MacBook Pro (I never even thought about it for years, using Macs exclusively), and I've never not had an issue with it on any Windows laptop I've tried (Lenovo Thinkpads, Asus, Dell, Alienware). All of the WinTel offerings seem to rely on a bog-standard Synaptics or Microsoft driver with mediocre-at-best palm rejection.

Maybe it just works better for some people than others?

msbarnett··on Tell HN: Azure is having a major outage
Probably their most important consumer and b2b off the shelf cloud service, yeah, but when people talk about Azure I presume they mean more like, the compute, database, hosted kubernetes etc products. Most of which people run Linux on and tend(?) not to integrate with ActiveDirectory, broadly.
msbarnett··on Tell HN: Azure is having a major outage
Yeah it's only a bit like that, in that AAD does identity stuff. It's way way way less critical than IAM though.
msbarnett··on Tell HN: Azure is having a major outage
The only thing that’s down is Azure Active Directory. If you’re not using that product, everything is working fine.

This is more like Amazon’s IAM product being down than AWS as a whole.

msbarnett··on Go Replaces Interface{} with 'Any'
My observation is merely that every additive change breaks the ability of new code to work with old compilers, and that it would be really, really weird to have a system in which you bump a major version because old code continues to work, but bump a minor when it would break or something.

If you "aren't proposing" that, then all you seem to be saying is "I think sometimes major versions should signal that they break compatibility with old code and sometimes they should signal that they maintain compatibility with old code because of some never-promised loss of reverse compatibility with new code on old compilers" which ... sounds uninteresting, unreliable, and frankly terrible from the standpoint of anyone who wants automated tooling to be able to make decisions based on signals in the version numbers (which, while not 100% reliable, is still a huge win over the old days of "versions can just be whatever, man" imo)

msbarnett··on Go Replaces Interface{} with 'Any'
> These replies are incredibly and bizarrely dogmatic. I never knew it'd be so hard to have a discussion about semver without people just going "semver is semver" as if that means something.

You seem to have misunderstood. We're not pointing out that "semver is semver", we're pointing out that semver as defined with respect to compilers, which is to say, the ability of existing code to run with a new version of the compiler, and what you "perceive to be a limitation in semver" are fundamentally in tension.

The only non-perf changes that would be allowed as non-breaking changes if we addressed what you perceive to be limitations in semver are precisely those changes which would be breaking in semver-as-it-exists, and those permitted in semver-as-it-exists are precisely those which you perceive as limitations.

Happy to discuss semver, but fundamentally the thing here is that what would address your perceived limitations is... the literal opposite of semver. Which is fine! But something not being its literal exact opposite isn't exactly a flaw in the thing itself; you simply want something else entirely.

msbarnett··on Go Replaces Interface{} with 'Any'
SemVer is about breaking changes to existing code when you upgrade compilers, not about making future code backwards compatible to older compilers.

Every additive language change would be a breaking change in this ReverseSemVer you’re imagining.

msbarnett··on Analogue Pocket Hate Story
> Endrift being unhappy with $10k-20k due to their current situation & cost of living is entirely different from the person I responded to claiming that "Analogue was hoping for a screaming deal on this software"

> Analogue wasn't looking for SV contractors, they were looking for contractors in any location (in this case, a remote contractor). That Endrift happened to be located in SV changes their specific appetite for the offer, but doesn't make the offer unreasonable or disrespectful, either.

I wouldn't expect to get cycle-accurate FPGA emulation work (by one of a handful of experienced experts in simulating the original hardware!) done for ~$30 USD an hour from basically anywhere on the planet. Contracting out of Eastern Europe or South America you'd end up paying about that much for a mostly incompetent web dev -- for what Analogue wanted, there's no real way to describe it other than "hoping to hit a homerun on an absolutely insanely unreasonable offer".

This is deeply specialist knowledge that Analogue is looking for.

msbarnett··on Analogue Pocket Hate Story
Endrift lived in SV at the time, as stated in TFA - she would obviously base her rate expectations on her location, not on wherever Analogue happens to be legally incorporated.
msbarnett··on Rust support in the Linux kernel
The rubric for decision making in Linux kernel driver development is not "what HN user b20000 thinks they need", as far as I am aware.
msbarnett··on Rust support in the Linux kernel
> not everyone is working on a device that needs to be secure.

And those drivers can continue to be written in C. Rust is merely an option.

msbarnett··on Do we really need undefined behavior?
loop optimization is intimately tied to being able to assume the index doesn't wrap and exit the array, no?

GCC says:

> -faggressive-loop-optimizations This option tells the loop optimizer to use language constraints to derive bounds for the number of iterations of a loop. This assumes that loop code does not invoke undefined behavior by for example causing signed integer overflows or out-of-bound array accesses. The bounds for the number of iterations of a loop are used to guide loop unrolling and peeling and loop exit test optimizations.

msbarnett··on Do we really need undefined behavior?
Its not about the size, its about the signedness being presumably not natural for an index, and the potential for having very inconvenient consequences for performance on modern CPU architectures if you were not able to assume the index never goes negative due to a wrap.

Basically, to get decent perf out of C loops, arithmetic overflow has to be left as UB for int. If the standard index variable type had historically been unsigned and defined to terminate on overflow or something, you could make wrap-on-overflow standard for int without killing the performance of hot inner loops.

msbarnett··on Who is the most accurate world chess champion?
> It would be hard to simulate Kasparov as if he were taught chess in Capablanca’s time (maybe not impossible and a fascinating project, I just don’t see how you’d do it).

I don't think they were suggesting that's the result they wanted - if you could somehow magically reanimate Capablanca in real life and pit him against peak Kasparov, he might lose badly.

A neural net having the same outcome is essentially what's being asked for. Kasparov raised on Capablanca's era chess or vice versa would be unrecognizably different players, and I don't think anybody expects an AI to simulate their soul.

msbarnett··on “Risc V greatly underperforms”
He literally addressed this, albeit obliquely, in the message

> I have heard that Risc V proponents say that these problems are known and could be fixed by having the hardware fuse dependent instructions. Perhaps that could lessen the instruction set shortcomings, but will it fix the 3x worse performance for cases like the one outlined here?

Macro-fusion can to some extent offset the weak instruction set, but you're never going to get a multiple integer multiplier speedup out of it given the complexity of inter-op architectural state changes that have to be preserved, and instruction boundary limitations involved; it's never going to offset a 3x blowup in instruction count in a tight loop.

msbarnett··on The American prison system’s war on reading
> Not saying we can't use alternative solutions, but your comment doesn't really support further discussion

Sure it does. We can only discuss solutions if we’re willing to accurately describe ALL of the causes of the problem.

The article we’re discussing is entirely about how the “contraband” claim appears to be a flimsy excuse that both doesn’t impact the primary source of contraband (the guards), and obviously has nothing whatsoever to do with issues like:

> With e-books, the situation is even worse, as companies like Global Tel Link supply supposedly “free” tablets which actually charge their users by the minute to read. Even public-domain classics, available on Project Gutenberg, are only available at a price under these systems—and prisons, in turn, receive a 5% commission on every charge.

“Books can smuggle contraband” has no explanatory power wrt marked up access to free ebooks. Profit motive does.

It’s you, rather than the person you’re responding to, who seems to be shutting down discussion of solutions by trying to rule discussion of private for-profit prisons making profit-optimal decisions that may be net-worse for society somehow out-of-bounds.

msbarnett··on List of 8000 security vulnerabilities in 1200 Wi-Fi routers
Asus' routers essentially run a skinned version of Tomato with some Asus-specific enhancements. The stock firmware is open source and there's a popular enhanced fork of it, asuswrt-merlin, that's a drop in replacement.
msbarnett··on List of 8000 security vulnerabilities in 1200 Wi-Fi routers
Yeah, that's an asuswrt-based router
msbarnett··on Microsoft and the Metaverse
> The "Metaverse" is not necessarily anything more magical than HTTP serving 3d models rendered on the screens strapped to our faces (rather than 2d documents rendered on the screens strapped to our desk)

But that's just it, isn't it? GP said:

> > That feeling comes back to me as a kind of "Build a robot" moment in cases like this. "In our virtual reality metaverse people will be able to attend concerts with one another and save the tickets as NFTs!" Okay, but what you have is a screen that you can strap to your face and is nothing like a virtual reality metaverse and you have no idea how to get there.

Why would most people want "HTTP serving 3d models to a screen strapped on their face" to take the place of "attending concerts with one another"?

Without significant, ground-breaking advancements in freedom of movement/input and feedback/presence beyond the screen & headphones strapped to their face and maybe some shitty rumble from a playstation controller, this isn't "attending a concert with one another" in any meaningful sense, this is just "watch a concert from your couch while talking to your friend over discord", except with a more expensive screen fewer people own or seem inclined to buy, and clumsier input.

msbarnett··on Falsehoods programmers believe about names – with examples (2018)
It's not fully French specific — conventionally, transliterated Japanese family names are rendered in ALL CAPS, particularly when it's unclear whether or not the name is being presented in Japanese-style family-name-first order to western audiences who may otherwise confuse the given and family names.
msbarnett··on Which is not Posix
> Interesting. Can you be a bit more specific? What in POSIX does systemd explicitly reject? And might there be a reason for that?

The project specifically rejects "caring about POSIX" in its entirety. Poettering has discussed this at length[1].

I'm not criticizing systemd here, I'm merely pointing out that Debian is already perfectly fine with shipping non-portable, aPOSIX or even anti-POSIX software by default (which I think is fine), and that the sudden pearl-clutching around `which` not being POSIX is completely inconsistent with many other decisions the project makes and has made.

[1]: https://archive.fosdem.org/2011/interview/lennart-poettering...

"In fact, the way I see things the Linux API has been taking the role of the POSIX API and Linux is the focal point of all Free Software development. Due to that I can only recommend developers to try to hack with only Linux in mind and experience the freedom and the opportunities this offers you. So, get yourself a copy of The Linux Programming Interface, ignore everything it says about POSIX compatibility and hack away your amazing Linux software. It's quite relieving!"

The interview notes various POSIX-incompatibilities as they existed in 2011. They have grown enormously since. It surfaces in userland in a huge number of ways, and *BSD ports maintainers have noted that it's increasingly hard to port any number of things due to the systemd-isms (which now extend to logging, cron, home directories, and many other core functionality replacements) they're baking in.

Again, this is not intended to criticize systemd, but this is precisely the sort of effect that people are hand-wringing about wrt `which` in bash scripts, but nobody is insisting that systemd needs be removed from Debian for having similar POSIX portability impacts. POSIX compatibility has simply never been a meaningful goal of Debian

msbarnett··on Which is not Posix
> As the Debian brouahaha pointed out, there are multiple incompatible implementations of which, so it's unclear which one (ha ha) POSIX should standardize on (and is it politically realistic to anoint one as the 'winner'?).

It's meaningless that there's no clear version that POSIX should standardize on – GNU `which` is the de facto standard on Linux. Debian is hardly going to ship FreeBSD's `which`, as even the discontinued Debian-on-FreeBSD kernel port shipped a GNU userland. (clarification: Debian ships its own `which`, which is not GNU `which` but is meaningfully close enough in behaviour that it's for the most part irrelevant and the fix, in any case, for being too nonstandard would be "ship GNU `which`", not "suddenly care about POSIX in this one case")

In practice, there is only one meaningful `which` on Debian, with clear semantics, and no possibility of confusion over behaviour.

Which is the reason for bringing up systemd. POSIX doesn't cover init, but it does cover many other system calls and behaviours that systemd explicitly rejects in favor of treating the behaviour of the specific Linuxisms it's built around as a de facto standard.

If Debian is fine with its init system being based on de facto standard, POSIX-incompatible Linuxisms, there is no logical reason for it to oppose treating the GNU userland as a similar de facto standard regardless of what the sclerotic POSIX standard says.

"Don't use `which` if your goal is to write a shell script portable beyond your specific Unix, because it has non standard behaviour" is fine advice, but "the Debian project must remove `which` because somebody might accidentally rely on its non-standardized behaviour in a script they also want to run on Illumos" is utterly daft given the hundreds if not thousands of other ways a Debian system goes beyond POSIX.

msbarnett··on Which is not Posix
Not sure why the outcome of "`which` is not POSIX" would be "essentially everybody should stop using `which` and start using `command -v`, which is poorly known, has different semantics, and is covered in relatively little introductory material" rather than "this is just another example of why POSIX has been nearly irrelevant for a long time now".

systemd is not POSIX, either, but that's not taken as some justification for removing it from Debian – this whole drama is just pointless pedantry over something precisely because it is so low stakes.

msbarnett··on Effect of early treatment with fluvoxamine on risk of hospitalization for Covid
> Aren't there many (>60) published studies showing varying positive effects of early treatment with Ivermectin though? (Despite a couple having been retracted for obvious fraud).

There are a number of low-quality (low numbers, methodological issue) studies with varying results. The primary "evidence" that got people excited about Ivermectin was a meta-analysis of these studies, but the meta-analysis itself pointed out that the largest amount of data and strongest evidence in their dataset came from one very large study – the study that was later withdrawn for having faked its data.

Since then, there's been no real compelling evidence at all that Ivermectin has any real impact beyond placebo.

> Compared with the quality of data surrounding remdesivir, molnupiravir etc, there seems to be a significant bias towards novelty (and therefore $$$).

There's a bias towards using treatments for which: 1) there is a reasonable expectation, based on understood science, that the treatment should impact the course of the virus

(preferably) and

2) there is some non-fraudulent, non-obscure and tiny dataset, indicating an effect.

The lack of strong data in support of Ivermectin is coupled with the fact that there's no particular reason to expect Ivermectin should have any impact on any particular virus.

> Similarly, it's been known for decades that vitamin D deficiency increases susceptibility to respiratory diseases, and most people in Europe/North America are deficient in winter. Why not hand it out? Worst case, it doesn't work.

This is mistaking correlation with causation. We know that many people who suffer serious respiratory illnesses, and who die from COVID-19, have low vitamin D levels. This is not believed to imply that low vitamin D levels cause death from COVID-19; rather it's simply the natural outcome of many old people having low vitamin D levels and age being a significant factor in COVID-19 deaths. People who die of old age also have low vitamin D levels; would you argue we should hand out vitamin D in an attempt to cure aging?

The idea that because these things are relatively safe we might as well just do them seems, in whole, silly. Sugar pills and crystals have a great safety profile too, but we don't expect physicians to use those on the theory of "well there's no real downside" either.

Science, not superstition, is the goal here.

msbarnett··on New Brunswick’s Mystery Disease
If they have reason to believe that, eg, the timing of the appearance of this cluster lines up with (to pull a hypothetical out of the air) industrial waste dumping in the Acadian peninsula water supply, attempting to muddy the water over whether this is a cluster with a shared cause or a bunch of fluke one-offs is certainly in their interests.
← PreviousPage 9 of 34Next →