sukhmel

Not sure this pricing crisis will not have an impact on consoles, too

‘X is an awful thing but it could be worse’ doesn't really sound like defending X

In cross-post section it shows the first post to be 4y ago: https://lemmy.ml/post/88664

Why is that relevant now?

I recently tried Pop!OS liveUSB without a mouse connected to PC, there were some accessibility issues but one was unrelated to mouse and pretty cursed:

I chose system language to be something non-latin-based, and ended up with a keyboard layout that can't input English text. There was no way to change the layout and adding the US layout didn't work, because system showed that the US layout is already the one and only available. So I couldn't input commands to set things up but also couldn't click in the UI to set things up

Might be the case, but I expect some things to be true, like desperation score and profit squeezing. I met call centre managers that were trying to optimise how little should workers spend without the call in progress, that might sound reasonable but they tried to ‘improve’ from less than 10s between calls already

I believe such petty technicalities should not bother the flight of your imagination

I believe you also upvote and downvote, but I want to emphasize that it's up- and downvotes you gave, not the ones you received

https://lemvotes.org/user/Formfiller@lemmy.world

I think, the point was: you up-/downvote something on abc.xyz, but lemvotes is not federated with abc.xyz, then it doesn't count that vote.

Don't know if that's any close to reality, though

Imagine how unbelievably good must be those 19 posts they upvoted

Paper has auto-ignition temperature higher than 420°F, I would expect wood to be at least same as paper or higher

Edit: ok, I found a link to the study that says the wood will ignite at a lower temperature but will require some time (maybe the same is true for paper, now I'm not sure, it definitely chars in the oven)

Also gold:

The compiler assumes mutable references are unique and optimizes based on that. When you break the assumption, the optimizer generates wrong code. Compiler skill issue.