"I decided time zones should be abolished..."

It reads as tongue-in-cheek to me :)

Just right for the "Abolish everything" show https://nebula.tv/abolish

> Here’s a simple app my toddler made to generate toy trains[0].

Can you explain what you mean by this? How did a 3-year-old (or younger) meaningfully contribute to the design of this app? Do they know how to read?

Good question! He can't type and the local voice assistants can't really understand him...

He simply asked it to make toy trains, all I did was clean up the text to "create toy trains"

From that prompt, it goes through steps to build out a UI and any back-end functionality (Loops) needed.

To use it, he tells me what type of train to generate ("underwater"[0]) and I type in the prompt. He has a lot of fun with it!

[0]https://app.magicloops.dev/storage/v1/object/public/images/d...

Yes! Children of Time starts with a AI-capable civilization and proceeds from there. I won't give anything away, and I recommend going in cold! https://www.goodreads.com/book/show/25499718-children-of-tim...

Go has surprisingly good "UX", which I don't hear people talk about much. It compiles very quickly and gets out of your way. I've found it useful for a few reasons:

1. The standard library has a real HTTP/2 implementation (unlike Python).

2. The Go compiler creates statically-linked binaries and cross-compiling is painless.

3. Channels and goroutines make it relatively easy to write parallel code. There are certainly sharp edges, like every language.

It is also conveniently easy to compile everything into a single file, using embed, and this helps with deployment in a few ways.

I love how readable it is, even by people who don't know Go.

C looks friendly enough, but it has many nooks and crannies filled with undefined behavior (UB). If your program accidentally does something like overflow a signed integer, you're toast.

Raymond Chen has the best write up on UB that I've seen: <https://devblogs.microsoft.com/oldnewthing/20140627-00/?p=63...>.

In addition to the "obvious" undefined behavior, strict aliasing is subtle and poorly understood in my experience. Consider the following:

    Foo ReadFooFromBytes(const char* data, size_t len) {
        Foo foo;
        assert(len == sizeof(Foo));
        foo = *(const Foo*)(data);
        return foo;
    }

    Foo ConvertToFoo(Bar bar) {
        return ReadFromBytes((const char*)&bar, sizeof(bar));
    }

The `ReadFooFromBytes()` function could exhibit undefined behavior, depending on the provenance of its pointer parameter.

If you gave it a pointer to a true array of chars, it's fine. If you use `ConvertToFoo()`, big bada boom. Truly baffling stuff, the first time you encounter it.

What about "my business model relies on copyright infringement"? https://www.salon.com/2024/01/09/impossible-openai-admits-ch...

There's CBOR, but it is not nearly as compact as the C in its name implies.

Not trying to be mean, but there's not much content here. It's a definition of the term "stringly typed" (from another blog) followed by the idea of using appropriate types.

I guess the author is "one of today's 10,000", as they say. Wiktionary attests the term from 2019 but I'm sure I've been hearing it much longer than that.

The post is a true web-log. Someone logged something they learned and put it on the web.

I first heard of it from Jeff Atwood in 2012, loads of fun concepts here I reference often. Favorite must be "shrug report"

https://blog.codinghorror.com/new-programming-jargon/

I was working with the Torque Game Engine in like 2008 which had a scripting language where almost all data was strings. Vectors? String of three numbers with spaces in between. Looking back I think it was kind of TCL inspired. But I definitely heard it called "stringly typed".

xkcd has a relevant take on this: https://xkcd.com/1053/

TLDR, we should totally be celebrating learning in public

That's not just a take, that's the origin of the phrase OP used :)

In a beautiful meta moment, you are one of today's 10k about the origin of 10k :D

I'm witnessing...something!

I don't think arthropods are capable of informed consent, despite what the author claims.

FYI, the author is a woman.