I don’t know who needs this but Gunship has a new album out and it’s awesome. https://open.spotify.com/album/4uAOIj4Sxh4sL6G0v5kykv?si=SHSb0OW7QDSQDxUz8rTKuQ
Microblog
Listening to the album Ocean Avenue by Yellowcard and realizing it is 20 years old this year.
Sometimes I miss CSS-Tricks. I really thought DO was gonna do a better job.
I've issued exactly one Cursorless command and I already feel the power coursing through my veins. https://www.cursorless.org/
✒️
Behind on my NaNoWriMo 2023 writing goal, as is the natural order of things.
This has to be the most poignant description of a font I’ve ever read. Also it’s a great font for anyone out there attempting #NaNoWriMo. https://indestructibletype.com/Drafting/
@tomfinley@wptoots.social Yeah WordPress itself is impressively backward compatible. Unfortunately PHP isn’t so much. I’ve been bit by breaking changes in PHP a number of times. Luckily, WordPress is actively developed and on top of things!
I often find myself humming the SMB 1 overworld theme. That has to be one of the most iconic pieces in the history of digital music.
@lewiscowles1986@phpc.social YES. I was thinking about that after hearing about PocketBase, which is an executable for a SQLite-powered backend.
I think the problem is the huge dependency trees. Small changes in dependencies end up snowballing until you’re forced to upgrade packages. And at some point, upgrading packages requires updating your code, which may or may not be feasible depending on the changes that would need to happen.
How does Slack not have syntax highlighting on code blocks? It's supposed to be *the* chat application for work. Discord’s code blocks are way better.
(Someone correct me if Slack does have this feature and I'm just using it wrong. But including a language abbreviation after the opening code fence doesn't seem to do it.)
🌌
Listening to the album Infinite Arms by Band of Horses while I work and, man, I forgot how good this was. #NowPlaying
I got an email announcing a State of React survey and SpamSieve flagged it as spam. I ain’t even mad.
“I’m not watching a horror movie tonight but I *am* doing a website migration which is its own kind of horror.”
GitLab don’t know how to act this morning. https://status.gitlab.com/
Continuing in my quest for nice Vue DX without build steps… I’ve learned two things:
- Even tho I’m using a downloaded ESM browser version, I can still install the Vue npm package and refer to its types from JSDoc.
- The composition API is much easier to type than the options API.
@kolombiken@strangeobject.space I just made this mistake the other day even though I know about the behavior. Rip.
Turns out you can place this over a function to explicitly type the `this` keyword.
/** @this MyType */
Vue devs, help!
Trying to get type support in regular JS using Vue’s ESM browser build.
Inside of the hasName computed value, VSCode thinks `this` refers to the `computed` object rather than the Vue app. What can I do here?
Another piece of nice-vue-but-no-build-step is using ES modules. That let’s me separate out components into their own files.
Still exploring type support, but adding a jsconfig.json with checkJs turned on is the first step. It kinda misinterprets things when using Vue’s options API, so it might be that the composition API is better for this use case.