Please create an account to participate in the Slashdot moderation system


Forgot your password?
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: One of these days (Score 1) 79 79

One of these days I'll have to get "into" QT. It looks like a great successor to some of the concepts originating with Neuron Data's tools, which I spent a lot of years learning and working with. For now I've been focused on Java server code, but I've never really been a fan of Java for writing client applications, and I've no interest in buying an Android device just so I can stick with Java while working on front-end code.

No, to me, client side means an actual computer, not a mobile device. And QT hits almost as many platforms as Java does, so it would seem to be an excellent fit for my goals. :)

Comment: Good idea (Score 4, Interesting) 107 107

Standards have a notorious habit of becoming bloated with rarely used features that never do get properly tested. Rethinking what is actually useful and needed is great for pruning code and handling the majority of use cases. Sure there will be edge cases it can't handle, but that's the whole point: they're edge cases that most programmers aren't going to need to use.

Comment: Re:Depends of what you mean by "Use" (Score 1) 164 164

Linking GPL code is considered the same as copying in the source code. The library has to be released under the LGPL to be used by non-GPL source.

But you are correct about invoking canned binaries of GPL products or sending IPC messages to a GPL product, provided you're not using the GPL messaging libraries provided with the product, but rolling your own which happen to be compatible at the messaging layer. But I'm pretty sure your messaging code would have to be written in a different language as well in order to avoid any claims that you copied code from the GPL source.

You're at Witt's End.