- Set up iCloud Keychain
- Remove icons and hide Dock
- Default address in iMessage
- Install Updates
- Add Ru Input Sources
- Set up Shortcuts
- Add text shortcuts Text
| { | |
| "remove-empty-rulesets": true, | |
| "always-semicolon": true, | |
| "color-case": "lower", | |
| "block-indent": " ", | |
| "color-shorthand": false, | |
| "element-case": "lower", | |
| "eof-newline": true, | |
| "leading-zero": false, | |
| "quotes": "single", |
extension_id=jifpbeccnghkjeaalbbjmodiffmgedin # change this ID
curl -L -o "$extension_id.zip" "https://clients2.google.com/service/update2/crx?response=redirect&os=mac&arch=x86-64&nacl_arch=x86-64&prod=chromecrx&prodchannel=stable&prodversion=44.0.2403.130&x=id%3D$extension_id%26uc"
unzip -d "$extension_id-source" "$extension_id.zip"Thx to crxviewer for the magic download URL.
In the below keyboard shortcuts, I use the capital letters for reading clarity but this does not imply shift, if shift is needed, I will say shift. So ⌘ + D does not mean hold shift. ⌘ + Shift + D does of course.
| Function | Shortcut |
|---|---|
| New Tab | ⌘ + T |
| Close Tab or Window | ⌘ + W (same as many mac apps) |
| Go to Tab | ⌘ + Number Key (ie: ⌘2 is 2nd tab) |
| Go to Split Pane by Direction | ⌘ + Option + Arrow Key |
Английская версия: https://evilmartians.com/chronicles/bootstrap-an-intervention
У CSS есть несколько базовых проблем, которые позволяют очень быстро отстрелить себе ногу при неправильном использовании:
-
Глобальный неймспейс – в серверном программировании все что написано в файле, в файле и остается. Все же что написано в css и js засирает глобальное пространство имен со всеми вытекающими. В JS эту проблему сейчас побороли всякими модульными системами, а вот с css сложнее. В идеальном мире это должен починить Shadow DOM и настоящие Web Components, но пока их нет единственный способ с этим бороться – следовать какой-то системе именований селекторов, которая по возможности уменьшает и исключает возможные конфликты.
-
Каскадность – если на один элемент может сработать несколько правил, то они все и сработают последовательно. Если есть элемент
h1.title, на него сработают все правила для теговh1и все правила для класса.title. Так как весь html состоит из тегов, то правил которые п
| { | |
| "ru": { | |
| "Your original english text": "Твой оригинальный русский текст" | |
| } | |
| } |
| # On slow systems, checking the cached .zcompdump file to see if it must be | |
| # regenerated adds a noticable delay to zsh startup. This little hack restricts | |
| # it to once a day. It should be pasted into your own completion file. | |
| # | |
| # The globbing is a little complicated here: | |
| # - '#q' is an explicit glob qualifier that makes globbing work within zsh's [[ ]] construct. | |
| # - 'N' makes the glob pattern evaluate to nothing when it doesn't match (rather than throw a globbing error) | |
| # - '.' matches "regular files" | |
| # - 'mh+24' matches files (or directories or whatever) that are older than 24 hours. | |
| autoload -Uz compinit |
| [+] Entered shellcode | |
| [+] UID: 0, GID: 0 | |
| [DIR]: . | |
| [DIR]: .. | |
| [DIR]: adm | |
| [DIR]: app_tmp | |
| [DIR]: data | |
| [DIR]: dev | |
| [DIR]: eap_user | |
| [DIR]: eap_vsh |
| CREATE_CARD = "createCard"; | |
| COMMENT_CARD = "commentCard"; | |
| UPDATE_CARD = "updateCard"; | |
| UPDATE_CARD_ID_LIST = "updateCard:idList"; | |
| UPDATE_CARD_CLOSED = "updateCard:closed"; | |
| UPDATE_CARD_DESC = "updateCard:desc"; | |
| UPDATE_CARD_NAME = "updateCard:name"; | |
| ADD_MEMBER_TO_CARD = "addMemberToCard"; | |
| REMOVE_MEMBER_FROM_CARD = "removeMemberFromCard"; | |
| UPDATE_CHECK_ITEM = "updateCheckItemStateOnCard"; |
A maintainable application architecture requires that the UI only contain the rendering logic and execute queries and mutations against the underlying data model on the server. A maintainable architecture must not contain any logic for composing "app state" on the client as that would necessarily embed business logic in the client. App state should be persisted to the database and the client projection of it should be composed in the mid tier, and refreshed as mutations occur on the server (and after network interruption) for a highly interactive, realtime UX.
With GraphQL we are able to define an easy-to-change application-level data schema on the server that captures the types and relationships in our data, and wiring it to data sources via resolvers that leverage our db's own query language (or data-oriented, uniform service APIs) to resolve client-specified "queries" and "mutations" against the schema.
We use GraphQL to dyn