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.
Looking to do an update on a #Perl script on the office webserver, I looked up the perldoc for a module and ran into, "PLEASE DO NOT USE THIS MODULE IN NEW CODE". 🤔
“The use of this module in new code is discouraged. Other modules are available which provide more straightforward and consistent interfaces. In particular, XML::LibXML is highly recommended.
"The major problems with this module are the large number of options and the arbitrary ways in which these options interact - often with unexpected results.”
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.
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 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
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?
@ic3l9@newt well, indeed XHTML ≠ XML, though the former may be viewer as the latter, forgetting about meaning of the tags, and indeed it is parsed as XML first and then the entities get interpreted
(I kinda know the difference, I generated #XHTML from custom #XML with #XSLT and wrote custom #DTD for the validation of the XML)
unlike "HTML5" e.g. all the tags have to be closed or the browser will just signal an error and won't show anything — that's a good thing, and the reasons are the same as for strongly, strictly, and statically typed GPPLs
problem with #JSON is not that it's a bad format (although it really is) but that it isn't human read-/writeable and discourages separation of internal data-structures from protocols — data-structures may vary between implementations and versions but protocols must be stable, and just passing lists of hash tables as they are is not really a protocol design
of course all windows behavior is intentional, even if malicious — never mistake hostility for stupidity
specifically in case of #Thunderbird, things like login failure for one server of one account block everything else, and the dialogs can't even be closed oftentimes — if it's intentional then they're just evil or it's a sabotage, should be avoided in either case
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.
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?
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 was refactoring a feature and wanted to know which options were used for a certain attribute in a XML file. I decided to level up my CLI skills for that.
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.
Finding used values of XML attributes using the command line (danielrotter.at)
I was refactoring a feature and wanted to know which options were used for a certain attribute in a XML file. I decided to level up my CLI skills for that.