please! nobody uses Xpath (coz json killed XML), it RDF (semantic web never happened, and one ever 10years is not fast), schema.org (again, nobody cares), PNG: no change in the last 26 years, not fast. the HTML "living standard" :D completely optional and hence not a standard but definition.

Xpath is still used for e2e tests and things like scraping. Especially when there aren't better selectors available.

The point is that you don't need the very latest version. The 20 years old version is enough.

XPath 1.0 is a pain to write queries for. XPath 2.0 adds features that make it easier to write queries. XPath 3.1 adds support for maps, arrays, and JSON.

And the default Python XPath support is severely limited, not even a full 1.0 implementation. You can't use the Python XPath support to do things like `element[contains(@attribute, 'value')]` so you need to include an external library to implement XPath.

XPath is used in processing XML (JATS and other publishing/standards XML files) and can be used to proces HTML content.

RDF and the related standards are still used in some areas. If the "Batteries Included" standard library ignores these then those standards will need an external library to support them.

Schema.org is used by Google and other search engines to describe content on the page such as breadcrumbs, publications, paywalled content, cinema screenings, etc. If you are generating websites then you need to produce schema.org metadata to improve the SEO.

Did you notice that a new PNG standard was released in 2025 (last year, with a working draft in 2022) adding support for APNG, HDR, and Exif metadata? Yes, it hasn't changed frequently, but it does change. So if you have PNG support in the standard library you need to update it to support those changes.

And if HTML support is optional then you will need an external library to support it. Hence a "Batteries Included" standard library being incomplete.

I think the best example I've seen of the pipeline approach: ASR(STT) -> LLM -> TTS is still from about 10 months ago in HN https://github.com/KoljaB/RealtimeVoiceChat

Just a pity the code is undecipherable :(

Don't be so hard on yourself :P

what do you mean "infer"? how does the LLM get anything it of this as input?

I guess if I'd done all that work on lobster and then bipolar built a ray traced voxel engine on top of that, end game would be to licence the engine. You have something here that the other game engines don't have, and something Minecraft is not likely to have (they are pretty stagnant development wise). This is easily 100 times better than Roblox. If you focus on making the world building tools easy to use and modding/game design you could easily be the next big thing. Don't get too bogged down in game design other than to use it as a proof of concept to help you understand what game designers will need.

Try norther Ireland.

Save to Instapaper and read on Kobo ;-)

Is that what putting a camera in the hands of everyone with a smartphone (basically everyone) did for photography?

Or making video editing + free, global publishing platform did for film? (see: doom scrolling).

Come on man, the usual reason: $$$

Its is Micro$oft after all :P

The reason we're getting this AI gumbo is that obviously the product people at M$ we're told: "Make money by selling AI features!!!". Which flipped their minds from their usual "I am Steve Jobs" fantasies, which tell them to _consider the User experience first_, to _Consider the companie$ experience first_, and they can't keep the two concepts in their little heads at the same time because they are, after all, just product people.