Skip to content

Native messaging example#55

Open
guest271314 wants to merge 3 commits into
andreiltd:mainfrom
guest271314:native-messaging-example
Open

Native messaging example#55
guest271314 wants to merge 3 commits into
andreiltd:mainfrom
guest271314:native-messaging-example

Conversation

@guest271314

Copy link
Copy Markdown

No description provided.

@andreiltd

Copy link
Copy Markdown
Owner

Hey, thanks for example! I'm currently trying to figure out licensing as I'm planning to donate the project to either BA or microsoft and I need to have clear understanding what it means in context of accepting external contributions. It is possible that this PR will have to wait until the project is moved.

@guest271314

Copy link
Copy Markdown
Author

Huh?

Why encumber this very useful project in organization and/or corporate licensing mire?

If anything "donate" the project to QuickJS NG. Or me. I'll slap Do What the Fuck You Want to Public License WTFPLv2 on it and be done with the matter. It's for the Public to use, not for some committee to pull strings on.

@guest271314

Copy link
Copy Markdown
Author

The Bytecode Alliance folks saw fit to ban me. So, that effectively means if they are gain control of this repository my PR will be shelved, like they shelved my PR over in jco world bytecodealliance/jco#1629.

Not so much because the code doesn't technically work, but because of some non-technical reasons, per them guest271314/banned#46.

Same thing kinda happened over in jco world. Do an example. Example gets done. Then for non-technical reasons example gets stalled from merging.

@guest271314

Copy link
Copy Markdown
Author

One interesting note on this. Historically, I think the most widely used programming linkages have come not from the programming language research committee, but rather from people who build systems and wanted a language to help themselves.

  • A brief interview with Tcl creator John Ousterhout

@guest271314

Copy link
Copy Markdown
Author

Re

donate the project to either BA or microsoft

Isn't this repository in direct conflict and competitition with Bytecode Alliance's StarlingMonkey project; and jco, which is all about Node.js?

I mean, componentize-qjs blows StalingMonkey and ComponentizeJS and thus jco out of the water.

StarlingMonkey would be technically dead on the spot. Why would anybody want a 13 MiB WASM binary instead of a less than 1 MiB WASM binary?

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

Successfully merging this pull request may close these issues.

2 participants