https://www.scienceabc.com/pure-sciences/why-are-coffee-stai...
1,711 karma · joined August 16, 2009
https://www.scienceabc.com/pure-sciences/why-are-coffee-stai...
I'm hoping this technique can be used in video games because it's significantly better than what we have now.
https://aws.amazon.com/about-aws/whats-new/2019/05/amazon-dy...
Here's my weekend Godot creation: https://basilrogers.itch.io/learning-godot-2
So I'm really glad there is a second edition and I'm wondering if there is a new story.
LibreELEC is just enough (Linux-based) OS to run Kodi. Kodi is entertainment center software.
Now, I understand and deeply appreciate this method. I believe it provides lots of benefits. It drives towards better docs that can be understood quickly by non-experts. When there are just a few minutes to review the doc, we don't have time to go digging for information on our own - the critical information must be provided in the material given. There will also be SMEs in the room who can clarify any shortcomings here. Because the audience of the docs is non-SMEs, it drives towards inclusion of other teams. From this, you get more diverse viewpoints, considerations, and experience. It also contributes towards cross-team awareness and education. It makes it much easier to participate as a contributor to the meeting while simultaneously less impactful when you don't. It let's us timebox our attention span - you won't accidentally spend hours rabbit-holing into a doc.
You cannot look at a commit on its own and know exactly how it's different from the previous commit, but you do have the complete new state. You have to look at the parent commit's references and do an object-by-object comparison to identify exact changes. On the other hand, when you look at a diff, you can see exactly what has changed, but you cannot produce the version that came before without also having a complete copy of the current version.
No, that has direct influence on all consumers of the products. These things aren't free. People are paying for Xorg to continue to work, and the people paying most are probably those maintainers who are telling you this is not sustainable. As a user of Xorg or Wayland, you are the recipient of the work of people who put effort into those products. If you want to pay the costs associated with maintaining your preferred solution, go ahead.
Maybe I'm getting the wrong message here, but it seems that the author is claiming to be the victim because other people won't pay for their preferred solution, so they attempt to shame the people who are paying.