| in_progress = 0 | |
| start_end_game = 1 | |
| game_over = 2 | |
| left=0 right=1 up=2 down=3 | |
| valid_moves = {left,right,up,down} | |
| function _init() | |
| player = {} | |
| player.x = flr(rnd(120)) |
Hi everyone
It's not often that we email our members, so please bear with me and read this to the end.
Recent events in the wider tech community, and reactions within the Software Craftsmanship community, have prompted wider discussions about the inclusiveness of the community, and I've decided to make some small but important changes to our local chapter.
Author: Chris Lattner
From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:
There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.
That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.
| #!/usr/bin/env lumo | |
| (ns spacedl.spacedl | |
| (:require [cljs.nodejs :as node] | |
| [clojure.pprint :refer [pprint]] | |
| [clojure.string :as string :refer [join split starts-with?]] | |
| [cljs.core :refer [*command-line-args*]])) | |
| (node/enable-util-print!) | |
| (.on js/process "uncaughtException" #(js/console.error %)) |
A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.
How to use:
Integrating third party JavaScript libraries not written with Google Closure Compiler in mind continues to both be a source of error for users when going to production, and significant vigilance and effort for the the broader community (CLJSJS libraries must provide up-to-date and accurate externs).
In truth writing externs is far simpler than most users imagine. You only need externs for the parts of the library you actually intend to use from ClojureScript. However this isn't so easy to determine from Closure's own documentation. Still in the process of writing your code it's easy to miss a case. In production you will see the much dreaded error that some mangled name does not exist. Fortunately it's possible to enable some compiler flags :pretty-print true :pseudo-names true to generate an advanced build with human readable names. However debugging missing externs means compiling your production build for each missed case. So much time wasted for such simple mistakes damages our sen
Source for this comparison of C and ClojureScript perf.
C source:
#include <stdio.h>
#include <mach/mach.h>
#include <mach/mach_time.h>
int main() {
| https://rfc3161.ai.moda | |
| https://rfc3161.ai.moda/adobe | |
| https://rfc3161.ai.moda/microsoft | |
| https://rfc3161.ai.moda/apple | |
| https://rfc3161.ai.moda/any | |
| http://rfc3161.ai.moda | |
| http://timestamp.digicert.com | |
| http://timestamp.globalsign.com/tsa/r6advanced1 | |
| http://rfc3161timestamp.globalsign.com/advanced | |
| http://timestamp.sectigo.com |
| ; Learn Datalog Today (http://www.learndatalogtoday.org) is a great resource for | |
| ; reading but its interactive query interface is broken. Below is how we can | |
| ; load the same data into a Clojure REPL and play with it using DataScript. | |
| ; After running the code below, many/most/all? of the queries on Learn Datalog | |
| ; Today should be functional. | |
| ; | |
| ; Create a new lein project, add `[datascript "0.15.0"]` to `project.clj`'s | |
| ; `dependencies`, run `lein deps && lein repl` and copy-paste the following in | |
| ; chunks, inspecting the outputs as needed. |