Tiny nitpick: you actually can pin messages in Signal group chats. It's a pretty recent addition though.
Apart from that, I would have been interested in more details about the author's experience with ~Revolt~ Stoat. To my naive eyes it looks pretty nice. I really like the nuanced takes about the other platforms in this article, so I'd guess the author has some good reasons to dismiss Stoat like that.
Its a bit easier as it can be read-only & static generated. Though there are some attempts to make it possible to reply using the Web interface, like HyperKitty /Mailman 3.
Those card suits in that post show up (for everyone) in HN because they are the proto-emoji ancient "Wingdings range" further encoded in the direction of HN without an emoji presentation variation selector. (Emoji presentation selector will color them, so hearts and diamonds would be more red, among other subtle distinctions in most fonts/OSes today.)
The number of "proto-emoji" that HN does not block is interesting given HN's preference to block emoji, but also illustrates some of the fun compatibility complexity of Unicode.
That is still relatively easy to cut your finger on.
I don't know that there's a correct way, really. You would probably have to take the time to file or sand the edges. Which kind of levels the playing field with the cable lacing option really in terms of time spent.
It still exists, and still works. I was sure I showed it to someone a few months ago, and just confirmed, it's still online. (I know the guy who built it).
It works over ipv4 and v6, with the ipv6 version having some additions ;)
Source? I guess you're thinking of long tap → Airdrop, but that essentially shares a link to the Appstore via Airdrop. You're not transfering the app itself.
While this is interesting and impressive, I kinda relate more to OP's link of more "normal" trees. Going through the list gives me a feeling how many cool trees there are all over the place.
Mostly the latter, but a lot of tools are so slow the former actually becomes a problem, too. Valgrind is a great example. For realtime applications, Valgrind and friends are pretty much a non-starter.
To your point about profile results, any profiler that adds more than a couple percentage points at runtime basically destroys the profile results (less than one percent is the acceptable margin, for me). Adding 50% is just laughable, and at the time I looked that was the best available option.
At the time, I was trying to profile ML models and some tooling surrounding them. There are several reasons you want your profiler to be low overhead:
1. If the profiler does a ton of useless shit (read: is slow), it has many deleterious effects on the program being profiled. It can evict entries from the CPUs ICache, DCache, and TLB entries to name a few, all of which can cause huge stalls and make something (such as a scan over tensor memory, for example) many times slower than it would be otherwise. You become unable to reason about if something is taking a long time because it's doing something stupid, or if the profiler is just screwing up your day. Introducing this kind of noise to your profile makes it nearly impossible to do a good job at analysis, let alone optimizing anything.
2. Somewhat unrelated to performance, but, you really want to know more than "this function take up a lot of time", which is basically all sampling profilers tell you. If you look at a flame graph and it says "fooFunc()" takes up 80% of the time, you have no idea if that's because one call to "fooFunc()" took 79% and the rest were negligible, or if they're all slow, or just a handful. That is key information and, in my mind, basically makes sampling profilers unsuitable for anything but 'approxamizing'. Which can be useful, and is often good enough, but if you need to optimize something for real, a sampling profiler exhausts it's usefulness pretty quick.
Anyways .. there are some random thoughts for you :)
Apart from that, I would have been interested in more details about the author's experience with ~Revolt~ Stoat. To my naive eyes it looks pretty nice. I really like the nuanced takes about the other platforms in this article, so I'd guess the author has some good reasons to dismiss Stoat like that.
reply