| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Fullscreen Image Viewer</title> | |
| <style> | |
| body { | |
| font-family: Arial, sans-serif; | |
| } |
| #lang at-exp racket | |
| (require urlang urlang/html urlang/react/urx) | |
| (require net/sendurl syntax/parse) | |
| ;;; | |
| ;;; Urlang Configuration | |
| ;;; | |
| (current-urlang-run? #f) ; run using Node? No, use browser | |
| (current-urlang-echo? #t) ; print generated JavaScript? |
Twitter abuses all media file uploads, each type in its own way. If we want to upload a good looking animation loop from some low-color, high-detail generative art, we have to game their system's mechanisms.
don't upload a video file, they will re-encode it into absolute 💩
create a GIF, which they will auto-convert into a video file 😱
The frames of the GIF will be resized to an even-sized width using an extremely naive algorithm. Your GIF should be an even size (1000, 2000,
A collection of useful git snippets and links for sharing. They're in no particular order.
| #lang racket | |
| ;; Usage information | |
| ;; Clone "https://github.com/papers-we-love/papers-we-love" | |
| ;; Use the download script under "scripts" | |
| ;; Create a file called "interests.txt" containing a list of | |
| ;; topics that you are interested in | |
| ;; Fill in the variable pdf-viewer with the path to your | |
| ;; pdf application (or #f if you don't want it to automatically oepn |
This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
| ;; -*- Gerbil -*- | |
| (export ~> ~>>) | |
| (defrules ~> () | |
| ((_ x) x) | |
| ((_ x (f a_1 ...)) (f x a_1 ...)) | |
| ((_ x f) (~> x (f))) | |
| ((_ x e e1 ...) (~> (~> x e) e1 ...))) | |
| (defrules ~>> () |
| Mute these words in your settings here: https://twitter.com/settings/muted_keywords | |
| ActivityTweet | |
| generic_activity_highlights | |
| generic_activity_momentsbreaking | |
| RankedOrganicTweet | |
| suggest_activity | |
| suggest_activity_feed | |
| suggest_activity_highlights | |
| suggest_activity_tweet |
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't really have SREs and they make engineers pretty much do everything,
A guide to better DE-Integration for the GNU Guix Package Manager.
This has been tried and tested (successfully) in the following desktop environments:
