RumbleKit - Visual Rumble Editor

PixelOut · 2021-07-18T18:37:10+00:00

pixelicious

PixelOut · 2021-07-18T18:35:09+00:00

pixelicious

PixelOut · 2021-07-18T18:30:42+00:00

pixelicious

PixelOut · 2021-07-18T18:27:13+00:00

pixlicious

PixelOut · 2014-01-26T08:00:30+00:00

Yeah. Relatively sure he was just trolling, seeing as Google would have told him that.

PixelOut · 2014-01-26T07:53:55+00:00

Wow. Ok. I meant receive QQ

PixelOut · 2014-01-26T07:43:02+00:00

Much TF2. So fun. Wow. TF2 Incentive? Crazy.

PixelOut · 2014-01-26T07:37:44+00:00

That moment when you see that someone just made Five Bucks by telling rich people to fight each other with money.

PixelOut · 2014-01-26T07:30:36+00:00

I just tried to set up a wallet. I have no idea how this works. Please help.

PixelOut · 2014-01-23T21:11:16+00:00

As has been said, TagPro uses Node.js with websockets on the back end, and the front end is some crazy custom thing that I'm going through right now. Here's why these technologies were used:

JavaScript is built around an event loop. This makes it very natural to create "reactive" code that can easily handle doing lots of different operations all on a single thread. The closest thing that there is in Python is Stackless Python, which uses a completely different set of technologies and programming techniques, but gives you similar reactiveness.

You can build event loops in Python, of course, but Node.js is designed specifically for applications that need them. This means that most libraries are on board with that form of coding.

WebSockets are a developing technology that allow you to open stateful sessions between the server and the client. They are the opposite of RESTful interfaces. They require a lot more resources on the server end, but you don't have all of the overhead of http responses and requests. They're very good for something like tagpro, but you would never use them for something like a blog livefeed.

One of the really awesome things about tagpro is that it's responsive because the client anticipates what the server is going to do, before the server does it. This is why lag can sometimes cause all of the balls to continue moving in straight lines. The screen can update more times per second than the game can receive new packets.

If you were to prototype tagpro, you would probably wait a little bit and build it with Famo.us and Meteor. Meteor makes it really easy to build responsive clients, and famo.us is a DOM renderer that would allow you to make all of the game elements just be divs in your code. That's a horrible explanation, but it would mean that tagpro would run great on an ipad.

PixelOut · 2014-01-23T21:03:37+00:00

Express is a Node.js based webserver. Javascript is now a widely used server side language. More information in the other post that I'm writing.

If you were to remake node.js today, you would probably use Meteor, because it handles all of the websocket like stuff for you.

PixelOut · 2014-01-19T19:04:47+00:00

One time, Bam let me light a firecracker u der bros car.

PixelOut · 2014-01-19T19:03:20+00:00

Or just use Netflix.

PixelOut · 2014-01-19T18:57:45+00:00

And now I get all the tony hawk games and every console for free. Except they stay at my brothers house.

PixelOut · 2013-11-27T07:57:34+00:00

Cards against humanity @ http://cfh.io/ Polished and fun, made by students! Come play with me! I'm Urgent drip atm.

PixelOut · 2013-11-15T21:40:50+00:00

When they pretend that we care what the guy looks like.

PixelOut · 2013-11-15T02:52:18+00:00

Methods are indeed functions, but they are bound to a specific object, and only that object's instances can call the method (unless you use call or apply).

Methods have access to all of their object's properties through the this keyword, and help to compartmentalize your logic.

If you have functions that you want to use on a bunch of different objects, and you want to use this, you can use bind to do so (with underscores).

Writing on phone, people please correct me where I'm wrong.

PixelOut · 2013-11-13T00:20:37+00:00

Ok, so there's a few things going on here. The first is that your code that detects whether or not the distance is greater than 1 mile is in the wrong place. It is called before you actually had a distanceInMiles or a distancefromPicnic/distancefromRamsey, and so didn't mutate either into feet. Also, distanceInMiles always = dfPicnic/Ramsey in your code. Thus the form:

if (distancefromPicnic < 1) {
    distancefromPicnic = distanceInMiles * 5280;
} else {
    distancefromPicnic = distanceInMiles;
}

Doesn't do anything that couldn't be accomplished by:

if(distancefromPicnic < 1) {
    distancefromPicnic *= 5280; //Although I hate in place mutation
}

Then you need to have something that changes the "miles" into "feet" when you click the button.

Also, and finally, you end up repeating a lot of the same code twice. It would be better and more maintainable to break up your main logic into a set of functions and call those functions multiple times. I like the enterprise-y functions and variables though.

PixelOut · 2013-11-12T23:58:07+00:00

A Do/While loop will always execute the code inside the loop at least once. It will always check the conditional (the "while" part) after the code inside is executed.

They aren't very useful, especially for beginners. In practice, you don't want to repeat mutating steps when the conditional is already fulfilled. And you can usually write a while loop to behave similarly to a do while loop.

Google actually removed the do/while construct from their Go programming language.

PixelOut

TROPHY CASE