weavejester

This is a design for a unnamed programming language that I don't intend currently intend to make. It's dynamically typed, heavily inspired by Clojure, and designed with little thought given to performance.

The main features are:

• Inbuilt pattern matching on functions
• Error values instead of exceptions
• Unconstrained polymorphism
• Modules that are easier to statically analyze than namespaces

Reader

bsless

(defn qualify-definitions
  [d prefix]
  (let [p (str prefix ".")
        p' (str "#/definitions/" p)]
    (into
     {}
     (map (fn [[k v]]
            [(str p k)
             (walk/postwalk
              (fn [o]

borkdude

import org.graalvm.nativeimage.c.function.CFunction;
import org.graalvm.nativeimage.c.function.CFunction.Transition;
import org.graalvm.nativeimage.c.function.CLibrary;
import org.graalvm.nativeimage.c.CContext;
import org.graalvm.nativeimage.c.type.CCharPointer;
import com.oracle.svm.core.c.ProjectHeaderFile;
import org.graalvm.nativeimage.c.type.CTypeConversion;
import org.graalvm.nativeimage.c.type.CTypeConversion.CCharPointerHolder;
import java.util.List;
import java.util.Collections;

roman01la

ClojureScript REPL Workflow

Short write up on using REPL when developing UIs in ClojureScript.

Hot-reload on save or Eval in REPL?

Everyone's standard approach to hot-reloading is to use a tool (Figwheel or shadow-cljs) that reloads changed namespaces automatically. This works really well: you change the code, the tool picks up changed files, compiles namespaces and dependants, notifies REPL client which then pulls in compiled changes, and re-runs a function that re-renders UI.

The other approach is to use ClojureScript's REPL directly and rely only on eval from the editor. This more or less matches Clojure style workflow. This approach might be useful when you don't want tools overhead or hot-reloading becomes slow for you or you just used to this style of interactions. Also changing code doesn't always mean that you want to reload all the changes. On the other hand it is very easy to change a couple of top-level forms and forget to eval one of them.

paulmillr

BLS Signature for Busy People

Summary

• BLS stands for

  • Barreto-Lynn-Scott: BLS12, a Pairing Friendly Elliptic Curve.
  • Boneh-Lynn-Shacham: A Signature Scheme.

• Signature Aggregation

• It is possible to verify n aggregate signatures on the same message with just 2 pairings instead of n+1.

yogthos

Introductory resources

• High level overview https://yogthos.github.io/ClojureDistilled.html
• An Animated Introduction to Clojure https://markm208.github.io/cljbook/
• Interactive tutorial in a browser https://tryclojure.org/
• Interactive exercises http://clojurescriptkoans.com/
• Clerk notebooks with introductory examples https://github.clerk.garden/anthonygalea/notes-on-clojure
• More interactive exercises https://4clojure.oxal.org/
• Lambda Island tutorials https://lambdaisland.com/
• Functional Programming with Clojure resources https://practicalli.github.io/

ai

Понедельник (AJAX)

• Проблемы AJAX и как их можно решать «в лоб»
• Как решить проблемы AJAX лучше с помощью правильной архитектуры
• Как эта правильная архитектура реализована в Logux
• Бонус: ссылки о выгорании

Вторник (найм)

tkachenko1503

This is my lightning talk submission to ReactiveConf 2018 https://reactiveconf.com/

In this talk, I want to share my experience gained during the development of frontend applications in several programming languages.

I think it's not a secret for anybody that developing large JavaScript applications is not so easy as it seems at first glance. We all want something simpler and more reliable. Therefore, many developers and even entire companies switch to different, compiled in JavaScript, programming languages. The bulk of such transitions is accounted for TypeScript and flow, and often, developers faced with more problems than they were before.

I wasn't the exception. Moving to a new project, I started using TypeScript and was disappointed. Luckily in my next project I used ClojureScript and it was like everything is illuminated!

plaidfinch

  ;; PRETTIFY SYMBOLS (with Pragmata Pro)
  (defun setup-pragmata-ligatures ()
    (setq prettify-symbols-alist
          (append prettify-symbols-alist
           '(("!!"   . ?)
             ("!="   . ?)
             ("!=="  . ?)
             ("!≡"   . ?)
             ("!≡≡"  . ?)
             ("!>"   . ?)

caskolkm

(ns app.logging
  (:refer-clojure :exclude [time])
  (:require #?(:clj  [clojure.tools.logging :as log]
               :cljs [goog.log :as glog]))
  #?(:cljs (:import goog.debug.Console)))

#?(:cljs
   (def logger
     (glog/getLogger "app")))