Posts

Showing posts from January, 2015

Light Table

Ok after some work with it I have to say that it's really one of the easiest IDE to start with Clojure. The auto complete is very well done and is the only ide that make possible to start trying clojure without any issue with the IDE. ps: if you create a leiningen project LightTable will use the clojure version that you set in it, by default it will instead use the clojure 1.5.1

Clojure Ide: LightTable

Ok it has been some time since I start using clojure. I have to restart... and what is better than starting with the IDE. I want to give LightTable a try again, it was interesting last time I tried it. It's open source (under MIT) and I like the design. Here the first problems I find, I'm used to projects, so I would like to see a "Start new project" or something like that. Instead in LightTable you don't have that. Actually you don't have either a way to start easily a clojure project.... Ok let's read docs.. "With Clojure... In the view menu click the   commands   item (or press Ctrl+Space) Where is the commands item....., ok I go with the Ctrl+Space, but I don't like when they point me to something that don't exist... Ok after a little (10 minutes... not so little) I was able to figure out how it works, you create a folder, then you open the folder and it become your workspace. Actually I would have like a way to create a works

Clojure + Clojure Script CMS

Ok after some feedback on my journey I have decided that I will go with a Clojure + Clojure Script site. Stay in touch I will try to do little steps each day to obtain the result. The things I will use to start: Compojure (first I thought ring) Bootstrap For now I will go with this. I will try the best approach I can think: Do easy thing first, cover everything with tests, use more tools only when needed Every comment or help in any post will be accepted with gratitude. I don't think there is a full written history of a new clojurer that try to do something, I hope this will help understand what can be improved in Clojure to help people start using it. Have a nice evening, post to you soon.

Clojure in a working from home company.

I'm happy to see that some experts are starting reading my blog. This is why I started this in first place. Now I would like to raise a question for anyone that is reading. In normal company is easier to check how people work, help them improve in the way code is written and help them improve as programmers by making in-company seminars and things like that. Working in a remote company I have the feeling that this is very hard to accomplish. This is why, even though my love for clojure became bigger every day, I feel that static compilation is great when you work on a remote company. For example the biggest problems we have are on our front end, build on groovy. Groovy really is great for front end and thanks to its DSL is also great for database querying.Its dynamic nature help a lot when you need to customize it for clients. The real issue is that it isn't compiled, this cause often problems because people don't test their code (actually they don't ever navigate in

Clojure, Scala, Java 8

Here I am, back finally after an interesting year. I changed my job, now I'm working for jBilling from home. Working in a remote company is a challenging experience, and in particular it let you understand that clean code (well written, full tested and easy to extend and change) is something that you can't live without. This year I want to start a project to search for the perfect software combination to create a complex project. Until now I have never started working on a personal project, now I think I'm ready. I will create a CMS. The idea is to try to reproduce the same things with 3 different languages, Java 8, Clojure and Scala in the backend. For the frontend I will go with Angular JS, that will communicate through Rest services to the backend. If you have any suggestion on the framework that I will have to use feel free to comment here. I would like to do something that will be interesting for anyone that is going to read this. Talk to you soon.