"The A1200 is essentially a Linux single-board computer running emulation, possibly one of the UAE (Ultimate Amiga Emulators) that have been around for decades. What makes The A1200 different from just building your own with a Raspberry Pi is that we get a full-sized recreation of the Amiga 1200, and that includes a working keyboard. "
"Can we use a distributed database instead? If the answer is ‘Yes’, why go for blockchain at all? Indeed, blockchain is slower and more resource-intensive."
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.
From at I remember, at least in Europe, it's only from 1994-1995 that you could start thinking having a better proposition with a PC than with an Amiga/Atari ST.
In order to surpass what you had on an Amiga 500/600 in terms of games, your needed at least a small 386 VGA.
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.
Glad to see those valuable principles written, even if it seems we are heading in the complete opposite. At least we can try to apply them on our side business.
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.”
As a regular user of this wonderful archive.org project, I found it a pitty that no agreement could be found with editors such as Hachette regarding old books.
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.
Go almost instant build time is a huge productivity boost when compared to Java. You get both the solidity of a typed language, and the development speed of interpreted languages (py, js).
The five gold ingots, used as currency by Chinese traders, were among the treasures picked up by some discreet divers around 1975 from the ocean floor off the coast of France. The ship they had been on, the Prince de Conty, was a frigate that belonged to the French East India Company, and it was just ten miles from shore, about to return to port at Lorient, France, when it sank amid fog and rough seas and an apparent navigational error by its captain on December 3, 1746. On board was tea, lots of Qing Dynasty porcelain, and around 100 gold ingots embossed with Chinese characters — each worth about $25,000 in today's dollars. Nearly 200 men drowned, and only 45 onboard survived the wreck.
Still, part of the industry is moving towards simple solutions.
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.