My key take away is that not-taken conditional branches are essentially free, and are not polluting the branch predictor, i.e.
if (__builtin_expect (DEBUG, 0))
Don’t use Google, use DuckDuckGo
Don’t use Gmail, use Tutanota
Don’t use Zoom, use Jitsi
Don’t use GoogleDrive, use Nextcloud
Don’t use Google Auth, use Aegis Auth.
Don’t use Twitter, use Mastodon
Don’t use Instagram, use Pixelfed
Don’t use WhatsApp, use Telegram
Don’t use Play store, use F-Droid
Don’t use Chrome, use Firefox
Don’t use MS Office, use LibreOffice
Don’t use Windows, use Linux
Don’t buy Bitcoin, buy Monero
Privacy comes first. Defend yourself against tracking and surveillance.
Good news: Supreme Court finds that as a matter of law, APIs can be reimplemented as fair use.
If it looks like a duck, walks like a duck, and talks like a duck, it's...
probably a #robot.
It is #2021, we are in crazy land folks (#hamburg):
The Assange case for extradition is still 90% upheld.
The judge refused extradition because the pending suicide risk would make it act of oppression.
The US going to appeal, so the decision will be taken to a higher court and has to be fought all over again.
The lawyers are now talking to Assange to prepare bail application, to be heared in 45 min.
That means, the US prision system is so bad that even this judge wouldn't send Julian into it.
via @johnwrees #FreeAssange
Judge rules against US extradition of Julian Assange, contending extradition would be oppressive by reason of Assange’s mental health.
The judge and defense are discussing an application for bail. US government is going to immediately appeal.
via @kgosztola #FreeAssange
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:
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 #Gimp does it.
Some users want to intentionally disable that though...
I'm working on a new knob for #Beast, with bidirectional and unidirectional modes.
Sadly, Chrome cannot compose *inside* and SVG, so I have some nasty splitting and layering of the #SVG 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"':
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).
DSP + DAW developer, Free Software author + advocate, contributor to ALSA/GNOME/procps/LibreOffice/etc.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!