reborg

State of Clojure Survey 2018 - Open comment question

This is a selection of the most articulated critique found in the open comments section Q25 at the bottom of the survey. Recurring themes are:

1. Elitism, ivory tower, "not smart enough to get it" attitude of frequent speaker or early adopters.
2. Poor basic documentation, error messages, beginner friendly resources.
3. Fear of contribution (with reasons like a. community-built tools open to attack and replacement by core team b. hostile contribution environment c. closed development process)

• The community has to grow to create more opportunities. Many organizations don't want to even consider using it because they fear not being able to find Clojure developers. Unless you have a mentor or are extremely motivated, Clojure scares away most imperative developers. My suggestions is to team up with a university and get a Clojure course on Coursera or a similar platform. This is the only way I got in

achikin

(defun dotspacemacs/layers ()
  "Configuration Layers declaration.
You should not put any user code in this function besides modifying the variable
values."
  (setq-default
   ;; Base distribution to use. This is a layer contained in the directory
   ;; `+distribution'. For now available distributions are `spacemacs-base'
   ;; or `spacemacs'. (default 'spacemacs)
   dotspacemacs-distribution 'spacemacs
   ;; Lazy installation of layers (i.e. layers are installed only when a file

sararob

'use strict';

// Dependencies
const gcloud = require('google-cloud', {
  projectId: 'sara-bigquery',
  keyfileName: 'keyfile.json'
});
const vision = gcloud.vision();
const fs = require('fs');
const async = require('async');

amalloy

*.clj  diff=clojure
*.cljs diff=clojure
*.cljx diff=clojure

arohner

(ns example.api.google
  (:require [cemerick.url :as url]
            [cheshire.core :as json]
            [clj-jwt.core :as jwt]
            [clj-jwt.key :as key]
            [clj-time.core :as time]
            [clj-http.client :as http]
            [clojure.string :as str])
  (:import java.io.StringReader))

inexorabletash

This demonstrates the implementation of full text search for documents in Indexed DB.

• Word-breaking and stemming is used to create a list of terms for each document.
• Document records are annotated with the list of terms when added to the database.
• A multi-entry index on the list of terms is populated.
• A query is similarly processed into a list of terms.
• A join over the terms is implemented using multiple cursors on the index.

The necessity of annotating records with the word list to populate the index is a limitation of the current Indexed DB API. A feature request to support custom

adstage-david

(ns page-helpers
  "All of the following page helpers take a \"page\", which is a map with
  key names for named elements tied to their CSS selectors.
  Page is expected to always have keys:
  - :page-name (string)
  - :page-id (css selector string)
  - :page-url (regex to match url)

  Using this as the first argument allows us to use the while-on and
  within-modal macros to fill in the page in repeated series of steps (they both

arfon

How many times shouldn't it happen...

-- https://news.ycombinator.com/item?id=11396045

SELECT count(*)
FROM (SELECT id, repo_name, path
        FROM [bigquery-public-data:github_repos.sample_files]
 ) AS F

gzeureka

• (:identity req) is auth backend independent way to access user data
• login and logout implementation depends on auth backend
• :current-user doesn't imply that authentication is required, route should also have :auth-rules if authentication is required

mfikes

Planck's shell support is modelled after clojure.java.shell. And, in particular, the command is separated from its arguments.

Here is an example sequence in a Clojure REPL illustrating this:

user=> (require 'clojure.java.shell)
nil
user=> (clojure.java.shell/sh "lein version")

IOException error=2, No such file or directory java.lang.UNIXProcess.forkAndExec (UNIXProcess.java:-2)