Firefox can not print objects with circular references, and an external library is needed to print deeply nested object structures.
>> JSON.stringify(web3, null, 2)
#!/usr/bin/env python3 | |
# Code for drawing a lot of SQLite databases | |
# https://github.com/yakshaveinc/linux/issues/29#issuecomment-533082911 | |
import os | |
import sqlite3 | |
from urllib.request import pathname2url | |
from sqlalchemy_schemadisplay import main |
-- Modes -- | |
i # | |
v # visual selection mode | |
Ctrl+v # visual block selection | |
ESC | |
Ctrl+o # in insert mode - run one command in normal mode | |
Firefox can not print objects with circular references, and an external library is needed to print deeply nested object structures.
>> JSON.stringify(web3, null, 2)
in Ruby all access to object attributes is thru methods
obj.field
in Pythonin Ruby method calls may have no ()
obj.method
is the same as obj.method()
# get all application routes
Slow by design
Terminals or "terminal emulators" are slow by design. They use only two streams - input and output for everything. No parallel key presses for battle game, no parallel drawing buffers or event queue from mouse of another controller. Terminals are stateful - you need to wait for output to switch to specific state before you can draw next symbol or process next key command. Terminals lose information about key
--- part 2: dreaming
How I would do this given enough resources? The humanitarian mission of WGC would not be just providing resources, it should also be educational to teach people the infrastructure - how to self host, store the results and share operational costs. The blockchain community did a lot of this in last four years, and a lot more should be done.
First step is transparency. Given the limited resources for only a handful of people, ensure that the whole system is sufficienty
getting mouseless
day1: Ctrl+Shift+P
to open command palette. Ctrl+B
to hide side panel.
featurecreeps
close side panel with Esc
.
It takes your source app code and containerizes it.
Yes, it is a Dockerfile replacement. Instead of creating Dockerfile for every little script you might have, just let the buildpack do the job.
What is lifecycle?
It is a go
program that executes logic in buildpacks. Much like docker build .
executes Dockerfile, the lifecycle
executes buildpack.
Why the hype?
https://help.github.com/en/actions - there docs are full of BS.
https://www.liatrio.com/blog/github-actions - but this link is awesome.
s/you can/you should/
and here is what you need to do.
You should create at least one workflow as a .yaml
/.yml
file
in .github/workflows/
dir.
Each workflow contains on trigger and jobs, each job contains steps.
What scons
is going to execute when launched?
How to dump the dependency graph without executing the build process?