5 ms·

There already was a GO programming language before Google decided to use the name, too.

by FreeFull 4y ago

subtra3t 4y ago
That doesn't justify them choosing an already chosen name now, does it?
- sieabahlpark 4y ago
  Unless it's trademarked it doesn't matter in the slightest
- laumars 4y ago
  I didn’t read the GPs comment as a justification.
- Beltalowda 4y ago
  Rune (the existing language) is a fairly small hobby project that only got started in 2020. The developer of this new Rune probably just didn't know about it. There is nothing nefarious here. There is no cabal. These things happen all the time. I've had it happen to two of my own small/obscure projects. It happens.
  - pkolaczk 4y ago
    Goggle's Rune is even a smaller hobby project.
tmtvl 4y ago
Ah, so they're repeat offenders. How's it go again? Cache invalidation, naming tconcurrencyhings, , and off-by-one errors?
- aredox 4y ago
  Google: - leader in AI and text generation - unable to find or create original names for langs
  - shit_game 4y ago
    Given how poor their search engine performs as of late, it's no surprise they can't seem to be original; they obviously can't find anything that already exists.
  - gl-prod 4y ago
    Hey listen, namin things is really hard
  - Avicebron 4y ago
    Nah they're doing just fine. I was googling alien porn and I landed here
xiaq 4y ago
As some other comments have pointed out, this seems to be a one-person project. FWIW, Go also started as a project by 3 people who happened to be working for Google (Robert Griesemer, Rob Pike and Ken Thompson), so it wasn't Google consciously choosing the name. Perhaps Google as an employer shouldn't allow employees to choose any name they like, and do some diligence to avoid name clashes. This may sound quite reasonable for outsiders, but internally this will be another step that requires manual review in the process of publishing open source code, and employees will see this as red tape and get discouraged from open sourcing their code in the first place. The benefit of requiring every project to go through a name clash review is also questionable: there are 2.5k repos under https://github.com/google https://github.com/google, and most of the them will never become popular enough for name clashes to be a problem anyway. This repo only has 177 stars despite hitting HN homepage. IMO Google should instead make it easy for people to publish their open source code wherever they like, but I suppose there are some messy legal reasons why they prefer employees to put their repos under https://github.com/google https://github.com/google. (It's not a hard requirement, but they do make you jump through extra hoops to open source your code elsewhere.) (I'm a Google employee, but I didn't know this project and don't work for the department responsible for the process of open sourcing code.)
- wycy 4y ago
  It shouldn’t need to be a company policy, you’d think a competent engineer would simply do due diligence in naming their project. I remember searching for name clashes for a project I wrote solo when I was ~13 years old in the early 2000s.
  - kweingar 4y ago
    Unfortunately Rob Pike, Ken Thompson, and Robert Griesemer are not competent engineers by this standard. I’m sure they’ll be sad to hear it.
    - tom_ 4y ago
      The competence is assumed. The disappointment comes from people who are competent not doing the due diligence that some think should be par for the course when naming a project.
throwaway50100 4y ago
Correction, there was a "Go!" programming language.
kybernetyk 4y ago
There also was a singer before Apple decided to name their programming language ;)

There already was a GO programming language before Google decided to use the name, too.

subtra3t 4y ago

That doesn't justify them choosing an already chosen name now, does it?

sieabahlpark 4y ago
Unless it's trademarked it doesn't matter in the slightest
laumars 4y ago
I didn’t read the GPs comment as a justification.
Beltalowda 4y ago
Rune (the existing language) is a fairly small hobby project that only got started in 2020. The developer of this new Rune probably just didn't know about it. There is nothing nefarious here. There is no cabal. These things happen all the time. I've had it happen to two of my own small/obscure projects. It happens.
- pkolaczk 4y ago
  Goggle's Rune is even a smaller hobby project.

tmtvl 4y ago

Ah, so they're repeat offenders. How's it go again? Cache invalidation, naming tconcurrencyhings, , and off-by-one errors?

aredox 4y ago
Google: - leader in AI and text generation - unable to find or create original names for langs
- shit_game 4y ago
  Given how poor their search engine performs as of late, it's no surprise they can't seem to be original; they obviously can't find anything that already exists.
- gl-prod 4y ago
  Hey listen, namin things is really hard
- Avicebron 4y ago
  Nah they're doing just fine. I was googling alien porn and I landed here

xiaq 4y ago

As some other comments have pointed out, this seems to be a one-person project. FWIW, Go also started as a project by 3 people who happened to be working for Google (Robert Griesemer, Rob Pike and Ken Thompson), so it wasn't Google consciously choosing the name. Perhaps Google as an employer shouldn't allow employees to choose any name they like, and do some diligence to avoid name clashes. This may sound quite reasonable for outsiders, but internally this will be another step that requires manual review in the process of publishing open source code, and employees will see this as red tape and get discouraged from open sourcing their code in the first place. The benefit of requiring every project to go through a name clash review is also questionable: there are 2.5k repos under https://github.com/google https://github.com/google, and most of the them will never become popular enough for name clashes to be a problem anyway. This repo only has 177 stars despite hitting HN homepage. IMO Google should instead make it easy for people to publish their open source code wherever they like, but I suppose there are some messy legal reasons why they prefer employees to put their repos under https://github.com/google https://github.com/google. (It's not a hard requirement, but they do make you jump through extra hoops to open source your code elsewhere.) (I'm a Google employee, but I didn't know this project and don't work for the department responsible for the process of open sourcing code.)

wycy 4y ago
It shouldn’t need to be a company policy, you’d think a competent engineer would simply do due diligence in naming their project. I remember searching for name clashes for a project I wrote solo when I was ~13 years old in the early 2000s.
- kweingar 4y ago
  Unfortunately Rob Pike, Ken Thompson, and Robert Griesemer are not competent engineers by this standard. I’m sure they’ll be sad to hear it.
  - tom_ 4y ago
    The competence is assumed. The disappointment comes from people who are competent not doing the due diligence that some think should be par for the course when naming a project.

throwaway50100 4y ago

Correction, there was a "Go!" programming language.

kybernetyk 4y ago

There also was a singer before Apple decided to name their programming language ;)