sdboyer

9 ms·

1.
by sdboyer 5y ago
I'd say all of these problems have answers in CUE. > I want to be able to write a "generic environment" module for each application and then parameterize it accordingly for each environment. This is pretty solidly in the t
2.
by sdboyer 5y ago
Cannot +1 this hard enough. It is the kernel from which all other useful things flow.
3.
by sdboyer 5y ago
If this is the sense in which the comment is intended - CUE is capable of some kinds of computation. It's just not Turing complete. My 2c - thus far, i've found the language features enabled by this constraint much more useful tha
4.
by sdboyer 5y ago
It's not necessarily easy to see, just from general descriptions of CUE, what's possible. Dagger was demo'd at the recent Dockercon - gives a bit more of a sense of the possible with CUE: https://docker.events.cube
5.
by sdboyer 5y ago
> real language In what sense is CUE not a real language?
6.
by sdboyer 5y ago
> you'll be able to serialize dashboards to Cue schema It'll be possible to serialize/represent the dashboards in CUE. Here's a handwavy, pseudocode-y example i use in the talk: https://gist.github.com&#x2F
7.
by sdboyer 5y ago
Very excited to see someone doing this! Right now, Grafana is [planned to] relying on an anemic CUE->Typescript translator for getting its schema to the frontend - https://github.com/sdboyer/cuetsy . (Somebody also p
8.
by sdboyer 5y ago
CUE is currently centered around its CLI, but AIUI, that's not the long-term goal. i read in some CUE issue somewhere that the goal is shifting towards enabling frameworks rather than driving people to the CLI, though i don't have
9.
by sdboyer 5y ago
re: Grafana (i'm the author of the linked issue) - i'm quite excited, i do think there's a world of possibilities here. Two-way sync with a git repo is one possible path, and we've talked a lot internally at GL about how
10.
Vgo Analysis: Failure Modes(sdboyer.io)
7 points by sdboyer 8y ago|0 comments
11.
by sdboyer 10y ago
in a post-dep world, this won't matter anymore. dep strips vendor directories out of any dependencies it pulls in.
12.
by sdboyer 10y ago
sadly, gb is one of the extant systems i haven't had a ton of time to explore. but... i guess the analogue to what you're describing would be 1. <add an import path> 2. `dep ensure` 3. `git commit -am "all of your vendo
13.
by sdboyer 10y ago
shit, if there were an actual company with real use for Merovingian numismatics, i would work there in a heartbeat
14.
by sdboyer 10y ago
Force pushes - by far more common than straight-up repository removal - are handled without problem; we let you stick with your old version. (At least, that's how it should be - there might be a couple more test cases to write. I know
15.
by sdboyer 10y ago
yeah, this is one of the main pain points there. the reason it's so difficult to solve in glide is intrinsically tied to the engine glide uses for version selection - otherwise we'd have dealt with it long ago.
16.
by sdboyer 10y ago
indeed, we've talked with them quite a bit :)
17.
Gta – test combinations of deps (golang)(github.com)
1 points by sdboyer 10y ago|0 comments
18.
by sdboyer 10y ago
nix/guix was not ignored. There are a host of other reasons that we could happily debate for years (no thanks), but bottom line: you can't use it everywhere you can write/compile Go code.
19.
by sdboyer 10y ago
it is, and works well enough for individuals, but doesn't make for the friendliest ecosystem.
20.
by sdboyer 10y ago
dep mgmt, at least, is poised to improve a lot in the coming months. we've got growing consensus around some metadata files, and i'm nearly done with my SAT solver (github.com/sdboyer/vsolver), which will be in glide, an
21.
by sdboyer 10y ago
> and then be able to compose the things you’ve proved separately This has always struck me as the really challenging, problematic part about correctness proofs. I've no formal training in this area (sadly), but how does one go a
22.
by sdboyer 11y ago
> Language package managers are good for quickly sharing code written purely in that language with other developers, but unacceptable for anything else. Right, so, what almost all of the FLOSS world is doing, almost all of the time. Miii
23.
by sdboyer 11y ago
A community, gaslit by years of poor tooling, IMO
24.
by sdboyer 11y ago
> What Nix/Guix are not doing is reducing the burden of specification. You write down all the details of a very specific, reproducible software stack, but you do not make that software much more composable or extensible than it alre
25.
by sdboyer 11y ago
Nix/Guix have been brought up a bunch of times in follow-ups. I was aware of Nix (though not Guix) before writing the piece, and I do need to check it out. But... The primary requirement for a PDM is that developers will actually use
26.
by sdboyer 11y ago
fwiw, folks on twitter suggested to me that npm may be moving in something like my "sync-based PDM" direction: https://twitter.com/rebeccaorg/status/698370989386694657
27.
by sdboyer 11y ago
Well, spoiler then: I don't advocate for generic package management. That's someone else's problem. Maybe, if the ideas I've put forth in there lay useful foundations, it's something that could happen, but I very mu
28.
by sdboyer 11y ago
I considered including some mention of crypto assurances of packages in the article. I did not, because it would take someone who knows the constraints dictated by such systems far better than I to come up with a means by which such mechani
29.
by sdboyer 11y ago
Glad you like glide, and thanks! Though I'm at the very most a co-author - I've contributed only ideas so far, and maybe a comment fix or two. Now that I'm finally done writing this, maybe I can write some code.
30.
by sdboyer 11y ago
As long as I briefly have HN's attention - how did y'all find the repo-as-universe, and universe alignment, metaphors? Useful? (This was the diagram leading up to it: http://imgur.com/bzy22DA )

More ›