Skip to content
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

Rename the project? #101

Closed
binji opened this issue Sep 15, 2016 · 13 comments
Closed

Rename the project? #101

binji opened this issue Sep 15, 2016 · 13 comments

Comments

@binji
Copy link
Member

binji commented Sep 15, 2016

sexpr-wasm-prototype is a very old name for the project, and doesn't really reflect what it is or does. Any ideas for a better name?

@dschuff
Copy link
Member

dschuff commented Sep 15, 2016

We may end up wanting to use it in some cases where we currently use binaryen if Binaryen's IR diverges from wasm proper.

So currently it's a text/binary encoder/decoder, an interpreter, and... anything else? Sort of analogous to binutils, but I wouldn't necessarily want to call it something derived from 'binutils' exactly unless we want to provide all those tools. Does sexpr-wasm do much handling or dumping of the various non-code sections currently? Other tools might include dumping the names section if it exists (a la nm), and maybe even more arbitrary sectiony stuff like objcopy.
We could do more of that, although I had thought we might want do some of that with LLVM, which has a lot of common infrastructure which would make it easier (and more accessible to boot). Although maybe it does make sense to have something more standalone too? e.g. if we have users of sexpr-wasm who like that property (being standalone). I guess readelf and bfd have existed side-by-side for years, so why not this too :)

If we don't want to be 'binutils' we could say wasm-utils or wasm-tools, but that's pretty generic. Even a wasm-binutils or wasm-binary-tools or some such doesn't quite capture it since it has an interpreter :)

@binji
Copy link
Member Author

binji commented Sep 16, 2016

So currently it's a text/binary encoder/decoder, an interpreter, and... anything else?

It can generate a JavaScript test file from a spec test. But yeah, not much else. sexpr-wasm is basically just a C implementation of ml-proto.

Does sexpr-wasm do much handling or dumping of the various non-code sections currently?

Yes, it can read or write the names section w/ a flag. Otherwise it strips it. I think it's reasonable to support other non-code sections too, when they come along.

if we have users of sexpr-wasm who like that property (being standalone).

I think some users do like that it is standalone and relatively simple. At least, I do. :)

Even a wasm-binutils or wasm-binary-tools or some such doesn't quite capture it since it has an interpreter :)

I guess that's the nice thing about picking a non-descriptive name -- you can make it do whatever you want :P

@dschuff
Copy link
Member

dschuff commented Sep 16, 2016

tool-utils it is then!

@titzer
Copy link

titzer commented Sep 16, 2016

WASM binary toolkit? Then again, I'm a fan of cutesy names, so maybe
Wabbit? :-)

On Fri, Sep 16, 2016 at 2:36 AM, Derek Schuff notifications@github.com
wrote:

tool-utils is is then!


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#101 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALnq1HKc3DuxEmEBwC7_7iXToV3OfPwvks5qqeSGgaJpZM4J-U4J
.

@dschuff
Copy link
Member

dschuff commented Sep 16, 2016

WebAssembly Toolkit (WAT?)

@binji
Copy link
Member Author

binji commented Sep 16, 2016

I was thinking about it, and the main differentiating factor is that it is written in C. So maybe just c-utils or c-tools. Another nice thing is that it unlikely anyone else would write in C. :-)

That said, wabbit and WAT are pretty great too. :D

@titzer
Copy link

titzer commented Sep 18, 2016

I'm voting all my TL points for Wabbit, however many that is :-D

On Fri, Sep 16, 2016 at 8:06 PM, Ben Smith notifications@github.com wrote:

I was thinking about it, and the main differentiating factor is that it is
written in C. So maybe just c-utils or c-tools. Another nice thing is
that it unlikely anyone else would write in C. :-)

That said, wabbit and WAT are pretty great too. :D


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#101 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALnq1Oza5imGQxM2T71GbnmX_eN-84rnks5qqtqIgaJpZM4J-U4J
.

@binji
Copy link
Member Author

binji commented Sep 21, 2016

Derek and I have started calling it Wabbit. Let's go ahead and make that change :)

@s3ththompson
Copy link
Member

s3ththompson commented Sep 26, 2016

Renamed the repo!

Looks like the next steps are:

  • Merge Introduction to WABT #111 to change name in README.md
  • Change name in design/TextFormat.md
  • Fix Travis CI (I didn't look at this too hard yet, but it looks like it doesn't see wabt yet)
  • Send mail to others affected by this change

@binji
Copy link
Member Author

binji commented Sep 27, 2016

Looks like Travis CI is working again.
Renaming design/TextFormat.md in WebAssembly/design#808.

@binji
Copy link
Member Author

binji commented Sep 30, 2016

This seems to be done. Who needs to be mailed? @s3ththompson can you do this?

@binji
Copy link
Member Author

binji commented Sep 30, 2016

Oh, and can you change the project description too? It still says "sexpression -> wasm" :-)

@s3ththompson
Copy link
Member

Updated description and sent out the name change to the other browsers as an FYI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants