proposal
Github-Ranking
Our great sponsors
proposal | Github-Ranking | |
---|---|---|
46 | 15 | |
3,285 | 5,241 | |
0.6% | - | |
4.4 | 9.5 | |
about 1 month ago | 2 days ago | |
Go | Python | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proposal
-
Does Go Have Subtyping?
The conclusion is pretty weird to me.
Go does rely on monomorphization for generics, just like C++ and Rust. The only difference is that this is an implementation detail, so Go can group multiple monomorphizations without worrying about anything else [1]. This form of hybrid monomorphization is being increasingly common, GHC does that and Rust is also trying to do so [2], so nothing special for Go here.
On the other hand, explaining variance as a lifted polymorphism is---while not incorrect per se---also weird in part because a lack of variance is at worst just an annoyance. You can always make an adopter to unify heterogeneous types. Rust calls it `Box`, Go happens to call it an interface type instead. Both languages even do not allow heterogeneous concrete (or runtime) types in a single slice! So variance has no use in both languages because no concrete types are eligible for variance anyway.
I think the conclusion got weird because the term "subtyping" is being misused. Subtyping, in the broadest sense, is just a non-trivial type relation. Many languages thus have a multiple notion of subtyping, often (almost) identical to each other but sometimes not. Go in particular has a lot of them, and even some relation like "T implements U" is a straightforward record subtyping. It is no surprise that the non-uniform value representation has the largest influence, and only monomorphization schemes and hetero-to-homogeneous adapters vary in this particular group.
[1] https://github.com/golang/proposal/blob/master/design/generi...
[2] https://rust-lang.github.io/compiler-team/working-groups/pol...
- Backward Compatibility, Go 1.21, and Go 2
- Defining interfaces in C++ with ‘concepts’ (C++20)
-
Why Turborepo is migrating from Go to Rust – Vercel
Go Team wanted generics since the start. It was always a problem implementing them without severely hurting compile time and creating compilation bloat. Rust chose to ignore this problem, by relying on LLVM backend for optimizations and dead code elimination.
-
Are you a real programmer if you use VS Code? No Says OP in the byte sized drama
Hold up, did the members actually push this forward or was support just often memed about and suddenly this proposal was made: https://github.com/golang/proposal/blob/master/design/43651-type-parameters.md
-
Major standard library changes in Go 1.20
As far as I can tell, the consensus for generics was "it will happen, but we really want to get this right, and it's taking time."
I know some people did the knee-jerk attacks like "Go sucks, it should have had generics long ago" or "Go is fine, it doesn't need generics". I don't think we ever needed to take those attitudes seriously.
> Will error handling be overhauled or not?
Error handling is a thorny issue. It's the biggest complaint people have about Go, but I don't think that exceptions are obviously better, and the discriminated unions that power errors in Rust and some other languages are conspicuously absent from Go. So you end up with a bunch of different proposals for Go error handling that are either too radical or little more than syntactic sugar. The syntactic sugar proposals leave much to be desired. It looks like people are slowly grinding through these proposals until one is found with the right balance to it.
I honestly don't know what kind of changes to error handling would appear in Go 2 if/when it lands, and I think the only reasonable answer right now is "wait and find out". You can see a more reasonable proposal here:
https://github.com/golang/proposal/blob/master/design/go2dra...
Characterizing it as a "lack of vision" does not seem fair here--I started using Rust back in the days when boxed pointers had ~ on them, and it seemed like it took Rust a lot of iterations to get to the current design. Which is fine. I am also never quite sure what is going to get added to future versions of C#.
I am also not quite sure why Go gets so much hate on Hacker News--as far as I can tell, people have more or less given up on criticizing Java and C# (it's not like they've ossified), and C++ is enough of a dumpster fire that it seems gauche to point it out.
-
Go's Future v2 and Go's Versioning
There will almost certainly not be a Go 2 in that sense. There is a Go 2 transition doc which extensively discusses what "Go 2" means. The conclusion is
-
What's the status of the various "Go 2" proposals?
As it says on that page - those were not proposals. They were draft ideas to get feedback on. You can see the list of proposals in this repository: https://github.com/golang/proposal
-
An alternative memory limiter for Go based on GC tuning and request throttling
Approximately a year ago we faced with a necessity of limiting Go runtime memory consumption and started work on our own memory limiter. At the same time, Michael Knyszek published his well-known proposal. Now we have our own implementation quite similar to what has been released in 1.18, but there are two key differences:
- Shaving 40% off Google’s B-Tree Implementation with Go Generics
Github-Ranking
- GitHub Ranking: Top Stars Projects
-
Awesome Lists is the GitHub side you probably never heard of, but you should definitely have a look!
5th highest number of stars of any repo on GitHub 🙃
- Ask HN: Why are so many PHP projects moving to Node?
-
Why are haskell applications so obscure?
This explains the uneven distribution of Haskell applications, but this does not explain why the distribution is more even in other languages. But is that even the case? You mention Python, and Python happens to be THE language of choice for data science projects, so I would expect to also see an uneven distribution there. And Java happens to be THE language of choice for writing Android applications, so I would expect an uneven distribution there too. And Rust is a systems programming language, so I would expect games and other things that really need to run fast. Let's look at lists of popular projects by language:
- Github Ranking: Github stars and forks ranking list. Github Top100 stars list of different languages. Automatically update daily.
-
My First Blog
The repo I chose was Github-Ranking, a repo to check the most starred and forked GitHub repos of the day. The link can be found here: https://github.com/EvanLi/Github-Ranking. I picked this repo because I've never explored the most popular repos before and this allowed me to see what a lot of people are working on.
- RustDesk ranks among top Rust open source projects now
- Top 10 Rust OSS projects updated
-
Benefits of React JS
Clocking in at 190K Github stars React's github ranking is easily ranked in the top 10.
-
Why We Switched from Python to Go
Here's a few other tools that are written in Perl, sorted by GitHub popularity: https://github.com/EvanLi/Github-Ranking/blob/master/Top100/...
Actually, that repo has lists like this for most languages: https://github.com/EvanLi/Github-Ranking
What are some alternatives?
go - The Go programming language
OnlyFans - Scrape all the media from an OnlyFans account - Updated regularly
vscode-gremlins - Gremlins tracker for Visual Studio Code: reveals invisible whitespace and other annoying characters
transformers - 🤗 Transformers: State-of-the-art Machine Learning for Pytorch, TensorFlow, and JAX.
avendish - declarative polyamorous cross-system intermedia objects
CSrankings - A web app for ranking computer science departments according to their research output in selective venues, and for finding active faculty across a wide range of areas.
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
tailwind-nextjs-starter-blog - This is a Next.js, Tailwind CSS blogging starter template. Comes out of the box configured with the latest technologies to make technical writing a breeze. Easily configurable and customizable. Perfect as a replacement to existing Jekyll and Hugo individual blogs.
golang-set - A simple, battle-tested and generic set type for the Go language. Trusted by Docker, 1Password, Ethereum and Hashicorp.
aur - A secure, multilingual package manager for Arch Linux and the AUR.
go-generic-optional - Implementation of Optionals in Go using Generics
gtunnel - Tunnel is a clean wrapper around native Go channel to allow cleanly closing the channel without throwing a panic.