Julio Biason 🐍 πŸ‘¨β€πŸ’» is a user on masto.io. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Julio Biason 🐍 πŸ‘¨β€πŸ’» @juliobiason@masto.io

(And, just for the sake of being clear, there is absolutely no issue with Masto.io.)

For no good reason (exception I'm getting a lot into this "functional" trends kids talk a lot these days), I'm transfering my account to `functional.cafe`, same handle: juliobiason@functional.cafe

In related news, the Java version in the Flink docs example actually worked.

Just for testing, I rewrote a Scala class in Java.

... and the Java version now looks better than the Scala version.

Irei viver grandes aventuras e aprontar altas confusΓ΅es nesse sΓ‘bado, no TcheLinux: poa.tchelinux.org/#speech-16

I'm really curious to see what interesting service Google will kill next year in its summer cleanup....

I want a "Thow-a-large-CRT-monitor-at-someone as a Service" just to use when someone says "we should increase the column limit to 2 billion, 'cause we have large monitors, LOL".

(Não que o email original seja uma obra de explicação e comunicação e demonstre esforço pessoal, mas VAI TOMAR NO CÚ COM UMA RESPOSTA DAQUELAS. Mas BEM TOMADO.)

Tavam falando da comunidade de Node, mas olha a pinta que aparece na lista do Django-Users:

groups.google.com/forum/#!topi

(Dica: Leiam todos os emails sem olhar o nome e descubram quem Γ© o brasileiro.)

I have this recurrent "If we had function composition, this code would be 1000x better to read" thought?

Sometimes I wonder if I should really reply to code reviews with memes...

Bash prompt progress so far:

FORE_BOLD="\[$(tput bold)\]"
FORE_WHITE="\[$(tput setaf 7)\]"
BACK_GRAY="\[$(tput setab 240)\]"
BACK_CYAN="\[$(tput setab 111)\]"
RESET="\[$(tput sgr0)\]"
export PS1="${BACK_CYAN}${FORE_BOLD}${FORE_WHITE} \u ${RESET}${BACK_GRAY}${FORE_WHITE} \w \$ ${RESET} "

"I think need a post-lunch coffee..."

Notices his leg trembling.

"Better not."

Actually I was wrong, but the shit keeps pilling up:

scala> 'a
res0: Symbol = 'a

scala> 'a.lowerCase()
<console>:12: error: value lowerCase is not a member of Symbol
'a.lowerCase()
^

Actually, because everything in Java is an object, you could turn `lowerCase` into a factory, which creates an "field" object with the field itself embedded, so the code looks pretty much the same in both languages (with the String/Symbol difference, though).

"But... What about Java?"

Fuck Java. Either you go with Strings and make everything compatible with Java or you do the right thing and use partials/high order functions. Fuck this current half-assed solution.

Look, way better:

.select(lowerCase('a))

in this case lowerCase() returns a function (so it's a high order function) applied as partial in the record.