2,259 karma · joined March 19, 2011
Our game engine is a thin layer on top of http://threejs.org/. Our real-time collaboration is powered by http://socket.io/ (WebSockets). Everything is written with http://www.typescriptlang.org/, http://jade-lang.com/ and http://stylus-lang.com/. The app is powered by Electron / Node.js. We use CodeMirror, Browserify, Gulp, Express, lodash and too many other awesome npm modules to name them all.
Thanks to the community for all the cool stuff we were able to reuse :)
During our 10 months of early access, we had a recurring / one-time support option on the website. We got (very roughly) about $1000 from that thanks to many generous people. After taxes and all, that doesn't leave much but we are pretty frugal, we live and work together so we've been able to afford it so far.
We're hoping to make a decent living with a mix of donations (we just setup a Patreon - http://patreon.com/SparklinLabs), maybe some sponsors? as well as part-time contract work around Superpowers or game development in general. If it doesn't pan out, well, we're very happy with what we've been able to accomplish so far, so we get to keep that! ^_^
Communicating with another behavior can be done like so:
Sup.getActor("Some actor").getBehavior(BehaviorClass).someMethod();
If you use an actor or a behavior often, you'll want to cache it into a member variable so you don't look it up every frame.By the way, we have open sourced all the games we've made for Ludum Dare and the Global Game Jam over the last year, you might like checking them out: https://github.com/superpowers-extra
Seems like Phaser's developer initially considered TypeScript but felt it was too early at the time too: http://www.html5gamedevs.com/topic/13599-reconsidering-build.... It looks like he's decided to go with Babel for Phaser 3 / Lazer: https://github.com/photonstorm/lazer
Hi! I've been working on live collaborative game development software for about 4 years (some of you might remember me from CraftStudio). For the past year and a half, we've been working on Superpowers with my two friends Bilou and Pixel-boy and now we've open sourced it, as promised back in March when we launched early access for supporters.
Superpowers at its core (http://github.com/superpowers/superpowers) is more than a game maker. It's a generic collaborative client/server Web app for building all kinds of projects. A project type is defined by what we call a system, and you can have any number of systems installed on your Superpowers server.
We spent most of the last year building the core along with a system called Superpowers Game (https://github.com/superpowers/superpowers-game), which is a TypeScript game engine built on top of Three.js along with a bunch of collaborative asset editors.
Now that the platform is maturing, we've started work on other systems. For instance, Superpowers LÖVE (https://github.com/superpowers/superpowers-love2d) lets you build Lua games for the LÖVE framework. Demo: https://i.imgur.com/yLybycP.jpg
Another example: Superpowers Web is (https://github.com/superpowers/superpowers-web) a Superpowers system for building static Websites. We've used it to build the official website (https://github.com/superpowers/superpowers-html5.com) in real-time collaboration. We have plan for a "Superpowers Node.js" system, and hopefully the community will embrace this extensibility and build cool tools for all sorts of engines and creative endeavours.
You can find lots of pictures of the app in the release notes: https://github.com/superpowers/superpowers/releases and many games made with Superpowers Game here: http://sparklinlabs.itch.io/. The devlog album has cool stuff too: http://imgur.com/a/NdIuH
Superpowers at its core (http://github.com/superpowers/superpowers) is more than a game maker. It's a generic collaborative client/server Web app for building all kinds of projects. A project type is defined by what we call a system, and you can have any number of systems installed on your Superpowers server.
We spent most of the last year building the core along with a system called Superpowers Game (https://github.com/superpowers/superpowers-game), which is a TypeScript game engine built on top of Three.js along with a bunch of collaborative asset editors.
Now that the platform is maturing, we've started work on other systems. For instance, Superpowers LÖVE (https://github.com/superpowers/superpowers-love2d) lets you build Lua games for the LÖVE framework. Demo: https://i.imgur.com/yLybycP.jpg
Another example: Superpowers Web is (https://github.com/superpowers/superpowers-web) a Superpowers system for building static Websites. We've used it to build the official website (https://github.com/superpowers/superpowers-html5.com) in real-time collaboration. We have plan for a "Superpowers Node.js" system, and hopefully the community will embrace this extensibility and build cool tools for all sorts of engines and creative endeavours.
You can find lots of pictures of the app in the release notes: https://github.com/superpowers/superpowers/releases and many games made with Superpowers Game here: http://sparklinlabs.itch.io/. The devlog album has cool stuff too: http://imgur.com/a/NdIuH
Direct link to ProseMirror's home page with live collaborative demo at the bottom: http://prosemirror.net/ (click "Change" to select a room)
And here's a link to the just-launched campaign to open source it (MIT license): https://www.indiegogo.com/projects/prosemirror/ . It's an all-or-nothing ("fixed") type indiegogo campaign, not the flexible kind where the funds are kept even if the goal isn't reached.
I guess it's just a stylistic choice in the end, but when we set up our own internal/informal style guide, my teammate and I spent a little while trying to come up with a justification for single vs double quotes. We ended up choosing double quotes based on the fact that JSON already made that decision for us: it requires strings be double-quoted.
(Although again, it's far from an important matter, as long as you're consistent), anybody has interesting rationales to share in favor of single quotes?
Maybe Taco Bell puts a lot of work in creating content that works well on the Reddit frontpage (which would definitely be manipulative, but hey, what are you gonna do), and maybe their own employees at home are upvoting it ("it's for the good of the company"), but I very much doubt the top people at Reddit are making a business out of this, if only because they couldn't justify it to their employees.
It just seems more likely to me that 1) a lot of material is organically upvoted, and it includes corporate stuff from well-known compagnies because a lot of people relate to them 2) some companies are (trying to) game the system in various ways that violate the spirit but not the letter 3) Reddit is trying to extract profit from all that but isn't being very aggressive about it because they don't have very high operating costs, are VC-backed and they'd rather find something that's compatible with the spirit of the platform and sustainable in the long run.
People can buy gold (a month of "reddit premium") to thank others for their contributions. In October 2013, they launched the "reddit daily gold goal" bar that displays how much gold is needed every day to pay for all (server?) costs (http://www.redditblog.com/2013/10/thanks-for-gold.html). I don't know if it includes other costs or just server costs actually. I've looked for some statistics over time to see whether the goal is being reached often or not but I can't find a graph.
They've got a couple other revenue sources like merchandising and their own advertisement system. But it would seem Reddit is not a massively profitable business at this point.
> and I also do if() even in cases where the language doesn't require it
This sentence could be parsed in multiple ways though :)
Looks like they intend to merge back with node mainline... ?
EDIT: Found this: http://blogs.windows.com/buildingapps/2015/05/12/bringing-no...
They're doing this to be able to run Node.js apps on Windows 10 ARM (on which V8 supposedly doesn't run?)
"We will be submitting a pull request to Node.js after stabilizing this code, fixing key gaps and responding to early community feedback."
"Going forward, we plan to work closely with the Node Foundation, the Node.js Technical Committee(s), IO.js contributors and the community to discuss and participate in conversations around creating JavaScript engine agnostic hosting APIs for Node.js, which provide developers a choice of JavaScript engine that they would want to use in their Node.js workflow"
Looks like the pull request will consist mostly of exposing new hooks to integrate with Chakra / other JS engines and won't involve pulling any Chakra code into Node.js (which would be unlikely to be merged). Might lead to a SpiderMonkey version of Node.js at some point, too. Nice to see IO.js mentioned. Looks like a very positive initiative (assuming it doesn't complicate Node core too much)