| ▲ | Cue Does It All, but Can It Literate?(xlii.space) |
| 41 points by xlii 4 days ago | 11 comments |
| |
|
| ▲ | spookylukey 3 hours ago | parent | next [-] |
| Please, please - just link to the actual "CUE" project. Not everyone has heard of your favourite thing. The first reference to `CUE` should be a hyperlink. For other people: I'm pretty sure the author is talking about https://cuelang.org/ |
| |
|
| ▲ | solatic 3 hours ago | parent | prev | next [-] |
| Is there anyone out there that has actually, in the real world, realized CUE's promise of bundling type safety + data/configuration + task running in such a way that does not require wrapping it in shell scripts? Can you set up your CI/CD pipelines so that it's literally just invoking some cue cmd, and have that cmd invocation be reasonably portable? The problem is, once you have to wrap CUE, the loss of flexibility within a special-purpose language like CUE is enough for people to ask why not just bother writing the scripts in a general purpose language with better ecosystem support. And that's a hard sell in corporate environments, even ones that find benefit in type safe languages in general, because they can just pick a general purpose language with a static type checker. |
| |
| ▲ | teh 11 minutes ago | parent | next [-] | | I can't fully answer your question but I did once spend about a week porting plain internal configuration to cue, jsonnet, dhall and a few related tools (a few thousand lines). I was initially most excited by cue but the novelty friction turned out to be too high. After presenting the various approaches the team agreed as well. In the end we used jsonnet which turned out to be a safe choice. It's not been a source of bugs and no one complained so far that it's difficult to understand its behaviour. | |
| ▲ | mxey an hour ago | parent | prev | next [-] | | Not sure if that’s what you mean but we have apps where all you need to deploy them to Kubernetes is run “cue cmd deploy”. > The problem is, once you have to wrap CUE, the loss of flexibility within a special-purpose language like CUE is enough for people to ask why not just bother writing the scripts in a general purpose language with better ecosystem support. cue cmd is nice but it’s not the reason to use CUE. The data parts are. I would still use if I had to use “cue export” to get the data out of it with a bit of shell. | |
| ▲ | maccard an hour ago | parent | prev | next [-] | | I can't speak for CUE, but I've worked with CI and "build orchestration tools"in the past. Most CI providers provide executor APIs that let you override it as a plugin. One example is https://buildkite.com/resources/plugins/buildkite-plugins/do... - you mark this as "this is using docker" and configure it in the environment, and then you provide the command. You need to be very careful about the design of the plugin, but I've done it a few times and it's viable. | |
| ▲ | CuriouslyC 2 hours ago | parent | prev [-] | | Cue.js has a wasm port. I really like cue for my spec driven development tool Arbiter, it is great for structured specs because it acts like a superset of most configuration/programming languages. |
|
|
| ▲ | jddj 2 hours ago | parent | prev [-] |
| Maybe it's unfair, unhelpful or overdone to call out llmisms, but if OP is reading this I stopped reading pretty quickly as a result of things like: > [CUE] does not just hold the text; it validates that the pieces actually fit. It ensures that the code in your explanation is the exact same code in your final build. It is like having a Lego set where the bricks refuse to click if you are building something structurally unsound. And that's despite having a passing interest in both cue and LP |
| |
| ▲ | CuriouslyC an hour ago | parent | next [-] | | Ah, the negative positive construction. Another casualty of the anti-AI movement. The semicolon was almost certainly inserted manually in place of an em-dash, models almost never use them. | | |
| ▲ | jchw an hour ago | parent [-] | | Accusing people of using generative AI is definitely one of those things you have to be careful with, but on the other hand, I still think it's OK to critique writing styles that are now cliche because of AI. I mean come on, it's not just the negative-positive construction. This part is just as cliche: > It is like having a Lego set where the bricks refuse to click if you are building something structurally unsound. And the headings follow that AI-stank rhythmic pattern with most of them starting with "The": > The “Frankenstein” Problem > The Basic Engine > The Ignition Key > The Polyglot Pipeline I could go on, but I really don't think you have to. I mean look, I'm no Pulitzer prize winner myself, but let's face it, it would be hard to make an article feel more it was adapted from an LLM output if you actually tried. |
| |
| ▲ | bakugo an hour ago | parent | prev [-] | | > Maybe it's unfair, unhelpful or overdone to call out llmisms Not anywhere near as overdone as posting AI generated/revised articles to HN that are an absolute slog to read. A real shame, honestly, because the other article[1] from this blog that made it to the front page recently was good. The difference in writing style between them is striking, and I think it serves as a really good example of why I just can't stand reading AI articles. [1] https://xlii.space/eng/i-hate-github-actions-with-passion/ |
|
