3 ms·

The user-facing file is called "Acornfile", with no extension at all. We do not use .cue for anything a user would see. You're looking at files that are an int

by V99 4y ago

The user-facing file is called "Acornfile", with no extension at all. We do not use .cue for anything a user would see. You're looking at files that are an internal implementation detail (and are valid CUE).

minwell 4y ago
Is the "One artifact across dev, test, and production" idea borrowed from cnab.io ?
- verdverm 4y ago
  The packaging multiple images into one is unintuitive to me, especially when packaging a database with an app. What does this mean generally with image pulling and loading in kubernetes? Why is this a good idea for databases? Today we think of them as separate running entities. We have one database service, which multiple applications talk to today. How does Acorn work within / related to how we currently think about running services today. The docs leave one wanting and wondering.
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 ago
  As 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 ago
    The 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.

by V99 4y ago

minwell 4y ago

Is the "One artifact across dev, test, and production" idea borrowed from cnab.io ?

verdverm 4y ago
The packaging multiple images into one is unintuitive to me, especially when packaging a database with an app. What does this mean generally with image pulling and loading in kubernetes? Why is this a good idea for databases? Today we think of them as separate running entities. We have one database service, which multiple applications talk to today. How does Acorn work within / related to how we currently think about running services today. The docs leave one wanting and wondering.

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 ago
As 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 ago
  The 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.