Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
| // Extend Ember.Route to add support for sensible | |
| // document.title integration. | |
| Ember.Route.reopen({ | |
| // `titleToken` can either be a static string or a function | |
| // that accepts a model object and returns a string (or array | |
| // of strings if there are multiple tokens). | |
| titleToken: null, |
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
| ### | |
| ### | |
| ### UPDATE: For Win 11, I recommend using this tool in place of this script: | |
| ### https://christitus.com/windows-tool/ | |
| ### https://github.com/ChrisTitusTech/winutil | |
| ### https://www.youtube.com/watch?v=6UQZ5oQg8XA | |
| ### iwr -useb https://christitus.com/win | iex | |
| ### | |
| ### |
| #include <iostream> | |
| #include <fstream> | |
| #include <vector> | |
| #include <string> | |
| #include <algorithm> | |
| #include <chrono> | |
| #include <functional> | |
| #define GLFW_INCLUDE_VULKAN | |
| #include <GLFW/glfw3.h> |
Git for Windows comes bundled with the "Git Bash" terminal which is incredibly handy for unix-like commands on a windows machine. It is missing a few standard linux utilities, but it is easy to add ones that have a windows binary available.
The basic idea is that C:\Program Files\Git\mingw64\ is your / directory according to Git Bash (note: depending on how you installed it, the directory might be different. from the start menu, right click on the Git Bash icon and open file location. It might be something like C:\Users\name\AppData\Local\Programs\Git, the mingw64 in this directory is your root. Find it by using pwd -W).
If you go to that directory, you will find the typical linux root folder structure (bin, etc, lib and so on).
If you are missing a utility, such as wget, track down a binary for windows and copy the files to the corresponding directories. Sometimes the windows binary have funny prefixes, so
Here's a list of my issues with the Brave web browser (www.brave.com).
https://github.com/brave/browser-laptop/projects/1
| New Release Runbook (if it doesn't work on your system) | |
| (if you get git network failures, try raising config http.postBuffer) | |
| Definitions: | |
| B-L-B: .../browser-laptop-bootstrap | |
| B-L: .../browser-laptop-bootstrap/src/browser-laptop | |
| MUON: .../browser-laptop-bootstrap/src/electron | |
| 1. Download it: |
| // Clean | |
| npm cache clean | |
| rm -rf ~/.node-gyp | |
| rm -rf ~/.electron | |
| rm -rf ~/Library/Application Support/brave-development | |
| rm -rf node_modules | |
| // Install | |
| npm i |
