HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bebraw
jswiki
JavaScript2011–2014
bebraw / jswiki

jswiki

JavaScript wiki. Focuses mainly on JS/HTML5/WebGL related tech.

13Distinct people
16Mentions
0Explicit recommenders
3.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

JavaScript wiki. Focuses mainly on JS/HTML5/WebGL related tech.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year16 dated mentions

Observed mentions: 2011-01-17 10:05:29 UTC to 2014-02-10 08:45:29 UTC.

02462011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 6 mentions; 4 submissions, 2 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC725
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC642
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC202
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Please see the wiki. :) Building Make sure you have ghw installed! Clone wiki (git clone git@github.com:bebraw/jswiki.wiki.git). This will create "jswiki.wiki" directory here. Clone gh-pages (git clone git@github.com:bebraw/jswiki.git, cd jswiki, git checkout -b gh-pages origin/gh-pages). After this you should have "jswiki" directory containing gh-pages branch. Run build.sh. Once that has been done, you should have a fresh build at "jswiki" directory. Commit and push to see it online. You can preview it offline before commit if you want.
Read the full README on GitHub

What Hacker News says

16 sources
Sorry, to clarify I want a solution so that we do not have to bake our own - Sencha abstracts it all away and handles everything the same across all devices (so I'm led to believe by the dev that chose and implemented it - I have very little experience with it). By 'native touch events' I mean very much like the link you've provided (which is a very promising resource, so thankyou for that), in that it offers a 'doubletap', 'swipe', and 'pinch' event for instance. (So more precisely _emulating_ native touch events?). I've found a good list of libraries in my research [1] but I was wondering if anyone had specific experience that could tip the balance in favour of one lib above Sencha (which to my eyes seems bloated and awkwardly constructed). [1: https://github.com/bebraw/jswiki/wiki/Touch]
In AngularJS powered mobile boilerplate app that also does offline out of the box
I like .NET/Mono stuff, and I totally understand the frustration of .NET developers. I would want to point out though that Javascript does have all the features you listed that .NET has, except the desktop stack - but of course that is precisely what Microsoft (and others, like GTK developers) may be developing. "what .NET is. It is a desktop stack, a server stack, a runtime for many languages, those many languages themselves, and countless libraries that are being actively developed" Javascript on the server: http://nodejs.org/ Javascript as a runtime for many languages (more than .NET even I believe at this point): https://github.com/jashkenas/coffee-script/wiki/List-of-lang... Countless javascript libraries: in the browser https://github.com/bebraw/jswiki/wiki and on the server: https://github.com/joyent/node/wiki/modules Even .NET cod
Read the rest
e can be ported to javascript via tools like: https://github.com/kevingadd/JSIL (as can java via GWT and so forth) Although of course System.Windows.Forms hasn't been ported (wouldn't surprise me if someone does though). By the way, I do educational software - we like applets and so forth. That was the main drawback to the .NET/Mono platform, from my point of view. When Silverlight was released to run .NET in the browser, that was great, but it only works in Windows, and Monolight doesn't seem to work too well as a replacement on other platforms. Now with HTML5 and canvas, it's even nicer than applets, although a bit slower (can't run a complex circuit simulation as easily, for example), plus it runs on mobile/tablet platforms of course.
In HTML5-based Windows 8 enrages .Net devs, alienates Linux and Mono
You're right. I'm 100% beside you on the value for time spent, but as you've mentioned there's also the 'learning value' that comes form building it from the ground up. (Think of how much I'd have to spend to learn it in a University course seen another way, I'm actually saving a few thousand!). Going with an engine also carries with it the weight of engine choice as well. Your investment is in learning how to do it from within that engine - versus - knowing how it's done at the 'raw-guts' level. There is likely a point at which I'll be better off cutting and moving across to an engine. (Though with the dozens of engines available deciding that IMPACT is the right one to go with isn't quite clear cut, for example, there's the ISOGENIC engine on its way, https://github.com/bebraw/jswiki/wiki/Game-Engines is the list on GitHub) What about R
Read the rest
ocket Engine? Maybe I should wait for that? What about Unity3d? Or Flash? Cocos2D (on github, widely used, BSD license) I'm honestly not trying to be facetious - but these are actual problems that run through my head when trying to decide. So I suppose maybe I got so stuck in the 'analysis paralysis' phase on the picking an engine phase and decided to look through what I could figure out on my own. Each puzzle brought with it a single interesting question (http://chesser.ca/jsSprite shows the order, beware step 12 it has crashed many weaker computers). There's also a number of interesting 'next steps' I'd like to try to figure out in a semi-assisted state (like on my own, but I get to ask experts when I've gotten really stuck). I'm really kind of excited about getting to look at something called 'quad-trees' And then there's all the setting up NODE.JS and WEBSOCKETS for adding multiple mobs to the screen at once. It's less about the finished product than it is about building valuable full-stack developer skills. With node specifically, I'm going to have to build an AWS instance and set up the brains of my operation... not to mention sending the correct data back and forth! (i'm getting a little giddy thinking about it). Placed in a broader context - I'm employed full time doing other stuff and would love one day to ship a working project - but at this phase am not totally ready to rely on 'magic functions'. If it's possible to give a short answer after all of that, you're 100% right & I agree 100% ... and I'm doing it the hard way because I'm a stubborn, dorky nerd (but my lights don't go out if I miss the ship-date).
In Build an HTML5 game in 30 minutes

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.