Hans Hofner's Blog šŸ—

Latest posts

See all posts

Latest Pictures

See all pictures

Devlog

See all devlogs

  • Some tech opinions as of recent:

    With all my musings I always come back to the very often suggestion that ā€œthe best stack is the stack you know the bestā€, that is, just use what youā€™re most proficient in and ā€œjust buildā€. Of course, me being me, I decide not to stick to this. I probably have used Vue most in the last 3 months or so, and probably know it best. But I just donā€™t want to use it anymore. Reasons being is that itā€™s a heavy SPA framework and itā€™s heavily tied to VSCode. Recently Iā€™ve been trying to move over to using Helix as much as possible, and Vue being a non-editor agnostic framework, has made it less appealing to me. Sure, setup for Vue in Helix is doable but it kind of goes against my initial reason for investing time into Helix, and that is that I barely touch the configuration. Vueā€™s LSP setup is super finicky and actually just awful to set up in anything other than VSCode. So I donā€™t want to use it anymore.

    Iā€™ve been trying to explore what other things there are out there. I donā€™t have much interest anymore in touching things like React, Svelte, Solid, Qwik, etc as they are just kind of the same to me. I am looking for things closer to vanilla JavaScript. Why not just vanilla JavaScript? Well, I do try to use it but often find myself struggling with the pain points that the above frameworks do solve. So ideally, something lightweight on top of JS, maybe JQuery? Iā€™ve used it once before and to be frank was a very nice experience. I guess this comes down to what Iā€™m building these days. Most of what I am buildingā€¦Iā€™m not sure if a framework is justifiable. Iā€™m also progressively believing most of whatā€™s built online really does not need to reach for a framework, in part thanks (or not thanks) to Alex Russelā€™s notes (hatred?) towards (JS) frameworks.

    I briefly touched VanJS, a ā€œultraā€ lightweight JS library. It seems really good actually! And I like that itā€™s no build tool based. Iā€™m starting to image a new stack of tools that I actually like and can continue building with.

    That then brings me to OpenProps. Itā€™s a CSS ā€œlibraryā€ that just basically provides tons of variables and a healthy CSS reset. The standard defaults it provides is like Tailwind, which you can just build off. I love this because while I kind of understand how nice Tailwind can be, I often find myself just absolutely hating the markup. Itā€™s awful to read and the more complex CSS gets the more awkward it gets. Any type of custom animation ends up being written as normal CSS anyways, and I personally really, really dislike conditional class rendering with Tailwind. Itā€™s hard for me to understand. Modern CSS is so powerful too nowadays, I wonder why we restrict ourselves to doing everything in strings. And on that note, one thing I like about modern CSS is nesting, which I think helps with readability of the styles tremendously.

  • I am exploring BiomeJS. I really wish for it to be the final solution to ā€œlintingā€ and formatting in JavaScript projects.

    For some time I was trying to use just eslint, with some opinionated rules. I donā€™t have too many particular opinions on formatting, just that itā€™s easy to read, which I find most peopleā€™s to be, so thatā€™s why I look to use other peopleā€™s. Unfortunately eslint formatting was not very good, and I often wished to go back to Prettier. So I guess I do have some opinions.

    The reason I chose to not use Prettier, is because I disliked the idea of adding yet another dependency when eslint, which seemed to be doing the same thing, was enough.

    So, here I am looking at BiomeJS. In particular, I am looking at setting it up with Zed. It looks to be okay, but now I have to see what I have done with the config. It has changed quite a bit since I last wrote about using eslint to format.

  • I guess thatā€™s what I get for using ChatGPT. The script that would create an entry in my devlog from the Drafts app would just take the first line and make a slug from it. I ended up with huge slugs.

    So Iā€™m using this small script now to generate IDs for the slug, even though itā€™s not really needed. I do plan to allow to access these devlogs via a link, though.

    function getSlug(_content) {
	// var slug = content.match(/^slug: (.*)$/m);
	// if (slug) return slug[1];
	// var firstLine = content.split("\n")[0].trim();
	// if (!firstLine) throw new Error("No valid title found");
	// return firstLine.toLowerCase().replace(/[^a-z0-9]+/g, "-").replace(
	// 	/^-|-$/g,
	// 	"",
	// );
	return "id" + Math.random().toString(16).slice(2);
}

Socials

Tags