Probably Germany
Our railways don't need sabotage - trains fail to run anyway.
Readit Newsmseepgood commented on Italy Railways Sabotaged bbc.co.uk/news/articles/c... · Posted by u/vedantnair
mseepgood commented on CSS now has an if() conditional function caniuse.com/?search=if... · Posted by u/aanthonymax
Give it enough time, every declarative language becomes a programming language. This is happening with all config files, markup languages, data formats.
The distinction between code, config and data is being erased. Everything is a soup now. Data is application, configuration is code. Code is an intermediate, volatile thing that is generated on the fly and executed in the temporary lambda containers.
So why do people still design declarative languages?
Never mind, I was wrong. Here’s a playground showing how go parses each one: https://go.dev/play/p/hyWPkL_9C5W
> Octals must start with zero and then o/O literals.
No, the o/O is optional (hence in square brackets), only the leading zero is required. All of these are valid octal literals in Go:
0600 (zero six zero zero)
0_600 (zero underscore six zero zero)
0o600 (zero lower-case-letter-o six zero zero)
0O600 (zero upper-case-letter-o six zero zero)
> Which makes sense, it's got the smallest language spec of any of them
I think go is fairly small, too, but “size of spec” is not always a good measure for that. Some specs are very tight, others fairly loose, and tightness makes specs larger (example: Swift’s language reference doesn’t even claim to define the full language. https://docs.swift.org/swift-book/documentation/the-swift-pr...: “The grammar described here is intended to help you understand the language in more detail, rather than to allow you to directly implement a parser or compiler.”)
(Also, browsing golang’s spec, I think I spotted an error in https://go.dev/ref/spec#Integer_literals. The grammar says:
decimal_lit = "0" | ( "1" … "9" ) [ [ "_" ] decimal_digits ] .
You're looking at the wrong production. They are octal literals:
octal_lit = "0" [ "o" | "O" ] [ "_" ] octal_digits .It gets more complicated if you do substring operations.
If I do s.charAt(x) or s.codePointAt(x) or s.substring(x, y), I'd like to know which values for x and y are valid and which aren't.
The values for x and y should't come from your brain, though (with the exception of 0). They should come from previous index operations like s.indexOf(...) or s.search(regex), etc.
mseepgood commented on The daily life of a medieval king medievalists.net/2025/07/... · Posted by u/diodorus
The supplicants brings to mind the opening scene of The Godfather.
I’m endlessly perplexed how a human with the same number of hours as me, can rule a kingdom, or run a modern country, or be CEO of a major company, meanwhile I’m working long hours every day and still get nothing accomplished.
Delegation is key
mseepgood commented on The daily life of a medieval king medievalists.net/2025/07/... · Posted by u/diodorus
So he only did four hours of actual work per day.
mseepgood commented on MCP: An (Accidentally) Universal Plugin System worksonmymachine.substack... · Posted by u/Stwerner
Is it some kind of CORBA?
mseepgood commented on Prompt engineering playbook for programmers addyo.substack.com/p/the-... · Posted by u/vinhnx
There is no such thing as "prompt engineering". Since when the ability to write proper and meaningful sentences became engineering?
This is even worse than "software engineering". The unfortunate thing is that there will probably be job postings for such things and people will call themselves prompt engineers for their extraordinary abilities for writing sentences.
You don't even have to write proper sentences. "me get error X how fix here code:" usually works.
I've achieved 3 and 4 orders of magnitude CPU performance boosts and 50% RAM reductions using C in places I wouldn't normally and by selecting/designing efficient data structures. TUIs are a good example of this trend. For internal engineering, to be able to present the information we need while bypassing the millions of SLoC in the webstack is more efficient in almost every regard.