A couple of days ago, I passed by the community training class and saw the teacher at the door trying to recruit students, while also stopping a few passing children to say a few words. In the past, students would seek out teachers, but now it's the opposite; those willing to teach a bit more are the ones who have the opportunity to retain people.
The developer ecosystem of the privacy chain is actually in this state as well. The barriers are high, the tools are immature, and most people prefer to stay in familiar environments, unwilling to spend time exploring an uncertain direction. It's not that they don't want to do it, but the cost is too high.
@MidnightNetwork has a straightforward approach regarding this matter; instead of waiting for developers to figure it out themselves, they actively lower the barriers. The Compact language uses a TypeScript-like approach, allowing developers who originally wrote for Web2 and front-end to directly get started without first having to digest a pile of underlying cryptography. The tools and documentation are also designed to be as user-friendly as possible, with the goal of enabling people to get up and running quickly, rather than getting stuck at the first step.
At the same time, they are tiering the developers. The Aliit Fellowship brings in a group of experienced individuals to write templates, create tutorials, and mentor newcomers. Additionally, by clearly providing desired application directions, they reduce hesitation in topic selection.
This logic isn't complicated; it's about proactively attracting people, teaching them, and providing direction. The key isn't in the design, but in the details. Whether the tools are user-friendly, whether error messages are clear, and whether the community has people who respond in a timely manner—these factors ultimately determine whether developers will stick around.
The real validation isn't in the white paper; it has to be seen after the mainnet goes live, whether anyone can use Compact to create usable applications. Only when it can run, can the ecosystem truly be considered to have begun.
#night $NIGHT
The developer ecosystem of the privacy chain is actually in this state as well. The barriers are high, the tools are immature, and most people prefer to stay in familiar environments, unwilling to spend time exploring an uncertain direction. It's not that they don't want to do it, but the cost is too high.
@MidnightNetwork has a straightforward approach regarding this matter; instead of waiting for developers to figure it out themselves, they actively lower the barriers. The Compact language uses a TypeScript-like approach, allowing developers who originally wrote for Web2 and front-end to directly get started without first having to digest a pile of underlying cryptography. The tools and documentation are also designed to be as user-friendly as possible, with the goal of enabling people to get up and running quickly, rather than getting stuck at the first step.
At the same time, they are tiering the developers. The Aliit Fellowship brings in a group of experienced individuals to write templates, create tutorials, and mentor newcomers. Additionally, by clearly providing desired application directions, they reduce hesitation in topic selection.
This logic isn't complicated; it's about proactively attracting people, teaching them, and providing direction. The key isn't in the design, but in the details. Whether the tools are user-friendly, whether error messages are clear, and whether the community has people who respond in a timely manner—these factors ultimately determine whether developers will stick around.
The real validation isn't in the white paper; it has to be seen after the mainnet goes live, whether anyone can use Compact to create usable applications. Only when it can run, can the ecosystem truly be considered to have begun.
#night $NIGHT