HNHacker News
TopNewBestAskShowJobs

turtledragonfly

914 karma · joined November 9, 2021

My company: https://festina-lente-productions.com/

email: contact@festina-lente-productions.com

submissionscomments
turtledragonfly··on Reverse-engineering an encrypted IoT protocol
Just piggybacking here to mention a variety of other "interpret structured binary data" tools. Apparently I collect links to these (:

* fq - like jq for binary data: https://github.com/wader/fq

* Kaitai Struct - https://kaitai.io/

** visualizer, for the above: https://github.com/kaitai-io/kaitai_struct_visualizer/

* HexFiend - a hex editor, but with "binary templates" feature : https://github.com/HexFiend/HexFiend

** binary templates, for the above: https://github.com/HexFiend/HexFiend/blob/master/templates/T...

* binspector - https://github.com/binspector/binspector

* binary-parsing - a collection of links to similar such tools : https://github.com/dloss/binary-parsing

* unblob - https://github.com/onekey-sec/unblob

* ImHex, which you mention

turtledragonfly··on On "Owning" Software
> Photoshop ... Consumers have voted with their wallets on #2.

Did they? Or did Adobe just stop offering #1, forcing customers into #2 whether they like it or not?

I'm partly being facetious, but it's also partly a genuine question. Is there some research you know of that shows a majority of people genuinely choosing #2, when both are on the table?

For a long time the standard model was "pay $X for the current version, then $Y to upgrade to the next version, if you want." That is pretty close to the best of both worlds, IMO, from a customer standpoint.

turtledragonfly··on On "Owning" Software
I liked this article, because (1) it's well-written and detailed, and (2) I somehow disagree with it in my gut, though I'm not sure precisely why. So, it makes me think — another plus.

I suppose the thing that bothers me is the general sense that it is advocating for "non owned" software — let someone else handle the support, etc. Makes sense from a business perspective, of course.

But I suppose the thing I don't like about such "non-owned" software is its tendency to mutate in ways I don't like, outside of my control.

Eg: perhaps a feature I like is removed, with no genuine alternative. Maybe I am a niche user of that feature, so the business is (understandably) focusing on their "core" product, and my pleas to the contrary don't really move the needle.

Basically, while I agree with the point that ownership is more expensive than it seems on the surface, I'd also like recognition that non-ownership is also more expensive than it seems on the surface, just in a different way.

Agreed overall about the various gradations of ownership available today, and it's worth thinking about the pros and cons all the way along the spectrum.

turtledragonfly··on Random Animations
You can see a list of them, in chronological order, from the main site — click 'latest animations'[1]

[1] https://bleuje.com/animationsite/2023_1/

turtledragonfly··on PIDs: Creating Stable Control in Games
Not the person you asked, but here's a video you might like: https://www.youtube.com/watch?v=LNidsMesxSE&t=268s

In that example, they do the character's physics first (just a ball), then match the animation to it. The animation speed is controlled by a "surveyor wheel" approach — go to to 336s in the video for that part.

So, the animation speed is derived from the physics, rather than the physics speed being derived from the animation.

I wouldn't call that "IK" exactly, which would be more for things like matching the foot to individual stair steps as the character walks up them, or such. But I suppose in a broader sense it is, since you're deciding on a physical goal a-priori, then forcing the animation to match that goal.

turtledragonfly··on Heat pumps, more than you wanted to know (2023)
Apropos of nothing, I had a not-great experience switching from an oil furnace to heat pump. Maybe somebody else going through research will benefit from my woes. Some day I'll make a blog post for it:

1. Noise levels (inside)

* Fundamentally, a heat pump runs more often than a furnace. So, air is semi-constantly blowing out of your vents, rather than a few bursts throughout the day. Also, the air is tepid, rather than warm. Previously, there was a "yay, the furnace is on" moment of enjoying the warm air. Now, it's more of a "jeez when will this thing shut up again?" throughout the day. It reduces my quality of life.

* One of our vents points at my back where I sit to work. With the furnace, that was enjoyable. With the heat pump, it's a nuisance. I taped over the part that blows on me. Similarly, we have a vent in the bedroom that we mostly keep covered with a pillow these days, due to the noise.

* In documentation, noise is often measured in decibels — indicating max loudness. And by that measurement, the heat pump is no worse than the furnace (maybe even a bit quieter). But the fact that it's on near-continuously at that noise level is what causes my annoyance. So, it's not just loudness, but also how continuous it is.

* We had existing ductwork, so the heat pump's air handler uses that (just like the old furnace). This is a common situation, but what nobody mentioned, across multiple estimators, is that it's likely the old ductwork will be "under-sized" relative to the new system. This means higher static pressure, and importantly, more noise at the output vents. Talking to the technicians, this is a bit of a crapshoot — you might get lucky with noise levels, or might not (like me).

* Loudness will also vary depending on how far from the central unit you are (my house is fairly small), how many vents there are, and various other factors.

* In theory, you can determine if the above will be a problem by doing measurements beforehand. None of the estimators mentioned this; they just want to sell you the system, of course. I didn't realize until too late that you can probably find someone, pay them a few hundred dollars, and get this information upfront. There's a whole science to it, with specialized tools. Look up "Manual J, S, D, T measurements," for a starter.

* However, even if you get that info, it still depends on your sensitivity to these things. For instance, my wife is much less bothered by the noise than I am.

2. Thermostats

We got a fairly modern "communicating" system. This means the outdoor and indoor units talk to each other, allowing better efficiency.

This sounds nice, but what it means is that you will be locked in to your vendor's choice of thermostats, since the communication protocol is proprietary. These are generally more expensive than the alternatives, and you won't have many options — perhaps only one.

If you get a "non-communicating" system, you will be able to try various different thermostats — eg: a simple one from your hardware store, or a Nest one, etc.

3. Other

* The old oil furnace was a simple machine, with a lifetime warranty on the heat exchanger (basically a hunk of cast iron) and can basically last forever with decent maintenance. The new heat pump has a 12 year warranty, and the system might last 25 years with good maintenance. The HVAC estimator seemed proud of this, but to me it doesn't seem like an especially long time.

* If you use old ductwork like mine, it may not be insulated to modern standards. This is both a noise issue and potentially a condensation issue when the AC mode is running.

* It's very difficult to know when the "emergency heat" mode is being used — where resistive electrical strips are used to generate extra heat, if the heat pump isn't producing enough. This mode is much more expensive than the heat pump alone. It boggles my mind that such simple (and useful) information is so hard to obtain.

* If you want to get government subsidies, do your research about what exact make/model is covered by it. Ironically, sometimes the more modern and efficient systems are not subsidized, presumably because there is some lag to update policies.

* Generally, remember that the estimator who might come to your house is a salesman, first and foremost (:

4. Pros

Okay it's not all bad; some positives include:

* AC in the summer. Probably the biggest positive.

* No dependence on oil — both for cost and environmental concerns and risk of tank leakage (ours was aboveground, so less of a worry)

* No carbon monoxide worry, since there's no combustion going on.

But overall, I'm not sure it was worth it for my case.

turtledragonfly··on The curious case of the Raspberry Pi in the network closet (2019)
I don't think the article proves that. I think these policies can be a bit of a McNamara fallacy[1].

When things go wrong, the benefits of aggressive termination are clear. But when things don't go wrong (vast majority of time), the alternative's benefits are not so clear — employees have more time to hand-off their work, document things that are in their head, better good-will towards the company and its management, etc.

So, because one approach has a clear, measurable benefit (avoid some disasters), and the other approach has un-clear hard-to-measure ones, people sometimes dismiss the hard-to-measure side as unimportant. That's the fallacy.

[1] https://en.wikipedia.org/wiki/McNamara_fallacy

turtledragonfly··on Herringbone Wang Tiles (2011)
One interesting application of this technique is how the world is generated in Noika: https://80.lv/articles/noita-a-game-based-on-falling-sand-si...

They found that the herringbone pattern hides the grid pretty well and cheaply, relative to other options.

They also credit Sean Barrett's prior work: https://nothings.org/gamedev/herringbone/herringbone_tiles.h...

turtledragonfly··on Color: From Hexcodes to Eyeballs (2018)
This is a nice article, bringing together various color/perception concepts.

For those interested, you may also like the article introducing the "OK Lab" color space[1] and others by the same author[2].

It's my current favorite, though definitely not perfect.

[1] https://bottosson.github.io/posts/oklab/

[2] https://bottosson.github.io/posts/

turtledragonfly··on Understanding the heap – a beautiful mess
Not so much the author's fault, but there's a bit of confusing terminology around the meaning of "pool" in memory allocator literature in general, and this article in particular.

In this article, they say:

> Pools ... involve: pre-allocating ... core resources that are frequently used in a program, which are self-managed by the program ...

This (IME) most often means some sort of "object pool," with fixed-size objects and O(1) allocation and de-allocation.

And also:

> a memory pool pre-allocates a large block of memory ... When the programmer releases the memory, it is returned to the pool ... and is merged with surrounding free memory blocks as much as possible.

This clearly is not referring to the object pool concept. In the article, the O(1) freelist approach falls under the "bins" nomenclature.

In general, memory allocator terminology is pretty messy, varying between sources and implementations. Words like "arena allocator" and "stack allocator" seem frequently abused/blurred, made worse by the fact that one can nest allocators in each other — eg: a stack allocator which allocates from an arena, but sometimes referred to one or the other interchangeably.

I had a bit of a rollercoaster ride trying to make heads and tails of it all when I was researching these things.

turtledragonfly··on Is Mathematics Invented or Discovered? (2020) [video]
> It is a metaphysical question, not a scientific question.

Well here I soundly agree with you. I believe that's what I was trying to communicate at the very start, when I said "those 'why' questions are exactly what math and science do not answer."

I suppose our difference relates to how we conceive of other kinds of "why" questions.

> Mathematics is constantly proving things true.

Also agreed with you there. That's one key difference between math and science, in my mind. For that reason, I suppose I'd put theoretical physics more in the "math" realm than the "science" realm, at least w/respect to the theorem you mention, and similar.

Small aside: thank you for the tenacious-but-respectful discussion — I always worry when a thread goes 3+ replies deep that it'll just become an angsty flamewar, so it's nice to have a counterexample in my training set (:

turtledragonfly··on Is Mathematics Invented or Discovered? (2020) [video]
You bring a small constellation of points to mind; sorry for the multi-part reply:

1.

The original question was about the natural world, not math, and I'd say that the connection between the two is not guaranteed by anything. So any conclusion in math does not dictate reality. We simply have no "givens" in reality to work from. Though certainly mathematical models are useful.

2.

Going back to your Noether example: are you saying that conservation laws are caused by symmetries?

If the theorem says "X => Y", then does that mean Y is "caused by" X?

I don't think so. It just means that if you observe X, you can be sure Y is there too.

Suppose later we find out additional information: Y => X

Now, we have "X <=> Y", and certainly it would be unfair to say one of these "causes" the other, no?

That would fall in your "uncaused" category, I believe.

3.

The scientific method does not prove things to be true, ever. It only disproves wrong theories, by providing counterexamples.

So, if you have a theory about "why" something is a certain way, you will never fully confirm it with the scientific method. You will only discover when one of your proposals was wrong, never that it was right.

It may be the case that a lot of people try very hard to prove it wrong, and fail. And it may be the case that it is useful at predicting the future and other novelties. But it could still be wrong, and you would never know — maybe the counterexample will be found tomorrow.

----

I really do think the bedrock answer to "why do apples fall from trees" is "we don't know." There's just a lot of interesting stuff to be discovered in the (failed) attempt at answering it, in the meantime.

turtledragonfly··on Is Mathematics Invented or Discovered? (2020) [video]
I disagree.

There was a "why X" question, and then an equivalence was observed, saying "X = Y" (which is useful, to be sure), but at the end of the process, there is still only one "why" question — "why X" and "why Y" are now shown to be equivalent, but the question remains unanswered.

Maybe we disagree on what "why" even means, though (:

turtledragonfly··on Is Mathematics Invented or Discovered? (2020) [video]
I appreciate what you're saying, but I think you missed my point.

In your example, you just moved the question of "why are there conservation laws" to "why are there symmetries?" The answer is still that we don't know. Though as you point out, understanding the relationship between the two is useful!

> Placing an arbitrary barrier on the questions that can be asked is called dogma.

I did not mean to place a barrier. It is fine to ask the question. But it is also fine (and honest) to answer it with "we don't know."

Edit: of course, please do not interpret "we don't know" as "we shouldn't try to find out" (:

turtledragonfly··on Is Mathematics Invented or Discovered? (2020) [video]
Those "why" questions are exactly what math and science do not answer (:

Not saying that philosophy or religion is particularly good at answering them either, but that's more the domain you're getting into, I think.

Brief excerpt from this Feynman interview[1]

  "Say pop, I noticed something: when I pull the wagon, the ball rolls to
  the back ... and when I'm pulling along and I suddenly stop, the ball
  rolls to the *front* of the wagon."  And I said: "why is that?"
  
  And he said: "That, nobody knows. But the general principle is that things
  that are moving tend to keep on moving, and things that are standing still
  tend to stand still... This tendency is called "inertia," but nobody knows
  why it is true."

[1] https://www.youtube.com/watch?v=NjUSO4u2di0
turtledragonfly··on Is Mathematics Invented or Discovered? (2020) [video]
Why is that? (genuine question)

Just because an approximation is really good in some cases doesn't mean it's more than an approximation, does it?

turtledragonfly··on The truth is always made of details
Your Holmes quote strikes a chord with a concept that I've had internally for a while: "bottom-up" vs "top-down" learning.

I'm more of a "bottom-up" learner myself — I like to immerse myself in the details and then over time build an idea of how things work from that.

But it's common to teach subjects in a more top-down way, especially in academic settings. You're told the big conclusions first, then maybe if you have time, get into the details of why. Perhaps in the homework assignments.

There are pros and cons to each, but I do have a soft spot for the hard-won high-level conclusions that are distilled from complexity rather than being taken for granted. It gives a more satisfying and thorough understanding of things, though at the expense of much time and effort.

I feel like Holmes' "this side" or "that side" of complexity refers to going through that effort.

turtledragonfly··on Representing Rectangles
Author here, in case you have any questions/feedback/etc (:
turtledragonfly··on A blog post is a long and complex search query to find people (2022)
As a counterpoint, a blog post is sometimes (often times?) more about the writing than the receiving of responses.

Is throwing a bottle with a message in it into the ocean a "complex search query to find people?" I wouldn't phrase it that way.

The article does say:

  It will seem like I am mainly talking about how to use writing
  to forge meaningful relationships ... But lurking behind it is
  a larger idea. Namely, that you can shape yourself by reshaping
  your relationships. By changing who you are addressing, and the
  responses you garner, you steer your development.
and I don't disagree with that, but at the same time, just forming the words helps you shape yourself, regardless of whether it involves other people. Or maybe the other people can just be in your own head.

I've got countless drawings and writings that nobody else will ever see, and likely will die with me. But they were very important for my self-shaping.

Maybe this is just a personality difference between me and the author — some people define themselves more in terms of their relationships with others than otherwise.

But regardless, I liked the article (:

There is some fine line between just being yourself and "singing into the void" as it were, versus trying to use your voice to make changes in the world. I must admit I lean towards the former, but the idea of "the summoning of a new culture" at the end of the article is interesting.

turtledragonfly··on Loyal workers are selectively and ironically targeted for exploitation
I see your "People X..., People Y..." language, and I just want to note that over-generalization can be a path towards depression[1].

I don't mean this directed at you specifically, but it's fairly common for people to take their bad experiences in a handful of places and extrapolate that to all places everywhere, and end up feeling depressed/nihilistic, as you mention. I find myself doing it too, from time to time.

So, maybe this is more directed at other readers who might see your comment and take it as validation of their "everyone sucks" suspicions — grain of salt, and all that.

But I agree that what you describe is genuinely demoralizing and a crap way to be treated (: I hope you get to experience a good work life, if you haven't already.

[1] There's a good amount of research on this topic (search for "depression, over-generalization"), in addition to my personal experiences.

turtledragonfly··on The Ashley Book of Knots (1944)
My understanding is that a lot of "knot culture" developed during the Nantucket whaling days. There were knots before, of course, but the variety and intricacy exploded. (a bit of a simplification of course, there are lots of cool Celtic knots and whatnot, too)

It was a somewhat special time, where you had a lot of relatively well-paid capable people stuck on a boat with nothing to do for sometimes weeks on end. Encourages some creativity, I suppose (: Scrimshaw is another product of that time — some really intricate stuff out there (eg: [1]).

For me, I feel like the bowline and trucker's hitch give you huge bang for the buck. Memorize those, and you can handle many things, with a bit of rope.

[1] https://modelshipworld.com/topic/27614-prisoner-of-war-bone-...

turtledragonfly··on Ian's Shoelace Site
Here's a nice short TED talk on tying your shoes right: https://www.ted.com/talks/terry_moore_how_to_tie_your_shoes

It doesn't use the "Ian's Secure Shoelace Knot", but it shows that for the typical way of tying your shoes, there is a "strong form" and a "weak form", and shows you how to tell the difference.

I got lucky and have been tying the strong form my whole life, but it's sorta 50/50 depending on how you learn.

turtledragonfly··on ImPlot: Interactive plotting library, ImGui style
Historically, in high-performance resource-constrained applications (eg: console video games), developers would use a "stripped down" version of C++ (eg: no RAII, no exceptions), which often included avoiding STL. It's less true these days, but still somewhat. In truth, STL will never be fully catering to these uses; that's not its goal.

One reason STL was avoided is that control over memory allocation was quite poor. std::allocator was somewhat conceptually broken for a long time, only recently remedied in C++14 and 17. So, there's still about 20 years of code out there from the days of old bad C++ (:

Another reason is that early STL implementations were poor, and not well-suited to high-performance use cases. Again, this has gotten better (some), but the legacy lives on.

Here's a good one to read: https://github.com/electronicarts/EASTL/blob/master/doc/Desi...

So, if you are designing a library to be used in video games (such as in TFA), and want wide adoption, then avoiding STL, RAII, exceptions is still generally a good idea, IMO.

turtledragonfly··on Twitter’s Rebrand to X Could Be a Trademark Nightmare Thanks to Microsoft
Microsoft's trademark is for just the letter "X", not the specific design.

This is extra-confusing on the USPTO site[1] because it says "Standard Character Claim: No" (which usually means not text), but it also says "Mark Drawing Type: 1 - TYPESET WORD(S) /LETTER(S) /NUMBER(S)".

And that last part is merely the old way of saying it is Standard Character Claim (that's the newer terminology). See their documentation[2] (page 7); the terminology changed in 2003.

Some more info here: https://trademarkgarden.com/2018/03/09/amazon-and-you/

So my understanding (not a lawyer) is that Microsoft's "X" is indeed generic text, though still limited to the specific goods/services listed in the application.

[1] https://tsdr.uspto.gov/#caseNumber=2693757&caseSearchType=US...

[2] https://www.uspto.gov/sites/default/files/products/applicati...

turtledragonfly··on Twitter’s Rebrand to X Could Be a Trademark Nightmare Thanks to Microsoft
No, I don't believe so in this case. Though I agree the USPTO page can be confusing (:

The Meta trademark is for this design: https://tsdr.uspto.gov/img/87980831/large?1690302463976

It's true that they use the text "X" in the (textual) description of the trademark, but that is not what's being trademarked. See the "Mark Information" drop-down on the page[1], for more detail.

[1] https://tsdr.uspto.gov/#caseNumber=87980831&caseType=SERIAL_...

turtledragonfly··on Twitter’s Rebrand to X Could Be a Trademark Nightmare Thanks to Microsoft
You can look at the trademark's registration in the USPTO site that was linked[1]. See the "Documents" tab. This one was first issued in ~2018, so would not need renewal until 2028.

You don't generally need to sue every infringer in order to keep your trademark. My understanding is it can vary by court and it gets a bit legally complex, and the final decision will depend on various factors (eg: [2]).

[1] for reference: https://tsdr.uspto.gov/#caseNumber=87980831&caseType=SERIAL_...

[2] https://www.dbllawyers.com/can-i-lose-my-trademark-rights/

turtledragonfly··on Twitter’s Rebrand to X Could Be a Trademark Nightmare Thanks to Microsoft
This is correct. I'm not a trademark lawyer, though I have filed some.

There are two main types: a "standard character mark" (which is text) and the rest, which are visual logo designs.

This one is the latter. That is, they're not trademarking the text "X", just that particular visual representation — the colors involved, etc.

You can tell in the TEAS system by looking in the "Mark Information" section, and the "Standard Character Claim: No" line.

turtledragonfly··on Stack Overflowed
Humor, I believe (:

Poking fun at similar sites that plaster tech company logos on their splash pages to make it seem like they're important, when any real affiliation may be tenuous at best.

turtledragonfly··on Being “rockstars”: when software was a talents/creatives industry
I feel like the author themselves is a bit scattered on this point.

In the very quote you lead with, they link to another post[1], which says "...MySQL is boring. Postgres is boring." Our author says they don't like that Boring approach, but then they advocate for a "pets, not cattle" approach, which I think is in line with administering a MySQL server, or such.

Maybe this all comes down to different people's definitions of Boring. Maybe modern developers think of "Cloud everything" as the boring/playbook approach, while other people (like me) see the older (in my mind simpler) idea of administering a few machines, maybe even on bare metal, to be Boring.

You wrote:

> So, do you leverage those solutions to help you solve your problem? Or do you let your engineers re-invent the wheel so they can feel smart?

In my charitable interpretation of TFA, I think they are saying to let your engineers use smaller-scale solutions/technologies that address the problem at hand, as needed, rather than getting pulled into the Cloud-everything solve-all-your-future-problems-you-don't-even-have-yet ball of wax that's often advocated these days.

I can get behind that sentiment, but yeah I'm not a big fan of the way it's framed in the article, and I have never liked the "rockstar" term.

[1] https://mcfunley.com/choose-boring-technology

turtledragonfly··on Making Games
> No business feature in my 15 year career has ever come close to the complexity of shaders, trig, and physics!

Yeah, it's wild how even simple-ish video games can put to shame reams and reams of "enterprise-y day job" code in terms of complexity and demands on you as a programmer. I love it (:

Aside: I wish DMs were a thing on this site; you should let me know your game if/when you make it public!

← PreviousPage 3 of 7Next →