swyxio

this is what i use so far, its obviously not a 100% replica of the typography plugin but looks good enough on my site

  /* replace typography plugin */
  .prose {
    @apply text-gray-700 dark:text-gray-300
  }
  .prose {
    & p {

cmod

Super fast, keyboard-optimized, client side Hugo search

This is a fork of and builds upon the work of Eddie Webb's search and Matthew Daly's search explorations.

It's built for the Hugo static site generator, but could be adopted to function with any json index.

To see it in action, go to craigmod.com and press CMD-/ and start typing.

kilbot

declare module '@nozbe/watermelondb' {
  import * as Q from '@nozbe/watermelondb/QueryDescription'

  export { default as Collection } from '@nozbe/watermelondb/Collection'
  export { default as Database } from '@nozbe/watermelondb/Database'
  export { default as CollectionMap } from '@nozbe/watermelondb/Database/CollectionMap'
  export { default as Relation } from '@nozbe/watermelondb/Relation'
  export { default as Model, associations } from '@nozbe/watermelondb/Model'
  export { default as Query } from '@nozbe/watermelondb/Query'
  export { tableName, columnName, appSchema, tableSchema } from '@nozbe/watermelondb/Schema'

sma

// run in DartPad: <https://dartpad.dev/c6a9111d58c3deb83711106cec6152ee>

import 'package:flutter/material.dart';

void main() {
  runApp(MaterialApp(home: RectsExample()));
}

class RectsExample extends StatefulWidget {
  @override

subfuzion

Overview

This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.

I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.

At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:

iampeter

When you need to handle text tags in Golang, eg. a Document can be tagged with software engineering, important and golang, you could do it with the Postgres text[] array type.

But with the jsonb type, you have all the marshalling and unmarshalling already there, so all you need to do is have a []string type, like below:

type JSONTags []string

func (tags *JSONTags) Scan(src interface{}) error {

shawntan

#!/bin/bash
STRING=$(< /dev/stdin)
KEY=
CHAT_ID=
curl -G -i -X GET \
    "https://api.telegram.org/bot$KEY/sendMessage?chat_id=$CHAT_ID&parse_mode=Markdown" \
    --data-urlencode 'text=`'"$STRING"'`'

pshinghal

alias glp="git log --color -p | less -R"
alias glg="git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit | less -R"
alias hlog='git log --date-order --all --graph --format="%C(green)%h %Creset%C(yellow)%an%Creset %C(blue bold)%ar%Creset %C(red bold)%d%Creset %s"'
alias cdg="cd \$(git rev-parse --show-toplevel)"

non

What is the appeal of dynamically-typed languages?

Kris Nuttycombe asks:

I genuinely wish I understood the appeal of unityped languages better. Can someone who really knows both well-typed and unityped explain?

I think the terms well-typed and unityped are a bit of question-begging here (you might as well say good-typed versus bad-typed), so instead I will say statically-typed and dynamically-typed.

I'm going to approach this article using Scala to stand-in for static typing and Python for dynamic typing. I feel like I am credibly proficient both languages: I don't currently write a lot of Python, but I still have affection for the language, and have probably written hundreds of thousands of lines of Python code over the years.

paulirish

/* bling.js */
window.$ = document.querySelector.bind(document);
window.$$ = document.querySelectorAll.bind(document);
Node.prototype.on = window.on = function(name, fn) { this.addEventListener(name, fn); };
NodeList.prototype.__proto__ = Array.prototype;
NodeList.prototype.on = function(name, fn) { this.forEach((elem) => elem.on(name, fn)); };