Origami is a new programming language that complements HTML and CSS for making small- to medium-scale websites.
This certainly looks intriguing.
Via: Mastodon
🔗 Ente - Private cloud storage for your photos, videos and more
Might be a suitable system for my photos should I want to get off Google Photos.
Via: Mastodon
🔗 YouTube: Replace batteries numpad Sculpt Ergonomic Desktop
It’s surprisingly complicated to open up the battery compartment of the Sculpt number pad. This video proved to be very useful.
TIL: CR2420 button batteries are not the same as CR2032, no matter what your eyes say to you.
🔗 Incomplete JSON Pretty Printer
This looks pretty useful. Requiring JSON to be syntax correct prior to formatting it is a huge pain.
Via: Simon Willison
I’ve started keeping links to interesting posts and software packages on a separate link blog. These links would usually go into my Linkding instance, but I may repurpose that for things I’d like to revisit later, whereas this site will be more of an archive of things I’ve seen.
This site, now served from Europe. 🇪🇺
Okay, I too tried out ChatGPT’s new image generator, mainly it’s graphics design capability. Got it to generate a logo for our bocce club. I’m impressed by the results: it’s pretty much what I imagining.
A bit more on the Godot game this morning, this time working on background tiles artwork. Made some grey masonry tiles for the end castle sequences. Also tried some background rocks for underground areas. I’m pretty rubbish at anything organic, but they didn’t turn out too bad.
It pains me that Forgejo’s CI “pipeline running” animation spins anti-clockwise, as if you’re going backwards in time. A metaphor, perhaps? Services get undeployed, binaries go back to the source code, projects return to their seeds of ideas. 🤔💭
Oh, build’s done. Never-mind. 😀
I don’t think I’ve ever regretted spending money on a solo or small team’s online publication. Sure I’ve cancelled subscriptions when I lost interest, but it’s not like I’ve said to myself that I wish I’ve never signed up in the first place.
I always felt a little sorry for the front-end developers on their team: always under the pump when UI changes come through, and well… (whisper) the tooling. So it was a suprise to hear one frontend dev who’s starting doing backend work that he always felt sorry for us backend devs: having 10 different services that we need to change and worry about.
The grass is always greener… eh. Well, actually it’s more like the reverse: as in our grass is greener and we fell sorry for our neighbour who just can’t get a lawn established.
One thing I’m noticing on Bluesky: very few hashtags in posts, including those in the Discover feed. I expected a hashtag-per-post ratio closer to that of classic Twitter, but it seems closer to that of Mastodon. It’s nice.
Now that trains are running again, it got me wondering whether my temporary commute, where I drove to a nearby station, is worth keeping. I don’t think it is. It got me into work earlier, which is nice, but with all the road traffic, getting home was slower and more of a hassle.
Added a few final things to my Godot game, such as a really boring title and end-title screen, before preparing a release for play testers (or play tester, I’ve got exactly one lined up). I think we’re ready.
Seeing sponsored features in Vivaldi is… well, it is what it is: they need to make their money somehow. And atleast they’re easy to remove. But I’m left wondering if Netscape’s attempted approach of charging people for a browser was the better way to go in the long run.
Two awesome vessels: a water bottle I got from AWS reInvent, and a keepcup I bought at Coles. What makes them awesome is that they’re double-layered, so my coffee stays hot and my water stays cool.
Still wishing for MR review software that allows one to make private notes. Some of the reviews I’m looking at today are quite large, and it would be good for me to annotate things I’ve seen. I could use notes or something, but UI for marking up the code is already there.
I’m finding, as I go through my Godot journey, that a good indication that a particular approach to a problem is the one preferred by the designers, is the amount of “infrastructure” that goes into making that approach easy to execute.
Case in point, I ran into an issue in my Godot game yesterday, where a nested scene, one included in another nested scene, was unable to get a unique node near the root of the tree. After a bit of reading I learnt about groups, which look to be a way of collecting nodes, regardless of where they are in the tree, in a group that is easy to reference later.
This indeed solved my problem, but it was’t my first approach. There were ways of traversing the tree to find the node in question that I explored first. And I probably could’ve gotten that to work with a bit less-than-great of code. But given that there are 10 methods that deal with groups on the SceneTree class, along with UI in the editor to create and manage groups, it’s clear that groups was what the developers intended as the right approach.