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

Example how to work in browser #3

Open
Enelar opened this issue Jul 25, 2016 · 5 comments
Open

Example how to work in browser #3

Enelar opened this issue Jul 25, 2016 · 5 comments

Comments

@Enelar
Copy link

Enelar commented Jul 25, 2016

How to setup code source map?
Should i use browserify?

@soliton4
Copy link
Owner

Hello @Enelar and sorry for my delayed reply.

i am very happy to see people are taking interest in promiseLand.

there is no sourcecode map implemented at the moment.
i am in the middle of rewriting the parser because of performance reasons. i was also planning to have a promiseland remote debugging tool which would be superior to in browser js debugging. but i guess its an ambitious project.

i will support source code map in the next minor release.

if you want to go ahead and help with the implementation let me know. i can give you pointers.

we basically have all the original location of every expression / statement.
so it should not be to hard to implement.

@Enelar
Copy link
Author

Enelar commented Jul 30, 2016

Yes, I'd love to, but first I need to get some experience. Could I use this
on client side? (like in browser)? Or it server only solution?

On 14:51, Sat, Jul 30, 2016 soliton4 [email protected] wrote:

Hello @Enelar https://github.com/Enelar and sorry for my delayed reply.

i am very happy to see people are taking interest in promiseLand.

there is no sourcecode map implemented at the moment.
i am in the middle of rewriting the parser because of performance reasons.
i was also planning to have a promiseland remote debugging tool which would
be superior to in browser js debugging. but i guess its an ambitious
project.

i will support source code map in the next minor release.

if you want to go ahead and help with the implementation let me know. i
can give you pointers.

we basically have all the original location of every expression /
statement.
so it should not be to hard to implement.


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

@soliton4
Copy link
Owner

the goal is to solve common shortages of javascript. so ofc you can use it in whatever javascript based runtime environment you want.

i recommend going through the features part of the wiki.

especially the frames part which shows you how you can easily connect server and browser code by using the same source base.
https://github.com/soliton4/promiseland/wiki/frames

https://www.npmjs.com/package/promiseland-webframework
is a reference implementation for a browser / node.js communication.
similar aproaches can be made to communicate between several node instances or workerthreads.

and if you want to get really deep into it there are synced objects which allow you to have the same instance of an object available accross several frames.

i am very interested in feedback from users. pls note that promiseLand is still in its early stage and will hopefully move forward a lot.

it also needs to keep up with new syntax models of ecmascript. since i want it to stay compatible with ecmascript.

@Enelar
Copy link
Author

Enelar commented Dec 17, 2017

Sorry for delayed replay. Thanks a lot. I've got inspired with your work.
I've dreamed few years about pure async language, but had no idea how to build VM.
Your frames / inter-frame communication is genius.

@soliton4
Copy link
Owner

thank you for noticing ;)
the work on promiseland has kinda stagnated but i am working on a language that will contain most of the features, especially the synced objects and inter-frame function calls. it is not js specific but i want it to be able to translate to any possible language.
wanna get involved?

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

2 participants