yat90

import com.google.gson.Gson
import org.jetbrains.exposed.sql.*
import org.jetbrains.exposed.sql.Function
import org.jetbrains.exposed.sql.statements.api.PreparedStatementApi
import org.postgresql.util.PGobject

fun <T : Any> Table.jsonb(name: String, klass: Class<T>, gson: Gson, nullable: Boolean): Column<T> {
    return registerColumn<T>(name, JsonColumnType(klass, gson, nullable))
}

fzakaria

/**
 * Too many examples on the internet demonstrate using self-signed certificates by disabling hostname verification
   or providing a weak TrustManager (i.e. SelfSignedTrustManager).
   This example shows how to properly start a server & client in the same JVM where the client knows about the 
   generated self-signed certificate.
   Also it's all done programmatically! Avoid using keytool and pulling in heavy dependencies like BouncyCastle!~
   **/
public class SecureServerTest {

    /**

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

jboner

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