I was writing a piece of code in Scala, which was supposed to de-serialize some Java object, previously serialized elsewhere. However, I kept seeing exceptions like these:
Recent versions of Idea (14 at the time of writing) play along quite nicely with SBT (Simple Build Tool - not so simple in fact). It can load project definitions, even when multiple subprojects are defined, and work with them. Unfortunately, it does the reading only once, when you import the project into the IDE. If you update your definitions afterwards, for example, when you add a new dependency, Idea might not be aware of the change. How to fix that?
I wrote earlier regarding the new product from Google - the Google Inbox. GI is still work in progress, so some features present in the familiar GMail are absent or broken. I counted the "mute" functionality among them, because there was no obvious menu for it. Mute allows you to ignore conversations, which you don't particularly care about. This can be very useful when you are subscribed to various mailing lists.
I gave Eclipse its fair chance. To be honest, I gave it more than one chance over the years. Each and every time it was a disappointment. It is actually amazing how broken the beast is. I tried various version and every time I tried to do anything that was even slightly out of simple Java editing using Eclipse' own project format, the thing failed in the most miserable way. For example, I tried repeatedly to install Android plugin so that I could write code for the platform.
DSL (Domain Specific Languages) are, as the name implies, software development languages created for a specific niche or limited domain. Where could one use a DSL? For example, when writing a library to evaluate highly complicated financial products, it might be very beneficial to have a language designed to describe such products. The language will check correctness of a new product, will allow sharing of common pieces of definition, will be able to generate output that can be fed into other systems (risk calculation, trade processing, graphic representation).
Scala is a great language. One of its strengths is the effortless interoperability with Java. However, given the fact that the language is still evolving, some compromises are needed in order to facilitate cooperation between Scala in Java. In effect, sometimes you can't write 100% pure Scala solutions. Sometimes you have to add some Java code to your project, even if very simple one. There are two common examples of this: enumerations and annotations.
I have upgraded from Android 4.4 KitKat to Android Lollipop on my Nexus 5 mobile phone over the weekend. Some observations so far:
Again I find myself thinking about how to write as little code as possible when developing applications for various mobile platform. I do find it annoying in the extreme, that iOS, Android and Windows Phone all have mutually incompatible technologies. As if they were doing it on purpose. But maybe they just do? It helps the companies to lock in software developers as well as end users, doesn't it? Maybe they hope, that the developers won't bother to write code for all the platforms and will just stick with one.
Yesterday I received an invitation to Google Inbox - a new mail service from Google on top of the famous GMail. I wanted to use it because it provided reminders and allowed you to snooze emails in the inbox until later. I find these features extremely useful. However, the current versions of both Android client and the web interface are not without issues. Here are some of them I have noticed so far: