Yes they share many similarities with the FSF, but they are separate, and have some different viewpoints on things. You can't use something they do as an argument as to why FSF is good, when the actual FSF doesn't do that thing. They also dislike RMS, who is also one of @onlinepersona@programming.dev 's arguments against the FSF.
I'm in the exact same situation, however the right shift key broke, and activates randomly. This laptop only ever moved between a cupboard and a desk, without the tiniest bump, but after a couple months of very light use the shift key breaks. I now have to have sticky keys enabled permanently.
Also the only way to enable sticky keys on the login screen is to triple click the power button. You would thing they could just put a button for the accessibility accessibility menu next to the one for the keyboard layout switcher, but no.
That is interesting. WASM seems like it's just a replacement for the TrueType hinting language (which is already a VM). So I guess it's benefiting from a more standardised and audited virtual machine.
It's also fairly limited to what it can do (source):
you can influence the process of mapping a string of characters into an array of glyphs, you can determine how those glyphs are positioned and their advance widths, but you cannot manipulate outlines, variations, line breaks, or affect text layout between texts of different font, variation, language, script or OpenType feature selection
I don't see how the mentioned future drawing API will fit into that though.
Krunner is better at displaying longer search results. The launcher truncates anything longer than 1 line. Dictionary definitions are an example.
Krunner also keeps what was last typed in, which is very useful if I'm adding up a bunch of numbers, or if I need to switch to a different application before using the result.
Not entirely true. As long as you hold the copyright to all of the code (there are no contributions from other people), you can change the license however you like. The important thing is that this only affects commits after the licence is changed. All earlier versions are permanently available under the license they were released with.
Step 3 is where the issue occurs. The last party to submit their value has control over the output. Any complex calculations can easily be passed off as network lag. One solution I can think of is to pass the values round in a circle, one by one. This would require each party to share their value before they have seen all other values. At the end each party would share their calculated values to verify they match. Probably other solutions as well.
I would usually describe it as grey. There have been a few times where a sunset or the moon have provided some contrast, causing the greenness to become slightly noticeable. Last night was the first time I've seen such an obvious pink.
Sadly it doesn't get dark enough here at this time of year, so my family down south had a better view.
I think they are complaining about the caption in the image.