The Typescript compiler, currently JavaScript, is being rewritten in Go. The 10x performance gain is in build time, which is still a major speedup and will shrink the development loop.
I had a great k3s experience with a silly, over engineered weekend project to automate my fog machine with motion sensors.
I connected motion sensors to battery & wifi enabled RPis, built a remote circuit to control the fog machine, and ran a k3s cluster with NATS to bring it all together. 10/10 would do again.
I disagree. It isn’t about smartness. There are plenty of intelligent women who may enjoy and be well suited for science, but were discouraged from pursuing it at a young age.
I noticed this, too. The summary bullets at the end of the post also oppose the diagram. Probably a simple mixup of credit/debit in the left column. The rest of the article usually lists do it first.
> Can someone else publish your work to this system and take the money?
I had the exact same question. What sort of controls will the Tea team have to add/remove packages, or modify owners. And how would this be any different from centralized package managers?
I usually have a knee-jerk reaction when I see grammar and spelling errors in blogs, but I try to remind myself that these posts aren't published works that made it through an editorial staff. Mistakes happen, especially when the author isn't a professional writer.
I think that the artificial restrictions designed to make money are kind of the point. The digital realm is being constrained as if it were physical. These systems are being built on blockchain which is supposed to bring trustlessness and decentralized authority. Instead, virtual land is turning into land grabs the same way physical land does. The players profiting may be different, but the game is the same.
The monetary case seems like the natural first step. The name service case seems more interesting. It isn’t a financial instrument, so it demonstrates DAP utility for non-financial application.
You referenced a few standards that the DAPs adhere to, which lines up with assumptions I’ve had about the data schema management. In a generalized sense, it seems that community members, or a governing body, will propose changes, and if the community accepts them, the changes will be implemented into the network.
It seems to me the name service case has parallels to identity management through protocols such as SAML and LDAP.
But I’m still trying to wrap my head around examples I’ve heard such as building DAP social media apps that allow users to move their data to another DAP social app. Thinking of the social media sites we have today, they all consider their profile structures and models proprietary, as market differentiators that set each one apart from their competitors, and make up the “secret sauce” that gives social value to their users.
How would a DAP be able to maintain similar differentiators? Or is the expectation that only certain things such as basic profile information be stored on the blockchain, able to move to other DAPs, while other proprietary functionality is managed elsewhere?
> financial applications have been built on top of Ethereum that all share the same database and users can move from application to application, keeping their data (and their login credentials stored in their wallet) as they go.
Does anyone have examples of this in the wild? I often hear data portability listed as one of the great benefits, but I don’t have a grasp on what that actually means.
In my mind, the data needs to be structured to be useful, otherwise other DAPs wouldn’t be able to act on it. Who defines the structure? And who manages changes?