Live data from Hacker News

Programming languages that are actively developed on GitHub

github.com

111–120 of 133 posts

Re: Programming languages that are actively developed on GitHub

#111
post #94

No offense, but this list is stupid in its current ordering if the order is meant to imply anything. I heavily use rust, python, and go and have not starred any of the repos because I have faith the current contributors and don't need to helicopter over current issues/PRs. Stars are for following a project because you need to pay attention to breaking changes, bugs, and major feature releases. If you need to do that…

GitHub has a distinction between 'Starring' and 'Watching' a repo.

A star is a far lesser commitment than you imply - it's a glorified browser bookmark / facebook-thumbs-up.

Re: Programming languages that are actively developed on GitHub

#112
post #104

Also missing: Ceylon - currently with 191 stars https://github.com/ceylon/ceylon

It has a nice homepage and good examples but what would a language like this provide over something like Kotlin? Also, I had to dig down into the homepage to find out that it compiled down to JVM byte code.

Well, you could turn it around since Ceylon is older than Kotlin ;)

There's not a huge difference between the syntaxes, but IMHO Ceylon integrates better with the general JVM ecosystem. It has an excellent module system and works well with OSGi too. Ceylon + Vert.x is a powerful combo.

Re: Programming languages that are actively developed on GitHub

#113
post #27

Wow Go has really gained traction. Coming from a Python, PHP, JavaScript background I have been contemplating learning Go or Elixir this year. I am drawn to Elixir because of the functional approach which is different than what I am used to.

I've been learning both this year. Go at work and Elixir in my spare time. Both have a lot of similarities and the differences largely boil down to some root design decisions.

They are both great languages. I find Elixir to be more applicable to most of the work that I do (web work), personally. Phoenix is so much more polished than any of the web options in Go, I'd tend to make it my default. Go is where I'd reach when I needed to performance tune a very specific piece of a system generally. Can be a bit tedious for high level things.

Re: Programming languages that are actively developed on GitHub

#115
post #109
post #72

Ruby's main repository is on a subversion server at svn.ruby-lang.or and GitHub is a mirror. See https://www.ruby-lang.org/en/community/ruby-core/ The wiki and the issues are also lacking from GitHub because they are on a Redmine server at https://bugs.ruby-lang.org/ GitHub was written in Ruby (and Rails) so the issue tracker already existed and they felt it wasn't worth migrating it. I can understand why they don't…

The core team indicated they quite like the sequential numbering that SVN gives them. I'm considering building it into GitLab as an option if they would use it to host ruby :)

Mercurial and bzr have those sequential numbers. They really aren't the awful apocalyptic problem that git users seem to think they are. bzr tries harder to make them sequential and meaningful, but even hg's more lax approach to revision numbers is still useful: they are still approximately semantic, much more than node hashes.

Re: Programming languages that are actively developed on GitHub

#116
post #112

Earlier quoted context omitted.

It has a nice homepage and good examples but what would a language like this provide over something like Kotlin? Also, I had to dig down into the homepage to find out that it compiled down to JVM byte code.

Well, you could turn it around since Ceylon is older than Kotlin ;) There's not a huge difference between the syntaxes, but IMHO Ceylon integrates better with the general JVM ecosystem. It has an excellent module system and works well with OSGi too. Ceylon + Vert.x is a powerful combo.

I should have done my research. I assumed since Kotlin has large support it has been around longer. Thanks!

Re: Programming languages that are actively developed on GitHub

#117
post #5

Some of these languages (ponyc) are still...prototypes. Yeah you can get them working for a limited set of "working" and with very specific setup->configurations. If every language included a Docker or VM with it already set up for some level of demo, I think a rate for adoption/learning them would uptick.

> If every language included a Docker or VM with it already set up for some level of demo, I think a rate for adoption/learning them would uptick.

Programming languages are for programmers - the kind of people that run programmer-friendly OSs/distros and figure out how to make their own packages when needed.

You don't need containers and virtual machines when you can simply "emerge dev-lang/pony" and be on your merry way.

Anyway, Pony is not the right example for the point you're trying to make because it already provides Gentoo, Arch, Debian, RedHat, macOS and Windows packages plus a Docker image.

Re: Programming languages that are actively developed on GitHub

#119
post #109
post #72

Ruby's main repository is on a subversion server at svn.ruby-lang.or and GitHub is a mirror. See https://www.ruby-lang.org/en/community/ruby-core/ The wiki and the issues are also lacking from GitHub because they are on a Redmine server at https://bugs.ruby-lang.org/ GitHub was written in Ruby (and Rails) so the issue tracker already existed and they felt it wasn't worth migrating it. I can understand why they don't…

The core team indicated they quite like the sequential numbering that SVN gives them. I'm considering building it into GitLab as an option if they would use it to host ruby :)

Inspired by Mercurial, we built such functionality for GIT backend in RhodeCode. So the numeric identifiers are used now for all 3 backends we support. Kallithea has it also implemented for GIT.

I personally never like the meaningless hashes. Those numbers act as good identifier of project size and progress. It quickly shows what kind of ranges we're taking when doing a compare, or simply looking at files and seeing those numbers.

It gives a lot of context. Just look how much more useful information a compare shows r1808:39334bf35fdf...r1819:3e8df3a82397 vs 39334bf35fdf...3e8df3a82397

Re: Programming languages that are actively developed on GitHub

#120
post #109
post #72

Ruby's main repository is on a subversion server at svn.ruby-lang.or and GitHub is a mirror. See https://www.ruby-lang.org/en/community/ruby-core/ The wiki and the issues are also lacking from GitHub because they are on a Redmine server at https://bugs.ruby-lang.org/ GitHub was written in Ruby (and Rails) so the issue tracker already existed and they felt it wasn't worth migrating it. I can understand why they don't…

The core team indicated they quite like the sequential numbering that SVN gives them. I'm considering building it into GitLab as an option if they would use it to host ruby :)

I'd like to understand how it could work. For the simple case with a master branch and one feature branche we could number commits as they are merged into master. What about two branches worked on at the same time, with multiple commits and merged to master? If the numbering has to reflect the timestamps of the commits it should be recomputed at every merge which is probably not desirable. However every branch has its own numbering and I don't know if it's desirable to have two numbers for the same commit.

Would you implement it using tags?

Post reply on HN