server {
listen 80;
listen [::]:80;
server_name example.com www.example.com;
#!/usr/bin/env python | |
## A tiny, nifty script for playing random musical notes on each keypress. | |
## | |
## Copyright Sayan "Riju" Chakrabarti <[email protected]> 2009-2019 | |
## Released under WTFPL Version 2 | |
## (DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE) | |
## Copy of license text can be found online at | |
## http://sam.zoy.org/wtfpl/COPYING | |
## | |
## External/System Dependencies: |
[Unit] | |
Description=headless chrome | |
[Service] | |
Type=simple | |
ProtectSystem=strict | |
DynamicUser=true | |
Environment=HOME=/tmp | |
ExecStart=/usr/bin/google-chrome --headless --disable-gpu --remote-debugging-port=9222 |
Warning: These views are highly oppinated and might have some slightly incorrect facts. My experience with typescript was about 2 weeks in Node and a week in angular2.
TypeScript is implementing their own take on JavaScript. Some of the things they are writing will likely never make it in an official ES* spec either.
Technologies that have competing spec / community driven development have a history of failing; take: Flash, SilverLight, CoffeeScript, the list goes on. If you have a large code base, picking TypeScript is something your going to be living with for a long time. I can take a bet in 3 years JavaScript will still be around without a doubt.
Its also worth noting that they have built some things like module system and as soon as the spec came out they ditched it and started using that. Have fun updating!
/** | |
* Created by Robert Kehoe on 09/06/2014. | |
* MIT Licensed. | |
* | |
* Permission is hereby granted, free of charge, to any person obtaining | |
* a copy of this software and associated documentation files (the | |
* "Software"), to deal in the Software without restriction, including | |
* without limitation the rights to use, copy, modify, merge, publish, | |
* distribute, sublicense, and/or sell copies of the Software, and to | |
* permit persons to whom the Software is furnished to do so, subject to |
# Change YOUR_TOKEN to your prerender token | |
# Change http://example.com (at the end of the last RewriteRule) to your website url | |
<IfModule mod_headers.c> | |
RequestHeader set X-Prerender-Token "YOUR_TOKEN" | |
</IfModule> | |
<IfModule mod_rewrite.c> | |
RewriteEngine On |
<!DOCTYPE html> | |
<head> | |
<title>Name</title> | |
<style type="text/css"> | |
html { | |
background: white; | |
color: black; | |
font: 14px 'Helvetica Neue', Arial, sans-serif; |
I have always struggled with getting all the various share buttons from Facebook, Twitter, Google Plus, Pinterest, etc to align correctly and to not look like a tacky explosion of buttons. Seeing a number of sites rolling their own share buttons with counts, for example The Next Web I decided to look into the various APIs on how to simply return the share count.
If you want to roll up all of these into a single jQuery plugin check out Sharrre
Many of these API calls and methods are undocumented, so anticipate that they will change in the future. Also, if you are planning on rolling these out across a site I would recommend creating a simple endpoint that periodically caches results from all of the APIs so that you are not overloading the services will requests.