Go, go, go!

C is fast, but boring,
Ruby is slow, but fun.
Go is right in between

Let's start with the fun bits:
- You don't import just a file, you import a repository.
Reading import "github.com/tiagodll/golib" is beautiful, that alone gets me excited about go.

- Returning multiple values. Yes, finally!
You can set resp, err := MyFunction()
- Ditching the ;. I never got the reason for it, maybe it is because I learned programming with VB, but to me it just doesn't make sense.

Now to the boring
- The name. Seems like nothing, but having a language called go makes google searches useless unless you use golang.
- Not having try/catch. It sucks. Although returning value, error makes up for it quite well.
- Having any not used lib/variable as an error instead of warning. It is ok when you have a final version, but that is really annoying while development phase.
And the worst of all: 
- the insane amount of extra lines to assign a variable such as
temp := MyType{id:123}
Printf("%v", temp)
Instead of a simple
puts get_value_from_mongo(123).to_s

and the grey area
- Not having classes. I like the idea of having all static methods (unless it is really about the object they are in), but not having classes could have some issues, specially because of inheritance.

Regardless, this is my current language of choice.
But this is just the beginning. 
Let's see next what go is all about.


Back in purple, well... that is the elixir's main color, right?

One of my favorite hobbies is to learn new technologies. This means almost anything. I like Languages, patterns, databases, and sometimes even hardware stuff (even though I am very bad at that)

That being said, from time to time I decide to revisit and adopt or abandon that technology.

This time is about Elixir. but not just about elixir, I realised that to properly learn elixir, Erlang is required.
No, you don't have to use Erlang code, but it is more about the programming style (and a bit about the libraries too).

So why to learn that?


Not only that, every time you learn a new paradigm, you bring good knowledge to yours. So learning Erlang might bring you some good improvements even in java. 
But seriously, it is 2014... leave java where it belongs: in the past!


Database evolution

"Someday your little database will grow up. When it hits the teenage years - about two in human years - it will get moody, sullen, and resentful. In the worst case, it will start undermining the whole system (and it will probably complain that nobody understands it, too)."
 Release it
Release It - Michael T. Nygard


Dart + start + polymer = ?

So as I said in my <a href="/2014/07/yeah-about-that.html">Dart, what do we think about it?</a> post, it is an interesting language to look into. It is lacking good libraries, but a problem can also be seen as an opportunity: it is a great time build your own.

Back to the topic, because of the pub system it is very easy to have dart + start <b>or</b> dart + polymer, but not as easy to have both.

There is a teeny-tiny detail it took me a couple of days to realize, but let me save this to the end of the post.

Start is simple, lets begin with that.
first, the pubspec

<code file="pubspec.yaml">
name: onemore
description: A sample Polymer application
  polymer: '>=0.11.0'
  start: any
- polymer:
    entry_points: web/index.html

Then all you need to do is to import the package and create a server side dart file to start it.
In this example I am only serving static files, it would be just as easy to handle dynamic content with the get(url).
<code file="app.dart">
import 'package:start/start.dart';

main(args) {
  start(port: 3000).then((Server app) { app.static('build/web', jail: false); });

Done, you have a web server running in http://localhost:3000 as soon as you run this code.

Now, the polymer part
to have a custom element we need 3 files: the dart, the html and the hosting html file.
this custom element expects a String list, and publish (sends to the client) both lst and plist.
<code file="elementlist.dart">
import 'package:polymer/polymer.dart';
import 'dart:convert';

class ElementsList extends PolymerElement {
  @published String list;
  @published List plist;

  ElementsList.created() : super.created(){
      plist = JSON.decode(list);

Here in the html we can use mustache style expressions
<code file="elementlist.html">
<link rel="import" href="packages/polymer/polymer.html">
<polymer-element name="element-list" attributes="list">
    <div>the list: {{ list }}</div>
      <template repeat="{{elmt in plist}}">
  <script type="application/dart" src="elementlist.dart"></script>

and then your index file you just have to add some references and include the custom element element-list.
<code file="index.html">
<!DOCTYPE html>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Sample app</title>
    <script src="packages/web_components/platform.js"></script>
    <script src="packages/web_components/dart_support.js"></script>
    <!-- import the click-counter -->
    <link rel="import" href="elementlist.html">
    <script type="application/dart">export 'package:polymer/init.dart';</script>
    <script src="packages/browser/dart.js"></script>
  <body unresolved touch-action="auto">
    before list<br>
    <element-list id="the_list" list='[{"id":1},{"id":2},{"id":3}]'></element-list>

Now, let me explain the little detail that made me lose so much time: start is just serving the folder specified above. The problem is that all the polymer javascript is generated in the build, and stored there. So our start must serve that folder instead.
to do that, all we have to do is to change the web to build/web in the start method:
app.static('build/web', jail: false);

That is all folks, hope you enjoy it.


Dart, what do we think about it?

yeah, about that...

Google's attempt to improve on Javascript and get a server-side language at the same time.
I have always wanted something else to thrive over javascript, and tried many good options like coffeescript or opal. Most of them are really good and easy to use as long as everything is correct.
Sadly that is not what happens. The bug fixing is a vital phase of software development, and in this is the problem with all the languages that compile to javascript.
Fixing the code is already hard enough as it is, imagine if you have to debug an auto-generated code in a language you possibly don't master.
For this reason I never adopted any of those for my development projects, and that is why dart quickly got my attention when they announced the dart VM embedded in chrome (ok, it is dartium, a branch of chromium but still counts).

Not just that, it is also a very flexible language where types are recommended but not enforced.
syntax is a bit outdated, they opted for the java style to make developers feel comfortable. With languages like ruby and python getting more and more users everyday I am not sure it was the best decision.
Although I have to agree, every developer feels familiar to a language with all the semi colons, curly brackets shenanigans that resembles java.

They have also done a good job in their package system, the pub. It feels just the same as using ruby gems.

Dart start is quite close to Sinatra, it is still lacking the template rendering, but it s a good start (pun unintended)

IDE. Ah, the IDE... why always Eclipse google?
It is so bad, rebuilds workspace every other minute, hangs all the time.
In fact, it hangs so much, my most used terminal command is "killall dart".
Seriously, why Eclipse again?

Overall it is good and I hope it works out.
Being a google product, I believe it will be forced upon us like google+ anyway, so why not to make the best of it and enjoy all the benefits?



So there is this new IDE now. Lean, lightweight... rip off?

I became a Sublime Text fan when I changed my language of choice from C# to Ruby.
Nothing is as good as Visual Studio, so moving on to the red side of the force I needed something to edit my files in, and please don't say VI.
VI could have been great years ago, but now I really can't see the point. Emacs is even worse, it is basically: you get all the bad features from VI, make them worse and call it an editor.

So in my search the first result was the Textmate, but at the time I didn't have a mac.
The closest thing I could find was SublimeText.
Sure, it is a paid software, and it seems silly to pay for a text editor like that when you have so many free options out there.
But it is so nice... I love its interface, the multiple selection, the command thing, well... almost everything in it, I just wish there was a file explorer to the side.

Now not only there is a copy of SublimeText, but they added the file explorer and made it free!

I just started using it, so maybe there will be a rant here in a few days, but for now this is my new editor of choice.

Also, don't forget to look for some plugins, they make this software so much better...