Since a definition is descriptive, not prescriptive, I think it’s paramount.
Since a definition is descriptive, not prescriptive, I think it’s paramount.
I suppose it depends on how exactly you define a blockchain. If you add distributed consensus algorithms and a requirement for BFT resistance, then it clearly isnt. Its the usual issue with definition…
I would beg to differ. It seems to be pretty useful for Software development. After all git repos are Blockchains. That being said: use a solution that fits your problem, don’t try to adapt a problen to your solution. Thats something a lot of the crypto- or AI-bros are apparently misunderstanding
Dear Debian users: please also update your Debian version, not just your packages. Like… once a decade would be an improvement for many poor servers.
Only acoustic guitar covers of Wonderwall
It’s not android, but Google as far as I am aware. At least my battery settings (latest graphene OS) are… limited to say the least
I want it to last. At least 5 years.
That is something that would be very hard to legislate. Especially since battery lifetime is dependent on a variety of external factors (charging-style, temperature of the device, luck). Build quality certainly also factors in, but even the best battery won’t survive a 10 year old regularly overheating their phones with games and charges it for the entire night. I would love to see OEMs implement nice things like “capacity settings”, where you can set your device to stop charging at 80% and show it as 100%.
I agree partially. For indie devs: get the game directly from the dev if possible, never get the codes, because the dev doesn’t really get money for those.
With AAA games, the picture is different. The business model for most has now pivoted to be about extracting money to the point where its absurd. And for them, I have absolutely no qualms with taking advantage of their bad business decisions.