Notices by Cecilie 🧙‍♀️ (cvennevik@hachyderm.io)

@aral I'm planning on storing the data in a plain JSON file, so I can easily sync it between devices and potentially create new (non-JavaScript?) apps to work with it!

@aral I was wondering about pinging you and asking 😊 I might just try it out!

Maybe what I'll have to end up doing is building the app in several different frameworks and comparing them!

(That sounds like the kind of ambitious thing that I'd love to do and, of course, never get around to)

I want to make a web app for viewing, creating, and modifying entries saved to a local file. I will use it on my old budget Android phone, and I want it to be as performant as I can possibly make it.

What do I use to build it?

#webdev

This is... such a good tutorial and now I'm going to rework my website's font sizes.

https://www.joshwcomeau.com/css/surprising-truth-about-pixels-and-accessibility/

@aral Oh I do want to check this out. Not sure I have the right use for the tech but I'm so charmed by the packaging.

@aral Kittens!

I've heard all this praise for Tailwind CSS and when I finally look into what it actually is I find out it's a framework for doing inline styles but using class names instead.

Hmm.

I mean I bet Tailwind is a nice way of writing inline styles but also I really don't vibe with writing inline styles. Traditional, semantic CSS with class names describing what it *is* instead of how it *looks* is so much more pleasant for me to read.

Long strings of Tailwind classes reminds me of div soup.

I am inclined to work closer to native HTML and CSS where I can. It's what actually renders in the browser, it's what all frameworks are built on top of, it's tech that will survive a thousand hype cycles, and it's usually possible to write simpler code in it.

Opting to place an abstraction layer of utility CSS classes between me and the actual CSS puts me off.