perwendel / spark

A simple expressive web framework for java. Spark has a kotlin DSL https://github.com/perwendel/spark-kotlin
Apache License 2.0
9.65k stars 1.56k forks source link

please consider renaming the project #463

Closed vnwarrior closed 8 years ago

vnwarrior commented 8 years ago

https://www.google.co.in/search?q=spark+java+postgresql&oq=spark+java+postgresql&aqs=chrome..69i57.5059j0j1&sourceid=chrome&es_sm=93&ie=UTF-8

it is very, very, very hard to google for anything around this project because of the big name conflict with Apache Spark. and it becomes very hard to become productive.

Taking an inspiration from TypeScript, you could also call it TypeSpark (P.S. TypeSpark.org is available) ... but please consider having something we can actually look for.

tipsy commented 8 years ago

We're looking into it.

kodonnell commented 8 years ago

Agree with @vnwarrior on this one - any progress? I thought I'd point out that I'm running a (web) Spark app from (big data) Spark ... well trying to. Not only does this make things even more confusing (especially when I'm searching for documentation on both!), but also when you get dependencies with the same name (i.e. "spark-core" for both). It doesn't break things, but it did have me confused for a while.

tipsy commented 8 years ago

Little progress I'm afraid. It's a very hard problem that we don't really have the capacity/skills to do deal with properly. We're open to suggestions though.

kodonnell commented 8 years ago

I've never done it before (so I'm probably missing something), but why not decide a new name and migrate on the next big release? I wouldn't worry about backward compatibility (though there may be a clever way to do that), and just rely on existing users (who want to upgrade) to make the code changes (as they usually have to do with big releases anyway). Overall, it's not going to take them long (a few sed commands should do most of it).

Then I guess it's just admin stuff - create a new (renamed) fork on github (leaving the old one round for maintenance), update the website, etc.

tipsy commented 8 years ago

It's not that hard to "just do it", but to come up with a new name that makes sense and doesn't collide with anything else, and doesn't cause us to confuse/lose our entire userbase, is a challenge. Then there's changing all the branding, redirecting old links, explaining to people who click old links that the project has been renamed, etc.

sandys commented 8 years ago

+1 on this suggestion. Spark is a very confusing name and IMHO Apache Spark has the SEO + mindshare here.

I dont see a reason for fear. Firebird -> Firefox , Seomoz -> Moz, Typesafe -> Lightbend (the Scala company. Read here https://www.lightbend.com/blog/typesafe-changes-name-to-lightbend and here http://www.lightbend.com/blog/whats-in-a-name) are good examples.

Old links will not vanish - you will just have a 301 redirect. Plus, i would say that you would rank better and be more discoverable.

Also, i would simply post about this on Producthunt and Hacker News and call it a day.

On Wed, Nov 2, 2016 at 12:50 AM, David notifications@github.com wrote:

It's not that hard to "just do it", but to come up with a new name that makes sense and doesn't collide with anything else, and doesn't cause us to confuse/lose our entire userbase, is a challenge. Then there's changing all the branding, redirecting old links, explaining to people who click old links that the project has been renamed, etc.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/perwendel/spark/issues/463#issuecomment-257666322, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEsU6D2ipRtiezIXYMxgc2ITEpnrX2nks5q55EVgaJpZM4HaBMq .

kodonnell commented 8 years ago

@tipsy, I agree that it's not easy, however it's largely just documentation-level changes. Some feedback on your arguments:

I see @sandys just made similar points.

sandys commented 8 years ago

i actually like the name TypeSpark - you anways have "NodeJS Developer? Using/Curious About TypeScript? Try Spark Instead!" on the front page. Also the name is a derivative of the previous name .. so you are not very far away.

TypeSpark.org is still available.

tipsy commented 8 years ago

I dont see a reason for fear. Firebird -> Firefox , Seomoz -> Moz, Typesafe -> Lightbend (the Scala company. Read here

The comments there are absolutely brutal though.

how many more users would you have if Google hadn't shown them Apache Spark?

Not that many I would guess. If you already know what we're called you won't confuse us for Apache Spark, and for our most relevant web searches (like "java web framework"), Apache Spark is (obviously) not listed.

I have disliked the Spark name since I joined, so I understand where you're all coming from, but the vast majority of our users have never visited us on GitHub, and I'm not sure they know about Apache Spark. If we get one complaint about the name per hundred thousand views, I'm not sure it's worth changing. I still really want to though, and instead of releasing Spark 3.0 I would much prefer creating a new project XYZ 1.0. It bothers me a lot.

kodonnell commented 8 years ago

for our most relevant web searches (like "java web framework"), Apache Spark is (obviously) not listed.

It may be me, but when I was searching, I went for 'spark java' (after finding it on one of the blogs about the "best web frameworks for java" etc.), in the same way I generally search ' ' e.g. 'python flask'. In addition, when I saw your website URI (sparkjava.com) I kept using that. As you'll see, Apache Spark is definitely there (and it's likely to be there more in future, in part due to the likes of Zeppelin which are kind of web frameworks for Apache Spark).

Is there any way you can gauge the feeling of the wider Spark community?

sandys commented 8 years ago

why don't you just send a survey? post it on your github page front, hacker news, etc.

lets see what people want.

IMHO, you cannot beat google. and the first 10 results for anything related to spark is Apache Spark. and people google a lot to understand code

On Nov 2, 2016 4:13 AM, "David" notifications@github.com wrote:

I dont see a reason for fear. Firebird -> Firefox , Seomoz -> Moz, Typesafe -> Lightbend (the Scala company. Read here The comments there are absolutely brutal though.

how many more users would you have if Google hadn't shown them Apache Spark? Not that many I would guess. If you already know what we're called you won't confuse us for Apache Spark, and for our most relevant web searches (like "java web framework"), Apache Spark is (obviously) not listed.

I have disliked the Spark name since I joined, so I understand where you're all coming from, but the vast majority of our users have never visited us on GitHub, and I'm not sure they know about Apache Spark. If we get one complaint about the name per hundred thousand views, I'm not sure it's worth changing. I still really want to though, and instead of releasing Spark 3.0 I would much prefer creating a new project XYZ 1.0. It bothers me a lot.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/perwendel/spark/issues/463#issuecomment-257721369, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEsUyVsIZrfef9-X_K0n07uDk2NdisKks5q58ClgaJpZM4HaBMq .

jakaarl commented 8 years ago

I always defeat the "other Spark issue" by googling "sparkjava", but I guess that leaves out quite a bit of potentially useful search hits. So yes, perhaps a name change is in order. Some ideas:

I kind of like "frank" or "exude", since the Spark API allows one to be "quite frank" and "express" one self rather clearly.

ruurd commented 7 years ago

I'm sort of used to searching for perwendel spark... BTW, which project came first? perwendel/spark or apache/spark?

tipsy commented 7 years ago

If I remember correctly, Apache Spark has earlier commits than Spark, but Spark was launched before Apache Spark.

weickmanna commented 7 years ago

The name conflict is definitely a shortcoming of this web framework. The impact of Apache Spark is just too big. I wouldn't change to another web framework just because of this, sure. But if I were already thinking of changing for other reasons, it might "just push it over the top".