[Development] As Qt contemplates its future..

[Thiago Macieira]

Em sábado, 15 de abril de 2017, às 10:14:45 PDT, Randall O'Reilly escreveu:
> > Because there's no such thing as binary distribution in the first place.
> > That means you cannot provide a component without the source. If we
> > insisted on all Qt users simply recompiling every time that Qt changed,
> > then we could apply the same to C++ and only retain source compatibility.
> > That is, after all, what Boost does.
> 
> That’s why the Go folks worry so much about super-fast compile times..
> 
> > By the way, is it even possible to distribute a binary application?
> 
> Yes, the final product of the compilation process is a (fat) static binary.

<sarcasm>
Oh, great! Super easy to fix a security issue or even a simple bug in a tiny 
component. Just rebuild the world!
</sarcasm>

> > Seems like we already have a binding to Go. What else do we need?
> 
> Yeah, but it’s not native Go, so it doesn’t really advance anything. 
> Potentially a usable stop-gap but given the limitations with the way that
> Go and C++ interface, I doubt many people using Go would find it a
> satisfying solution.  The proposal is that this is an opportunity for “next
> gen Qt” not a plea for a port of the existing product..

We're NOT going to rewrite Qt in Go. That's simply not going to happen.

The best you can expect is an officially supported Go binding, with some extra 
goodies.

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