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.
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 […]
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.
Latest version of #HTML standard includes a warning that advises against using the #XML syntax (formerly known as #XHTML), stating that it's "essentially unmaintained"🧐 :
Wer ihre/seine #Mastodon-Lesezeichen über ein Script herunterladen und in #RSS, #XML, #JSON oder #CSV umwandeln will - ich hab gestern Abend mal was gebastelt.
CRAN is looking for someone to maintain #XML package: #rStats
"So we are looking for a person volunteering to take over 'XML'.
Please let us know if you are interested."
The task is not easy: many thousand of packages depend on it. Anyone taking it will be doing a great service to the R community.
I have a post about the situation they are in but it seems lacking the plots and some content. I'll update this toot once I fix it, to provide a link to it.
Fun fact: had #ActivityPub object representation been #XML#RDF instead of #JSON, little more than a thin wrapper with #XSLT and #noJavaScript would have been sufficient to serve them on the web —statically.
I post a lot of sample code on this blog. My CodePen is full of little snippets of this and that. Quite often, these snippets need data to do something useful. A good example of that is my Lit example from this past week. Coming up with that data can be complicated, though. That is why I created a site for assorted test data. If you want to have a little rummage through it, I also made the git repository public for the site. While I was at it, I also put it behind a Cloudflare proxy to speed it up a little.
Have any questions, comments, etc? Please feel free to drop a comment below.
I have a #Java app that loads user created #JSON. I also have a JSON file that describes the content of this format, which I’m using to to validate the content of the user created JSON. This lets me determine if the user forgot to include some properties or if they’re of the wrong type or out of range. I can then display some errors accordingly.
Is there a library that would do this for me? I guess it’s the equivalent of #XML and XSDs.
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.
I was planning to have my parser and XML parser packages published to crates.io by now, but while writing example code I keep finding new features begging to be added, such as the ability to specify a default namespace before reaching for a chain of child elements.
But I'm pretty sure they say that scope creep always leads to the best outcome, right?
Okay, finally published my #Rust powered parser and XML-specific parser packages to crates.io.
sipp: "Simple parser package"
spex: "Simple(ish) parser and extractor of XML"
I've not had time to push them to my Codeberg account yet, and there are problems with my initial attempt at README pages. But hopefully there's enough there to give an idea of what the packages offer.
Feedback welcome, especially about the "shape" of the public interface and how it "feels" in actual use.
Ich sammle Fitnessdaten von meiner Bluetooth-Waage und Sport-Apps in der App Apple Fitness. Mit der Auswertung bin ich nicht zufrieden. Gibt es Alternativen?
I am co-founding a new startup! #InputLab creates test data for thousands of formats from electronic invoices to retail orders, covering all input features – and we just got an 800k€ initial funding to start as a #CISPA spin-off in September.
Phew, had me worried for a minute. I'm writing a simple XML 1.0 parser in #Rust just for practice, and on feeding it a 4.4MB XML file it took 56.5s to read it. I've done nothing to optimise it yet, but even so that sounded dire.
Then I remembered to use "release" mode, and the time dropped to 3.9s. Whatever the compiler is doing behind the scenes, I'll take that 14x speed boost, thank you.
#XML is a great configuration language. Yes, I'm not joking. It has a terrible syntax, and it hasn't been in vogue for many years, but semantically it's better suited than #JSON and #YAML for many tasks.
With YAML/JSON you have to choose between arrays (nesting) and maps (keys). XML gives you both nesting and keys for every single element in the config. It's a much cleaner abstraction since it's all nodes all the way down. But it's rather ugly!
Hey, #XML crowd! I've got a mark-up puzzle to solve that my trainer can't answer.
How to I tag Germany or Italy in a historical context that predates their existence as a codified state? So, for Germany any time before 1871. Do I ignore historical reality and just go ahead and code it with [gw]?
There's no fancy unmarshalling; the entire document just gets read into an element tree. It does support namespaces, though, and I spent a lot of time creating traversal mechanisms (XmlPath and cursors) in the hope it makes it easy to grab the desired data out of the tree.
Probably not a JAXB substitute, but maybe useful in some scenarios.