My boss has obligated me to install VSCode and do a TypeScript project instead of a perfectly working Clojure one. We are a Clojure shop, but sacrifices have to be made, I guess. Sitting there for an hour waiting for VSCodium to compile. Hit full RAM clogging thrice already. And I've not even touched TypeScript yet! Uuuuuuuugh.
(I know that TypeScript knowledge might be a good asset, but I want to stay in my productive Lisp niche for as long as possible.)
I don't get it. Why do people use dates as identifiers for blog posts? It's neither descriptive nor memorable. The only benefit I can see is the provenance for when a certain thought was born. But, even then, one has to look into the files and see the post titles/descriptions.
And then, date information can be inferred from filesystem/version control. Coupled with descriptive post filenames, this makes provenance tracking extremely easy. So the only benefit of dated posts I can think of is... awkwardly redundant?
Really, why use dates as post identifiers?
There's a worse system—unique IDs (or even UUIDs) for each post. But let's discuss dated posts first.
Oh, so #Mustache doesn't support recursive tag expansion. I.e. you cannot have your data contain text with mustaches in it. It will be inserted verbatim/escaped, without being interpreted by Mustache. Or, at least, that's how reference implementation works—the spec is quite lacking in these matters.
Yet another reason for me to stay with #ed as my static site generator.
Comment in the corporate codebase I'm working with:
> NOTE: do not forget to do something with it
The problem is: the person that wrote this comment is no longer in the company and likely forgot what this "it" and "something" might mean. #theRant
It sucks that #Linux tech is fragmented in terms of fonts. Like, the most sensible behavior for fonts is using one main fonts and falling back to other fonts when a given #Unicode codepoint is not found in the main one. But! my window manager uses raw #X11 APIs for text output, and these are primitive enough to just display ??? when they encounter an unfamiliar glyph. Which is... too often, because I have a lot of #Russian and a bit of #Armenian in the stuff I window manage. So I have to guess what all these question marks mean. Not cool.
Who in the world though it a good idea putting their custom readtables into libraries intended for outside use? I don't want your hash table syntax, I want MINE. Don't pollute the readtable and other aspects of someone else's image if you're providing a library. The library you're making should be portable and clean #CommonLisp, not some unreadable #DSL you use in your #REPL. It's fine in the REPL, but not in libraries. Keep it clean. Simple courtesy.
Not pointing fingers, but everyone doing that shall be ashamed.
I'm installing VSCodium, and it has already eaten up 5GB of my disk space. And I have only 80GB left. I'm scared and unsure whether removing VSCodium will get my disk space back.
Unsubscribed from a really annoying mail spammer that got my email from the job search bot. But this annoying company is not the worst thing in the situation. The worst thing is: their subscription canceling form had a single button _that didn't work without #JavaScript_. Like hey, you have a single button and a wrapping form, just send a simple POST request! Ugh.
Artyom Bologov