n17r4m

At the "low" level, if you need to get some quick and dirty database queries up onto the web, PHP is probably the best way to do it. Big and bloated PHP web apps are the worst, but if you are looking for a way to add and remove a few entries here and there, then it is a good solution for a targeted problem.

The theory is simple, practise is difficult. Aim for the absolute most bare bones side project you can, and throw a few weekends (or other time to spare) at it, and get it going. From there, improve when you can. Given time, your dream project emerges.

What about setting up a second site with a form: enter twitch name and answer a turing test question. also ask for person to create a new turing question with answer. Person has ability to request a few new questions before deny.

Submitted questions are approved by admins via rapid fire Y/N buttons, with ability to fix typos, etc.

This authenticates that user for something like 5-15 minutes or however long to participate in voting.

IMHO, its been getting progressively better as time goes on. It has great support for React and Angular now, in addition to its own Blaze templating engine (I prefer Blaze, actually).

The data sync is fast enough to be useful for real-time games.

When it comes time to scale up, ditch the built-in mongo (or sql) and set up your DB cluster, and for the web bits, use something like https://github.com/meteorhacks/cluster and you are off to the horizontal scaling races.

In response to the linked posts criticism:

No API-based authentication: having a REST api to interface with Accounts is not there by default, but Meteor does support adding REST endpoints, where one could easily roll a solution that does a server-side auth and respond with an auth token which could be stored in the user's record as appropriate. I'd be surprised if there wasn't already a package available which does exactly this.

App shutdown: Once you are running a 'real' site, you will probably have a separate mongo instance. This solves most of the problems, however yes, it is still possible for some 'in-flight' data to be lost. Adding a maintenance mode like https://github.com/yogiben/meteor-maintenance-mode solves this though.

Subscriptions scalability: It's all about writing publish functions that only send what you need for a particular screen / template / page. In practice, it is not difficult and can scale up quite nicely: http://meteor.redandivory.com/

Server-side rendering for SEO: As the link points out, there are community packages that can make this happen. The beauty of meteor is the huge amount of community packages available that are almost universally of high quality. Their use should be encouraged, and is not considered "hacky".

My 2c.

Online at c9.io, they support c and c++. I'd imagine that would translate to the self-hosted edition. I really enjoy the features provided, and so far it has coped well with every language I've thrown at it, including outliers like livescript, purescript, etc..

https://developer.mozilla.org/en-US/Learn is a good place to start.

http://eloquentjavascript.net/ does a great job, especially in the later chapters.

http://learn.shayhowe.com/advanced-html-css/responsive-web-d... 'Responsive' site design is a must-have now-a-days.

http://alistapart.com/article/dao The philosophy and theory of web design

I have some other links you may be interested in on a blog post I wrote a while back: http://mygen.ca/develop-developing-developers/

I cannot scroll on firefox os.

Left pane is ok. Right pane is unresponsive.

1) Get computer

2) Install Gentoo

3) Set up ssh / webserver / mail server / irc / etc...

4) Buy domain and point to your server

5) Successfully run your own site/blog/wiki for a while, have it do neat stuff, write about and share your experiences of learning to be a sysadmin

6) While under oath, swear by the SysAdmins creed.

7) ???

8) Profit.

High score: 01233 Those Pterodactyls, hehe.

Best played after pressing ctrl + plus a few times.

Runs smooth.

Personally, I think there is a lot of magic yet to be discovered in dynamically manipulating the CSSOM (CSS Object Model).

Case study: If trying to manipulate some ~100 inline-block elements into a grid, with dynamic (say, zoomable + pannable + screen size dependant) width, height and offset. It makes way more sense to programmatically modify the stylesheet using the CSSOM API with fast calculated values, rather than applying unique styles to each of those 100 elements in the DOM, O(1) vs O(n) - yes?

Livescript - http://livescript.net

I'm swingin' thru the top of the valley

Feeling like the missing link

There's another schematic

Look, she's gettin' me a drink

By putting flowers on his crypt

'Cause Valentino's lost the script

---

I know I'm being overdramatic

But I think I'm going to run that risk

I'm walking down that same old plank

And baby I'm about to tank

But everything will turn out fine

Not super funny, but pretty cool/weird stuff in a project I inherited:

app <- -> exports.setup = it

in LiveScript seems to compile to

(function(it){ return exports.setup = it; })(function(app){})

which is pretty crazy.

Another one, just above some code making many deep monkey-patches to the Sequilize db driver:

/* HOLY FUCK THIS IS THE SKETCHIEST THING EVER */

made me smile.

Yes, of course. The core tenants though, shouldn't be evicted, ever.

I honestly cried when alt.* on usenet was lost. We lost so much.

I hope not. Email is one of the few remaining, totally decentralized, original services which anyone can set up a server and run with. I've never had any issue with it across 25 years, honestly.

It just 'fits' with the web. name@address.tld - it's fantastic.

Frankly, I'm cool with the idea of the quantum corrections being inserted into general relativity's field equations. And I'm cool with the idea that this might imply a universe that didn't start with a bang.. But how does the new hypothesis explain the (increasing and accelerating) red-shifts found when observing distant galaxies?

Meteor.org is not too bad; apps built with it are comprised of a controller layer, and a presentation layer. Generally, both are very lightweight, and not much configuration is required. Just pull in the packages you need. Optionally, you may define hooks on your data collections, e.g. Posts.before.update = function(userId, doc, ...)

Might be a bit on the heavyweight side, but TikiWiki ( http://tiki.org ) might be a good fit for this.

Fair enough! Thank you for the feedback! It's tough as the developer of a product to get an objective 'feel' for how others may receive their first impressions.

The h1 "Welcome" is where we are letting the visitor know what our product is about and how it can help them.

The "Welcome" button is the 'Main Menu' where the visitor can navigate through the different modules of the app.

The text of this button changes depending on which module the visitor is in... so.. when on the Welcome page, it says, well, "Welcome".

I wonder if it would be better to change the way the text of the button operates, or adding in a 2nd main-menu control with all the modules listed within the welcome page, or something else?

The post title (I think) was along the lines of "Email will never die"

However using the search reveals no recent results..

This is also what I sort of assume. All of these tech companies like facebook, and google, probably got so many requests for info from the feds that at a certain point, it must have somehow made sense to switch it up and just give them an automated web form somewhere. (direct access to servers..) The telcos have probably had these since way back.. Eventually, there would be quite a few of these web forms, so some 'top' coders put together a system for the feds to query all of the forms at once with one request. Paint on a GUI and call it PRISM. It was nice to hear that Yahoo! still sorts out their fed requests by hand.