Can anyone working at #Netlify comment on the current discourse regarding small hobbyists with static sites having to unexpectedly deal with huge, sudden bills?
I aim to code a new toggle switch each day in 2024. But work comes first, and I fell a bit behind on this personal challenge... So, I coded 8 toggle switches this weekend using a single HTML element and CSS.
I'm only going to the @eleventy symposium to learn what the enemy is up to. I'm gonna Keep Making Web Sites Real Bad, actually. So bad, you won't even believe it. 😏
Today is comiCSS second anniversary. Two years ago, I started this "ridiculous" idea of having a comic about web development (in general) and CSS (in particular) fully coded in HTML and CSS. To celebrate, this last week I coded a daily carton (vs weekly) and collected all of them in this article: https://alvaromontoro.com/blog/68051/css-cartoons-for-comicss-second-anniversary
Has Chrome changed something on how the fonts are rendered? (Especially the bolds). It upgraded and now many sites (not all) look weird: bold text looks darker and thicker than on Safari or Firefox.
Design question: should a toggle switch have a pointer cursor? And a follow up: how about if the design is "not standard"?
I was leaning towards "no" based on checkboxes/radio-buttons not having a pointer cursor and pointer being for links. But then, if it's a custom design that is not standard, it may not be obvious that the element is interactive.
This slider is a single HTML tag styled with CSS. No images and no JS (apart from an inline command to update a CSS variable.) It's responsive and works on all major browsers.
So wait is it "nobody wants to work anymore" or "we have too many people working for us and need to lay off a bunch"? Help me understand I'm confused. 🙃
@dalias It's complicated. There's a thin line between the two... The poverty line.
Jobs that pay enough for living: "we have too many people and need to lay off a bunch".
Jobs that pay below poverty line: "nobody wants to work anymore".
Oh well....I guess it wasn't that complicated after all 😅😓
@aardrian It's a nice addition, but the implementation seems a bit rushed. The control doesn't scale properly and visually breaks when changing the zoom level.
@aardrian@SteveFaulkner Joke aside, there is no easy way to do it. Maybe not even a way at all. It is just frustrating that we are putting the burden and blame on (millions of) developers for not doing everything they can when this problem could (and should) be fixed by a handful of bad (and powerful) actors.