4 ms·
first off, I agree that file-based content management is the way to go. thank you for working to make better tools for it. > we wanted something 1) faster and
by mitchtbaum 8y ago
first off, I agree that file-based content management is the way to go. thank you for working to make better tools for it.
> we wanted something 1) faster and 2) easier
1) a) why didn't you write a new library using the same spec? b) do you have speed tests to show your libraries are better than existing ones?
2) how is this spec easier? (like a basic rundown)
- RussianCow 8y ago> b) do you have speed tests to show your libraries are better than existing ones? The OP linked to their benchmarks in [3]: https://github.com/eno-lang/benchmarks/ https://github.com/eno-lang/benchmarks/
- simonrepp 8y agoHey, first off thanks! :) 1a) because faster was only one aspect, it also needed to be easier, even more pressingly that in fact. 1b) see answer by other poster (thanks!) 2) Not whitespace sensitive, no way to enter wrong types through syntax mistakes, hardly any learning curve for users because there is so little syntax to memorize, fully localized, hand written parser and validation errors (provided on the library side) ... and so on, check out the website for more, it's all there! ;) Thanks!