Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Runnable – jsfiddle for everything

runnable.com

Post reply on HN
Print view View original

91–100 of 105 posts

Re: Runnable – jsfiddle for everything

#91

Post by Alupis »

ykumar6 wrote: post #65
emilv wrote: post #46

It's pretty strange to get root access to a server, even though it's just a Docker VM. We can install anything we want, compile any C code we want, DDoS and spam anyone we want... The machine is also crazy loaded right now, with 100% load on all cores (according to htop that I installed from the package repo), almost run out of RAM and disk space decreasing fast.

We are a bit overwhelmed by the load right now, didn't expect to get hit by HackerNews today :) We are spinning up more servers

This is a good problem :)

You guys have a very nice looking product.

Re: Runnable – jsfiddle for everything

#92

Post by general_failure »

stevekemp wrote: post #60
general_failure wrote: post #58

Earlier quoted context omitted.

FUD

Example here: http://blog.bofh.it/debian/id_413 * Got root in the countainer. * You "know" where that is mapped to on the host, because it is based on the UID of the container which is set as the hostname. * You configure a trigger to run a script, using that knowledge. * Code happens on the host, outside the container.

The above example is about LXC and sysfs. We are talking docker which uses aufs.

Re: Runnable – jsfiddle for everything

#93

Post by Anandkumarpatel »

Alupis wrote: post #88

Here's some system specs they are running your code in: ~~~~~~~ Executing Build Command: javac /root/HelloWorld.java Executing Run Command: java -classpath /root HelloWorld Cores: 4 CPU Arch: amd64 Total Mem (Bytes JVM sees): 236257280 Max Mem (Bytes JVM sees): 3506438144 Free Mem (Bytes JVM sees): 235023784 Root Dirs: / Get OS (direct output): Linux Get OS (sanitized output): Unix/Linux OS Arch: 64 Process exited su…

to be specific it is an Amazon EC2 m3.xlarge instance running with magic inside

Re: Runnable – jsfiddle for everything

#94

Post by gcb0 »

singingwolfboy wrote: post #51

What's the monetization model? This looks awesome, but it needs a way to pay the bills if its going to survive.

First thing i looked was a "pricing" page to send to my company bean counter!

i want that installed internally so we can send live code instead of boring pastebin links

Re: Runnable – jsfiddle for everything

#96

Post by taternuts »

This really is an awesome site, and I was really impressed when I first discovered it. It's like having a nitrous.io box provisioned on the spot in whatever stack you want, for something as simple as a 3 line snippet of code to a full on project (although probably not the best place for that). I hope more people start using it and contributing to the examples, it's really nice to be able to walk through full-stack snippets

Re: Runnable – jsfiddle for everything

#97

Post by stevekemp »

general_failure wrote: post #92
stevekemp wrote: post #60

Earlier quoted context omitted.

Example here: http://blog.bofh.it/debian/id_413 * Got root in the countainer. * You "know" where that is mapped to on the host, because it is based on the UID of the container which is set as the hostname. * You configure a trigger to run a script, using that knowledge. * Code happens on the host, outside the container.

The above example is about LXC and sysfs. We are talking docker which uses aufs.

Indeed, this is an LXC attack, rather than docker-specific.

But, that said, the attack works as specified against docker 0.11.0. Largely because guests do have sysfs mounted at /sys.

Re: Runnable – jsfiddle for everything

#98

Post by haphazardeous »

ykumar6 wrote: post #62
NathanKP wrote: post #54

Earlier quoted context omitted.

I'd be willing to bet that someone has already run a fork bomb just to see what would happen.

Yes, I'm from Runnable. People have tried fork bombs. We are pretty good and cleaning them up. Please do not try this and let other users enjoy the platform

I'm sorry to say I did run a piece of java code to see how it handled creating many threads.. Didn't mean to cause any harm. I was just curious.

Re: Runnable – jsfiddle for everything

#99

Post by mariusasdf »

mcv wrote: post #52
vcherubini wrote: post #13

Earlier quoted context omitted.

It has Node.js, which I guess is JavaScript. Or do you want direct access to V8? Edit: If you expand the list of supported languages, it shows Python too.

Yeah, but node.js is a framework, not pure js, and I suspect it doesn't do DOM-related stuff. jQuery is probably better suited for general in-browser javascript.

This reasoning seems fundamentally confused, so I feel like clarifying some concepts:

On Runnable you can create basic client-side JavaScript files to be run in the browser (without jQuery) and do window and DOM manipulations.

Node.js isn't a framework for the browser (like jQuery), but a server application platform (with a bunch of objects and functions).

"Pure js" doesn't exist as an environment. It runs within a parent environment (e.g. a browser or a server) and manipulates the global objects in that environment.

JavaScript is just a language specification, and can be implemented in any environment. (For instance, it's implemented in Adobe Illustrator.)

Re: Runnable – jsfiddle for everything

#100

Post by mcv »

mariusasdf wrote: post #99
mcv wrote: post #52

Earlier quoted context omitted.

Yeah, but node.js is a framework, not pure js, and I suspect it doesn't do DOM-related stuff. jQuery is probably better suited for general in-browser javascript.

This reasoning seems fundamentally confused, so I feel like clarifying some concepts: On Runnable you can create basic client-side JavaScript files to be run in the browser (without jQuery) and do window and DOM manipulations. Node.js isn't a framework for the browser (like jQuery), but a server application platform (with a bunch of objects and functions). "Pure js" doesn't exist as an environment. It runs within a p…

Yes, but jQuery is not the only way to use javascript in the browser. Why that restriction?
Post reply on HN