Lady @Lady@cat.family

@wallhackio but it's winter

@gaditb oh i need to get back to writing this

@aschmitz i wish JSX was better standardized and less wedded to reactive rendering usecases but i’m otherwise not opposed to it!

it involved kissing girls

last night i dreamt an entire Catholic easter mass, except it was actually way better and more ceremonial than a real Catholic mass, it was still like several hours tho

@jamey i should probably add to this that i am quite fond of GNU Make, which is (at any high level of complexity) basically built on top of string templating, so

@aschmitz oh i don't mind tasty syntactic sugar, but i am bothered by taking something structured and treating it as tho it is unstructured. it feels like a lot of templating languages do this latter thing

@jamey unrelatedly, you know a lot about Atom feeds! i currently keep the full text of my blogposts in my Atom feed, which is good, but i worry it will result in a Quite Large filesize over time. i know i can use RFC5005 to paginate the feed, but do you have any thoughts on this besides? how big is too big for Atom feeds, or is size not really a practical concern?

did our recipe fail because we used european butter? or is it just a bad recipe? who can say

@jamey well, i prefer XSLT if the data source is XML. if the data source isn’t XML then you might have issues

let’s take a durable, easily‐processable, semantic, and structured markup format and let’s deal with it by ignoring all of that and substituting strings for other strings

is

<element name="h1" namespace="&xhtml;">
<value-of select="atom:title"/>
</element>

really better than

<h1>{{ post.title }}</h1>

?? no. but also yes

i’m not saying you should generate websites the way that i generate websites, but whenever i look at how other people generate websites i am very unimpressed

if you list programming languages on your profile i’m just going to assume you’re incapable of learning new ones