clojurescript

It’s weird that I am writing about editors so much but trying a new editor every few months kind of became a tradition. It spices things up and allows me to learn something new that I maybe didn’t know yet before. Or just discover a new tool that improves my workflow. When I wrote about spacemacs, I thought spacemacs would be the thing that I would use for everything. Then I ported it to atom with proton and thought that would be the tool I would be using for everything since I could just implement features on the spot that it didn’t have yet....

I like learning new languages, I think that’s no secret. It’s a fun task that teaches you new interesting takes on existing problems. A language can make your programmers life very easy but could also turn it into a living hell. In fact, I am always on the hunt to find the perfect language for me. That thing that I want to use for everything. Meet ClojureScript Lately I’ve been doing a lot of clojure....

I recently wrote about my attempt to bring spacemacs style editing to atom. A lot of stuff happened that I wanna tell you about! In review Since the last post, proton acquired 72 stars, 13 watches and 4 forks. We now have 3 people that actively contribute changes. Proton became a good amount more stable, removed a lot of the ugly hacks it had in the beginning and added some really cool stuff on top....

If you read my last posts you might notice that I really like editors. Something about finding better and better tools is very interesting and fun. Plus using a new tool for a couple of weeks is keeping things fresh even when you work on the same codebase. The problem is that since I started using spacemacs, I can’t really use anything else. It just… doesn’t work. The shortcuts are too awkward, get overriden by third party plugins and all the manual config orchestration is just a pain....

I recently talked a lot about om and react native. Since people seemed quite interested in this topic, I decided to hold a little presentation at the last Tokyo iOS meetup in November. People were a bit overwhelmed (many never saw clojurescript before) but the general feedback was quite good. I am sure I convinced at least 1 person to give it a spin! In any way, here is my talk from that iOS meetup....

I mentioned already earlier that I believe om.next will be the future. Not particular om itself but the idea it implements: demand driven applications. The component declares what data it needs and the server is just there for delivering it. Components don’t want to coordinate 20 ajax requests just to gather all the data they need to operate. Components also don’t need all of the data your API provides in most cases, so why even the need to download all of it?...