"Germanic languages have special words for 11 and 12, such as eleven and twelve in English, which are often misinterpreted as vestiges of a duodecimal system. However, they are considered to come from Proto-Germanic ainlif and twalif (respectively one left and two left), both of which were decimal."
In Latin seventeen is septendecim, and sixteen is sedecim (fifteen is quindecim). Language drift has shortened most French words from their Latin ancestors, and the same goes for the numbers for 10-20. I presume that the early French chose to use dix-sept when their words for septendecim and sedecim started to sound the same.
As for dix-huit and dix-neuf, the Romans counted down from twenty; duodeviginti (two-down-from-twenty) is eighteen and undeviginti (one-down-from-twenty).
So it probably made more sense to the early French to say dis-huit and dix-neuf instead.
But one interesting thing about French numbers that you have missed is that it possess a vestigial remnant of the vigesimal (base-20) number system of the Celtics, where 80 is quatre-vignts (four-twentys) to the French, and 90 is quatre-vignts-dix.
70 is sixty-ten (soixante-dix), then 71 is sixty-eleven... and so on, up to 99: four-twenty-nineteen. Indeed, 80 is 4 times 20, hence "four-twenty" (quatre-vingt, without the "s" at the end).
Interestingly enough, French-speaking Belgians use the regular forms: 70 is "septante", 80 is "octante", and 90 is "nonante".
Is that actually a vestige of a hexadec system, or just a strange quirk? Note that 2 sounds similar to 12, 3 to 13, and so on. That implies there's a relationship between those numbers, which only exists in decimal.
Technically, there is no difference at all in how they function.
But I only use //example.com/ if an API is truly available on both http and https (very unlikely, nearly all APIs should be on https only if they use some form of access token in the querystring for auth), and I only use https://example.com/ if the end point exists on some other domain.
As there is no technical difference I opt to save some bytes in the bandwidth.
So what's the best IDE?
If you're an eclipse user, it's Scala IDE (http://scala-ide.org/). You can find a full download eclipse + Scala IDE plugins on the typesafe homepage (http://typesafe.com/stack/scala_ide_download).
If you're an IntelliJ user like myself you just need to install the Scala plugin.
Both IDE's have there drawbacks, none is perfect. I guess the easiest way to start is using the Scala IDE.
I don't hate ORMs, but I hate when they are too intrusive. What I like about Ebean is that it was designed to only handle the simple stuff "ORMish" and provide a very smooth and easy breakdown to raw SQL so you get the best of both worlds. I also love "autotune", it tracks your call stack for queries and after it has enough statistics it'll start only fetching the fields that you actually ended up using. So if you have an object with 25 fields and one page A you only use 5 of them, it'll only fetch those 5, but since its based on a the call stack and not hardwired into the model, it can can track that you used 5 different fields on page B and optimize that query too.
I didn't quite understand it. From your example, it looks like ORM layer knows about 'pages', which are in views. Isn't it against clean separation of concerns?
It doesn't know about pages, it knows about the stack trace that resulted in a query being generated, e.g. it know that a specific method in the ProductController called a specific method in the ProductService, etc, leading to a query being generated.
It also know which fields of the object it returned were accessed prior to going out of scope and more importantly, which fields were never accessed. With those two bits of information gathered over many calls it can figure which fields are actually worth fetching from the database and which should be left off and fetched lazily in the odd case that they are needed.
I'm living in Germany and to support this 'Energiewende', I'm only buying green electricity. It is more expensive but I'm happy to pay more if I can boost the industry around it and also help our environment. Many young people think like this.
For me, the eclipse plugin is crashing (or the whole IDE is freezing for a few seconds) too often when I try to get code completion. On the other hand, in IntelliJ the Scala plugin is pretty good! (Use the nightly builds!)
