Felix Kohlgrüber05/08/2019, 12:48 PM
Daniel Hines05/17/2019, 6:29 PM
Edward de Jong / Beads Project05/17/2019, 8:41 PM
ibdknox05/20/2019, 7:20 PM
pbiggar05/20/2019, 8:43 PM
pbiggar05/20/2019, 8:44 PM
easy to read, understand, and edit”
if (x % 5 == 0)
pbiggar05/20/2019, 8:45 PM
Edward de Jong / Beads Project05/21/2019, 6:36 AM
Edward de Jong / Beads Project05/23/2019, 7:45 AM
Stefan05/23/2019, 3:56 PM
shalabh06/02/2019, 4:56 PM
robenkleene06/03/2019, 8:32 PM
yoz06/03/2019, 11:33 PM
Garth Goldwater06/06/2019, 5:43 PM
robenkleene06/11/2019, 6:36 PM
Quietly living inside file managers built by operating-system companies “served us well,” says Dropbox CEO and cofounder Drew Houston.
yoz06/11/2019, 6:54 PM
Dan Stocker06/11/2019, 10:05 PM
Garth Goldwater06/13/2019, 10:18 PM
Garth Goldwater06/18/2019, 7:14 AM
>> Enter TurboEditor. Because of this one simple little thing (not so little actually) that my friend found, we were able to decompile the entire CanDo program and figure out how it worked. Remember that important thing? Yes, that’s right, CanDo is actually written in itself and it could actually modify pieces that are currently executing. Let me clarify this just a little. One card could modify another card, then pull that card into focus. The actual card wasn’t currently executing, but the deck was. In fact, we came to find that CanDo was merely a facade. We also found that there was a very powerful object oriented, fully reentrant, self-modifying, programming language under that facade of a UI. In fact, this is how CanDo’s UI worked. Internally, it could take an element, decompile it, modify it and then recompile it right away and make it go live, immediately adding the updated functionality to a button or slider.
While CanDo could modify itself, it never did this. Instead, it utilized a parent-child relationship. It always created a child sandbox for user-created decks. This sandbox area is where the user built new CanDo Decks. Using this sandbox approach, this is how CanDo built and displayed a preview of your deck’s window. The sandbox would then be saved to a deck file and then executed as necessary.
Dan Cook06/22/2019, 3:43 PM
Stefan06/28/2019, 12:27 PM
"I want to understand the most important programming paradigms and learn about the broadest set of language features out there. What is the minimal set of programming languages I should look at? Popularity and how widely used these languages are doesn't matter, I just want the highest 🤯:🤓 ratio to maximize my learning."Here's what I think: • C — for a simple, pragmatic, influential, and still widely used procedural language and to understand memory management • Smalltalk — for a highly dynamic language and environment, message passing and the origins of OOP • Lisp — because you wouldn't take me seriously if I left it off such a list • Haskell — for a pure functional, strongly typed language with laziness and strong compiler support (error checking, synthesis, etc.) • Forth — for an even simpler, but still highly expressive, extensible, and dynamic language • Datalog — for logic programming and constraint solvers (or maybe Prolog instead?) • Erlang — for actor model and concurrent programming What would you respond?