ghiaadev

Tried a test run for my node repo. It worked fine when I used the semver version of the action, but not when I pin the action to the latest release hash as shown in the GitHub marketplace listing docs (Shouldn't the safer practice here work by default??)

Dask itself (and its commercial entity Coiled) seems to be investing heavily in the PyData/ml library ecosystem. I feel like it's about time until they reach feature parity, which would be a huge win for existing users of the PyData stack.

Electron all the way

Personally I think the MVC framework causes more overhead for startups. It's like trying to shoehorn your use case into complexity for nothing. Classic example of a best practice that needs to be revisited

I don't think its a good idea on take on Vault's complexity. One of the value props i see here is the simplicity of using 'garnet run <scope> -- <executable>' which is something you don't get in Vault unless you write a wrapper (although envconsul provides a similar abstraction: https://github.com/hashicorp/envconsul).

It is plausible that some of these new accounts were made in response to this post, but I don't think its fair to blame the project's developers for it as it isn't necessarily in their control. It seems like they are seeking feedback from the community and there doesn't seem to be a commercial plug here.