HNHacker News
TopNewBestAskShowJobs

CookieCutter2

8 karma · joined June 30, 2015

submissionscomments
CookieCutter2··on Ask HN: Has anyone here programmed in Kotlin? What do you think about it?
Without proper Option deconstruction and map()/flatMap() syntacic sugar Option code beside map() is not very pleasent to read or understand to my eyes :-(
CookieCutter2··on Ask HN: Has anyone here programmed in Kotlin? What do you think about it?
This is hard to explain and I didn't understand it either, after programming Java for 15 years. After 5 years of Scala I can't think of not using Option.

If you allow null as a return type you need to check for null if you want to use it or not. If you return Option[_] people e.g. just use map() on the return value and then map().map().map().map() on that etc. With Option your code usually does not care to check until the very last moment. Sorry my English is not good enough to make the point :-( And I know, saying "You need to use Option (and Applictives etc.) some years to grok" sounds arrogant and unsatisfactory. But I would not go back to a language without Option (and Applicatives etc.) usage in it's culture.

CookieCutter2··on Ask HN: Has anyone here programmed in Kotlin? What do you think about it?
1. Option solves a long list of programming problems (mostly around things being there or not, but others as well) while non-nullable types only solve NPEs.

2. Sorry, wording is vaque, often deconstruction is

val MyValueObject(a,b,c) = myObject

CookieCutter2··on Ask HN: Has anyone here programmed in Kotlin? What do you think about it?
I was not 'arguing with them' but when asked what was missing I offered deconstruction for nicely using Option/Maybe for which I was told there are non-nullable types. Rest see above.

I personally would listen instead of attacking me.

CookieCutter2··on Ask HN: Has anyone here programmed in Kotlin? What do you think about it?
To clarify:

Option/Maybe solves the problem of things either being there or not (from databases, domain modelling, ...). As a side effect this solves NPEs.

Non-Nullable Types is there to solve (accessing non initialized variables) NPEs.

CookieCutter2··on Ask HN: Has anyone here programmed in Kotlin? What do you think about it?
Always looking for something more simple than (my current) Scala.

- Argued with the developers, they have not clue about Option/Maybe and what it's good for. They offer non-nullable type which solves just one - minor - problem with Null

- No deconstruction

- Their documentation in the beginning mixed features and planned features without discrimination. Spend a lot of time to find out trying to make them work that the features they've described in detail were fantasies.

- With deconstruction I would give it a try in a project.

CookieCutter2··on Ask HN: I'm going to have to lay people off, and want your advice
I've laid off several people several times.

To me it was much harder than firing people - hard by itself - because mass layed off people ask "why me" where I had no good answer.

Keep handkerchiefs around.

CookieCutter2··on Dude Sneaks into Game Studio… Eats Their Food… Discovers Unannounced Game
I want to know if HL3 is coming.
CookieCutter2··on Test Pilot Admits the F-35 Can’t Dogfight
The Phantom F4 had no main gun because everyone thought there were no dogfighst but only missle fights. Reality was different and they added a vulcan gun.

The F35 is not designed for dogfights but long range missle fights and stealth.