I'm porting the web UI from Vue-2 to -3. Turns out to be more involved than I originally anticipated.

I kept getting an odd exception during my tests. It looks like Vue-3.0.0 can become confused when state watchers (created via Vue.$watch) are unregistered during a later stage of a component lifecycle - trying to remove item from `null`.

I fail to see the error in my code at least (which works fine in Vue-2) and suspect it's a genuine Vue bug, filed here:

github.com/vuejs/vue-next/issu

Has anyone experience with deterministically building files for ?

Using svgtofont via npm I've not managed to get this to work yet.

Can we please, please – PLEASE! not make the nonsensical US date format month/day/year the default in applications? 🤦‍♂️

PRE 👏 TTY 👏 PLEASE

And to all users of that format: it makes no sense, it's counter-intuitive, it makes collaboration frustrating, it introduces inconsistencies and errors... Just stop. Please. Use international standards.
(And don't get me started on your other units of weights, volumes and distances. Bloody hell.)

Boost if I'm right.

Now I'm wondering if Pen + Eraser work better as piano roll cursors, or if it is better to always use a cross-hair + tool icon cursor, like does it.

Some users want to intentionally disable that though...
reddit.com/r/GIMP/comments/8zu

The standard CSS cursors don't really look suitable to convey insert + erase for piano roll notes.

Here is a first draft at creating cursors myself for editing notes in the piano roll editor, hotspots marked red.

Fiddling…

I'm working on a new knob for , with bidirectional and unidirectional modes.

The updates may only use "transform:rotate(angle)" to utilize acceleration during automation.

Sadly, Chrome cannot compose *inside* and SVG, so I have some nasty splitting and layering of the elements going on...

3/3 While the ability to run at nice priority -20 still requires root permission for the initial setup (or SYS_CAP_NICE), even that could *potentially* change with the introduction of a latency nice setting, if the kernel developers manage to implement unelevated latency re-nicing without opening up the gates for DOS attacks.

These developments are described in the LWN article 'The many faces of "latency nice"':

lwn.net/SubscriberLink/820659/

2/3 Not only is the risk of system lockups unwarranted to avoid audio drop outs, there is also no need for it to be taken.

Just prioritizing the audio rendering threads to run at nice level -20 is sufficient to prevent drop outs in low-latency setups, i.e. setups with <10ms round trip time. BTW, such setups require audio fragment sizes <= 128 samples (or "periods with <= 128 frames" in ALSA language).

1/3 On the topic of Linux low-latency audio setups…

Installing jackd (1 or 2) still requests "realtime priority" to minimize latency.

This project should really get its act together and stop demanding this kind of elevation from benign audiophile users.

Don't enable this! Running a process with realtime scheduling priority allows it lock up the system for good (and no code is bug free).

»Video: Wie wichtig Abstand halten ist, um andere nicht mit dem Coronavirus zu infizieren, zeigt ein faszinierendes Video.«

futurezone.at/science/video-so

Most of us are undergoing a lot of stress right now. People under stress can be short-tempered and impatient and can lash out. Try to be patient, empathetic, sympathetic, and avoid causing more stress or irritate or antagonize.

Try to be extra clear in your own communication, and ask others to clarify if they're not unambiguous. Be explicit about your feelings and expectations.

If you make a mistake, apologize.

BAD G++!

Apparently, g++-9.2.1 does *not* const-initialize a `static Class x;` with a constexpr ctor, *if* it also happens to have an uninitialized uint64_t array member. It does not generate a warning either, but surely triggers the "C++ Static Initialization Order Fiasco" at some inconvenient future point.

If you use certificates, check your hostname here to see if the cert is going to be revoked tomorrow, and you need immediate renewal: unboundtest.com/caaproblem.htm

More details:
community.letsencrypt.org/t/20

I just signed a petition to the European Commission:

Demand the Right to Repair your smartphone.

Sign here: repair.eu/smartphones/

I've written down the details of compatibly selecting modern instruction set extensions for the builds in a blog article.
The crux is avoiding extensions that are Intel only or AMD only.

testbit.eu/2020/intersecting-i

Web packaging technology is torture.

The last week, I've been fighting webpack, parcel, , babel and bili, just because vue stopped supporting and I had to figure what to use as a replacement in .
^^^ If that sentence sounds like it has too many web tech buzzwords, that's *exactly* the problem.

And it's only a fraction of packages I had to deal with...
Most packages have documentation, but only provide tiny puzzles of a much bigger picture that is revealed nowhere...

Yay! Power loss due to some digging work outside.

Hope the BTRFS disks in the main server survived the sudden outage.

The client for is shell only and really rocks!

But it got way too late again, will have to continue setting up the new Testbit site tomorrow, good n8!

github.com/lukas2511/dehydrate

Show more
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!