Are you talking about Recall, which got such huge negative press they delayed it a year and added a clear opt-in? And never sent anything off the device itself?
If anyone has evidence of constant tracking and reporting then please share it.
But it is not really XML like syntax, is it? It is still a string, even if a template string or whatever it is called, no?
That still leaves the door open for XSS. A good (proper?) (e?)DSL would have the things that make the DOM as keywords in the language, and then we could ensure, that things which should merely be a text, are really only rendered as text, not injected DOM nodes. And the next failure is, that this DSL that is jsx needs to rename HTML attributes, because of overlap with JS keywords like "class". It lacks the awareness of context and therefore is not truly like HTML, no matter how hard it tries to be. It also comes with hacks like "<>" or fragment.
Overall it is usable, but not a particularly well made DSL. It might be as good as it gets with JS.
For inspiration check SXML in various lisps, which comes with immunity to XSS and which works just like the rest of the language, can be structurally pattern matched upon and iterated through, like a proper tree structure.
> It is still a string, even if a template string or whatever it is called, no?
No.
> That still leaves the door open for XSS.
The door for that in React is called `dangerouslySetInnerHTML`, but it's extremely rarely used.
> jsx needs to rename HTML attributes, because of overlap with JS keywords like "class"
That's not really inherent to JSX, just React's use of it. SolidJS, for example, uses `class` instead. But in any case – JSX didn't make up those names. Those are the property names on JavaScript's DOM classes. The fact that there's confusion between "attributes" and "properties" is pretty baked-in to the Web platform, even causing confusion in standard Web Components. Every DOM library and framework (even jQuery) has needed to decide whether it's operating on properties or attributes.
const div = document.createElement('div');
div.className = 'foo';
> It also comes with hacks like "<>" or fragment.
The DOM has the same concept, DocumentFragment. How else would you represent e.g. "two sibling nodes with no parent node"?
> It lacks the awareness of context and therefore is not truly like HTML.
On the contrary, I'd argue it has way more context. It knows, and will warn you, if you try to do any DOM element nesting that the HTML spec forbids, for example.
> can be structurally pattern matched upon and iterated through, like a proper tree structure.
You are literally describing the output of JSX. Glad you like it ;)
(1) They couldn't imagine anyone ever closing their gloriously developed MS Teams.
(2) Since everyone knows MS Teams and sitting in meetings all day is the one most important thing to get stuff done, they went ahead and made MS Teams a "priority". F using anything else! Maybe if it doesn't release the audio input, it will be 50ms faster next call! That ought to be enough for you!
It actually does or at least did, until at least a few years ago. When you opened the audio mixer (alsamixer or pulse audio control?) on XFCE, you could still see MS Teams labeled as Skype there. Not sure how it would be now, because I only ever use MS Teams isolated in a separate Ungoogled Chromium browser now, and have given up on the client for GNU/Linux.
Let's not forget how stupid the client on GNU/Linux was regarding audio devices. Every other app I had installed, that has anything to do with microphone (OBS, Audacity, Discord, Discord in Browser, Signal, ...) recognized my mic, which was connected via jack. Not MS Te-eams!!! Tada! Had to buy another headset with USB plug for Teams to get it.
I get the same issue on Mac, if it's any comfort. I had to close and reopen the app 7-8 times to have my microphone recognized, despite it worked reliably on every single tool I ever used, both on Linux and later on Mac. Teams couldn't do that either with the native client or with the web client.
And then we will get rid of them again, because some suits are telling us that we don't actually want them, that they are "complicated", we must trust them and that recursive data types are too hard to get right. Let's all write SMS again. Or better yet, send fax.
Some engineers will facepalm super hard but won't be listened to, as usual, and we will enter the next cosmic age of self-inflicted suffering.
I guess we could concoct something made out of PHP4/5 and jQuery and use Xampp stack, to get something worse. Or wait, I have it! We build it on top of MS Excel!
As bad and evil as MS Teams may be, I recently got invited to a Zoom meeting, and you simply can't use it in the browser! They just force you to download their shitty app to join. Naturally, I did not install crapware and closed the tab, as fortunately it was no mandatory event for me. At least in MS Teams I can isolate it into its separate ungoogled Chromium installation and treat that as a shitty app, without having to install crap onto my system.
Zoom calls work fine in the browser. They first make it look like you need the native client, but there's some dance you need to make to get the web link. Reload, wait, spin in your chair, something like that.
Of course I would never choose Zoom or Teams if I had the power, but Chromium does work with both when those are the tools your client uses.
That's how some people do their "computing" these days, if they do any that deserves the name at all. I had to do some of that on vacation. With a modern phone it's possible, but mentally taxing. Phones feel like MS-DOS operating systems, where each application is fullscreen. Most people are just consumers. This is probably true for Anki decks as well. Only a small minority creates decks, the vast majority only consumes.
reply