Since Twitter doesn't have an edit button, it's a suitable host for JavaScript modules.
Source tweet: https://twitter.com/rauchg/status/712799807073419264
const leftPad = await requireFromTwitter('712799807073419264');
Since Twitter doesn't have an edit button, it's a suitable host for JavaScript modules.
Source tweet: https://twitter.com/rauchg/status/712799807073419264
const leftPad = await requireFromTwitter('712799807073419264');
Note: this is a work-in-progress and will be updated with more information over the next few days.
This guide will walk you through deploying your own instance of the open-source Parse Server. This would be a good starting point for testing your existing application to see if the functionality provided by the server is enough for your application, and to potentially plan your migration off the Parse Platform.
This guide will walk you through using Elastic Beanstalk (EB), which is an AWS service similar to Heroku. Why use EB rather than Heroku? Elastic Beanstalk does not lock you into Heroku-specific ways of doing things, is likely cheaper to run your backend on than Heroku, and it integrates with other services that AWS offer (and they offer almost everything one needs to run an application these days).
I fell in love with CoffeeScript a couple of years ago. Javascript has always seemed something of an interesting curiosity to me and I was happy to see the meteoric rise of Node.js, but coming from a background of Python I really preferred a cleaner syntax.
In any fast moving community it is inevitable that things will change, and so today we see a big shift toward ES6, the new version of Javascript. It incorporates a handful of the nicer features from CoffeeScript and is usable today through tools like Babel. Here are some of my thoughts and issues on moving away from CoffeeScript in favor of ES6.
While reading I suggest keeping open a tab to Babel's learning ES6 page. The examples there are great.
Holy punctuation, Batman! Say goodbye to your whitespace and hello to parenthesis, curly braces, and semicolons again. Even with the advanced ES6 syntax you'll find yourself writing a lot more punctuatio
* { | |
font-size: 12pt; | |
font-family: monospace; | |
font-weight: normal; | |
font-style: normal; | |
text-decoration: none; | |
color: black; | |
cursor: default; | |
} |
#include <iostream> | |
#include "Time.h" | |
Time::Time() | |
{ | |
} // Time() | |
Time::void update() | |
{ |
/* | |
Meteor allows you to store functions on the server for handling things like data. | |
This is the server-side component to the Meteor.call() example in add-taco.js. | |
*/ | |
Meteor.methods({ | |
// Define our method. Note, we're passing an argument for the tacoToInsert value we passed to our Meteor.call() method. | |
'addTaco': function(tacoName){ | |
// Here we do our insert again. | |
Tacos.insert({ |
use HTML::FromANSI (); | |
open (LOG, '>>hnchatlog.html'); | |
select((select(LOG), $|=1)[0]); | |
print LOG "<body bgcolor=black>\n"; | |
while (<>) { | |
my $h = HTML::FromANSI->new(); | |
print LOG $h->ansi_to_html($_), "\n"; | |
} |
[ | |
{ | |
"timestamp": 0, | |
"input": "W", | |
"type": "search_local", | |
"latency": 0 | |
}, | |
{ | |
"local_results": [ | |
"ddg_search", |