5,020 karma · joined September 23, 2022
JSON Canvas:
graph primitive
easier to read, write, and reason about
harder to render
path primitive
easier to render
harder to read, write, and reason abouthttps://codepen.io/ItIsHappy/pen/vEXrXxg
Yes, I'm being pedantic, but that was the point of my comment. SVGs aren't interactive by default, you need to bring your own interactivity.
For static content, SVGs work great, but for interactive content the additional sematic layer of JSON Canvas has a clear benefit. SVGs represent connections using paths, while JSON Canvas uses a graph. This means SVG cannot connect a single node to more than 2 adjacent nodes. If I want to draw arrows from Alice, Bob, and Charlie all to Dave, then I need to create a second Dave or reference to that location somehow. (You can see this in your sword example by moving one of the edge points. The sword delaminates because only two of the four edges at that point can be connected together.) SVG provides limited tooling for this, but it gets rather complicated rather quickly.
What a nightmare! Are your findings and this list of malicious extensions published somewhere?
If your linter is able to action requests, then it probably makes sense to add too.
I bet it sounds like a dial-up tone!
A single spreadsheet used locally is probably the best imaginable tool for answering "what if I changed that."
That same sheet shared across an organization suddenly becomes a game of "what caused that change."
They never said they didn't.
> Really, I am not a co-processor in a bus for you to dispatch a job to me and raise an interrupt line whenever the fuck you fancy doing it.
I am! I'm perfectly capable of managing my own time and shoeing others away if needed. Please bother me! That's why I have a cell phone and a salary.
Almost certainly relevant: I work in manufacturing.
Here's a line from my local library's site:
> Our auditoriums are provided as a public service for use by individuals, institutions, groups, organizations, and corporations for a small fee, when not being used for library-affiliated or sponsored activities.
To promote some further reading:
OKLab isn't actually a perceptually uniform colorspace. It's better than others, but it was specifically chosen as a tradeoff between accuracy and speed (hence the name OK). When you start digging this deep, you quickly learn that we have yet to invent any perceptually uniform colorspaces; even the most precise models we have end up using fits and approximations. Color has some really inconvenient properties like depending strongly on brightness and background. Frankly, given the differences in human biology (having orders of magnitude differences in relative numbers of each cone, for instance), it's surprising we agree as much as we do! Human color perception is an endless pit of complexity.
(Note, I don't say any of this to detract from what you've built here, merely expand. Your site is awesome and I love it!)
Nobody is "pretending" anything. These have all been around for 15+ years at this point. Your ignorance does not imply intent to deceive on others part.
The flickering in particular was fixed only on the logo example, but now exists on the Three D Light Source Position example as well.
For issues, may I recommend a more "human-in-the-loop" approach?
The entire Manim CE Logo example, the `x - x_1` text from the Brace Annotation example, all text from the Sin Cos Plot example, and the entire Heat Diagram example all flicker roughly once per second.
The text looks rather fuzzy, especially the large M from the Manim CE Logo example.
The Three D Light Source example also doesn't appear to have any functioning directional lighting.
The ability to record authorities is something I fully support, but I still don't want to be in that video if I can help it.
On top of that, most smartglasses are not private. If authorities can access the feeds, then my neighbor with RayBans becomes an authority, and it makes it that much harder for me to avoid them like the plague. This similarly applies to Ring doorbells and Flock ALPRs.
use experimental :rakuast;
my $ast = RakuAST::Call::Name.new(
name => RakuAST::Name.from-identifier("say"),
args => RakuAST::ArgList.new(
RakuAST::StrLiteral.new("Hello world")
)
);
Edit: I should have looked deeper, `DEPARSE` does exactly this:
https://docs.raku.org/type/RakuAST
Neat!
> No one shall be subjected to arbitrary interference with his privacy, family, home or correspondence, nor to attacks upon his honour and reputation. Everyone has the right to the protection of the law against such interference or attacks.
That doesn't seem as clear cut as you're implying.
Here's a quote from one of the creators:
> But here's the super cool thing about our language! Since we don't store your code in a text/source code representation, and instead as a typechecked AST, we have the freedom to change the surface syntax of the language very easily, which is something we've done several times in the past. We have this unique possibility that other languages don't have, in that we could have more than one "surface syntax" for the language. We could have our current syntax, but also a javascript-like syntax, or a python-like syntax.
My issue is that I don't have the ability to audit every smart glasses user to find out what their tech stack is, so I'm looking at averages. If I saw that smart glasses were being used and promoted as assistive technology, I would likely form a different opinion. Unfortunately, that's not what I perceive. I am open to the possibility that smart glasses could end up a net positive on our society, but the history of similar technologies does not encourage.
I will think more on your comments here. I find them quite insightful.
Edit: For a rather recent example of my threat model, I will repost part of my comment from elsewhere in the thread:
> I watched a guy setup a cell phone to record his laps in a pool yesterday. He swam one lap right about a meter from the 15 year-old girl playing with her mom, then climbed out of the pool, shut off his phone, and walked away. The remainder of the pool was open. Should I have called him out? I couldn't decide, and therefore didn't. This is normal now.
I do not agree that the existence of surveillance tech justifies the expansion of surveillance tech.
The same talking points still apply to cell phones. I think people who record TikToks in public are similarly gross and I go out of my way to avoid them.
I watched a guy setup a cell phone to record his laps in a pool yesterday. He swam one lap right about a meter from the 15 year-old girl playing with her mom, then climbed out of the pool, shut off his phone, and walked away. The remainder of the pool was open. Should I have called him out? I couldn't decide, and therefore didn't. This is normal now.