nasser

(import Selection MeshFilter Vector3 Mesh Mathf)
(use 'clojure.repl)

;; mesh updates
(defn update-mesh! [^MeshFilter mf vs tris]
  (set! (.. mf mesh vertices)
        (into-array Vector3 vs))
  (set! (.. mf mesh triangles)
        (into-array System.Int32 tris)))

ZevEisenberg

osascript -e 'tell application "iOS Simulator" to quit'
osascript -e 'tell application "Simulator" to quit'
xcrun simctl erase all

john2x

Clojure Destructuring Tutorial and Cheat Sheet

(Related blog post)

Simply put, destructuring in Clojure is a way extract values from a datastructure and bind them to symbols, without having to explicitly traverse the datstructure. It allows for elegant and concise Clojure code.

Vectors and Sequences

hofmannsven

Git

Global Settings

• Related Setup: https://gist.github.com/hofmannsven/6814278
• Related Pro Tips: https://ochronus.com/git-tips-from-the-trenches/
• Interactive Beginners Tutorial: http://try.github.io/
• Git Cheatsheet by GitHub: https://services.github.com/on-demand/downloads/github-git-cheat-sheet/

Reminder

Press minus + shift + s and return to chop/fold long lines!

jbenet

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

chriseidhof

• Joris Kluivers
• NSHipster
• objvimmer.com
• oleb.net
• sealedabstract.com
• petersteinberger.com
• ashfurrow.com/
• blog.8thlight.com/uncle-bob/archive.html
• www.mikeash.com/pyblog/
• floriankugler.com

janl

127.0.0.1 aachener-zeitung.de
127.0.0.1 a-beig.de
127.0.0.1 abendblatt.de
127.0.0.1 abendzeitung.de
127.0.0.1 aerztezeitung.de
127.0.0.1 alfelder-zeitung.de
127.0.0.1 aller-zeitung.de
127.0.0.1 allgaeuer-anzeigeblatt.de
127.0.0.1 allgemeine-zeitung.de
127.0.0.1 all-in.de

praeclarum

//
// Copyright 2012 Frank A. Krueger
// 
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
// 
//     http://www.apache.org/licenses/LICENSE-2.0
// 
// Unless required by applicable law or agreed to in writing, software

cjohansen

tl;dr

If you must nest functions in a way that requires access to multiple this', alias outer this to something meaningful - describe the value it's holding. Treat this as the invisible first argument.

In general though, avoiding the situation (nested functions and frivolous use of this) will frequently produce clearer results.

Naming this in nested functions

I was accidentally included in a discussion on how to best name this in nested functions in JavaScript. +1's were given to this suggestion of using _this.

Giving style advice on naming nested this without a meaningful context isn't too helpful in my opinion. Examples below have been altered to have at least some context, although a completely contrived and stupid one.