It’s amazing how everyone thinks this sculpture’s message doesn’t apply to them. “My side’s flags are different, it’s the other side’s flags that are bad”. So many people here making this argument. It’s beyond parody, yet really so predictable. Amazing lack of self awareness. I thought this place was more rational than Reddit, but apparently not!
Is it? Most people I know who have flags proudly displayed are left wing and their flags are usually one of: the Palestinian flag, the ukrainian flag, the LGBT rainbow flag, or the trans flag.
I wasn't asking it to define it. I came up with the list of principles first, then spent ages trying to think of a suitable name for them. It was quite gratifying when ChatGPT, without any context, when asked to guess what the term "freehold" might mean with respect to software, came up with almost the exact same set of principles. That told me that the "freehold" term is a pretty good fit. It would be an incredible coincidence otherwise.
When I posted about this project here and on reddit a few months ago I got a lot of people asking for advice and learning resources. I promised I'd one day provide a detailed write-up explaining everything, so here it is :)
unique_ptr is much better because then each object has a sole owner, which makes object lifetimes much easier to reason about and you can't end up with cyclic references causing memory leaks.
I wrote a game of Tetris in JavaScript with SVG many years ago. It had nice graphics and was smoothly animated. I hadn’t heard of anyone else using SVG like that at the time.
That’s not what I was saying at all. I was using Go as an example of what the experience of being helplessly outclassed by a superior intelligence is like: you are losing and you don’t know why and there’s nothing you can do.
> What's the difference between your "agentic AIs" and, say, "script kiddies" or "expert anarchist/black-hat hackers"?
Intelligence. I'm talking about super-intelligence. If you want to know what it feels like to be intellectually outclassed by a machine, download the latest Go engine and have fun losing again and again while not understanding why. Now imagine an ASI that isn't confined to the Go board, but operating out in the world. It's doing things you don't like at speeds you can scarcely comprehend and there's not a thing you can do about it.
I agree unfortunately. I might be a bit of an extremist on this issue. I genuinely think that building agentic ASI is suicidally stupid and we just shouldn’t do it. All the utopian visions we hear from the optimists describe unstable outcomes. A world populated by super-intelligent agents will be incredibly dangerous even if it appears initially to have gone well. We’ll have built a paradise in which we can never relax.
Couldn't agree more with the necessity for fast feedback loops. I've experienced the opposite, and it's not fun.
I worked with Clojure/ClojureScript (mostly ClojureScript) for a couple of years many years ago. It was the first time I'd worked professionally with a functional language, so I made a game of minesweeper in my free time to help get to grips with it: https://github.com/robjinman/cljsmines
Back then, I fully bought into the idea that functional language like Clojure were the future, especially on the web. The way application state is managed is perhaps the key virtue of functional programming - if you get it right, you can design your program to consist mostly of completely pure functions. I remember how enlightening that was once I understood it.
Interesting, I’ve only tried it on two machines - my (fairly old) laptop with integrated graphics and my desktop with an RTX4060. I’ve also tried it on the desktop on Windows in a Linux VM running Ubuntu 24.04. It runs way smoother on the laptop.
Thanks for trying it :)
BTW, is there a problem with the JavaScript on my website?
Double-entry bookkeeping is very easy to understand once you ditch the ridiculous "credit" and "debit" terminology.
Essentially, the goal is to keep the accounting equation true at all times. The equation is: Equity = Assets - Liabilities. Eventually, earnings (Income - Expenses) will become part of equity, so splitting that out, you have: Equity + Income - Expenses = Assets - Liabilities. Rearranging to get rid of the minus signs you get: Equity + Income + Liabilities = Assets + Expenses. This equation must be true or something has gone wrong - like money appearing or disappearing out of nowhere. To keep it true at all times, it should be clear that any time you add money to an account on the left side of the equation (say, to an Income account), you must either add the same amount to an account on the other side or subtract the same amount from the same side.
For example, you sell a lemonade for $5. You add $5 to Sales (Income) and add $5 to Current Account (Assets).
The "credit" and "debit" terminology is ridiculous because their definitions swap around depending on which account you're talking about, which is an utterly absurd (mis)use of language and the main reason people find this confusing.
