142 karma · joined June 19, 2019
The key factor when assessing a blockchain project is indeed to see what is the advantage of a blockchain vs a usual database.
Most of the time, there is none. Worse, cost of a blockchain is more expensive as pointed by the article.
And you still need an authoritative registry somewhere if there any physical item involved.
In addition to that, blockchain projects faces another business issue: to be really decentralized, you have to lose control of what you put on the blockchain, which is hard to conceive for a private company.
Before that, the only way to get a configuration at the same price was typically some Amstrad PC (typically the popular PC1512), far less capable in terms of graphics and music.
The Radio-Electronics TV Typewriter magazine is also mentioned by Steve Wozniak while working on the Apple I.
https://developer.apple.com/tutorials/swiftui-concepts/explo...
These were also true in the early ages of aviation:
“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”
― Antoine de Saint-Exupéry
Without archive.org, it seems no money at all was made from them. A subscription to access these old books would be a win-win, with a part redistributed to editors. Access could be made from archive.org or why not, directed to a frame in editor websites.
Same for old magazines which are really appreciated by the retrocomputing community.
They were also translated in French and quite popular.
Usborne introduction to electronics: https://archive.org/details/usborneintroduct0000beas
Fun with electronics: https://archive.org/details/funwithelectroni0000mcph/mode/2u...
A refreshing experience was a mobile app Apple device, with Swift and Swift UI. It was a real joy, works as expected, produces concise code, small files, live preview and reasonably fast build time. Sure, it's closed environment, but last time I felt so productive doing UI dates back to Visual Basic.
Counter-example: a simple web app, nothing fancy, and my node_modules filled with around 500MB of files, hundreds of declarations of injected things everywhere.
But nobody forces us to use Kubernetes, nobody forces us to climb the Rust learning curve, nobody forces us to use this multi-platform framework that solves all the problems of the universe.
I try to stick to standard solutions, oft proposed by the vendor: Kotlin on Android, Swift on Apple, c# on Windows. Server code: stick to Java, or try the simple Golang (another refreshing language).
Also, I try to stay late to adopt tech, just starting to be confident in Docker and will see in a few years if Kubernetes could be useful.
But, an architect needs complex solutions to justify its job, a team lead needs as many dev as possible to tell at the next family dinner, and the new dev wants to try this new fancy tech to put on his resume. So they are all fine with that. Just don't tell the company ownership.
The finding that students’ responses to PISA test items reflect general ability rather than domain-specific abilities, if replicated to other countries, could have important implications for the design of large-scale assessments and the interpretation of analyses of large-scale assessment data.
Admittedly, there is little to program, but we can imagine all sorts of auctions, games (tokens becoming playable items in a virtual world, but still exchangeable for real bottles), etc., around those tokens.