Clojure (clojure.org) is a robust, practical, and fast programming language with a set of useful features that together form a simple, coherent, and powerful tool.
ClojureTV brings together talks and presentations from the community, major Clojure conferences, and Cognitect (cognitect.com). Here you can find Clojure/conj, Clojure/west and EuroClojure talks, as well as custom video tutorials and presentations from Rich Hickey and the Cognitect team.
I've used this technique to good success. Some good tip is to have the variants be represented (sometimes when applicable) by the pseudo code or API, to make it easier for readers to recognize what the column represents. Overall, this combines well with his hierarchy of problems. With the hierarchy of problems, we need to put most of our energies on hard/significant problems, which we pay more for or more often. This decision matrix technique has the focus aspect by keeping the most important items front and center. Problem solvers can better use their analysis/mental resources on what's important.
I 100% agree. The biggest problem with Clojure and ClojureScript is that it is not advertised or marketed like other languages. Most developers don't even know it is an option until they go researching functional programming (Usually because they are like me and are 1000% done with broken JS and bloat). I think that Clojure is the most beautiful language so far, it is absolutely brilliant and I wish other front end devs knew about it and ClojureScript. ❤
I am not sure of the distinction between describing situation） and diagnosing （problem). Sounds like describing situation focuses on describing the symptoms, while diagnosing (problems) finds the root causes of the symptoms?
00:30 🤯 Simplicity is a prerequisite for reliability in software development, and we need to focus more on building simple systems. 02:34 📚 "Simple" means one fold or one twist, while "complex" means braided or folded together. Understanding this distinction is crucial in software development. 07:20 🤖 Easy can refer to being physically near, familiar, or within our capabilities. It's essential to recognize these different aspects of "easy" when discussing software. 11:54 🏃 Focusing solely on ease (fast development) at the expense of simplicity (understandable and maintainable code) will eventually slow down software development. 19:50 💡 Some constructs that seem easy can lead to complex and incidental complexity in software. Prioritizing simplicity in output is critical for software quality and reliability. 21:51 🧩 Simplicity leads to increased flexibility, independence of decisions, and easier policy changes in software development. 23:23 🧠 To deal with complexity, rather than trying to become smarter, simplify by reducing incidental complexity in your software. 27:18 🧶 "Complect" means intertwining or braiding, and it's a source of complexity in software. 30:19 🔄 Simple components allow for horizontal separation and vertical stratification, leading to robust software design. 39:31 🕸 Various software elements like state, objects, methods, inheritance, syntax, and more can contribute to complexity by intertwining different concerns. 42:38 🧩 The talk emphasizes the importance of distinguishing between "simple" and "easy" in software development. 43:07 🛠 Developing software can be simplified by choosing simpler tools and focusing on the essence of the problem, rather than complex constructs. 44:09 📦 Use values and persistent collections for simplicity, and avoid unnecessary complexity in data manipulation. 45:38 🌐 Simplify communication by using data instead of arbitrary command strings, and aim for polymorphism ala carte. 47:02 🔀 Simplify complex systems by using declarative rule systems and focus on consistency, transactions, and values. Made with HARPA AI
One thing I wonder about regarding maven central being immutable is: if a package is found to straight up malware, is it removed, making maven not immutable after all? More commonly a package is found to be insecure, and it seems like we keep providing it for backwards compatibility, maybe with a big warning. Then again nothing is perfectly secure I suppose.
As best I can tell, this is the only way for someone like me to build something Datomic-based, full-stack, and production-ready. I just don't have 20 years of dev experience. I _do_ have a desperate need to get a system up and running. Thanks Chris - and Rich, Alex, Stu, Jaret, Marshall, the rest of Cognitect/Nubank, and the whole Clojure community.
I’m a Clojure advocate at a windows/Java shop. I want to try the latest stuff, and lein fell apart when I tried to point it at a newer JVM. Tools.deps seems like the way to go, but on a managed PC, “just run this beta(?) PowerShell script” is a hard sell to start with.
In the 15:22 observation you can see what this mean. The light beam looks normal like just a single point, however the light pass though atoms, then when the magnetic field change, the atoms move, therefore the atoms absorve the photons, and then create shadows
Etymonline is a great resource for unpacking our language and getting back to the essence of our words. Fun fact: "complect" is in there (from the "simple made easy" talk)
As a web developer of almost 30 years, who has never seen a line of Clojure, I've probably watched this talk 5 times over the last 9 years and recommended it dozens of times. Ewald perfectly captures a philosophy of software development that has been lost in the age of massive tooling stacks and complex frameworks. Most developers I've hired or worked with over the last 15 years have never worked without a framework. More than that, they don't even realize that working without a framework is an option. They don't apply for web development jobs, they apply for [insert tech stack and framework here] jobs and they have no idea that they can work faster, build better products, save money, and actually understand what they are shipping if they go back to programming with hand tools. As a side note, I also built myself a great workbench, bought some wire holdfasts (don't waste money on cast ones), and started buying up planes, chisels, and dividers and other layout/marking tools at antique shops and garage sales. I also absolutely love my table saw (and band saw, thickness planer, cnc router, 60w laser, etc) , but knowing when and how to use hand tools changes everything. I no longer measure anything when I have a geometric/mechanical solution.
They're not... they're using ClojureScript _with_ React. React is a library, not a language (JSX is not React - JSX is a language and tool which ships "with" / alongside React). That said, one would choose ClojureScript over JSX + JavaScript if they preferred the ClojureScript language and available tools and libraries, and felt confident enough that they could create abstractions in ClojureScript as powerful or moreso than what JSX provides.
I am a Next.js dev myself and want to learn a functional language because I am sick of all these front-end runtime exceptions. I need a sense of security when developing but not at the expense of productivity. Hence languages like ClojureScript seem perfect for people like me
@think myelin maybe because design is an inherently consensus-building and shared-meaning/definition activity that wouldn't make sense to delegate to AI. implementation can in various aspects be delegated to machines/automaton.
@@thinkmyelin I can't talk for the OP, but I agree with them because this talk shows that good software is more about _thinking_ than _coding_. AI like co-pilot currently is just a predictive model of code out there. It doesn't do high-level thinking. Though admittedly, many human programmers don't either!
