While the accessibility tree is great in many aspects it has its own limitations for example when it comes to stacked views or lazy loading outside the viewport.

I think screenshots also don't help with stacked views and lazy loading outside the viewport

Looking at the examples on the front page it reminds me even more about Parse.

This makes me think about Vinylon[1] and this article from Reuters[2]

[1] https://en.wikipedia.org/wiki/Vinylon [2] https://www.reuters.com/investigates/special-report/northkor...

Vinalon is an organic polymer, like many other synthetic fibers we wear, but derived from coal instead of oil because North Korea has no oil.

The basalt fiber OP describes is not organic at all. It sounds more like asbestos actually.

The Reuters article title is "Fabric made of Stone" (as it is made of coal and limestone), that is why it came to mind.

Yeah, but the vibes are the same as basalt textiles

Got a https://en.wikipedia.org/wiki/Leisure_Suit_Larry#Leisure_Sui... vibe from it.

Spaceballs 3: The Search For Spaceballs 2: The Search For More Money

Unfortunately there is a Spaceballs 2 set for release in 2027 and it doesn't look like they're going with that name.

What kind of tasks do you use it for?

How does this compare to https://huggingface.co/ibm-granite/granite-docling-258M in performance and how they work?

The granite Dockling models are unfortunately quite far below SOTA. dots-ocr and PaddleOCR were best here.

That is why I like the idea of having as much of the documentation as possible in code. Tests that describe how things are supposed to work, infrastructure as code the describes the parts of the system and so on. Then you are forced to keep them up to date.

Still seem to be down, a link for status updates: https://status.claude.com/incidents/6xlfx3mrb8ct

I have (Firefox on macOS), still easy to miss.

I have Firefox on macOS as well, but I don't see a scroll bar until I start scrolling. Could be because I'm using an external trackpad, and not a mouse.

On chrome the scroll bar is very visible.

I don't think you can blame Chrome for this... this is just bad design by Firefox.

This is different from the Minimum Deployment, which I current have set to iOS 12.0 in Xcode 16.2.