mergesort

import SwiftUI

let colors = [
    Color.pink,
    Color.blue,
    Color.green,
    Color.orange,
    Color.purple,
    Color.black,
]

hanslovsky

#!/usr/bin/env kscript

@file:DependsOn("com.drewnoakes:metadata-extractor:2.13.0")
@file:DependsOn("org.apache.commons:commons-lang3:3.10")
@file:DependsOn("info.picocli:picocli:4.2.0")

import java.io.File
import java.nio.file.CopyOption
import java.nio.file.StandardCopyOption
import java.nio.file.Files

toddlipcon

Before and after comparing the CPU usage of the kudu tserver,
scanning the ~3.4B rows of the l_shipmode column from TPCH lineitem:

Before
=============
 Performance counter stats for 'numactl -m 0 -N 0 build/release/bin/kudu-tserver -fs-wal-dir /data/1/todd/tpch-kudu-data/ts-0/wal/ -fs-data-dirs /data/1/todd/tpch-kudu-data/ts-0/data/':

        137,685.93 msec task-clock                #    3.356 CPUs utilized          
           106,215      context-switches          #    0.771 K/sec                  
               706      cpu-migrations            #    0.005 K/sec                  

raysan5

CUSTOM GAME ENGINES: A Small Study

A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.

Nowadays lots of companies choose engines like Unreal or Unity for their games (or that's what lot of people think) because d

gsurrel

###########################
# Phone apps and services #
###########################
adb shell "cmd package install-existing com.android.stk" # SIM toolkit
adb shell "cmd package install-existing com.android.stk2" # SIM toolkit (maybe for dual-sim devices)
adb shell "cmd package install-existing com.sec.android.app.simsettingmgr" # SIM card manager, maybe required, contains configuration and settings for handling dual SIM (give a SIM an icon, a name, and so on)
adb shell "pm uninstall -k --user 0 com.samsung.android.smartcallprovider" # The 4th tab in the Phone app for 'local places'
adb shell "pm uninstall -k --user 0 com.sec.vsim.ericssonnsds.webapp" # NSDSWebApp. The Non Sim Device Solution (NSDS) is linked to VoLTE and VoWifi (Wifi Calling). NSDS allows connecting non sim devices to IMS core: https://uk.linkedin.com/in/hemant-kumar-dewnarain-2b779679
adb shell "pm uninstall -k --user 0 com.android.cts.ctsshim" # Part of the Android Compatibility Test Suite: https://source.android.com/compatibility/cts/setu

klzgrad

调查目的：了解当前各基于TLS的协议方案中ClientHello的指纹独特性。理论背景见 https://arxiv.org/abs/1607.01639 。

指纹数据库：

• https://tlsfingerprint.io
• https://github.com/cisco/mercury

naiveproxy v78.0.3904.70-4

（利益相关：我是这个的作者）

gpeal

...
apply from: './flavors.gradle'
...
android {
    buildTypes {
        productFlavors {
            project.flavors.each { flavor, config ->
                "$flavor" {
                    dimension 'scope'
                    if (flavor != 'full') {

tclementdev

libdispatch efficiency tips

The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).

My take-aways are:

• You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.

• Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse

mikeash

#!/bin/bash

# Exit the script immediately on error
set -e

# We'll work in /tmp
cd /tmp

# Clone mach_override unless we already have it
if [ ! -d mach_override ]; then

neubig

"""
DyNet implementation of a sequence labeler (POS taggger).
This is a translation of this tagger in PyTorch: https://gist.github.com/hal3/8c170c4400576eb8d0a8bd94ab231232

Basic architecture:
 - take words
 - run though bidirectional GRU
 - predict labels one word at a time (left to right), using a recurrent neural network "decoder"
The decoder updates hidden state based on:
 - most recent word