-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Will node-webkit change names? #2745
Comments
Yeah. And #2742 makes the 'node-' part irrelevant as well. Any suggestions on the new name? |
Yes. I think we should not call it something that suggests a dependence on some specific technology. Both because it can (and has) change(d), but also because it won't be complete and, well... it's just not a good idea! :) Suggestions: JS Desktop |
Suggestions: Native Web So that acronym stays with nw. |
Let's see... Joint Sdk (JSdk) Good luck node-webkit ;) |
Wang Kit. Say it out loud. I'm sorry. |
I also think the acronym "NW" should stay intact. Was the compass picked as node-webkit logo, because NW means also "Northwest"? (but compass on icon points actually to Northeast :) ) So maybe call it NorthWest? |
@szwacz not bad. As long as people don't mind that it's also the name of Kim & Kanye West's child. |
NW? Native Wannabe :P |
If nw is going to move to io.js, perhaps it makes sense to follow a similar name convention (e.g. nw.js). |
nw.js actually is a pretty good name. Cryptic enough to allow for changes in tech, and short. |
+1 for nw.js. That way you don't have to change things that were already referring to nw, and people looking for node-webkit not knowing the change are still likely to find it and understand its the same thing. |
+1 for nw |
+1 for nw or |
smiling-Jack: Seriously? You keep talking about Webkit even though it's not been in the product for a long time? |
+1 for nw (with the variations of NW, nw.js or nw-js) |
chromeo (yeah, it's already closed by musical duet, and also chromeo in transcription for russian language means as 'lame man') also, suggested earlier nw.js & nw-app looks nice. |
DesktopJS could be fine. node.js brought us server-side JS, and node-webkit helped us create fully-functional desktop apps in JS. |
blinkJS! Or maybe, blink.io? nw-app, suggested by @smiling-Jack sounds good too. |
nw.js |
"Native Wannabe.js" which in short will be nw.js :) |
nw.js fits the best for a variety of reasons. So it's settled. |
BlinkDesk |
node-ui |
nw.js is good, but there is more than javascript in the whole product.. webdesk (silverlight and flash are already taken) |
moonlight also taken.. |
Ok, so far, so good. We have a plenty candidates. How do we gonna choose now? Vote? Or Roger will decide for us ?:) |
Vote to help Roger decide 👍 |
Stop spamming Google cancer, please. |
As a noob I had a recent experience in finding nw and understand what it was. I think it could be faster to get when the name means clearly what it does, so Mu vote goes to DesktopJS. I also user this tags to search for it: portable js, deploy, js executable, app js and so on. |
As @allencblee suggest NativeWeb sounds pretty close to what it does since it brings the web to native desktop app. It also keeps the nw intact. |
NativeWeb is also a really good name! |
NWJS |
|
NoBlink ( for Whovians ^_^ ) |
Web.IO ? |
nnw – not node webkit :) |
Chromio => (Chrom+iojs) |
Since we're replacing webkit with blink and node with io.js, how about |
+1 for blink.io |
*0 for blink.io 😛 |
There is a lot of NW.JS but none NW.IO. Now there is. Why .io anyway? But this name shaw not change in a blink of web nodes! 👀 |
not sure about the .io move and lock in NW's name, there is currently a lot of energy and hype around the new io.js, and it will be interesting to see what will happen in the next 6/12 months. I really like this article http://www.reddit.com/r/node/comments/2onjg9/nodejs_is_forked_not_fed/ since the real outcome might not be a full fork, but a best of both words (and after all a fork is a healthy sign in FOOS projects). In a way NW should support both and ensure that it can work with both distributions. |
Hi,
Agreed. I really don't think it's a good idea to lock the name in again with the frameworks used "currently". Since it can change again in the future. Laszlo
|
Agreed with Laszlo
Hi,
Agreed. I really don't think it's a good idea to lock the name in again with the frameworks used "currently". Since it can change again in the future. Laszlo
|
blinkbox |
NodeDesko |
Some ideas: |
Since WebKit has nothing to do with Chromium since a long time, should node-webkit be renamed? I think it would be a good idea. Every single person I mention node-webkit to starts lecturing me about what I already know: WebKit is not part of Chromium. It's Blink since what feels like forever.
Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: