- 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/
| /* ******************************************************************************************* | |
| * THE UPDATED VERSION IS AVAILABLE AT | |
| * https://github.com/LeCoupa/awesome-cheatsheets | |
| * ******************************************************************************************* */ | |
| // 0. Synopsis. | |
| // http://nodejs.org/api/synopsis.html | |
This describes how I setup Atom for an ideal Clojure development workflow. This fixes indentation on newlines, handles parentheses, etc. The keybinding settings for enter (in keymap.cson) are important to get proper newlines with indentation at the right level. There are other helpers in init.coffee and keymap.cson that are useful for cutting, copying, pasting, deleting, and indenting Lisp expressions.
The Atom documentation is excellent. It's highly worth reading the flight manual.
| syntax = "proto3"; | |
| package chat; | |
| option go_package = "github.com/defenseunicorns/leapfrogai/pkg/client/chat"; | |
| // ChatRequest is the payload to Chat creation | |
| message ChatRequest { | |
| repeated string inputs = 1; | |
| } |
| ############################################################################ | |
| # _ | |
| # | |_ _ __ ___ _ ___ __ | |
| # | __| '_ ` _ \| | | \ \/ / | |
| # | |_| | | | | | |_| |> < | |
| # \__|_| |_| |_|\__,_/_/\_\ | |
| # | |
| # Cheatsheets: | |
| # https://devhints.io/tmux | |
| # `property not found` issue: |
For a long time I've been really impacted by the ease of use Cassandra and CockroachDB bring to operating a data store at scale. While these systems have very different tradeoffs what they have in common is how easy it is to deploy and operate a cluster. I have experience with them with cluster sizes in the dozens, hundreds, or even thousands of nodes and in comparison to some other clustered technologies they get you far pretty fast. They have sane defaults that provide scale and high availability to people that wouldn't always understand how to achieve it with more complex systems. People can get pretty far before they have to become experts. When you start needing more extreme usage you will need to become an expert of the system just like any other piece of infrastructure. But what I really love about these systems is it makes geo-aware data placement, GDPR concerns potentially simplified and data replication and movement a breeze most of the time.
Several years ago the great [Andy Gross](ht
| HEADER | |
| { | |
| CompileTargets = ( IS_SM_50 && ( PC || VULKAN ) ); | |
| Description = "Hologram Effect"; | |
| } | |
| FEATURES | |
| { | |
| #include "common/features.hlsl" |
| -- script.lua | |
| -- Receives a table, returns the sum of its components. | |
| io.write("The table the script received has:\n"); | |
| x = 0 | |
| for i = 1, #foo do | |
| print(i, foo[i]) | |
| x = x + foo[i] | |
| end | |
| io.write("Returning data back to C\n"); | |
| return x |
| # Add this to the end of your development.rb and add | |
| # | |
| # gem 'pry' | |
| # | |
| # to your Gemfile and run bundle to install. | |
| silence_warnings do | |
| begin | |
| require 'pry' | |
| IRB = Pry |