Mark Malstrom markmals

Diff output of two lldb commands

Setup

Copy the contents of the last snippet (lldbinit) from the gist page, and paste into your .lldbinit file. This makes the ksdiff macro known inside lldb.
Put file ksdiff.py in ~/.lldb/
sudo pip install temp
Restart Xcode debug session

Example

(lldb) ksdiff ;

My call for Kotlin as a major frontend language

I try to push for quite a long time for first class support for WebAssembly in Kotlin because I really believe that frontend development is a domain where Kotlin can be as strong as in mobile, and because this is something that would also help to increase even more the adoption on server-side.

I truly appreciate all the work already done by Kotlin/JS and Kotlin/Native teams. The dead code elimination tool and the initial WebAssembly support in Kotlin/Native are important steps in the right direction. But I believe that Kotlin needs now to make frontend a real priority to take it to the next level.

Need for a consistent and unified web frontend strategy

The first point I would like to raise is that what Kotlin needs IMO is a consistent strategy about web frontend wich includes both Javascript and WebAssembly related efforts. I can u

State of String: ABI, Performance, Ergonomics, and You!

Hello, I’ve been working on implementing, optimizing, and improving String in preparation for ABI stability, and I thought I’d share the current status of String in Swift 5 and some potential directions to go. This is the product of conversations with open source contributors and my colleagues on the Swift standard library team at Apple.

The primary area of focus is stabilizing String’s ABI, but we’d be remiss if we couldn’t also fit in performance and ergonomic improvements. String’s ergonomics in particular is one area where we think the status quo is woefully inadequate, and over half of this email is devoted to that topic. At the end, there’s a section about a community initiative that we hope can help users of String as well as guide future development.

(Note: I’m sending this to swift-dev because much of the contents revolve around implementation concerns. I’ll also cross-reference on swift-evolution and swift-users. See also the [StringManife

	#!/usr/bin/swift sh
	import Foundation
	import PromiseKit // @mxcl ~> 6.5
	import Swifter // @mattdonnelly == b27a89

	let swifter = Swifter(
	consumerKey: "FILL",
	consumerSecret: "ME",
	oauthToken: "IN",
	oauthTokenSecret: "https://developer.twitter.com/en/docs/basics/apps/overview.html"

	import JavaScriptCore

	extension JSContext {
	subscript(key: String) -> Any {
	get {
	return self.objectForKeyedSubscript(key) as Any
	}
	set{
	self.setObject(newValue, forKeyedSubscript: key as NSCopying & NSObjectProtocol)
	}

	.PHONY: install uninstall test set-default

	test:
	sudo apt install plymouth-x11
	sudo plymouthd ; sudo plymouth --show-splash ; for ((I=0; I<10; I++)); do sleep 1 ; sudo plymouth --update=test$I ; done ; sudo plymouth --quit

	uninstall:
	rm -rv /usr/share/plymouth/themes/first \|\| true

	install: uninstall

	<html>

	<head>
	<script>
	customElements.define("star-wars-planets", class extends HTMLElement {
	constructor() {
	super();
	this.attachShadow({ mode: "open" });
	}
	static get observedAttributes() { return ["loading", "planets"]; }

	import UIKit
	import CoreServices
	import ImageIO

	class Writer {

	let output = NSTemporaryDirectory().appending("output.heic")
	lazy var outputUrl: CFURL = {
	return URL(fileURLWithPath: output) as CFURL
	}()

	import Foundation

	/// `StringScanner` is a fast scanner for Strings and String-like objects.
	/// It's used to extract structured bits from unstructured strings, while
	/// avoiding making extra copies of string bits until absolutely necessary.
	/// You can build Scanners over Substrings, allowing you to scan
	/// parts of strings and use smaller, more specialized scanners to extract bits
	/// of that String without needing to reuse another scanner.
	public struct StringScanner<Input: StringProtocol> {
	let input: Input

	#!/usr/bin/env bash

	# Installs ffmpeg from source (HEAD) with libaom and libx265, as well as a few
	# other common libraries
	# binary will be at ~/bin/ffmpeg

	sudo apt update && sudo apt upgrade -y

	mkdir -p ~/ffmpeg_sources ~/bin
	export PATH="$HOME/bin:$PATH"