Developing is still a good option. I develop then scan my photos. Color is arguably easier to develop than b&w, you need a constant temperature and time but you don’t have to worry about pushing or pulling.
> Color is arguably easier to develop than b&w, you need a constant temperature and time but you don’t have to worry about pushing or pulling.
Color may be easier nowadays because sous vide cooking gear is fairly inexpensive, and lets you keep temperatures constant. It was much harder to do this in the past, so B&W was easier (chemical-wise).
"Worrying" about pushing and pulling with B&W is an advantage to some because it lets you tweak your final print compared to what your exposure is.
Per Bruce Barnbaum, put your shadows in Zone IV so you don't lose information, and then print it down to Zone III:
I know nothing about developing film but I’m curious about the chemicals used and how you dispose of them afterwards? Does it require any special process?
Not sure if this is entirely what you are after but Andreas Kling of SerenityOS builds an IDE from scratch[1] for his own operating system. While I don't personally know C++ I found the videos interesting and fun to watch.
I sometimes listen to podcasts to fall asleep. I use the PocketCasts[1] app that has the ability to pause the podcast after an episode is over or after a certain length of time, which is nice if you just want it to fall asleep too and not play all night.
Podcast wise my goto is Phoebe reads a mystery[2], she reads various mystery novels and never fails to get me to sleep (sorry Phoebe). She is also the host of the Criminal podcast which is another good one, but too interesting to fall asleep to.
If you're going to use something like Tailwind, please still add legible class names (e.g. "thumbnail") and don't just write things like class="m-0 md:m-4".
One could argue that `class="m-0 md:m-4"` is more legible because it describes exactly what is happening. No margin on small screen, margin of 4 units on medium breakpoints. Where the styling on thumbnail is unknown and the breakpoints are unknown, unless you look at the css, then if you need to override that css you have to worry about specificity.
You're talking about CSS. I'm talking about classes.
> `class="m-0 md:m-4"` is more legible because it describes exactly what is happening
If by "what is happening" you mean "how it's styled", but that's extremely presumptuous. You might as well argue that there's no difference between Flash and an equivalently styled web page since if you took a screenshot of each they'd be visually identical—as if the whole thing begins and ends with getting the "rectangle full of little lights" to change in a particular way <https://xkcd.com/722/>. It's very narrowminded.
I'm not saying you have to be full on schema.org-conformant, but include something that actually makes sense instead of being as useless as the spew that CSS compilers put out.
But then again, if you're going to use meaningful class names, i.e., names that suggest what the thing is rather than what it looks like, then you're not really doing the Tailwind thing.
You don't have to sacrifice semantics in order to opt in to Tailwind's cutesy approach at expressivity. class="thumbnail m-0 md:m-4" works wherever class="m-0 md:m-4" does and isn't user-hostile.
I think the person above is referring to the text being very small on a mobile device. The font size is set to 2.5vw which renders the text as 9.375px on a device width of 375px.
"They also made government services much more accessible."
I would say the value of making the forms accessible was worth it. Also with the flexibility to make changes to the forms in the future will save even more time.
I think there will be such a group but you won’t know about them because they won’t be on social media telling people about it. I don’t think their identity will be anti-social media, but an identity to strive for a slower way of life.
