![]() ![]() Just build the app (CMD+B) and then Archive it > Copy App > navigate to Applications and confirm to save the app there. I think that providing the source code, plus detailed and understandable instructions for compiling, and the level of community engagement that I do, is well beyond what some other projects do, while asking for even more. ![]() Even though my initial plan was to make Cork’s compiled versions completely free for everyone, according to my previous experience as an open source developer and a member of other FOSS communities, I have discovered that this approach is just not sustainable to me. The reality of being an open source developer is that people always expect the world from you while not providing anything in return. I put a great deal of effort into making the compilation instructions understandable and accessible.Ĭreating the app, responding to bug reports, implementing new features, fixing bugs and engaging with the community takes massive amounts of time and effort, not even including the work needed to maintain a Homebrew tap and a cask. 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) At least on my computer (M1 Air), Cork is more performant, with the UI feeling a bit faster.That doesn't mean that Cakebrew is poorly designed at all, and many would prefer the more classic macOS design, but to those that prefer the "modern" macOS look, Cork is closer Cork is more in line with modern macOS design principles.Cork is in active development, while Cakebrew seems to be abandoned (no commits to the repo since March 2021).Cork has a free and usable demo, but it is not getting future updates, except critical bug and security fixes You can still compile Cork from source, which makes it inaccessible to less tech-inclined users that want Cork for free. Right off the bat, Cakebrew is available pre-compiled, while pre-compiled versions of Cork are not. ![]() I have not used Cakebrew before, so I downloaded it and played around with it a bit, and these are the main things that I have discovered (I'm doing my best to not be biased :D ): ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |