You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an issue to track the repository rename to darwinkit. GitHub does redirect from old names to new names, but we also want to update the Go module name at the same time. I'm not entirely sure how this will impact older releases, I think as long as GitHub redirects they'll work fine.
So I think it would go smoothly, but to be safe I'm planning to do everything but rename the repository up until the actual 0.5.0 release. This will hopefully give a chance for anybody to point something out I haven't thought of.
As a minor discussion point that might as well live here, I'm curious whether people think the rename should be to "darwinkit" or something like "go-darwinkit". I'm not usually a fan of those kinds of prefix/suffixes unless it's a library made for several languages. There is the loose possibility that someday the generation toolchain could be used to make a DarwinKit for other languages, and I also feel like it might be helpful to indicate this project is .. for Go. But I don't have strong feelings either way. Let me know yours.
The text was updated successfully, but these errors were encountered:
I asked A.I. to come up with some names for this project. Here is what it came up with:
GoKit: A simple and catchy name that combines Go and Kit, implying that it is a toolkit for using Go with Apple’s frameworks.
GoSwift: A name that suggests that you can use Go as a swift alternative or complement to Swift, Apple’s native language for iOS, macOS, watchOS, and tvOS development.
GoApple: A name that emphasizes the compatibility and integration of Go with Apple’s platforms and technologies.
GoUI: A name that focuses on the user interface aspect of your project, which allows you to use Go with Apple’s UI frameworks such as UIKit and SwiftUI.
GoCore: A name that highlights the core functionality and performance of your project, which enables you to use Go with Apple’s core frameworks such as Core Data, Core Animation, Core Graphics, etc.
If you did decide to rename this project I would vote for GoKit. But if not darwinkit seems good enough.
This is an issue to track the repository rename to darwinkit. GitHub does redirect from old names to new names, but we also want to update the Go module name at the same time. I'm not entirely sure how this will impact older releases, I think as long as GitHub redirects they'll work fine.
So I think it would go smoothly, but to be safe I'm planning to do everything but rename the repository up until the actual 0.5.0 release. This will hopefully give a chance for anybody to point something out I haven't thought of.
As a minor discussion point that might as well live here, I'm curious whether people think the rename should be to "darwinkit" or something like "go-darwinkit". I'm not usually a fan of those kinds of prefix/suffixes unless it's a library made for several languages. There is the loose possibility that someday the generation toolchain could be used to make a DarwinKit for other languages, and I also feel like it might be helpful to indicate this project is .. for Go. But I don't have strong feelings either way. Let me know yours.
The text was updated successfully, but these errors were encountered: