Looks like its a AVIF image. AVIF is not well supported unfortunately. Even on the latest version of Android it’s not 100%. But support is significantly worse on older versions of Android.

It works fine in the browser because browsers bundle their own AVIF decoders.

Support will gradually get better over time.

Maybe you have not played for a while but in the latest versions of minecraft, the caves are pretty insane specifically when talking about how varied they are in both size and depth.

You can also realistically get a lot of diamonds by just caving now.

I often times end up with a stack of diamonds just from exploring a cave without the intention of finding diamond at all.

I thought about it but i think it wouldnt look very realistic so I didnt end up going through with it.

My cat once jumped on the counter when I was cutting raw chicken. He stole a piece and I just let him have it… He knows I’m powerless and my threats are empty T_T

Yeah but are large rocks bad to the head? Are small rocks bad to the head? Can we draw a clear line where a rock is no longer considered small?

This experiment only showed that more experiments are needed for rocks to the head.

I’ve had this problem with abstractions for the longest time. Of course whenever I say anything negative about abstractions I just get dog piled so I don’t usually like to discuss the topic.

I think abstractions as a tool is fine. My problem with abstractions is that most developers I meet seem to only talk about the upsides of abstractions and they never take into account the downsides seriously.

More often then not, I just think people treat abstractions as this magical tool you cant over use. In reality, over use of abstractions can increase complexity and reduce readability. They can greatly reduce the amount of assumptions you can make about code which has many many additional downsides.

Of course I’m not saying we shouldnt use abstractions. Not having any abstractions can be just as bad as having too many. You end up with similar issues such as increased complexity and reduced readability.

The hard part is finding the balance, the sweet spot where complexity is minimized and readability is maximized while using the fewest amount of abstractions possible.

I think too often, developers would err on the side of caution and add more abstractions then necessary and call it good enough. Developers really need to question if every abstraction is absolutely necessary. Is it really worth it to add an additional layer of abstraction just because a problem might arise in the future vs reducing the number of abstractions and waiting for it to become a problem before adding more abstractions. I don’t think we do the latter enough. Often times you can get away with slightly less abstractions than you think you need because you will never touch the code again.

Finite time is trivial /s

I swapped out all the coils and drip pans last summer. I didnt realize you can just tug on the coil and it just comes off. Game changer.

I cleaned the hoose and ended up with a box of stuff i wanted to toss. I listed everything in the box on nextdoor/fb for free and everything was gone by the end of the day. People love free stuff.

Niceeee. Love the windmill.

Thanks!

Thank you!

The most common one, complimentary reimagined.

Thanks!

Thank you! It is a green house thus all the glass :D

Thank you

Thanks!

Alternatively, eat using a funnel so that the food skips your mouth and ends up directly in the stomach. Then it cant damage your teeth and you still get all the nutrients /s

Thats why I never neuter or spay my cats. /s