Huh. SPAs are "static"?
I'm attaching a screenshot of the code example from that article.
Notice the coloring. Purple parts run in the browser; red parts run on the server. Photon "magically" handles ensuring the two runtimes stay in sync and execute in lockstep, with as little overhead as possible. Hell, it's quite likely that their overhead is *lower* than typical server/client communication people roll by hand.
Photon is relevant to this thread in two ways.
One, their trick is to compile your code to an explicit DAG.
Ok, found the culprit.
Apparently Firefox now defaults to picking website light/dark-mode based on... the color theme you've picked for Firefox UI (as if anyone ever changes that). The default one, despite being quite dark, is considered "light".
See screenshot attached.
Short-term solution: select "Dark in settings.
Long-term solution: software vendors stop doing stupid shit and overriding user preferences like that.
Correct default should be "System theme" - that's literally what it's there for!
Woah, someone on a certain job recruitment / dating site platform threw this at me (see attached image).
Learning Pyramid. I haven't seen this bullshit in almost a decade. I honestly hoped it died already.
Since it's apparently still alive and kicking, here's the obligatory article that explains why the aforementioned pyramid is utter and complete bullshit.
(TL;DR: someone did a very creative interpretation of a picture in 1950s research publication.)
As an extra bonus, if a function was added to a shortdoc group, the built-in help will mention that group!
See another attached screenshot, showing how the help buffer for `time-convert' mentions my shortdoc group.
As more functions hopefully get their shortdoc entries, this will greatly aid discovery. It's potentially much more ergonomic than the options we had so far, namely:
- Finding the part of Info manual that mentions a function;
- Jumping to source and poking around.
#Emacs tip of the day: shortdoc-display-group. Amazing new built-in functionality!
By default a little empty, but it's a great way for creating your own "cheatsheet" lists as you learn more about Emacs / #elisp.
See attached screenshot for an example - here I started making a cheatsheet for date/time manipulation functions I've been researching recently.
I hope the core developers will soon recognize the utility for user-maintained shortdocs, and improve the interface a bit (e.g. give us a defcustom).
Well, they said "*sensitive data* is never tracked", not "no data", and especially not "no activity".
This is to remind everyone that:
1) Sales copy is always to be read wearing a language lawyer hat;
2) Software companies are now aware privacy and data control are features for some segment of the market, so they will (technically-not)lie and cheat about it. Just because someone mentions "tracking" and "privacy" in their copy, doesn't mean they don't do former and respect the latter.
Just copy-paste the code below into an Org Mode buffer (and C-c C-c on "<<<Radio links>>>" for extra effect). Or see the screenshot attached below.
*** Two new things I just ([2022-04-02 Sat 01:25]) learned about Org Mode
1. [ ] Ordered lists can have checkboxes too!
2. <<Target links>> are a thing, distinct from <<<Radio links>>>
Target links need to be [[Target links][linked to explicity]], while Radio links don't!
TL;DR: we forgot which ton (short, long, metric) we meant for the denominator. Fortunately, the numerator is derived from empirical measurements, so we'll define it as a range - so whichever ton you pick, it still works out.
Right, except for private windows.
How this plays out is this: you have no obvious indication that an update is pending, until that one time, you click a link and instead of your page, you get this tab. The browser is now unusable until you let it restart, interrupting whatever it was you were doing at the moment.
Like e.g. being in the middle of a multi-step form filling process on a government page.
I run two POCs against CVE-2021-4034 on my machine and neither worked, but can't really verify if I'm vulnerable or not, unless the fix for this was floated a while ago already.
Is this #CVE just a planned disclosure with fixes released by distros long time ago?
I mean, flowchart in image 1 produces a working example of "the most useless machine in the world" (image 2). A webpage with a switch that turns itself back off after a delay.
Now were I to try and write it from scratch in any of the programming languages I normally use, I'd waste a day on it - most of it on setting up the project, build system, dependencies, but also assembling the UI, etc.
Of course, normal programming grants me much more freedom, but it seems to come with big costs for simple tasks.
I'd also add:
NOT ENOUGH TIME
TO DO IT
LOTS OF TIME,
MIGHT AS WELL
DO SOMETHING ELSE
So it turns out #OrgMode file header (that with #+stuff) supports comments, which means you can annotate stuff in there. A useful thing if you're using #+setupfile to create a central set of tags. See example screenshot.
CC @publicvoit - guessing by your article on tags vs. categories, you probably are using a setupfile.
So I'm trying to visualize how all those arrays and their types have to get transformed, and I can't find any prior work that would help me with this.
I'm currently hacking a PlantUML Activity Diagram for that purposes, so I'll post a rough sketch of what I'm talking about as an attachment. But my question is, is there a standard graphical language for this kind of drawings?
I vaguely recall seeing such diagrams on websites teaching algorithms, but nothing in the industry.
#Emacs #OrgMode something silly I wrote the other day. A bit of code that allows you to markup your Org Mode notes with arbitrarily-fontified text, through a custom link that renders using a specified face.
See attached screenshot for a demo. Code in copyable form here:
The previous toot had a notation change on the diagram - function application is made explicit, and so is ordering of the edges (to compensate for PlantUML/Graphviz "optimizing" it).
But operators are functions too, so how about the same, but with all function applications explicit?
Attached is a picture of a proper graph form of the code.
I wonder, is that a more useful form to work with than AST?
I'm likely reinventing a branch of #compsci here; pointers to existing body of work appreciated.
Just a coder / space enthusiast.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!