2 ms·
Building something alone is how all projects start. A single person initiates it, either by proposing it, by planning it or by building it. That initiation is t
by lelanthran 4y ago
Building something alone is how all projects start. A single person initiates it, either by proposing it, by planning it or by building it. That initiation is the result of a single vision.
At some point others are added (other people support the proposal, other people contribute to the design or other people join the building effort), and that vision will not be perfectly shared by everyone.
Sure, they may all be heading towards the same general idea, but the specific destination will be different to each member of the group.
The case for building something alone is the default case. Any change from the default case needs a motivation, such as:
1. The intended final product will be too large for a single person to build (for example, a single person can build a garage, but they won't be able to finish a skyscraper in their lifetime).
2. The intended final product has an ETA that is past the time when it is needed (for example, a single person can build a small house in a few years, but that is moot if they need that house in a few months (baby on the way, getting married, getting thrown out, etc))
3. The final product needs expertise from several different industries (for example, building a shed needs only building and a rudimentary engineering expertise, while building a bridge requires sign-off from multiple experts in different disciplines).
Now, when building a programming language, it's clear that none of the above are required: a single person can build it, can do so relatively quickly, and requires no other expertise than some undergrad CS (see Javascript).
To make it popular and useful, though, requires a ton of libraries, which is where the group/team approach is needed. A single person can probably not produce a standard library that (for example) is as comprehensive as that shipped with Java or C#.
Therefore, the author is on the right track here, so far. If, at some point, the author wants to add features to his language that makes it competitively useful with other languages in that domain, he will have to start accepting contributions.
- deleted 4y ago[deleted]