I can't help but agree, and sometimes I think about the alternate version of the web where XML realized its full potential as the dominant technology. The obvious problem with XML is that the syntax is so verbose and redundant that it's only barely human-writable, but this is 100% a solvable problem.
Yeah, XSLT 1.0 has some really obvious missteps, so much so that to my knowledge basically nobody just implements XSLT 1.0. What they actually support is (most of) XSLT 1.0 plus a handful of EXSLT extensions (which are completely unofficial and not part of any XSLT spec, by the way). In my opinion the EXSLT stuff is the bare minimum needed to make XSLT 1.0 at least a passable language. Meanwhile, the XSLT spec evolved into 2.0 and 3.0, which as far as I'm aware, even to this day, has no complete open-source implementation.
I've read a few articles by Chris Lee, and I normally like them quite a bit. However, IMO there's something missing from this one, like how does this experiment push the frontier of quantum entanglement research? Is this the most complex entangled state ever created in a lab, or something like that?
The editor’s summary of the linked paper may be of more use:
> The ability to cool levitated nanoparticles to ultralow temperatures for accessing mechanical quantum states of the system provides a platform for probing fundamental physics. Deplano et al. demonstrated the generation of entanglement between a macroscopic mechanical oscillator and a freely propagating optical field. Such optomechanical entanglement at room temperature involving a levitated nanoparticle and a propagating optical mode and could also be used to develop quantum sensing technologies.
I think part of this is simply “no one has ever previously mechanically linked a classical-scale object to quantum-scale entanglement” and they managed to do so, which is pretty cool. To construct a theoretical idea as analogy of sorts: Imagine a supercooled fiberoptic link where the two transceivers both fire a laser at a liquid nitrogen hose filled with glass beads, and so packets end up sent by the tranmissions vibrating the suspended nanospheres entangled with both transceivers which can be sensed instantaneously by the receiver since they’re quantum-mechanically entangled and thus not subject to lightspeed delays, rather than having to wait for a wave packet arriving at the mere speed of light through photonic propagation as they do today. This is probably formally wrong on some level but it’s only meant as an analogy to get a toehold of understanding, not as a statement of outcome or certainty.
Pretty poor reporting here, but let me see if I can get this straight: Georgia ballots weren't truly anonymous, but contained enough identifying information (through these ID numbers) to be correlated to individual voters.
Here's the most important thing:
> Georgia’s outgoing secretary of state, Brad Raffensperger, locked down the tabulation data that someone might use to identify a voter, ordering any public release to redact the ID numbers after an election, which “substantially address[es] this flaw”, said Ben Adida, an MIT-trained cryptographer and the founder of the election technology non-profit VotingWorks, as he addressed the board on Thursday.
But if the unredacted data still exists anywhere, it's still a massive liability. It can still be leaked by unscrupulous people who have access to it, or disclosed to other unscrupulous actors via coercion. The flaw hasn't been fully addressed until the data is expunged and the system is updated to avoid creating it in the first place.
By the way, if I'm reading between the lines correctly...it appears the flaw has nothing to do with "AI," which is why I've called this "poor reporting." The academic who discovered the exploit either used an LLM in their research, or simply demonstrated that AI models have enough knowledge to give out the steps to do the exploit. If the LLM is somehow integral here, that is very poorly explained. My guess is either the author or editor decided to make the story about AI, to ride the current wave of "dangerous AI" hysteria, and then stuck it into the story everywhere they could.
This is a cool concept and something I was looking into recently!
IMHO, XML as a concept is a bit underrated and misunderstood nowadays. Unfortunately the way the culture of XML has evolved over the past decades probably has a lot to do with that, but that shouldn't mean we have to throw out the baby and the bathwater.
For one small example of what I mean, Jupyter notebooks are JSON, while it certainly seems to me that XML would be a better fit, minus any concerns about tooling. A cell's content is represented in the file as an array of strings, while in XML it would just be a text node with the literal contents. But more generally, I increasingly feel that XML should have become the lingua franca for abstract syntax trees of all types. Hopefully it can still become that, and Invisible XML seems like a good step in that direction.
By the way, I should point out that the CommonMark AST has an official XML representation, but as far as I know that's the only Markdown dialect that does, and I also don't know of an ixml grammar. Wouldn't it be great if every Markdown dialect had an ixml grammar though? If Invisible XML has any limitations that prevent this from happening, then IMHO those really should be addressed, since if it can't represent Markdown, then it's probably just not very useful after all.
The difference between big-company and FLOSS UX design, including profit-motivated behaviors (a bit indirectly, but it's definitely there), is specifically addressed in the article, so I don't think that's a very fair characterization.
I actually agree about customization, but that's only part of it, and seems to be pretty orthogonal to what the article is talking about. You can only customize to features that are actually implemented by the system, and coming up with those seems like the harder problem.
I hope I'm mistaken with my unfair characterization, but until I'm proven wrong I'll take these addresses as suggestions rather than core principles.
> You can only customize to features that are actually implemented by the system
> (Customisation) is only part of it, and seems to be pretty orthogonal to what the article is talking about
It's not orthogonal because implementation without ergonomics is meaningless, which is what customization accessibility is all about. It needs to be a core design focus on the end user and not some obscure API only maybe Redhat will use to implement business support.
We have lots to work on already. Hyprland on archlinux is crazy customizable, but it's a far cry from what we should expect from a customizable and accessible system intended for a more mainstream audience.
> The final, particularly strong, objection from the tech community is "don't touch my stuff". People get angry when they have worked hard to get their desktop environment just as they like it and something changes to disrupt that.
Yeah, this can be a little extreme, and I feel we can benefit from being a little more open to trying new things.
The part about designing specifically for large displays and widescreen monitors was interesting. We can also reverse it, though: right now I'm away from home, and I only have this old laptop which is mostly great but has a shitty touchpad as the mouse, and I have to think this must be really common. However, this situation seems to be completely ignored by all desktop UX design. We seem to be pretty good at coming up with ways to use the mouse in our programs, but when the mouse is hard to control and unreliable, it causes pain. I guess I can use ratpoison or something, but that seems to be giving up too much.
Regarding the AI going deep into the filesystem and organizing my data...I'm extremely skeptical of inserting any kind of inherent unpredictability into how I interact with the computer. Giving a command or input should produce a well-defined and predictable (in principle) action. Getting rid of that paradigm fundamentally changes the relationship between the user and the computer in a way that, in my opinion at least, greatly diminishes its usefulness as a tool.
> Yeah, this can be a little extreme, and I feel we can benefit from being a little more open to trying new things.
Sure, sometimes, when we have the time and surplus to deal with changes to things that already work well enough, and are not essential to doing our actual job.
That should be something you can opt in to.
Changing things for someone who's actually doing real work on top of the existing setup, is an undesired hurdle.
People are change-averse because they've been taught that change is costly, and they completely rationally ask "what's in it for me?".
You want them to buy in to the change, you better give a good answer to that, one which is a more than negligible benefit in a few cases that the user may not care about.
"Good enough" is good _enough_, it doesn't _need_ changes. Any change has to pay for its own retraining cost, in time and mental effort, otherwise it's a net negative for that user.
Being change-averse is the rational default behavior. Ignoring that, or even belittling it, is disrespecting your users.
I think the big issue is that the user doesn't have a choice in many cases. Windows obviously doesn't give the user a choice, they made the start menu much shittier and you had to live with it or go away. Popular distributions like Ubuntu also focus on one desktop environment, and it's often not easy to switch (it's possible of course, but at least when I tried it a long time ago just installing a different desktop wasn't enough).
Making it easier to choose allows for much more experimentation. I'm using Niri right now, which certainly isn't something you can just give users as a default.
Here's another thing that's just completely ignored: touchpad as anything other than a mouse replacement. It's possible for a touchpad to allow things like pinch-to-zoom, but nobody's really doing that. You could even use it as a low res painting tablet.
Well, Apple is doing it. The touchpad experience on macbooks is really on another level than all other laptops and one of the main reasons that's keeping me there.
How is the primary way of interacting with your computer being good a gimmick?
I try to use my partner’s windows laptop and it’s borderline unusable for me. She only almost uses it with a mouse plugged in. Meanwhile I don’t think I’ve ever seen someone plug in a mouse to a MacBook that wasn’t docked to a monitor and keyboard.
Pinch to zoom and two finger scrolling work well for me in most Windows apps. Apple has a few touchoad gestures that I don't believe have equivalents elsewhere, but they would be pretty neat.
The main issue with going beyond the mouse is that it involves changes across the event handling stack. For track pads, you have to build multi-touch infrastructure up ro a point and then there is a decision: what are gestures that are handled at a desktop level? What are gestures that get converted into semantically similar events (e.g. tap->LMB click)? What gets passed through as multi-touch? This ends up touching a lot of parts of the desktop software stack and the amount of required buy in to get this done on Linux seems massive.
Then change the stack. We can't be stuck on obsolete inefficient mental models. We are programmers, we can change software to fit new requirements. We already found ways to deliver keyboard input to the focused window.
Pinch-to-zoom is handled by libinput, and exposed to gtk apps. Works fine in firefox. Works in GtkWebkit views. works in Loupe the image viewer. works in Gnome Maps. Even works in Emacs, ffs.
I don't understand your initial comment at all, then. You want touchpads to have features they already have, which you haven't tried, because you don't have a touchpad?..
You understand that I can understand that parts of the system I don't personally use right now have issues right? Like I don't use systemd, because it sucks, but I can still say systemd sucks.
People from outside the tech community also do not like things changing, they just do not have the same choices or have the same voice. I have come across people who use old versions of Windows because they do not like UI changes, but they cannot do it forever, and they not have another choice.
> Or is it because they then publish those docs somewhere else?
Exactly, I use Sphinx to make a nice website from the markdown sources (although it doesn't have to be markdown). That includes generating a full API reference page from all the docstrings.
I completely agree. When the docs are in the same repository as the source code, at least you can keep the documentation atomically synced to the code. No other method allows this (not counting setups with Git submodules, which is the same thing with more steps), and that should be an immediate dealbreaker.
Docs being updated to reflect the code can then (and must, IMO) be a blocking constraint on all pull requests.