HNHacker News
TopNewBestAskShowJobs

fargle

1,337 karma · joined August 28, 2019

submissionscomments
fargle··on Limits to running speed in dogs, horses and human
that's absolutely not how horses work. just like people athletes, horse athletes have a very strong competitive spirit. they understand they are competing and the good ones really love it. they will push themselves extremely hard, easily to the point of injury or exhaustion if not pulled back. a good horse also trusts his rider and will do what the rider asks, simply because he asked. if you were to ride a horse like that to exhaustion and then ask it to go on and on, he would, just because you asked, until he physically collapsed.

you may be thinking of mules, who are famous for refusing to overwork themselves.

fargle··on Police can't stop sideshows. Solution: Make the streets more annoying
that is untrue, and a disingenuous argument. there is no requirement for violence simply to arrest them.

but if street racing assholes decide to escalate to violence (and a car is a weapon), then both staying alive and protecting the public requires willingness to use lethal force in reaction to the criminals' violent and dangerous behavior.

and that isn't disproportionate at all, that's how it should be. and i'm grateful that there are people who make that sacrifice and have a willingness to protect me with lethal force if necessary.

fargle··on Police can't stop sideshows. Solution: Make the streets more annoying
or, instead of installing basically speed bumps in all the intersections, they could show up and arrest the participants for misdemeanors and felonies that are clearly visible on video, actually book them into jail with serious bail. impound the cars as evidence and don't give them back unless they prevail at trial.

if the political system isn't interested in enforcing, of all things, these kind of laws, speed bumps aren't going to help.

fargle··on Wtfpl License
this license is a hilarious satire that lambasts the inevitably overly pedantic world of software licensing and the lawyers who created that mess.

just don't forget that and use it for anything serious.

** the above comments are dual-licensed under the following [at the authors' choice]:

    - AGPL 3.0
    - BSD 4-clause
    - WTFPL 1.0 and/or 2.0
fargle··on Translating All C to Rust (TRACTOR)
to be fair, from his perspective, it's often the rusty crowd who is stoking the flame wars - this sounds like a reaction to them.

how often do we hear something like "C and C++ are horribly flawed and completely unsafe. it's basically a crime against humankind and gross negligence to use them"?

i get weary of that kind of thing too. i wouldn't approach it by reacting in the same way as the GP comment, but i get it. and it's not really that much of a strawman. it's more exasperation and sarcasm.

personally, i'm very interested in rust. but everytime someone at best "overhypes" it or at worse, outright dogs on other languages, it's a negative point toward dealing with the whole rust ecosystem.

fargle··on Incorrect Quotation
the original source appears to be someone calling themselves "richard" trolling a podcast: https://youtu.be/QlD9UBTcSW4?si=lFm_pzZFSQ4Xi3JK
fargle··on [dead]
amusing. (not) solving a "snake oil" https://en.wikipedia.org/wiki/Snake_oil problem with a patent miracle solution!
fargle··on Microsoft blames EU rules for allowing biggest IT outage to happen
or, the users could kick CS and McAfee out of the kernel space themselves - by not using those products or features that require these dodgy kernel modules.

the CTOs and engineering staff are the ones in control of their machines, not M$. or at least they should be. problem is that they thought they were solving a problem by installing this kind of software, but instead were simply handing over their responsibility to a 3rd party that was totally irresponsible - and certainly doesn't accept it. they took a compliance short-cut with "box checking" software. that's where the problem lies - lack of responsibility and engineering rigor in the IT orgs.

fargle··on CrowdStrike Update: Windows Bluescreen and Boot Loops
such stupidity. our $$$ corporate geniuses mandate multiple so-called security software which is:

- unaccountable black boxes

- of questionable, and un-auditable, quality

- requires kernel modules, drivers, LocalSystem, root access, etc.

- updates at random times with no testing

- download these updates from where? and immediately trust and run that code at high privilege. using unaccountable-black-box crypto to secure it.

- all have known patterns of bad performance, bugs, and generally poor quality

all in the name of security. let's buy multiple "solutions" and widely deploy them to protect us from one boogeyman, or at least the shiny advertisements say. while punching all sorts of serious other holes in security. why even look for a Windows ZeroDay when we can look for a McAfee or Crowdstrike zero day?

fargle··on How do jewellers capture every last particle of gold dust? (2017)
oh there is a short ton, a long ton, a metric ton. the normal ton in the US is "short ton" which is 2,000 lbs.

https://en.wikipedia.org/wiki/Ton

we also often encounter a "f*ck ton" or even a "metric f*ck ton". these are usually informal units related to the number of things (especially annoying things) rather than strictly weight.

fargle··on Supreme Court Ruling Threatens the Framework of Cybersecurity Regulation
^^ this exactly. it doesn't matter which wing you like, all outcomes of chevron were bad. the over-turning is not.

you may or may not like the decisions of congress. you may or may not like the decisions of a court. i could live with either.

but an unaccountable bureaucracy's kangaroo court needs to be checked severely.

fargle··on 2014 Nissan Leaf: first impressions (2024)
ok, the author lost me at: "My first choice would have been a Mitsubishi i-MiEV ... Shame, because it is a much cooler car than a Nissan Leaf."

wow, this is a different country: "1600 kg! ... being about 2x as big and heavy as necessary." [i really butchered these quotes, fyi, not trying to do it dishonestly but to focus on these statements]. to me the leaf is a tiny little car. 1600kg is like 3500 lbs - not big or heavy at all to me.

Ioniq 5 is 4850 lbs or so. model 3 and y are almost identical in weight/range/etc.

the leaf is a very cool niche car in a way - but it's a "city car". something 1/2 step up from a golf cart. but, used, actually cheaper in most cases.

fargle··on “Technical” Skills
disagree with this. there is clearly a difference between "technical" and "non-technical" people.

the definition "technical people" are using when they make that distinction is close enough to 1a of Webster: "having special and usually practical knowledge especially of a mechanical or scientific subject"

now, it's fine to be non-technical. but don't try redefine "people-people" as "technical, but in a different way". part of being a good manager of technical people is to understand the distinction and the different way they think. i've had great managers and leaders that were technical people that became managers. and the very best managers i've had were non-technical people that were extremely skilled leaders. they grew to understand, trust, and manage technical people. they knew the difference and thrived by providing complementary viewpoints and skills.

but i've seen a whole lot of amateur politicians that didn't really understand people as well as their supposed expertise was touted to. they don't have strong technical skills or even the right mindset, so the recast themselves as being good at other things instead (if not good at engineering, they must be good at management, right?).

they chafe at people calling it "soft-skills" or "non-technical". they use analogies like basketball a lot (and sewing, and rock climbing). to try to equivalate a technical engineering mindset to the way the author thinks is a tell that they don't understand the difference at all. the attempts to change the reality by changing language. mis-ascribing phrasing as some kind a value judgement or slight.

all of this tells me this person is not as skilled in technical fields OR with people as they think they are.

[1] https://www.merriam-webster.com/dictionary/technical

fargle··on Ask HN: Should I learn Awk or Perl? Or is that a bad question?
AWK is better suited to command line ad-hoc and shell script use. it is simple, straight-forward, and surprisingly powerful. most of the time sh+awk can replace sh+sed+cut+grep constructs. GNU awk (gawk) flavor is ubiquitous and it has a great manual [1]. and you have the AWK book [2] (not "free", but easily found).

perl is more of a completely replacement for sh+awk for a standalone script/program. it was the first scripting language i know of that could do sockets networking and other complex things you'd previously need to write in c. it has extremely powerful text processing capabilities, like awk. but it's a big complicated, unusual scripting language. if you want a big complex full-featured scripting language to make a complete tool these days, why not use Python? if you only need really fancy text manipulation, maybe Perl, but i don't see that use a lot.

[1] https://www.gnu.org/software/gawk/manual/html_node/index.htm... [2] https://awk.dev/

fargle··on Booting Linux off of Google Drive
i keep parsing this headline as "kicking Linux off google drive". huh?

oh.

fargle··on [dead]
this guy (OP) is dumber than a GPT.

1.8m * 1ft / .3048m = 5.905 ft

0.905 ft * 12 in / 1 ft = 10.86"

5' 10.86"

if the difference between 5'9" and 5.11" is emasculating, but you feel fine about flaunting your "math" "skills", then sure. google is the problem.

fargle··on Git: Please Stop Squash Merging
upvoting! "I also don't want a commit history that looks like London's tube system map"

i don't care how you do it. squashing? git reset followed by sensible commits? intense ninja-like git commit hygiene? or my favorite, liberal amounts of git rebase -i?

the only things i care about are these:

1. your PR contains a series of atomic commits

2. each commit makes a single logical change.

3. that each logical change is adequately described by the corresponding commit comment

4. extra credit if the series of changes is consistent to build and work at each step

i don't want to see "ONE" commit per-feature unless it's trivial.

i do want to see the development process, but in a "publish"-able form

i don't want to see "WIP", "almost working", "fixed broken", "redesigned ...", etc. sausage being made. i especially DON'T want to see patches to files be changed and reverted multiple times as mistakes are made and fixed.

the final PR should be you publishing a nice finished series of patches to accomplish a new feature.

then! we simply rebase that nice simple series on top of master and merge it with an optional merge commit. this gets you a nice linear history while avoiding the information loss with simply squashing everything in a PR/feature into a single commit.

fargle··on How to get root access to your Sleep Number bed
you absolutely need to do this. we call it the "internet of shit VLAN".
fargle··on The weirdest QNX bug I've encountered (2021)
yep. it's really trash. used it 20-25 years ago when they were just introducing "neutrino" vs. the classic QNX4. the former had a good rep with auto and medical usage.

- very bad port of GCC was buggy and generated bad code. it was the result of some idiot blindly haphazardly applying a ton random incoherent patches to try to get it to build instead of porting it properly. (to be clear mainline GCC at that time was fine; we re-ported it ourselves instead) - and, of course, they used their own faulty compiler to build their libraries and services ;) causing unknown carnage waiting to be discovered.

- malloc broken (heavy use under multiple threads causes heap corruption). replaced with dlmalloc.

- serial port driver broken. rewrote a new one.

- intel network card driver crashes. replaced hardware with 3com to survive.

- certain math library functions broken (iirc, fmod). replaced.

and so on and on.

it doesn't matter what certification your RTOS (or whatever) has. if you cannot examine the source, rebuild it, etc. (oss or private source available) - it cannot be trusted. this was one of the worse examples, but it's always like this with "proprietary" OS/toolkits.

fargle··on FDA warns top U.S. bakery not to claim foods contain allergens when they don't
> This is about sesame.

yes!

> This has significantly harmed consumers who are actually allergic to sesame.

maybe. more like: "This may have slightly annoyed..."

> It was a clear and flagrant abuse of the "may contain traces" mechanism.

nope. absolutely not. the did not say "may" they apparently said "contains". but what do you want them to do if there's a 0.0001% chance of two particles of sesame in a product?

> The bakeries caused harm

nope. the FDA caused harm for consumers by regulatory overreach

the result will be one of three things:

1. FDA redrafts the sesame rule to define what is cross-contamination and what is not in a realistic way that bakers will agree to abide by and doesn't have these counter-productive side-effects.

2. Bimbo stops saying "contains sesame" and starts saying "may contain sesame" (the FDA officials acknowledged Tuesday that statements that a product "may contain” certain allergens "could be considered truthful and not misleading.")

3. Bimbo actually adds a tiny bit of sesame as other bakers did and keeps the packaging verbiage the same.

which one is least unhelpful to the 0.2% of people with sesame allergies?

fargle··on Denver gave homeless people $1k/mth. Year later, nearly half had housing
a very slight uptick in % housed for those who got the money in a lump sum might make sense: it's enough for first month rent + deposit.

other than that, agree. sure looks like no real effect. i wonder what % housed would be after a year for people who didn't even get $50/month? it's probably also the same. for the reasons you state.

fargle··on Apollo 8 astronaut William Anders ID'd in WA plane crash
if i live to be 90, i'd wish to die quietly in my sleep like my grandpa.

not screaming in terror like his passengers.

fargle··on Let rand = main as usize (2022)
"ASLR is a significant barrier to attacks."

that is a position statement, not a fact.

i don't care for, as is a very common theme here on HN, techbro-splaining that "it's a settled/widely known/etc. fact" when it is an opinion.

actually, that's really all the author pointed out - didn't say it wasn't valuable, just said it could be debated. thus goading, of course, a snarky response (including a "random" quote from an unnamed book) about what ASLR does and therefore there can be no debate.

i might agree with you, i might not agree you. but presenting facts, opinions, and arguments to support to reject a position sounds like a debate to me.

what i will also say is that any universally qualified statement about the value of a security hardening feature, risk of a vulnerability, etc. is always wrong until the threat model and all other engineering factors are properly weighed. what is "significant" to situation A may be "security theater" in situation B.

fargle··on Let rand = main as usize (2022)
> It's not debatable at all

you do appear to be debating it...

fargle··on TPM GPIO fail: How bad OEM firmware ruins Intel TPM security
i like the way you think
fargle··on Cat as a Service
and how, exactly, does your cat murder birds? did you leave the bird cage open?

oh. you meant feral cats. outdoor cats.

cats really shouldn't be outdoors in most circumstances, and they should never ever be feral.

and feral dogs kill cats, dogs, chickens, goats, sheep, and sometimes horses.

no animal does this for personal satisfaction. see that little word in there: "person". it means what humans do, nothing to do with feral or wild animals which do what they do because they are actually animals. it's a moral code that is far simpler and far more perfect than ours. no animal other than human has ever murdered another (killed certainly).

so you can be a "dog" person or a "cat" person or a "chinchilla" or "rat" or "fish" or "horse" or "chicken" person, or all of the above and more. its means you love and get along with the particular psychology of and interaction with those kind of animals. that's fine. one likes what they like. you may not understand someone else's attraction to spiders or weasels and that's fine too.

but you can't compare bad or feral animal A with domestic family member animal B as some excuse for why your favorite animal is better. that kind of superficial "reason i like X" is a sure tell one doesn't really understand any animal relationship at all.

the attraction to any domestic animal really boils down to the fun and achievement of learning and trust and communication across different brain and psychological types. it's also pretty good practice for communication with different human psychological types. it should be a symbiotic relationship. cats nay be a little trickier than dogs because, at least superficially, some dogs are natural "people pleasers". but dogs can be difficult in their own way. cats are a little less followers. they might agree to be your peer, if you are worth it. it's good for your humility, if nothing else.

and cats make this awesome rumbly noise when they sit on your belly and are happy.

fargle··on Rust is not about memory safety
i don't disagree, but will register a bit of counter argument. i think it's great that the software engineering discipline is maturing. i think it's great that we study formal semantics and work towards making it easier to create correct programs and harder to create incorrect ones. new-thing-better, gotcha.

but old-thing-bad-shouldn't-they-have-ism i do not like at all.

i think it is a misrepresentation of what "C" was, and is, to falsely compare it with a modern "safe" language (we saw this before with java. oops i mean pascal. oops i mean ada, oops lisp, etc.). it was never meant to be a "safe" language. it was, and is, basically a portable high-level assembler. it allows, but does not enforce, "structured programming" and user defined types, and was portable. that was at the absolute forefront in the 1970s and 1980s. and the productivity was "off-the-chart". sure, your UNIX might crash now and then, but you "just yell down the hall and reboot it" instead of waiting on a multi-decade project to "do it right" to materialize.

so what now? 50 years hence? is it an appropriate language for string parsing in a security sensitive application? probably not. is it a "bad" language, or inappropriate for some other task? and why aren't we wailing and screeching about the lack of memory safety in assembler, for example?

the problem to me is not the language, but the application of it. say you have an application A where language X is a better fit than language Y, but they used X. you don't call out the designers of language X for not anticipating A, you should instead build A' using language Y and let it prove itself.

fargle··on Are the Imaginary Numbers Real?
i'm not sure about the whole of platonist philosophy or competing theories, but the platonist way of handling "numbers" seems exactly what i use internally:

- "imaginary" numbers are exactly as real as irrational, rational, integers, natural numbers, zero and the rest.

- all these kinds of "numbers" are real, but exist as symbolic abstractions. e.g. not observable in the physical universe.

for one thing, while you can observe two cows, you cannot observe more than 2*100 cows. but these are both natural numbers. it would be an unsatisfying (to me) definition of real if realness depended on the size of a natural number, and probably its application (cows vs. subatomic particles).

and while you can't really observe the number two by itself, it can still be used to communicate and reason about the number of cows and other objects. it's a symbol, a very useful abstraction. real in the platonic sense, but abstract - a distinct type of real outside time and the physical universe.

irrational numbers and even complex numbers are then simply other useful abstractions. it's useful to learn this about mathematics and physics in general because, e.g. "is velocity real?", "what about string theory? - is the 10th dimension real?"

the rest of the article dives further down the rabbit hole of structuralism, another philosophy of mathematics, apparently a reaction to platonism.

at this point, my interest in philosophy has dropped to a level that can not be represented by any number at all. meta-unreal (a level of real that is not real even in the abstract sense), and so rational as to be completely irrational.

i've concluded that numbers are also exactly as real as the theories and philosophies of reality, but far more useful.

fargle··on The rise of the disposable car
if anyone was even willing to do this for paid service, it'd be more like at least 150% of the labor costs.

https://www.reddit.com/media?url=https%3A%2F%2Fexternal-prev...

if you can find a good mechanic friend, and pay with beer and pizza, you'd be much more likely to be successful.

fargle··on C Is Not a Programming Language Anymore for Developers
i'm wondering if it's an artifact of "dark mode"? but apparently not.
← PreviousPage 6 of 34Next →