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?
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.
I guess I'll just have to settle with using Visual Studio Code for linux.
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.
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.
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.
https://en.wikipedia.org/wiki/Development_of_Doom#Programmin...
NeXT was BSD with a Mach kernel.
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...
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...
> 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...
Yeah, customers can be so dumb.
https://github.com/valvesoftware/steam-for-linux/issues/3671
rm -rf "$STEAMROOT/"*
Now, don't get me wrong. I have a dedicated win10 partition for gaming. I gave up that fight a long time ago.
Valve has been and is doing a lot of work to expand Linux support. I wonder where Linux gaming would be today without them.
Most common closed gaming middleware works on Linux today (Wwise, Umbra3D and so on). And that's besides open source options of course. So the above is very unprofessional view.
About 10 years has passed since I concluded that Ubuntu was more userfriendly than Windows. I had "installed"[0] Windows on someones computer and it took 4 hours to get it finished from pressing the power button the first time until bthe last nagware antivirus was gone and the computer was ready for use[1].
By comparison an Ubuntu installation at the time was 20-45 IIRC minutes depending on disk speed.
Ubuntu would the be ready to write a document, create a spreadsheet and browse the Internet, everything the typical user would wish.
There's only a few things Windows would do better at that time, most notably running Windows-only software and look familiar to Windows-only users.
[0]: or configured, it was supposed to be preinstalled so no idea why it used two hours just to get me to a login screen.
[1]: I've been a sysadmin so I'm well aware that Windows can be slipstreamed etc, but my experience here is what an end user would see.
Most of the time you're hunting through documentation to find the correct settings. It's nothing new in general, it's not some kind of exciting math that's new to you, and you're rarely actually learning how the thing works. It's mostly trying a series of things until you figure out that some strings go in a place.
I appreciate it more when I'm writing software, but largely because I can actually invest the time to really solve the problem, that it fucking stays fixed, and that people will get back hours of their life that would otherwise be spent getting frustrated and searching aimlessly.
However most people dont know how to install or configure Linux, Windows (or any other OS) on their devices.
This also happens to be the reason why Linux is not popular on the desktop; it lacks the strong relationship with the OEMs that gets an operating system pre-installed.
Just the uptick on Gaming on Linux youtube content from previously windows-centric sources would indicate demand is climbing.
So, there's a market, and it seems to be getting larger over time. What's troubling to me is that the Vivox employee seemed to think the developer just didn't know that Linux was a smaller market, or hadn't bothered to make a rational decision.
Then again, I also play things like Adventure, and the odd round of Lemmings.
Serious question, as I haven't looked... Does proton work on MacOS? In any case, planning on switching my desktop to Linux in a few months when I put together my next desktop (Yay, Zen 2).
I wonder if the increasing popularity of Proton will mean more developers will simply stop targetting or porting to Linux. Games like Tomb Raider and Hitman got proper Linux releases that run great. Will we see a drop in quality with Proton? Or will Proton simply mean that targetting Linux becomes cheaper? That is, there is still a need to perform proper QA of course, but only a minimal amount of coding (mostly fixing bugs found during QA).
A zealous Tuxist, slighted by the insolence toward their beliefs but bitterly satisfied by the backpeddling was quoted as saying,
>Basically yea, but it's nice to know they'll keep their opinions to themselves from now on.
I use Arch (Manjaro cough) btw. I practically use Linux exclusively. But stuff like this is kind of funny. We live in a strange (dark?) time with respect to the OS ecosystem. This is an artifact of it.
The main OS is a bloated, closed, insecure, arguably hostile one, while the open, free one enjoys a kind of ethereal salience (both pragmatic and ideological) in the hearts, minds, and practice of technologists. That gives the open one a political protection completely disproportionate with its tiny consumer base and economic relevance to consumer-facing capitalists (who drive the entire technology sector).
Video games being locked into Windows is a huge drag.
Their original reply makes me think of a hotel that can't accommodate a family of four so they suggest you leave the kids to the grandparents and go on vacation alone. It solves their problem, not yours.
They suggested the developer change plans. I agree it was a bit of a dick move to suggest that and I think an apology and training is in order, but... I'm surprised there's a need to "issue a statement".
I'm positive if you polled developers today Mumble would be missing critical features or performance characteristics that Teamspeak / Vivox are working on to improve while Mumble is stalled out because the money isn't there to keep up healthy maintainership in the long run.
That's a pretty short sighted point of view.
It's the same thing every time and it's getting old.
The best solution is to drop Vivox, which is kind of dated and crashes and restarts frequently.
I gave up on the linux gaming years ago, after suffering with WINE.
Why would companies pour hundreds of thousands in resources to support a platform that has almost no serious gamers?