It is 2023. XHTML is dead and buried. HTML is a "living standard" with billions of users. So what kind of idiot would want to build a website using XML? Me. I am that idiot. Last year, I launched a "web page" which didn't use HTML. Called, appropriately enough, "YOU DON'T NEED HTML!" That (ab)used […]
I have, belatedly, realised that my #Rust#XML parser needs to use dynamic dispatch, because the character encoding can only be determined at runtime. Which means all of my rigidly static generic structs need to have dynamic equivalents. But I want to keep the static generic versions too, so that (for example) a JSON parser can be built from them (JSON is always UTF-8 so no need for runtime determination).
The dynamic/static files are almost identical. Any way to avoid duplication?
Dear lazyverse: is there an XML validation tool using RelaxNG compact schemas that I can install on Fedora and that doesn't depend on Java? Assume I know about jing and rnv
Someone really wants me to add docx support in my app (I already have odt support), so I was looking at the Office Open XML (aka docx) standard, and what a mess it is.
I know the Open Document standard (odt) pretty well, and while it's a complex format, it is quite logical and sensible, and not least: flexible.
Docx is pretty much the opposite. It's partially based on Microsoft's older proprietary binary formats, and an obviously self-serving "standard".
I'm looking for a new job (remote or #PDX), please boost!
I am a research software engineer with 11 years experience developing interdisciplinary scientific software that is robust, #accessible, and user-friendly.
Working on a legacy #PHP codebase with this #XML-based framework where the dev had the genius idea of mixing business logic with presentation logic.
Okay, that happens. But each XML fragment is isolated, with no way to inject data into it, so what ends up happening is every single XML fragment is doing db lookups to get data that the parent template already has.
Why is the application slow? Hmmm, what could it be...
I also wrote about my one disagreement with Russ where he advocates for writing drafts in XML, but I have become a strong advocate for using Markdown in most cases.
Die heutige CMS-Klausur hatte natürlich auch Bezüge zu #XML-Basics und dann darüber hinaus zu konkreten Formaten, Standards und Vorgehensweisen. Dabei gab es eine Referenz zur Serie #ForAllMankind mit fünf Fehlern und zwei vermeintlichen Triggerpunkten.
BREAKING NEWS: A generation that knows nothing about #RSS and #Atom has finally grown up.
During the podcast recording today, a user in a live chat reached out to me saying that the #feed button on my personal site is broken 'cause it returns an #XML.
How could I miss out on #VisiData for so long? This might become my new favorite #CLI tool.
If you do anything with data and enjoy working in the terminal, check it out. It can
• provide a #TUI for viewing and editing data in #CSV, #Excel, #SQLite, #JSON, #YAML & #XML files and quite a few more
• sort, filter, join and edit that data, across files and across formats
• convert between the formats (interactively or not)
• record & play macros
• be scripted in #Python
Yes, of course #GNOME#Boxes, when I click "Edit Configuration" on my VM, dealing with raw #XML directly in a text editor is exactly what I want to do, why would anyone be surprised by that?
Is there some markup language you really like?
Do you have a vision of what a perfect markup language should look like?
Do you write your UIs without a markup language, just with code?
I figure doing XML in Rust is rather obscure. I queue for lunch, mention it to someone, someone else just ahead of me in the queue says "oh I am working on that too!"
I also chatted to two different speakers at the conference who worked on a different XSLT engine in the past (way before Rust)