TL;DR: It was my first time at FOSDEM and it took some time to feel comfortable, this post may help newcomers. As I mentioned in my previous post, I spoke at FOSDEM this year. It was my first time there (in the whole Europe, btw!) and it took some time to get used to the way the event goes. This post will show some tips that may help FOSDEM newcomers and maybe some veterans as well.
This year my proposal to speak at FOSDEM was accepted and I spoke at the Desktop devroom! :) It was my first talk in English, so I decided to do as many rehearsals as I could. I was 8 in total, but as expected, it was still a little bit faster than expected. :P I had 30 minutes to present and I did it in 26. I usually speak fast and this presentation was made to be fast because I had a lot of content to show in 30 minutes.
TL;DR: I like colemak, and it is a very good layout. I found some equivalent pros and cons, so I can’t recommend it to anyone without a little bit of philosophy. :) For those who don’t know Colemak, it is a keyboard layout created to make the most used keys stay in the home row as well as make you swipe between your right and left hand. There is a keyboard layouts heatmap for you to understand the benefits of using a keyboard layout that was designed to help you to be confortable and fast when typing instead of one that helping the operator to not jam the typewriter.
Pode ser que eu seja meio burro (heheh) mas eu ainda achava que o Ruby e o Python usavam Green Threads, mas depois de conversar com uma galera me disseram que eram threads nativas. Pesquisando na internet eu vi que eram mesmo, mas decidi rodar um strace para ver elas rolando e postar sobre isso. Fiz dois scripts simples: Python import threading import time for i in range(5): t = threading.
I’ve started using Go last month and I really liked to work with the language. The project I’m working on is dead simple and just retrieves metrics and save on a redis server (the data will be analyzed by a different project that I’m working on). So I have 15 goroutines retrieving data constantly and I’m using just two native threads. I did some CPU profiling on the code using my current machine for Golang 1.
Depois de muito tempo desenvolvendo finalmente terminamos o Skeleton-Jigsaw em outubro! Demorei para postar sobre isso aqui no blog por falta de tempo, mas aqui está! Eu e o Rafael Masoni trabalhamos nesse jogo durante quase 1 ano (começamos a falar dele no comecinho de janeiro) investindo nosso tempo livre para fazer todas as partes do jogo (audio, programação, arte, game design, level design e etc). Vou descrever um pouco do que fizemos e como organizamos, mas vai ser apenas um resumo do que falamos na nossa palestra no Guru-SP:
Since I bought an Acer notebook to use Linux again (I sold my mac, I have a post about it but in portuguese) I started to compile my own kernel. The reasons for the decision: I have a hardware that works better with the newer kernels. I really want to understand the linux kernel better. As Judas Priest sings on Painkiller song: “I’m living on the eeeeeedge”. LOL How to proceed There are some steps to follow when compiling a new kernel for your Linux box:
TL; DR Usei mac por mais de 6 meses e decidi voltar ao Linux. Na minha opinião mac não é ruim, mas Linux é melhor. A idéia desse post não é fazer um flame war, muito menos justificar porque eu voltei para o Linux (afinal, eu não devo nada pra ninguém), e sim falar um pouco do que eu vi de vantagens e desvantagens no Mac e porque eu resolvi voltar a usar Linux.
Desde que eu terminei a faculdade eu venho lendo bastante coisa útil (foi muita coisa inútil durante 4 anos…) e aprendendo bastante coisa. Nos ultimos meses eu li vários code reviews dos códigos do Quake e do Doom. Os review foram feitos por Fabien Anglard e estão todos disponíveis no site dele http://fabiensanglard.net. O primeiro artigo que eu li foi sobre o code review do código do Quake 2 de 1997.