zkldi

Hi leerob,

Where is the support thread?

I have ticket T-D95851 at the moment, if you could get someone to resolve it. I do not want to use cloud agents.

Thanks

zk

AI slop article. It wasn't just X. It was Y.

Also, $500/mo for 64GiB of RAM and 16 mystery meat CPUs. LOL! You guys are all being ripped off and you don't even know it.

All of these replies are AI slop.

AI slop article, sorry.

It's just not what the word axiom means nor how anyone uses it. An axiom is unprovable by definition - is it a thing we accept to be true because it is useful to do so (e.g. there exists an empty set)

"Provably Correct Axiom" is nonsense. An axiom is unprovable.

Just "provably correct" would've been fine. This chess stuff is hilariously pretentious.

Jesus Christ. We've made the psychosis machine.

I just don't understand how this can be this slow. What on earth is it doing to get 193 requests per second on static, cached content?

The article doesn't dig too deep into this sadly, rather just accepts that it's slow and uses a different tool.

But seriously, this is responding to a request with the content of a file. How can it be 100,000x slower than the naive solution. What can it possibly be doing, and why is it maxxing out the CPU?

If no-one else looks into this, I might get around to it.

But this isn't even true, and NextJS is well into egregiously complexity. Remix was an alternative option in the space that is now deprecated in all-but-name for React Router v7, which (for those just tuning back in), react router is now a framework.

If you wrote your app in NextJS 2 years ago, you would already have to rewrite chunks of it to get it to compile today. These tools are NOT solidified, they are releasing breaking changes at least once a year.

The blog post you've linked doesn't justify what you've said about it at all.

In the netflix blog post they're complaining about increasing latency over time because they have a function that *reloads all express routes in-memory* that didn't properly remove all the previous routes, so the routes array got bigger and bigger. That's not a fundamental problem with express[1], that's an obscure (ab)use case implemented wrong. Hardly a damning indictment of express.

This turned out be caused by a periodic (10/hour) function in our code. The main purpose of this was to refresh our route handlers from an external source. This was implemented by deleting old handlers and adding new ones to the array. Unfortunately, it was also inadvertently adding a static route handler with the same path each time it ran.

[1]: Admittedly an array is not the "best" data structure for routing, but that absolutely wasn't the performance issue they were having. Below a couple thousand routes it barely matters.

Extremely misleading title.

The software in question is the winning entry in a hackathon from 2020: https://github.com/DevrathIyer/ballotproof

Inside that repo they have a script called `generate.py` which generates ballot test data.

Look at it for yourself: https://github.com/DevrathIyer/ballotproof/blob/master/gener...

It's a ~100 line python script that generates some test data. The last commit on is as naive as "hope this works".

What a horrendously misleading title. It's just some kids making something with OpenCV to scan images. Ridiculous.

I'm in the same boat. Where did you move to?

An interesting one is "bread" to refer to money; I believe it comes from cockney rhyming slang. Bread and Honey = Money.

cargo is a bad example as it's universally `cargo build`.

Make on its own is great but most of the time I've worked with C projects it's been cmake/autotools + global pkg installs, which you Do have to frequently look up.

That makes sense to be honest, I thought it was intentional but then seeing so many other maths errors in other DFW works led me to believe it might very well not be.

There's quite a lot of mathematical mistakes (obvious ones, even) in DFWs work. I'm not sure whether it's intentional or not, but given that he also makes mistakes in his nonfiction it might just be that he's not a great mathematician.

Like in TPK, 0/0 is Infinity and in IJ, Pemulis explains differentiation completely incorrectly, also that stuff about the mean value theorem is irrelevant?!?

Still one of the greatest authors; deep technical correctness is more of a Pynchon thing.

I'll bite: What specific parts of rust syntax do people find so ugly?

I keep hearing this from decent chunks of people who don't write rust, but the language doesn't seem that far off C to me. It's certainly no haskell.

[...] You've heard of the Kirghiz Light? well that's the ass end of a firefly compared to what we're gonna—oh, you haven't heard of the—oh, well, too bad. [...]

Could you give any examples of syntax you've hit that didn't make sense or seemed awful?

an errant comma after the last object property doesn't cause any issues

Tools win not because they are "better" in some platonic ideal of a programming language but because they are more practical for solving the problems people have.

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.

Weird. I've seen this exact job posted by this exact company every single month for the past year.

I even applied at one point and heard nothing back. Looks like nobody else has ever heard anything back either.

Bizarre.

What's rule 0?

why isn't the default secure? if the default isn't secure we have learned time and time again that people will use the default unknowingly exposing themselves to security holes.

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.

that's on you i think. quite a lot of people enjoy tofu and it's a cute name imo.

both of these scripts break on perfectly valid filenames with whitespace, it's pretty rough how shell scripting directs you towards writing subtly broken scripts.

the shebang is literally handled by the kernel, so fish has nothing to do with this here.

are you sure you're running `./scriptname` or bash scriptname`

C# doesn't have anything resembling proper pattern matching. C#s pattern matching is akin to a marginally improved switch or if/else-if chain. C#s pattern matches aren't exhaustive, and the compiler doesn't properly check them at all.[0]

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)),
    };

that's not using `try` as an expression. can you do `let foo = try <code> (plus some handling for diverging in the other case?)`

fun addendum: StepmaniaX doesn't have note receptors because konami's patents for DDR are so broad that the idea of notes scrolling towards a visible note outline is something they can sue you for.

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.

BUT HAVE YOU SEEN MY TECH STACK?