5 ms·
Simple Made Easy (2011)
- rcarmo 10y agoNeeds a (2011) in the title. Still a very good session, though.
- nailer 10y agoDone.
- romaniv 10y agoThis is a classic. Definitely worth watching for everyone working within IT.
- corysama 10y agoSimple Made Easy is a great introduction to the Rich Hickey Fanclub [1] ;) Other recommendations for early viewing are "Hammock Driven Development", "The Value of Values" and "The Design of Datomic". [1] https://github.com/tallesl/Rich-Hickey-fanclub https://github.com/tallesl/Rich-Hickey-fanclub
- amelius 10y agoHickey may be a brilliant software architect, but I'm wondering how high he ranks as a business leader. How is his company Datomic doing? Also in the light of the new database service Cloud Spanner just launched by Google.
- Scarbutt 10y agoDidn't see anything about time-series features in spanner.
- rch 10y agoAnecdotal, but I've run into a couple of companies currently using Datomic in analytics and ML (with Clojure).
- mh8h 10y agoDatomic is very different from the typical database in terms of the operations it supports. I don't think Google Spanner, or the other similar products, are direct competitors. I don't know much about how they are doing financially though.
- pmarreck 10y agoI would love to know how using Datomic is vs. rolling your own data-immutability solution via other mechanisms but using off-the-shelf SQL/big-data tools.
- pmarreck 10y agoYou forgot "Are We There Yet?", which blew my mind at the time ("with respect to other code, mutability is an immutable function with a hidden time argument") and which was MY introduction to this fanclub. https://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey https://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hi...
- deleted 10y ago[deleted]
- swah 10y agoAt some point it felt like Clojure was the future, the new thing, so amazingly better - was that just a feeling of novelty? Or something went wrong with its use case? Of course, these days its about Rust, Swift and LLVM, but it doesn't have those lispy properties we love...
- afandian 10y agoI've been using it for 3 years and as I get my teeth further into my current project, I am grateful for Clojure every day.
- chousuke 10y agoI think Clojure is doing just fine. I've seen it used in "real-world" proprietary software (custom-made for a client by a third party). It's just usually packaged as a jar file, so no-one notices unless you look for certain tells.
- nepeckman 10y agoI feel like every new language has a honeymoon period. Clojure is still alive and well (and growing bigger consistently) but it doesn't have that new language hype anymore.
- jcadam 10y agoCurrently using Clojure on a side-project. It makes me so much more productive -- a real win when I don't have a ton of hours to devote to a project due to also having a day job :) If only I could find a day job using Clojure...
- rlander 10y agoI felt like that, like Clojure was the future, around 2009/2010. But then Java libraries and their impossible stack traces got in the way. I've been waiting for a native Clojure implementation (or on top of Python or the Erlang VM) ever since.
- pjmlp 10y agoThere are few abandoned attempts. Writing from scratch those Java libraries, including a good quality AOT compiler and GC is not something to do as hobby on the weekends.
- nailer 10y agoOne thing I've found super helpful on my current project (which happens to be node) is using OSS concepts and npm as a unit of modularity. Eg, everything is just a grab bag of functions in an npm module (sometimes with a closure holding some state - I either reject or don't understand FP people when they claim FP doesn't have state). Each module has tests, dependencies, a README, and if it is reusable by other projects, is even OSSd and published. Writing software as if it's going to be published makes me be more modular. Being modular makes things easier to reason about and therefore has stopped by codebase from becoming complex to work with.
- chowells 10y agoFP people have never claimed they don't have state. That's a straw man used to argue against something no one is saying. The claim is that there is no hidden state - everything is made explicit.
- nailer 10y agoI have no argument against FP, not am I making one here. But plenty of FP advocates claim FP "avoids state". It's not a straw man, it's just experience from asking people to explain FP.
- steinuil 10y ago> I either reject or don't understand FP people when they claim FP doesn't have state). But that's not what state is, closures are just an easier way to define lots of functions with similar parts. EDIT: Sure, you can call "whether or not f() or x are defined at the moment of calling (y) => f(x, y);" a form of "state", but this is called late binding and is simply not a thing in purely functional languages like Haskell; the existence of f() and x is checked at compile time.
- mdgart 10y ago"I either reject or don't understand FP people when they claim FP doesn't have state" FP has state, but it makes it explicit avoiding side effects inside functions and using persistent data structures, that means, instead of mutating the state you create a new state. Without state basically any program is totally useless.
- mmphosis 10y agohttps://github.com/matthiasn/talk-transcripts/blob/master/Hickey_Rich/SimpleMadeEasy.md https://github.com/matthiasn/talk-transcripts/blob/master/Hi...