HN user

5-

920 karma
Posts3
Comments284
View on HN

all of game boy advance and nintendo ds hardware is exhaustively documented in a single text file:

https://problemkaputt.de/gbatek.txt

(but you can replace txt with htm for a fancier version)

this ranges from physical description to compact arm instruction set reference -- you really only need this document (and a way to get your console to run your code!) to program completely from scratch.

i've picked up a dsi because it can load code from an sd card, so only the console, an sd card and a computer is required for programming it, but see https://news.ycombinator.com/item?id=47706877 further down this thread for the case for preferring the gba.

doesn't the same argument apply to ordinal dates? i see some people on hn also using longnow-style five-digit years, but i really can't see the point.

did the crossing of the rhine take place in 00406, 0406, or 406? what extra information do the two former styles convey?

also, what about the year 100000?

we are somehow doing just fine without leading zeroes for other quantities.

there is an argument to be made about e.g. iso8601 datetime formats that need to be lexicographically sortable; but i don't see any of the longnow fans using anything like those.

Making a brochure. You need a photo of a happy family.

do you really?

you don't quite know what the panels need to look like.

look at your competition, ask your users, think?

Most people know they can't fly a plane

this isn't how llm products are marketed, and what the tfa is complaining about.

as long as you remember what you've built

yes! like any craft, this works only if you keep practising it.

various implementations of k, written in this style (with iterative improvements), have been in constant development for decades getting very good use out of these macros.

indeed. with how good and cheap/free decompilers have gotten over the years my preferred way to read abstraction-happy c++ and rust code is to compile it with optimisations and debug symbols and then read the decompiler output.

perhaps it's a trivial observation that people tend to conflate the programming language in the strict sense (syntax, semantics, compiler implementation etc.) with its standard and/or community libraries and tooling.

of course these are very important, but perhaps i'm just a language nerd/pedant who gets confused when an article about a programming language tends to be about async i/o libraries.

If you sit down and write out what you might want a robot to do for you: a lot of tasks end up being kind of wet.

yes, but i thought this wasn't that kind of article.