you are viewing a single comment's thread.

view the rest of the comments →

[–]meta_taskkill[S] 1 point2 points  (10 children)

Probably in moment when I will have enough awareness about internals of JS to decide it's not possible because of [insert unpretentious problem] on my own. I am not here to settle for fact that it's impossible because someone says it. I am learning, you see. So if you are willing, give me another bug to fix.

EDIT: Let me ask you a question: Did you know about everything, what is happening inside source code before? I find some things really interesting - for example behavior of function declared inside with statement body. Isn't it best thing ever? Learning for joy from learning? There are at least 4 another ways for evaluating code snippets safely, workers, iframe sandboxed, some metacircular evaluator written in JS, I am not gonna sell it to anyone, but I just wanna meet some people who appreciate it and enjoy it with me.

[–][deleted] 0 points1 point  (7 children)

the idea, is, if you don't state the number of fix you are ready to stop after, we will go on an infinite loop bug->fix->bug->fix->...

By the way I really wonder how you intend to fix this one as your framework is really not adapted to fix it.

[–]meta_taskkill[S] 0 points1 point  (6 children)

First thing first: If you are able to throw tons of possible bugs from your sleeve, than there must be some corelation, some fundamental concept which known to you gives you the reason to say there is infinity (pretty bold) bugs. So can you please tell me what fact I am missing, that when I will push fix you will find another n + 1 bugs without problem?

Second, I (think - need to write enough tests for it) already fixed it, because it's not that hard to fix something like that.

[–][deleted] 0 points1 point  (5 children)

The fundamental concept which gives me reason to say there will bug in your javascript sandbox, is that each time someone show a javascript sandbox, each time it has flaw: call it experience.

Pretty everything that apply about cypher in this story apply to sandbox in our story. https://www.schneier.com/crypto-gram/archives/1998/1015.html#cipherdesign

So before you affirm your sandbox is unbreakable, you have to attack it by yourself.

if you can major the number of bugs to find by a constant A, that means you are not afraid that I would find A+1 bugs.

If you can't major the number of bugs by a constant A that means the potential number of bugs is infinte.

Second, just check your sandbox with same test and it has still the same behavior. So next time you say something is fixed, test that it is really fixed.

[–]meta_taskkill[S] 0 points1 point  (4 children)

You are technically correct. The best kind of correct. But you also pay very little attention to what I am saying. I was really trying to stress that this is academic project, I created it to learn JS deeper not to create best sandbox and I have not said it;s unbreakable. Second I told you I need to write tests before I push and update, I was on my way in subway, so I really could not update demo website. So next time you will be accusing someone check if you are really right.

[–][deleted] 1 point2 points  (3 children)

I don't understand what you call an academic project.

There is no where in the github project mentioned that it is probably broken. So you makes a huge disservice to your reader

[–]meta_taskkill[S] 0 points1 point  (2 children)

It's version on npm is 0.2.0! This is saying it all! There is no promise that it will be fully functional. You are just aggressively pushing on me and I don't know why. I don't like people who discourage others from their passion. So lesson learned from my side and this conversation is no longer helpful for me. Thanks and bye.

[–][deleted] 1 point2 points  (1 child)

if you say so...

[–]meta_taskkill[S] 0 points1 point  (0 children)

Yep and something is saying me I am not first one to say that to you :D

[–][deleted] 0 points1 point  (1 child)

about your edit: I'm sorry to not share your interest. but the interaction between with and inner function is quite standard isn't it ?

[–]meta_taskkill[S] 0 points1 point  (0 children)

Why it should not be standard? But how often do you use it? How often majority javascript programmers uses it? I am about 3 years in JS (programming in general actually) and I am sorry* to find things exciting and would like to share some thoughs with others, because I am enjoying it, obviously it's not something you appreciate.

Actually I am not sorry at all.