I’m aware of that, and that’s why, if someone doesn’t want to pay, they can always compile from source. Cork and Cakebrew have a similar memory impact (both around 65MB).Cakebrew has these features that Cork lacks for now:.Cork has a more performant package installation workflow.Cork has support for showing more package metadata.Cork has a more user-friendly way of showing why packages fail do get uninstalled (an alert with an explanation of what happened, compared to Cakebrew just showing the terminal output of a failed command).Cork has support for package caveats (Cakebrew might also be able to show them, but I couldn't figure it out).Cork can pin packages to a specific version.A more comprehensive maintenance workflow (in addition to what Cakebrew can do, Cork can also uninstall orphans, purge caches and delete install bundles of downloaded packages).Cork has some features that Cakebrew lacks:.As an example, the first start of Cakebrew took around three times as long to get to a usable state compared to Cork (2 seconds for Cork, 7 seconds for Cakebrew)
0 Comments
Leave a Reply. |