Hacker News: apaprocki

New comment by apaprocki in "Artemis II Launch Day Updates"

apaprocki — Thu, 02 Apr 2026 00:02:53 +0000

You should always seek out the best. From watching lots of Everyday Astronaut streams over the years, I knew the stream would be the best live experience because they care about and focus on the production. NASA cares and focuses on the rocket, astronauts, mission. I'm fine with that.

New comment by apaprocki in "Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2"

apaprocki — Sun, 22 Mar 2026 17:59:37 +0000

And for parents: 1.1.1.3 blocks adult content :)

New comment by apaprocki in "Temporal: The 9-year journey to fix time in JavaScript"

apaprocki — Thu, 12 Mar 2026 13:35:20 +0000

I feel like those not involved in this space might not realize so much stuff that benefits the entire web/world comes from volunteers like anba and companies outside the usual browser vendors. Whether you’re an individual contributor or you want to push your employer to contribute or let you contribute, the best time to get involved is always now. We owe anba a big one. Thank you!!

New comment by apaprocki in "Temporal: A nine-year journey to fix time in JavaScript"

apaprocki — Wed, 11 Mar 2026 21:08:03 +0000

Yes, please try! One of the main motivations for doing all this work is to slim down both the amount of code that has to be delivered and executed by providing everything that's needed by the platform. In addition, you're slimming the potential bug/attack surface as well, which is always nice.

New comment by apaprocki in "Temporal: A nine-year journey to fix time in JavaScript"

apaprocki — Wed, 11 Mar 2026 21:05:37 +0000

Depending on the situation, the data lives either within the browser or within the OS. Chrome releases ship versions of tzdata that correspond to the version of tzdata shipped with the ICU it uses, and they do backport updates to prior Chrome releases within a certain window. Apple has a sideband way of deploying tzdata to all devices that doesn't appear via the normal Software Update mechanism. So it all depends on which particular OS/browser combo you're interested in and the decisions those owners made.

New comment by apaprocki in "Temporal: The 9-year journey to fix time in JavaScript"

apaprocki — Wed, 11 Mar 2026 16:20:36 +0000

I would characterize it more as Joda likely informed Moment.js, which better informed TC39 because it was within the JavaScript ecosystem. As we discussed in plenary today when achieving consensus, every programming language that implements or revamps its date time primitives has the benefit of all the prior art that exists at that instant. TC39 always casts a wide net to canvas what other ecosystems do, but isn't beholden to follow in their footsteps and achieves consensus on what is best for JavaScript. So my view is this more represents what the committee believes is the most complete implementation of such an API that an assembled group of JavaScript experts could design over 9 years and finalize in 2026.

New comment by apaprocki in "Temporal: The 9-year journey to fix time in JavaScript"

apaprocki — Wed, 11 Mar 2026 15:55:28 +0000

Node 26! Only a matter of time... :)

New comment by apaprocki in "Ghostmd: Ghostty but for Markdown Notes"

apaprocki — Sun, 08 Mar 2026 11:52:12 +0000

Welcome to the club. It’s like when people say “Bloomberg Terminal for X”. You just can’t really say anything because everyone knows it’s not Ghostty, based on it or will ever be it, but it’s about the vibe… and if you then chase after them, it only serves as free advertising :)

A First Look at the Future of the Bloomberg Terminal in the Age of Agentic AI

apaprocki — Mon, 23 Feb 2026 14:21:28 +0000

Article URL: https://www.bloomberg.com/professional/insights/press-announcement/meet-askb-a-first-look-at-the-future-of-the-bloomberg-terminal-in-the-age-of-agentic-ai/

Comments URL: https://news.ycombinator.com/item?id=47122702

Points: 1

# Comments: 0

New comment by apaprocki in "Ask HN: DDD was a great debugger – what would a modern equivalent look like?"

apaprocki — Mon, 26 Jan 2026 08:00:17 +0000

Check out Binary Ninja if you haven’t. Especially if you have large binaries!

New comment by apaprocki in "Some C habits I employ for the modern day"

apaprocki — Sun, 25 Jan 2026 19:54:46 +0000

I’m simply stating how actual Gtk is written:

https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gtk/gtklabel....

New comment by apaprocki in "Jurassic Park - Tablet device on Nedry's desk? (2012)"

apaprocki — Sun, 25 Jan 2026 19:44:08 +0000

Completely possible. In the early 90s everyone was buying SGI Indys to run Apache on and put the cool “Powered by SGI” badge on their site. I admin’d a local ISP then and that Indy was on my desk and IRIX was my daily driver. Their UI just felt leagues beyond other commercial Unices of the time, so rather than being plausible, I’d expect it due to the lab/science/dataviz aspect.

edit: Just last night a friend was watching MiB and Tommy Lee Jones looks at a Motif UI. It was obviously SGI but it was IRIS ViewKit and not the later Interactive Development Environment. Narrowed down likely creator being Van Ling from Banned From The Ranch Entertainment. If you’re out there…

New comment by apaprocki in "Some C habits I employ for the modern day"

apaprocki — Sat, 24 Jan 2026 15:45:07 +0000

Yes, using the same Gtk example, the way you’d forward declare GtkLabel without including gtklabel.h in your header would be:

    struct _GtkLabel;
    typedef struct _GtkLabel GtkLabel;
    // Use GtkLabel* in declarations

New comment by apaprocki in "Some C habits I employ for the modern day"

apaprocki — Sat, 24 Jan 2026 15:35:35 +0000

`-Wvla` Friends don’t let friends VLA :)

New comment by apaprocki in "Some C habits I employ for the modern day"

apaprocki — Sat, 24 Jan 2026 15:31:28 +0000

Sure, the parent was commenting more about the capability existing in Ada in contrast to C. Ada variable length local variables are basically C alloca(). The interesting part in Ada is returning variable length types from functions and having them automatically managed via the “secondary stack”, which is a fixed size buffer in embedded/constrained environments. The compiler takes care of most of the dirty work for you.

We mainly use C++, not C, and we do this with polymorphic allocators. This is our main allocator for local stack:

https://bloomberg.github.io/bde-resources/doxygen/bde_api_pr...

… or this for supplying a large external static buffer:

https://bloomberg.github.io/bde-resources/doxygen/bde_api_pr...

New comment by apaprocki in "Some C habits I employ for the modern day"

apaprocki — Sat, 24 Jan 2026 10:08:13 +0000

You can allocate dynamically on the stack in C as well. Every compiler will give you some form of alloca().

New comment by apaprocki in "Some C habits I employ for the modern day"

apaprocki — Sat, 24 Jan 2026 09:39:40 +0000

FWIW, Coverity (maybe others) has a checker that creates an error if it detects tagged union access without first checking the tag. It’s not as strict as enforcing which fields belong to which tag values, but it can still be useful. I’d much rather have what was proposed in the GCC bug!

New comment by apaprocki in "Some C habits I employ for the modern day"

apaprocki — Sat, 24 Jan 2026 09:33:06 +0000

In C++ you would have a protected constructor and related friend utility class to do the parsing, returning any error code, and constructing the thing, populating an optional, shared_ptr, whatever… don’t make constructors fallible.

New comment by apaprocki in "Some C habits I employ for the modern day"

apaprocki — Sat, 24 Jan 2026 09:19:10 +0000

You can play tricks if you’re willing to compromise on the ABI:

    typedef struct foo_ foo;
    enum { FOO_SIZE = 64 };
    foo *foo_init(void *p, size_t sz);
    void foo_destroy(foo *p);
    #define FOO_ALLOCA() \
      foo_init(alloca(FOO_SIZE), FOO_SIZE)

Implementation (size checks, etc. elided):

    struct foo_ {
        uint32_t magic;
        uint32_t val;
    };
    
    foo *foo_init(void *p, size_t sz) {
        foo *f = (foo *)p;
        f->magic = 1234;
        f->val = 0;
        return f;
    }

Caller:

    foo *f = FOO_ALLOCA();
    // Can’t see inside
    // APIs validate magic

New comment by apaprocki in "Some C habits I employ for the modern day"

apaprocki — Sat, 24 Jan 2026 08:56:41 +0000

I got the impression the author was implying because CHAR_BIT is enforced to be 8 that uint8_t and char are therefore equivalent, but they are different types with very different rules.

E.g. `char p = (char )&astruct` may violate strict aliasing but `uint8_t p = (uint8_t )&astruct` is guaranteed legal. Then modulo, traps, padding, overflow, promotion, etc.