- Visit fmhy.net/android-iosguide#ios-ipas for more sources.
- Sideloading Guide: https://rentry.co/sideloadingguide
Discover gists
| # AFF | |
| # 如果你想支持我,可以通过我的邀请链接购买机场 | |
| # 感谢支持 | |
| # 1. 倾城极速 邀请码: 0jiB5uAA https://qcjs.ovh/#/register?code=0jiB5uAA | |
| # 2. ssLinks 邀请码: fSo2OhzH https://98a6251b6cd7471da86cca993b6dbe6f.36d.biz/#/register?code=fSo2OhzH | |
| # 一定要填我的邀请码,不填我哭给你看😭 | |
| # mihomo (Clash Meta) 懒人配置 | |
| # 版本 V1.22-250718 |
| #!/usr/bin/env python | |
| #-*- coding: UTF-8 -*- | |
| from reportlab.lib import colors | |
| from reportlab.platypus import Paragraph, SimpleDocTemplate, Table, TableStyle | |
| from reportlab.lib.styles import getSampleStyleSheet | |
| from reportlab.lib.pagesizes import A4 | |
| from reportlab.pdfbase import pdfmetrics | |
| from reportlab.pdfbase.ttfonts import TTFont |
Nix generally assumes run-time dependencies is a subset of the build-time dependencies.
This means many Nix builder functions try to automatically scan the output for runtime dependencies and "rewrite" them for runtime usage.
However shell scripts which are often exported by packages do not get this automatic scanning treatment.
This means you have to use the makeWrapper package and use either the makeWrapper or wrapProgram utility functions.
If you encounter a problem where you cannot commit changes in Git – neither through the terminal nor via the GitHub Desktop application – the issue might be a freeze during the Git commit process. This is often caused by GPG lock issues. Below is a concise and step-by-step guide to resolve this problem.
Open your terminal and try to perform a GPG operation (like signing a test message). If you see repeated messages like gpg: waiting for lock (held by [process_id]) ..., it indicates a lock issue.
| <?php | |
| // This code is what the Symfony Dependency Injection container performs | |
| // under the hood when registering a listener. | |
| $eventDispatcher->addListener( | |
| KernelEvents::REQUEST, | |
| function ($event) { | |
| // only when here, MyListener and ExpensiveDependency trigger autoloading | |
| // and the time of calling their constructor is spent. | |
| (new MyListener(new ExpensiveDependency))->onKernelRequest($event); | |
| }, |
By: Chamin Morikawa (https://www.linkedin.com/pulse/writing-related-work-section-paperthesis-chamin-morikawa/)
For most students, writing about what they did on their own is not hard. But writing about others' work - which is what you have to do in the "State of the Art" or "Related Work" section - is quite hard for them. Here are a few guidelines to make this task a bit easier.
Let's lay down our assumptions before continuing. I assume that you want to write a "Related Work" section for a research paper or a thesis that describes your approach to solve some problem. Let's also assume that there are other publications that attempt to solve the same problem, but the solutions in them are not perfect. Finally, let's assume that your approach has some difference when compared to those by others, and some improvement (faster, more accurate, easier to afford, etc.).
| function trigger(el, eventType) { | |
| if (typeof eventType === 'string' && typeof el[eventType] === 'function') { | |
| el[eventType](); | |
| } else { | |
| const event = | |
| eventType === 'string' | |
| ? new Event(eventType, {bubbles: true}) | |
| : eventType; | |
| el.dispatchEvent(event); | |
| } |
| extends KinematicBody2D | |
| export var move_speed = 200.0 | |
| var velocity := Vector2.ZERO | |
| export var jump_height : float | |
| export var jump_time_to_peak : float | |
| export var jump_time_to_descent : float |
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |