News for hackers. Stuff that matters.
Re:After suggesting a developer drop Linux support, Vivox ha... by grandinj on Wednesday May 01, 2019 @12:12PM (#19798513)
Really? I regularly manage to get most of the linux toolchain to bork, and have particular "fun" getting the profiling tools to work properly.

And never mind getting a nice IDE environment like Visual Studio up and running.

So it may just be a matter of familiarity and/or the particulars of the projects you work on.

Re:After suggesting a developer drop Linux support, Vivox ha... by Vogtinator on Wednesday May 01, 2019 @01:00PM (#19799142)
Here getting a nice IDE installed is just a single "zypper install qt-creator".
Re:After suggesting a developer drop Linux support, Vivox ha... by Asooka on Wednesday May 01, 2019 @01:14PM (#19799312)
You need a license for qt-creator if you want to work on commercial software (or that was the case last time we checked about a year or two ago). There might be exceptions for your case, do check, because it is a nice product. Other paid IDE alternatives are CLion, which I hear is excellent, as well as SlickEdit, which is closer to an editor than a full IDE, but does offer building, debugging, completion.

Free alternatives would be Visual Studio Code, which is pretty ok even for C++, or KDevelop, which almost kind of works, or SpaceVim / SpacEmacs and about a week of learning how to use it. I'm in the final camp, since basically every serious C/C++ dev on Linux has a Vim or Emacs setup they've built themselves that does about 90% of what Visual Studio gives you out of the box, with some things better and others worse. It can work pretty well, but you have to understand it's not VS and it works in its own way.

If you have the money, you can buy a good IDE for Linux. Otherwise, learning to make your own out of high-level building blocks is also a useful skill, but takes a little bit of time. Personally the first time I had to write C for Linux out of college it did take me about a week before I was up to speed with it (but I was already sort of familiar with vim as a pure editor).

Re:After suggesting a developer drop Linux support, Vivox ha... by redlynx on Wednesday May 01, 2019 @01:28PM (#19799478)
Could you provide a reference to why you think you require a commercial license for QtCreator to work on commercial software? The core application is licensed under (L)GPL. The commercial version adds a few specific features. I have been using QtCreator for a long time and as far as I know there's never been any sort of "cannot be used for commercial software" clause.
Re:After suggesting a developer drop Linux support, Vivox ha... by rhinoceraptor on Wednesday May 01, 2019 @01:41PM (#19799625)
I think they're mistaking Qt Creator with Qt itself. Certainly if you're using Qt in your application, you need a license or release as L?GPL. The IDE/editor has nothing to do with it.
Re:After suggesting a developer drop Linux support, Vivox ha... by detaro on Wednesday May 01, 2019 @01:56PM (#19799808)
LGPL (and not GPL) specifically means that you do not need to release your application under an open license.

Small parts of Qt for specialized applications are under GPL, and abiding LGPL in embedded hardware is hard, but for normal desktop software it's not a problem.

Re:After suggesting a developer drop Linux support, Vivox ha... by rhinoceraptor on Wednesday May 01, 2019 @06:06PM (#19802150)
If you statically link to QT, that’s a derivative work so you need to release as GPL or buy a proprietary license.
Re:After suggesting a developer drop Linux support, Vivox ha... by detaro on Wednesday May 01, 2019 @06:07PM (#19802167)
That's why approximately nobody links Qt statically on desktop systems. (technically you can also share compiled, proprietarily licensed object files a customer can re-link themselves, but I suspect that's even rarer) I should maybe have clarified that above what obligations the LGPL does bring, but that case basically matters only on mobile and embedded.
Re:After suggesting a developer drop Linux support, Vivox ha... by KingMachiavelli on Wednesday May 01, 2019 @01:56PM (#19799805)
Based off of Qt's comparison between their commercial and open source licenses, you would only absolutely need the commercial license if you were making modifications to Qt itself instead of linking to the shared libraries. Even in that case you could simply publish your Qt modifications as GPL seperetly.

https://www.qt.io/download

Re:After suggesting a developer drop Linux support, Vivox ha... by rhinoceraptor on Wednesday May 01, 2019 @01:43PM (#19799655)
This is like saying all software written with Emacs needs to be GPL.
Re:After suggesting a developer drop Linux support, Vivox ha... by munk-a on Wednesday May 01, 2019 @01:51PM (#19799759)
I mean... that's a valid analogy - but still, RMS would be absolutely for this.
Re:After suggesting a developer drop Linux support, Vivox ha... by detaro on Wednesday May 01, 2019 @01:58PM (#19799823)
> You need a license for qt-creator if you want to work on commercial software

No, you do not need a commercial license for creator, neither did you at other points in the past few years.

Re:After suggesting a developer drop Linux support, Vivox ha... by Avery3R on Wednesday May 01, 2019 @01:37PM (#19799571)
VS code is more of a text editor, not an ide.
Re:After suggesting a developer drop Linux support, Vivox ha... by meko on Wednesday May 01, 2019 @02:01PM (#19799858)
Those lines have become increasingly blurred.
Re:After suggesting a developer drop Linux support, Vivox ha... by chupasaurus on Wednesday May 01, 2019 @02:03PM (#19799885)
I.e. a browser.
Re:After suggesting a developer drop Linux support, Vivox ha... by dejaime on Wednesday May 01, 2019 @01:54PM (#19799787)
You can use the IDE without problems. It's like Gimp, for an example. It is GPL, but you are not incorporating the software itself.

Even though I would argue QtCreator is only bearable when working with Qt.

Re:After suggesting a developer drop Linux support, Vivox ha... by russh on Wednesday May 01, 2019 @04:05PM (#19801075)
"And never mind getting a nice IDE environment like Visual Studio up and running."

I guess I'll just have to settle with using Visual Studio Code for linux.

Re:After suggesting a developer drop Linux support, Vivox ha... by CoolGuySteve on Wednesday May 01, 2019 @06:41PM (#19802394)
So what? I don't agree with you at all but it's irrelevant, the important thing is that the tools are there and they make your code more robust.

If you're willing to sacrifice the stability and performance of your output for a saccharine IDE and its installer then that really speaks more to your priorities as an engineer.

Re:After suggesting a developer drop Linux support, Vivox ha... by rich-tea on Wednesday May 01, 2019 @01:43PM (#19799651)
They are serious tools for professionals and you have to learn how to use them. I don't know why people think they should be able to use things without training these days. Once you know what you're doing, the toolchains are solid as a rock.
Re:After suggesting a developer drop Linux support, Vivox ha... by grandinj on Wednesday May 01, 2019 @02:02PM (#19799877)
Just a teensy bit condescending there?

You mean like

- gdb randomly sucking up 16G of ram - gdb crashing with internal errors - clang/gcc miscompiling my code - perf refusing to record stacks - perf refusing to symbolise stacks because it's having a disagreement with the compiler people about debug data formats.

- locking up X11 and having to SSH in to fix it (because, you know, X11 doesn't have per-application input queues, unlike WindowsNT3.5)

- and a ton of other minor little annoyances with hardware support that Mac/Windows ironed out years ago

I like Linux a lot, the tools are great, but let us not pretend they are all that, they still have a way to go.

Re:After suggesting a developer drop Linux support, Vivox ha... by zelon88 on Wednesday May 01, 2019 @04:05PM (#19801072)
You say "ironed out" but what I think you mean is "layered on top of each other and ironed together; impossibly thin."

I feel like developing on Windows is more difficult because of all it's abstraction layers. WMI, DCOM, the registry, overlapping snap-in functionality, ect.

To me programming on Windows feels like you've got to peel apart all these layers to understand what's between them. Linux is one layer and you can already see right through it.

> - and a ton of other minor little annoyances with hardware support that Mac/Windows ironed out years ago

Uhh, did you just say that Mac has ironed out harware support? For what? They only support their own hardware. The hackintosh community will be the first ones to tell you that Apple purposely doesn't iron out hardware... ANYTHING unless it already says "Apple" on it.

Re:After suggesting a developer drop Linux support, Vivox ha... by davvolun on Wednesday May 01, 2019 @06:00PM (#19802096)
For the first half of that, I was pretty sure you were still talking about Visual Studio. That's...pretty much what I'm looking at with VS on my computer right now.