Map (Int, Int) Int. Kind of a bad example because tuples have special-case infix syntax, the general case would be Map Int (Either Int Bool). Follows the same exact syntax as function application just that types (by enforced convention) start upper case. Modulo technical wibbles to ensure that type inference is possible you can consider type constructors to be functions from types to types.

…function application syntax is a story in itself in Haskell because foo a b c gets desugared to (((foo a) b) c): There’s only one-argument functions. If you want to have more arguments, accept an argument and return a function that accepts yet another argument. Then hide all that under syntactic sugar so that it looks innocent. And, of course, optimise it away when compiling. Thus you can write stuff like map (+5) xs in Haskell while other languages need the equivalent of map (\x -> x + 5) xs (imagine the \ is a lambda symbol).

The actual reason why let … in syntax tends to not use C-style “type var” like syntax is because it’s derived from the syntax type theory uses, and type theorists know about parameterised types. Generics, in C++ parlance, excuse my Haskell:

let foo :: Map Int String = mempty

We have an empty map, and it maps integers to Strings. We call it foo. Compare:

Map Int String foo = mempty

If nothing else, that’s just awkward to read and while it may be grammatically unambiguous (a token is a name if it sits directly in front of =) parser error messages are going to suck. Map<Int,String> is also awkward but alas that’s what we’re stuck with in Rust because they reasoned that it would be cruel to put folks coming from C++ on angle bracket withdrawal. Also Rust has ML ancestry don’t get me started on their type syntax.

Sandwich.hs:6:11: error: [GHC-83865]
    * Couldn't match type ‘Bread’ with ‘Cucumber’
        Expected: Bread
        Actual: Cucumber

This wouldn’t have happened with Burritos.

Yep exactly that. A fascinating side-effect is that models become better at logic when you tell them to talk like a Vulkan.

Is that some new-fangled GNU thing? It’s certainly not POSIX.

Should be \~ in most shells, certainly bash. Use mkdir and rmdir when messing around to prevent accidents.

Your ld.so contains:

Entry point address: 0x1d780

EDIT: …with which I meant, modulo brainfart: My libc.so.6 contains a proper entry address, while other libraries are pointing at 0x0 and coredump when executed. libc.so is a linker script, presumably because GNU compulsively overcomplicates everything.

…I guess that’s enough for the kernel. It might be a linux-only thing, maybe even unintended and well linux doesn’t break userspace.

Speaking of, I was playing it a bit fast and loose: _start is merely the default symbol name for the entry label, I’m sure nasm and/or ld have ways to set it to something different.

Did you know that main is usually a function?

How does executing a program actually work?

Way too long an answer for a lemmy post

It has an executable flag, but what actually happens in the OS when it encounters a file with an executable file?

Depends on OS. Linux will look at the first bytes of the file, either see (ASCII) #! (called a shebang) or ELF magic, then call the appropriate interpreter with the executable as an argument. When executing e.g. python, it’s going to call /usr/bin/env with parameters python and the file name because the shebang was #!/usr/bin/env python.

How does it know to execute “main”?

Compiled C programs are ELF so it will go through the ELF header, figure out which ld.so to use, then start that so that it will find all the libraries, resolve all dynamic symbols, then do some bookkeeping, and jump to _start. That is, it doesn’t: main is a C thing.

Is it possible to have a library that can be called and also executed like a program?

Absolutely. ld.so is an example of that.. Actually, wait, I’m not so sure any more, I’m getting things mixed up with libdl.so. In any case ld.so is an executable with a file extension that makes it look like a library.

EDIT: It does work. My (GNU) libc spits out version info when executed as an executable.

If you want to start looking at the innards like that I would suggest starting here: Hello world in assembly. Note the absence of a main function, the symbol the kernel actually invokes is _start, the setup necessary to call a C main is done by libc.so. Don’t try to understand GNU’s libc it’s full of hystarical raisins I would suggest musl.

Pure SQL, as in relational algebra, is LOGSPACE/PTIME. Datalog is PTIME-complete when the program (“query”) is fixed, EXPTIME-hard otherwise.

It’s all quite tractable, but there’s definitely turing-complete declerative langugages. Not just pretty much every functional language, but also the likes of prolog.

Functional is also declarative because control flow is implicit/unspecified.

What’s actually missing is logic programming, of which the likes of SQL are a subset.

It’s fine memes are permitted to make jokes and it’s more of a paradigm than vibe coding.

The one paradigm that’s actually missing is logic programming, I would’ve gotten rid of unstructured to include it. The whole paradigm thing really only started with Dijkstra’s rant about unstructured gotos (not the ones C has, in C you can’t jump to the middle of another function).

Not reliably, no. Python is too dynamic to do that kind of thing without solving general program equivalence which is undecidable.

Use a static language, problem solved.

NixOS. Gentoo gets into trouble when you need multiple versions of the same library at the same time. Also while the infrastructure supports it it’s annoying that gentoo doesn’t provide pre-built binaries, like yes some people might want to have reason to build their own bash but I think I’ll be fine with a standard build. NixOS? If you install something usually it’s going to be pre-built. Change a couple of configuration flags? May or may not be pre-built. You want to apply a custom patch? It’s going to seamlessly build from source.

Not really, they’d clash all the time. 8080 is the default port for a non-privileged webserver, that is, web server, something you put your own stuff on, not applications/daemons that happen to have a web interface. E.g. ComfyUI uses 8188 for its web interface, deluge 8112, neither will serve your index.html.

Because PATH_MAX is? Also because it’s a 4k page.

FILENAME_MAX is not safe to use for buffer allocations btw it could be INT_MAX.

255, generally, because null termination. ZFS does 1023, the argument not being “people should have long filenames” but “unicode exists”, ReiserFS 4032, Reiser4 3976. Not that anyone uses Reiser, any more. Also Linux’ PATH_MAX of 4096 still applies. Though that’s in the end just a POSIX define, I’m not sure whether that limit is actually enforced by open(2)… man page speaks of ENAMETOOLONG but doesn’t give a maximum.

It’s not like filesystems couldn’t support it it’s that FS people consider it pointless. ZFS does, in principle, support gigantic file metadata but using it would break use cases like having a separate vdev for your volume’s metadata. What’s the point of having (effectively) separate index drives when your data drives are empty.

awk is practically made for record processing, within the shell you can set $IFS. The reason so many ancient UNIX file formats use : as separator is because that’s the default setting of $IFS.

It’s all a huge PITA, though. I mean there’s a reason why people started using perl instead. Nushell is great for that kind of stuff, even more so if you have random json or such lying around it loads just as easily. “Everything is a string” was a mistake.

You quit it just like you quit ed or ex, just that you have to enter the prompt (:) yourself as vi is not by default in prompt mode. And you should know ed, ed is the standard editor.

I use Helix btw.

The large initial percentage of female coders was due to computer having been a female job, because secretary was. Their role within companies didn’t change, what changed is that they were using machines to do the computing instead of doing it by hand.

We’re kinda lucky to have the woke trifecta (Ada, Grace, Alan) (first programmer (woman), inventor of compilers (woman), absolute unit (gay)) to keep the chuds at bay. Even if we weren’t all socially inept nerds (or pretending to be so to bosses) there’s only so much you can do, culturally, if the population is growing exponentially. Uncle Bob (yes I know he’s a chud) did the maths at some point IIRC it was something like the number of programmers doubling every two years. Which also means that at any one point in time roughly 2/3rds of programmers have no idea what they’re doing, which explains the javascript ecosystem.