indeed, I like your project. Negativity of the community can be discouraging. I stopped a project of mine because of a combination of the negativity and from the reality of having to hiring and train people to use my language.
/r/programming is one of the most pedantic forum I have ever seen but I also see it as a place where programmers flee and shelter from the non-technical bullshit and vent a bit.
If you submit anything there, be prepared for harsh criticism. There is some real value in there, but encouragement and cheerings won't come from there.
My experience is that there is a lot of toxicity on the internet, but also outside of it. I'm disappointed by how toxic, money-obsessed, and ignorant many people are. On the internet, all that is concentrated and delivered straight to your face.
I would recommend presenting projects first in person to people before putting them on the internet for debate.
Imagine how it must be for the people behind Rust. Yet, people from the team regularly show up, are polite and nice and are open to arguments in spite of all the negativity they surely face. I think it is easy to become bitter, suspicious, and unfriendly when faced with social pressure, but they seem to continuously find the arguments in even not so polite comments and patiently give good insights and own arguments.
I intend to write about this, and this is a reason I am keeping some of my personal projects less open source and invite very few people in that I can mentor.
I think it is a shame that the default tends to be negative comments rather than constructive, but I also recognized that giving into toxic emotions is easy.
In the demo video (https://youtu.be/Rwo6KJ_Pa9Q) there is a part where I am editing the same code in 4 languages (C#, TypeScript, Ruby and PHP) simultaneously.
But yeah, generally only a limited subset of a language is supported. This is the price of writing code targeting multiple language. That's why you cannot (and probably won't be able to) convert existing code.
I am probably not emphasizing this enough, but One is currently a "toolkit" for converting syntax between languages.
`Math.random()` is ~a standard library function. One has limited knowledge about language's StdLibs. But you can make `Math.random` (or any method) work without modifying the compiler, only by adding the appropriate implementation and StdLib definitions to appropriate files. (Even now only using the WebIDE).
The plan is to make One plugin-able and create a "package" manager infrastructure, so anybody can implement `Math.random()` or any other methods, publish it and then you can just download that package.
Implementing every language's StdLib is not a one-man job, so I've always considered this out-of-scope.
Sorry if any published information regarding this was misleading.
Oh, ok I think I understand it better. That sounds like a really useful tool. Actually in a project I was in last year we really hesitated between writing a lib in C++, C# or Java (Native android, Unity3D lib, Android java) and had good arguments for either but no budget for maintaining all three.
I would have seriously considered your option at the time.
I have no time to dive into this now but I'll bookmark it and come to wave at your gitter.
Is it realistic to contribute to it with knowledge of C++/C#/Java/Python but a pretty poor grasp of JS?
Tl;dr: you cannot use One in production now, but the grand plan is to make One as hackable and flexible as I can.
So here is the plan:
- the compiler does not contain any target language-specific part, you can add a new language by creating a few hundred lines of template file (this actually works already, it is not just a plan)
- rewrite One in One, so you can convert from any language to any language in any language
- there is no StdLib, but libraries can be created by anyone. We publish interface and implementation definition separately, and you can eg. implement a Web client interface for PHP and Node, while somebody else can implement it for C# and Swift. Behaviour defined by interface tests, if your implementation passes interface test => good. If there is no test for an edge-case => undefined behaviour. Read more here: https://github.com/koczkatamas/onelang/issues/9
- you write a library in One and it helps you to publish to every language's package manager (npm, pip, NuGet, etc). You can reach much more developer with your library compared to targeting only one lang's developer base
This idea has been ronning around in my head, paired with a mining and crypto element.
The language specific implementations of those interfaces could be mined(by hand or automated) for coins to directly incentivise engineering effort. The block acceptance would be based on the universal tests/benchmarks passing.
