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?...

If you follow clojurescript development you might have already heard about the next iteration of om, om.next. om.next is David Nolens attempt to bring together what big companies like facebook with relay and netflix with falcor are doing at the moment. I will not go into detail but instead of REST, it implements a architecture in which components clearly declare what kind of data they need to operate. A server / router is then gathering that data and passing it back....

Today, let’s talk about editors. Why? Because currently there are more editors than anything else. Microsoft decided to launch an editor, github decided to launch an editor - heck, even facebook suddenly invests into editors. We have closed source ones, open source ones, big full powered IDEs and of course the old school family. The good thing, I actually like playing with editors. Sometimes I feel like just opening a new tool and test it out....

I decided to create another simple blog based on jekyll next to my medium one. Why? let me explain. Medium is an amazing platform for writing. That’s what works really damn good on it. But writing doesn’t equal blog. Medium is a magazine - a collection of articles and columns from individual writers. When you see a post about ‘How to set up php’ with a big editorial picture and a ton of quotes, don’t you also think that it kind of feels… out of place?...