Let's have some command-line fun with curl, [jq][1], and the [new GitHub Search API][2].
Today we're looking for:
Let's have some command-line fun with curl, [jq][1], and the [new GitHub Search API][2].
Today we're looking for:
| #include <GL/glew.h> | |
| #include <GLFW/glfw3.h> | |
| #include <vector> | |
| #include <cmath> | |
| #include <cstdio> | |
| #include <limits> | |
| #include <chrono> | |
| #include <thread> | |
| #include <mutex> |
| // Rust 0.10-pre (Tue Mar 18, 2014) | |
| // $ rustc -L rust-openssl/build/ -L rust-toml/lib doing.rs | |
| // assuming https://github.com/sfackler/rust-openssl is cloned and compiled, | |
| // and https://github.com/mneumann/rust-tom is cloned and compiled | |
| #[feature(macro_rules)]; | |
| #[allow(deprecated_owned_vector)]; | |
| extern crate openssl; | |
| extern crate serialize; |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| # Snake for Neovim! Adapted from https://gist.github.com/sanchitgangwar/2158084 | |
| # To install, create a ~/.vim/rplugin/python/snake.py file with this | |
| # code, then run `nvim -c 'UpdateRemotePlugins' -c 'q'` from a shell. | |
| # | |
| # Make sure you have read the internal help explaining how to setup python | |
| # host for external plugins(:help nvim-python) | |
| # | |
| # To start a new game, use the `:SnakeStart` command on an empty buffer(uses 80 | |
| # columns and 20 rows) | |
| from threading import Thread, Lock |
I hereby claim:
To claim this, I am signing this object:
| #!/usr/bin/env python | |
| import random | |
| matches = 0 | |
| total = 1000000 | |
| people = 5 | |
| for i in range(total): | |
| month = random.randrange(12) | |
| for j in reversed(range(people - 1)): |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent| package main | |
| import ( | |
| "bytes" | |
| "crypto/tls" | |
| "encoding/xml" | |
| "fmt" | |
| "io/ioutil" | |
| "net/http" | |
| "strings" |
i was wondering if we should/could list common errors in the gl get started thing too, after debugcallback/renderdoc chapters or probably in some appendix, if you have more of those, let me know then we can compile those together into some comprehensive unfuck gl list
you use glad and its giving you a hard time, symbols not found, multiple definitions etc
nothing works:
setup glDebugMessageCallback see here