IndieAuthenticated.

A step-by-step guide to signing in users with IndieAuth, mostly as an aspirational own future reference I will tell myself I will totally use (then probably never will . . . oh well).

2021-06-24T09:10:16+10:008th July, 2021|Tags: , , |

‹script src=haxx0rd.js›

As someone who spends a non-zero amount of time trying to explain to developers that, yes actually, the code they’re just randomly importing into the environment from npm is actually a massive, massive security vulnerability and they need an active plan to manage it, this post is basically my nightmare scenario…

Edit: Also, TIL apparently WordPress doesn’t sanitize HTML out of post titles.

2021-02-26T07:48:19+11:0018th March, 2021|Tags: , |

Over-React.

modern web dev is an extreme overreaction to not liking some php

Scott Jehl says R.I.P. to his mentions.

One of the things that bugs me so much about modern webdev is that, if things had been (gestures around) Like This when I was a Callow Young Lass, I never would’ve started programming. Never. I’m here because Back In My Day pretty much anyone could, at any time, vomit up a shared host webserver with PHP (and, before that, CGI with languages like Perl and even C) and start hacking away making crappy little webapps that did exactly what people wanted them to in all kinds of weird and wonderful ways. Things like fanlistings and guestblocks1 and even blogs and Facebook wouldn’t exist if this quick and dirty little homebrew ecosystem hadn’t existed.

Nowadays even looking under the hood of WordPress—something that’s even written in a language I know pretty well—makes me exhausted.2 Why is everything so abstracted? Why so many libraries? Why are the libraries so big? Why is every webpage downloading like fifty megabootoos of JavaScript? Why are the entire contents of everyone’s databases dumped to the browser as JSON regardless of what the page is actually loading? Why do I need to roll up esoteric command-line container infrastructure every time I want to fart “Hello world?” Why does React look like hot fucking garbage and why does everyone insist on using it to make their website look like hot fucking garbage, too?

“All that shitty PHP you used to write was pretty shitty, though.”

Uh. Yeah. It was. But, like. So what?

It got people coding. It got girls—and other people not traditionally positioned in the STEM-to-FAANG pipeline—coding. It was basically the indie craft scene for the internet and it was wild, man, and it just… doesn’t exist anymore? Everyone is too busy trying to scale Kubernetes architecture and write The Next Facebook after their one week at Reactcamp and yes, I am Too Old and yes, I freakin’ hate it.

“Yeah but you can use GitHub and a static site—”

First of all, GitHub is Microsoft. Just say it: Microsoft GitHub. I can use Microsoft GitHub to what, exactly? Increase its parent company’s stock price? Go fuck yourself.

More importantly: the fact that the random little shit we used to write was interactive was the point. We made little community tools for our little community. Static site generators are for jaded fucking hipster nerds who spend all their socializing time whining on Twitter about how Twitter sucks and T.I.N.A. as if all of this isn’t related somehow.

Where is my small shit code for small shit projects? Where are my tools or languages or frameworks that aren’t designed to serve the financial and architectural needs of a pile of rusted Silicon Valley titans? Yeah, PHP had problems and it produced a lot of shit (ref: Facebook) but at least it didn’t require a hundred thousand dollars of vendor bootcamps and a subscription to MSDN to get anything done with it.

Ugh.

  1. Remember those? They were like… kind of like a guestbook but made up of little pixel tile images that looked like stacked-up blocks. They were extremely cute. Assuming you had enough Internet Friends to, like. Use them. Which I did not. []
  2. And don’t even get me started on fucking Composer… []
2020-12-18T14:34:21+11:005th January, 2021|Tags: , |

文言。

An esoteric programming language designed to look and read like classical Chinese literature.

For the non-compsci set, an esoteric language is one that’s mostly meant “for funsies”, rather than something intended for wide scale use. Generally they can be used in this way—programming languages are for humans to understand, and by the time the code gets to the computer itself it’s been translated through several other layers of increasing abstraction anyway—but their oddball natures tend to make them, at minimum, difficult to write and even harder to maintain. But they’re pretty popular all the same, because programmers are Like That…

2020-01-29T12:36:55+11:0028th May, 2020|Tags: , |

gatekeeping.js

As someone whose (primarily web-based) programming output decreased in inverse proportion to the rise of JavaScript, I really feel this article a lot…

2019-01-03T09:25:10+11:005th May, 2019|Tags: , |

Emoji code.

Swift, Apple’s multi-purpose programming language for its various platforms, apparently supports full Unicode.

The actual intent of this is to assist programmers whose native languages use non-Roman character sets. The practical result is that it means you can type code that looks like:

infix operator ⛏ {}
public func ⛏(set: Set, count: Int) -> Set {
    func rnd(i: Int) -> Int {return Int(arc4random_uniform(UInt32(i)))}
    var items = set, chosenItems: Set = []
    (1...count).forEach { _ in
        let whichOne = items
            .startIndex.advancedBy(rnd(items.count))
        chosenItems
            .insert(items.removeAtIndex(whichOne))
    }
    return chosenItems
}

Set(["a", "b", "c", "d", "e"]) ⛏ 3 // pick 3 members
2018-04-27T13:58:50+10:002nd April, 2016|Tags: |
Go to Top