1,734 karma · joined March 10, 2021
Python, JS, C, Bash aren't even particularly great at the problems they solve, but they succeed mostly on inertia (it's where all the libraries are, it's what people know) and occupying developer mindshare.
They are full of obvious design mistakes; things that not even the creators of the language (nor any of its users) can defend, yet those languages are used infinitely more than languages that eschew those mistakes. Why? Because they solve problems people have.
If this sounds terrible to you, the good news is that there is a tonne of low-hanging fruit in the programming language design space. Consider that most developers know nothing of sum-types, or eschew the idea of typing entirely. Consider that most developers see no fundamental problem behind having to venv or dockerise software lest it bitrot over a month. Consider that programmers actually use bash.
These terrible, obviously broken tools are somehow the most pragmatic things we actually have. The fruit is low-hanging; the door is wide open, if you wish to grab it.
I even applied at one point and heard nothing back. Looks like nobody else has ever heard anything back either.
Bizarre.
Here's just a couple examples off the top of my head:
- `$variables` in bash are subject to arbitrary code execution via word splitting without escaping
- PHP register_globals
- PHP, express, and some others parse `?a[b]="foo"` in a query string as an object, allowing for prototype pollution or other exploits
- string concatenation for SQL + escape_string being the default for years
- perl array expansion in function calls
- XML entity inclusion on by default allowing you to read arbitrary files
- log4j executing arbitrary code inside its logs
- passing a variable to printf's first arg
- no difference between escaped and unescaped tags in php
- xargs splitting on whitespace
- yaml allowing arbitrary code execution (it got rails good!)
and there's probably loads more.
are you sure you're running `./scriptname` or bash scriptname`
There are no proper sum types in C#, so 80% of the point isn't even there.
enum Season
{
Spring,
Summer,
Autumn,
Winter
}
... int PatternMatch(Season season) =>
season switch {
Season.Spring => 1,
Season.Summer => 2,
Season.Autumn => 3,
Season.Winter => 4,
// compiler can't prove the above code is exhaustive because no proper sum types
// compiler needs nonsensical branch here that diverges
_ => throw new ArgumentException("Invalid enum value for command", nameof(command)),
};I believe that patent has expired now at this point, but it's the reason StepmaniaX doesn't have receptors.
Similarly this is the reason games like Guitar Hero/Rock Band/ITG have hallway style viewports instead of straight lines. It was to mitigate the patents on having things scroll towards receptors in a straight line.
The whole things about "rules of hooks" should tip people off that it's sketchy. I mean, have you ever actually thought about how:
function Component() {
const [state, setState] = useState(1);
return <>{state}</>
}
actually works? How does `useState` know what bit of state to grab? (it's a global store identified by the function you're in, and an index. it's why you can't change the order of hooks nor call them conditionally).Hooks are literally javascript in the sense that they're functions you can call in javascript, but they don't operate under any of the rules people actually think of when they write javascript. If for any `function x() {}`, `if (condition) { x() }` was a fatal error, people would consider that terrible API design and the function shouldn't need to care whether it's called conditionally.
Sure, react hooks 'compose' better than class components, but they also don't compose *at all* with anyones mental model of how JS works. What they needed was different syntax or a DSL in general (what svelte does is a lot more understandable, imo).
[0]: jsx is a DSL but it's merely one bit of syntax sugar. they needed a hell of a lot more.
GWR is purely just marketing, none of their records should be taken with any merit.
It will then compile for that version.
utf-8 is a variable width encoding and if you treat it like ascii your software just isn't going to work outside of the ascii range.
i mean, it sucked, but it was kind of that middle layer.
Generally, everyone was using their own personal spreadsheets or ancient "just render everything" tables to analyse their scores and progress before this and I'm pretty happy with how it's turned out.
What I'm probably most proud of is that adding support for a new game is adding a new module for it - all of the other features automatically work with it. This turns a "each game needs to have its own full-site tracker" into a "each game needs a configuration for this one tracker", not unlike how LSP simplifies adding language support for editors!
Taught me almost everything I know about scaling a codebase, and despite being a niche tool it's picked up a lot of momentum (2k users, ~3m scores).
VR is not in the early days.