Understand your Mac and iPhone more deeply by tracing the evolution of Mac OS X from prelease to Swift. John Siracusa delivers the details.
You've got two main options:
// I'm tired of extensions that automatically: | |
// - show welcome pages / walkthroughs | |
// - show release notes | |
// - send telemetry | |
// - recommend things | |
// | |
// This disables all of that stuff. | |
// If you have more config, leave a comment so I can add it!! | |
{ |
The idea is to improve the SQL language, specifically the join syntax, for the special but common case when joining on foreign key columns.
Example below taken from PostgreSQL documentation [1]
In SQL-89, we didn't have any JOIN
syntax yet, so queries were written in this way:
class Graph { | |
class Node { | |
var connectedNodes: List[Graph#Node] = Nil | |
def connectTo(node: Graph#Node): Unit = { | |
if (!connectedNodes.exists(node.equals)) { | |
connectedNodes = node :: connectedNodes | |
} | |
} | |
} | |
var nodes: List[Node] = Nil |
import java.sql.Types | |
import scala.annotation.tailrec | |
import scala.concurrent.Await | |
import scala.concurrent.ExecutionContext.Implicits.global | |
import scala.concurrent.duration.Duration | |
import scala.meta._ | |
import slick.dbio.DBIO | |
import slick.jdbc.meta.{MColumn, MQName, MTable} |
package aecor.testkit | |
import aecor.data.PairE | |
import aecor.encoding.WireProtocol | |
import aecor.encoding.WireProtocol.{ Encoded, Invocation } | |
import cats.data.ReaderT | |
import cats.tagless.FunctorK | |
import cats.tagless.implicits._ | |
import cats.~> | |
import scodec.bits.BitVector |
#!/usr/bin/env bash | |
# To fix the " gpg: WARNING: unsafe permissions on homedir '/home/path/to/user/.gnupg' " error | |
# Make sure that the .gnupg directory and its contents is accessibile by your user. | |
chown -R $(whoami) ~/.gnupg/ | |
# Also correct the permissions and access rights on the directory | |
chmod 600 ~/.gnupg/* | |
chmod 700 ~/.gnupg |
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the