News for hackers. Stuff that matters.
Re:After suggesting a developer drop Linux support, Vivox ha... by CoolGuySteve on Wednesday May 01, 2019 @11:20AM (#19797865)
At least for high performance C++, the Linux toolchain improves code quality by so much. Between valgrind/cachegrind, asan, efence, always having the latest clang and clang_analyzer, and Dockerfiles for continuous integration environments, programming on Windows feels like I have a hand tied behind my back.

Even something basic like replacing malloc with your own instrumentation to track errant allocations is basically impossible since every DLL in Windows loads its own allocator.

I know Windows has similar tools but wrangling Visual Studio, especially remotely or across multiple developers, is significantly more painful in my experience.

Even if you don't ship on Linux, programming on Linux is worth it imo. I mean, Carmack wrote Quake on a NeXT and shipped on Windows, so if he was doing it back in the day, how wrong can it be?

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.
Re:After suggesting a developer drop Linux support, Vivox ha... by GuB-42 on Wednesday May 01, 2019 @02:09PM (#19799938)
I do most of my C++ dev on Linux and I prefer it that way, for the reasons you mentioned.

However, Windows has great tools too. And by that, I mean Visual Studio. In particular, I really miss its debugger when I am on Linux.

It is just a different philosophy with its pros and cons. On one side, you have a lot of small, loosely coupled tools, text files and command lines. On the other you have a well integrated monolith and GUI.

Re:After suggesting a developer drop Linux support, Vivox ha... by bitwize on Wednesday May 01, 2019 @12:54PM (#19799051)
Yes, but these days Carmack swears by -- wait for it -- Visual Studio. Microsoft developer tooling has a reputation for being absolutely top notch. The integrated debugger alone makes Visual Studio well worth it; nothing even remotely comparable exists under Linux.
Re:After suggesting a developer drop Linux support, Vivox ha... by dboreham on Wednesday May 01, 2019 @01:40PM (#19799606)
I'll dispute this because I find the jetbrains IDE on Linux to be comparable. If you're talking specifically about C development then I'm not sure because I haven't written C in a long time, but for Java, Python, JS the jetbrains products work as well as VS for me.
Re:After suggesting a developer drop Linux support, Vivox ha... by bitwize on Thursday May 02, 2019 @12:14PM (#19809474)
I was referring specifically to C and C++ development, for which JetBrains CLion is supposed to be pretty good, but still nowhere near as comprehensive as Visual Studio, particularly when it comes to debugging. In fact, concerning gaming specifically, one of the reasons why DirectX won the API wars is because Microsoft included a GPU debugger for DirectX with Visual Studio. I think Vulkan might have comparable tooling, but OpenGL emphatically did not.
Re:After suggesting a developer drop Linux support, Vivox ha... by ryanackley on Wednesday May 01, 2019 @11:51AM (#19798246)
NeXT wasn't Linux. My understanding is that it was a completely proprietary POSIX based operating system. That being said there is something to be said for POSIX based (unix, linux, os x), terminal based development tools. It's where most of the innovation happens in the developer community.

There is also something easy about GUI based development and debugging on Windows. A runtime environment that is fairly standard for gaming is also a big plus.

Re:After suggesting a developer drop Linux support, Vivox ha... by asveikau on Wednesday May 01, 2019 @11:57AM (#19798343)
NeXT wasn't Linux, but the point being made was that it would have been easy to dismiss NeXT as a "fringe" platform at the time. It is an argument for developing with platforms [and porting to them] when they may not be a priority for your end users.
Re:After suggesting a developer drop Linux support, Vivox ha... by thrax on Wednesday May 01, 2019 @12:09PM (#19798489)
It wasn't Linux but was based on mach Unix iirc. And they weren't cheap.. but they were cheaper than a similar horsepowered SGI workstation at the time, iiarc. But probably 10x the cost of a Windows machine.
Re:After suggesting a developer drop Linux support, Vivox ha... by usefulcat on Wednesday May 01, 2019 @01:15PM (#19799337)
Actually it was Doom that was developed on NeXT. A big advantage of doing development on NeXT vs DOS was that dereferencing an errant pointer couldn't take down the whole machine.

https://en.wikipedia.org/wiki/Development_of_Doom#Programmin...

Re:After suggesting a developer drop Linux support, Vivox ha... by inflatableDodo on Wednesday May 01, 2019 @01:05PM (#19799199)
>NeXT wasn't Linux. My understanding is that it was a completely proprietary POSIX based operating system.

NeXT was BSD with a Mach kernel.

Re:After suggesting a developer drop Linux support, Vivox ha... by adw on Wednesday May 01, 2019 @01:24PM (#19799437)
It was, in most significant ways, proto-MacOS.
Re:After suggesting a developer drop Linux support, Vivox ha... by newnewpdro on Wednesday May 01, 2019 @01:11PM (#19799282)
> Carmack wrote Quake on a NeXT and shipped on Windows, so if he was doing it back in the day, how wrong can it be?

This claim has mutated so grossly over the years it's comical. I clearly recall reading back in the day, probably in Dr. Dobbs Journal or Game Developer Magazine, that the NeXT Cube was largely used just for tools like the level editor, and they were generally seeking uses for the novel machine.

It was not the primary development environment. They only had one of these expensive machines after all, and the photos I saw from the era were of designer Tom Hall using it [1].

Do you really think John Carmack and Tom were sharing a computer while they hurried to create Doom?

From the caption for the NeXT Cube photo in the linked gallery showing Tom Hall, it's clearly his machine:

  This picture was taken during DOOM development in 1993.
  Tom's busy working on a map in my map editor, DoomEd,
  but don't worry - you won't be able to make out anything on
  the screen! Tom started many of the original DOOM maps and
  after he left, Sandy Petersen finished them -- some of the
  maps had very little work done to them, in fact.
 
  On Tom's monitor is a little printout that says, "Quality".
  He always has notes stuck to his monitor to keep him
  reminded of .... things. That orange thing could very well
  be the very first keyboard wrist pad -- made by a friend of
  his back before you saw them in stores. The speaker at the
  far right is one of the first Altec Lansing clamshell
  models. The microphone in front of Tom was there for
  NeXTSTEP's awesome email feature - built-in voice emails! We
  always sent them back and forth... I think I might have some
  of them lying around here...

[1] https://romero.smugmug.com/Video-Games/The-Archives/i-T8gzwx...

Edit:

It's possible they all moved onto NeXT machines after the success of Doom, but I am not aware of it. The NeXT tooling was not mature at the time and targeting x86 Windows/Dos from NeXT would have been a real nuisance. That's why it made sense for tools, since they could develop and run them on the NeXT machine.

Actually, I stand corrected, if Romero's account here is honest they appear to have done it all on NeXT. This is entirely inconsistent with what I read at the time:

https://web.archive.org/web/20070305165006/http://rome.ro/20...

Re:After suggesting a developer drop Linux support, Vivox ha... by Stratoscope on Wednesday May 01, 2019 @01:21PM (#19799407)
Mobile friendly quote:

> This picture was taken during DOOM development in 1993. Tom's busy working on a map in my map editor, DoomEd, but don't worry - you won't be able to make out anything on the screen! Tom started many of the original DOOM maps and after he left, Sandy Petersen finished them -- some of the maps had very little work done to them, in fact.

> On Tom's monitor is a little printout that says, "Quality". He always has notes stuck to his monitor to keep him reminded of .... things. That orange thing could very well be the very first keyboard wrist pad -- made by a friend of his back before you saw them in stores. The speaker at the far right is one of the first Altec Lansing clamshell models. The microphone in front of Tom was there for NeXTSTEP's awesome email feature - built-in voice emails! We always sent them back and forth... I think I might have some of them lying around here...

Re:After suggesting a developer drop Linux support, Vivox ha... by salthound on Wednesday May 01, 2019 @02:09PM (#19799946)
Kudos for looking into it, and offering a correction. If you don't trust Romero's account for some reason, you can find this corroborated by Carmack (his only answer on Quora [1]).

[1] https://www.quora.com/profile/John-Carmack

[dead]
Re:After suggesting a developer drop Linux support, Vivox ha... by CoolGuySteve on Wednesday May 01, 2019 @12:50PM (#19799008)
Here you go: https://www.gnu.org/software/libc/manual/html_node/Hooks-for...

It's not even a page of copy/paste code to make a hook do whatever you want. Writing a .so for LD_PRELOAD is similarly a handful of lines.

Or you can use the plethora of open source debugging LD_PRELOAD libraries like efence.

And in a larger sense, you should try learning more and getting better at programming instead of being so dismissive.

Re:After suggesting a developer drop Linux support, Vivox ha... by logicallee on Wednesday May 01, 2019 @01:48PM (#19799731)
Thanks for the link. I had no idea this could be considered "basic". You're right, I didn't hear about this while developing some C++ programs.

Out of curiosity, what's something you consider difficult or at the edge of your abilities while programming C++ in Linux? (Maybe something related to code generation?) You're clearly a very advanced user.

Re:After suggesting a developer drop Linux support, Vivox ha... by monocasa on Wednesday May 01, 2019 @12:41PM (#19798911)
Why are you laughing? It's pretty common in anything vaguely real-time.
Re:After suggesting a developer drop Linux support, Vivox ha... by logicallee on Wednesday May 01, 2019 @01:49PM (#19799736)
thanks, I didn't know. It didn't seem basic to me, but an advanced technique.
Re:After suggesting a developer drop Linux support, Vivox ha... by dejaime on Wednesday May 01, 2019 @01:15PM (#19799338)
Never used C++? Most cases where Cpp is a good fit will require some memory usage and allocation profiling sooner or later.