4 ms·
Using Go in anger for a few years has made me realise just how much a good package management solution adds to an ecosystem, and just how difficult a bad one ma
by cybrexalpha 5y ago
Using Go in anger for a few years has made me realise just how much a good package management solution adds to an ecosystem, and just how difficult a bad one makes life.
- sieabah 5y agoI've been flip flopping between Rust and Go and landed on primarily Rust due to not liking how imports are done by URL in Go. Probably works for Google, but it doesn't make sense for most use cases where you want to handle major version changes.
- prpl 5y agoThat’s fine when you are working within one language, but many of these people work on packaging across language boundaries (executables and libraries)
- BiteCode_dev 5y agoIf you don't embed a c lib, or don't need to setup a database.
- cpach 5y agoI can imagine FFI being tricky. But what’s tricky with regards to databases in this context?
- BiteCode_dev 5y agoIf your app depends on postgres, the current habits to state in the readme you have to install it and setup it yourself. That's not packaging. Goog packaging deals with that for you.
- cpach 5y agoI’m not sure I follow… If you write an application in Java/Javascript/Python/C/C#/C++/Racket/Common Lisp, isn’t it the same story there? I.e. that you’re expected to provide the DB yourself. If one desires a convenient solution there’s always Firebase, DynamoDB or even hosted PostgreSQL solutions. For local development one can spin up a Docker image for the DBMS.
- BiteCode_dev 5y agoYes, that's why packaging is more complicated as soon as you use more than your own language. Go solves only one problem, albeit very well.