3 ms·
With the example.cue at the root of the repository, it's hard not to see this as user facing CUE: https://github.com/acorn-io/acorn/blob/06478f1173bbd758ca0c074
by verdverm 4y ago
With the example.cue at the root of the repository, it's hard not to see this as user facing CUE: https://github.com/acorn-io/acorn/blob/06478f1173bbd758ca0c07414b43a4c9295a62d7/example.cue https://github.com/acorn-io/acorn/blob/06478f1173bbd758ca0c0...
Having looked at the product more, I can see how people are getting confused. You expose CUE without saying it. As more people continue to adopt CUE, they will see the CUE in acornfiles. It's obvious to anyone familiar with the syntax.
There are several other issues with Acorn that seem to go the opposite way the market is going. I'll not relay them here because the other places we've conversed make it seem like you don't want any feedback critical of your product.
- V99 4y agoAs I said the other two places you posted about this, we spent a lot of time testing starting with vanilla CUE and concluded less would be more. You disagree, that's fine. Again if there's an Acornfile still called .cue somewhere, it's an oversight. You've pointed out an actual example now, so it's been removed.
- verdverm 4y agoThe best way to approach criticism is with curiosity rather than defensiveness, especially when it is from the community around a technology you are building on. One does not simply remove the file extension to remove the association, users will see through it.