[Development] Notes on "Qt Build Systems" @ QtCon 2016

Thiago Macieira thiago.macieira at intel.com
Tue Sep 6 15:26:30 CEST 2016

Em terça-feira, 6 de setembro de 2016, às 16:52:47 PDT, Ch'Gans escreveu:
> > Which is, in itself, an argument: why learn yet another buildsystem?
> Good question, maybe because it's more powerful, it fits better your
> needs, it is more fun, it uses new concepts, ...
> Or just out of curiosity!
> Why learn yet another programming language?

I haven't learnt any new programming languages since PHP in the late 90s. That 
specifically excludes major languages like Python, C# and even QML itself. I 
have yet to write a single QML file (disclaimer: my last GUI application was 
qdbusviewer, in 2006, and it was also my first).

I think I'm not doing that bad...

> If I followed this reasoning, I would still be writing my programs in
> Motorola assembler...
> Luckily, I've learned other languages like C, C++, Python, Lua, JS,
> Qml, etc, ...
> An average software developer knows about, says 10 to 20 programming
> languages, maybe even more depending on the definition of "language".
> Why should he/she knows just one build system?

There's a difference between "I could read that thing if I needed to" and "I 
can write very good code in this language". I can read Python, C# and QML, Go, 
Lua, Tcl, LISP, Rust, maybe even Haskell; but I have no interest in becoming 
an expert in any of those.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list