Dubem dubeme

## selenium-screenshotting.md

      
              1 file
            
          
              19 forks
            
          
              4 comments
            
          
              70 stars
            
          
                dannguyen
                / selenium-screenshotting.md
            
            
              Last active
              February 15, 2023 15:59
            
              
                Using Selenium and Python to screenshot a javascript-heavy page
              
          
    Using Selenium and Python to screenshot a javascript-heavy page

As websites become more JavaScript heavy, it's harder to automate things like screenshotting for archival purposes. I've seen examples and suggestions to use PhantomJS for visual testing/archiving of websites, but have run into issues such as the non-rendering of webfonts. I've never tried out Selenium until today...and while I'm not thinking about performance implications yet, Selenium seems far more accurate than PhantomJS...which makes sense since it actually opens a real browser. And it's not too hard to script to do complex interactions: here's an [example of how to log in to Twitter, write a tweet, upload an image, and send a tweet via Selenium and DOM element selection](https://gist.github.com/dannguyen/8a6fa49253c1d6a0eb92

  
## Facebook Hackercup Solutions.md

      
              4 files
            
          
              3 forks
            
          
              11 comments
            
          
              7 stars
            
          
                kokx
                / Facebook Hackercup Solutions.md
            
            
              Last active
              December 11, 2015 21:09
            
              
                Solutions to Facebook Hackercup. Feel free to fork and make improvements! I didn't really take much time to write this, so help on clarifying the text is very much appreciated!
              
          
    Disclaimer: I have no idea if this are indeed the correct answers. I just solved the exercises like this. I think that they are right though.
I have added my own code to this gist. It is ugly as hell, just like you can expect from code created in a contest like this.
Beautiful Strings

Difficulty: easy
It is simple to see that a greedy solution is good enough.

  
## text.js

var express = require('./')
var app = express();

app.use(function(req, res, next){
  if (req.is('text/*')) {
    req.text = '';
    req.setEncoding('utf8');
    req.on('data', function(chunk){ req.text += chunk });
    req.on('end', next);

## latency.markdown

      
              2 files
            
          
              742 forks
            
          
              49 comments
            
          
              4384 stars
            
          
                hellerbarde
                / latency.markdown
            
            
              Created
              May 31, 2012 13:16
                — forked from jboner/latency.txt
            
              
                Latency numbers every programmer should know
              
          
    Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 µs
SSD random read ........................ 150,000 ns  = 150 µs

Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs

	var express = require('./')
	var app = express();

	app.use(function(req, res, next){
	if (req.is('text/*')) {
	req.text = '';
	req.setEncoding('utf8');
	req.on('data', function(chunk){ req.text += chunk });
	req.on('end', next);