Open Source Software Community - it's about ethics in Code of Conducts

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Okay, but consider this. The worst news that Windows had in the recent years was Pajeets writing shit code making Windows shit and annoying. Not key Windows developers being exposed as sadistic pedophiles.

Windows may be shit, but at least it's drama free.
The absence of evidence is not the evidence of absence. Micorosoft employs how many pajeets? Do you think they're all perfect gentlemen? Just because their organization is less public doesn't mean they're morally better.
 
i would not be surprised if more of their actual development resources were being put into linux than in windows at this point
lately windows is just a dumping ground for trendy-looking electron apps and the latest cloudshit
Oh yes. Linux has been a huge priority over Windows for quite a number of years.
This shift in focus happened due to prioritizing Azure (and declaring Winows legacy and shifting all development of it to India).
Cloud today is virtually a Linux-only play. The vast vast majority of customer VMs running in cloud are running some sort of linux. The most recent info I had was that a number of years ago RHELand derivatives made up ~60-70% of all paying Azure customer workloads and other Linux the majority of the remainder. The amount of Windows VMs is in the single digit percentage.
It is like the "Linux desktop percentage but in reverse".

If Microsoft knows anything they know how to follow the money and Windows is not where the money is.
All high-value work today and all engineers at these sites today work with Linux and focus on Linux. This includes premiere campuses like Redmond.

I think WSL was a last attempt to keep Windows relevant for enterprises but if you are going to run and develop on Linux why not just run Linux. Why go the detour of using WSL? And that is why it failed to take off.

Then in the last few years AI really started to take off and 100% of all AI work on the server and training side of things is Linux. Making the Windows itself even more irrelevant in the eyes of Microsoft.
Windows still exist and will continue to exist but Microsoft is no longer putting any priority into it or making any significant investment. It has all been shifted over to India and is never coming back. All high-priority work and engineers are 100% invested in Azure and AI and that is basically 100% Linux.

EDIT: Just look at how Windows have evolved since around ~2016-2018. Virtually nothing of importance has happened aside from ads and tweaks to the desktop UI. You can se that for yourself. This is what happens when things are deprioritized. Things stagnate and innovation grinds to a halt. Don't take my words for it. Compare innovation velocity in Windows from the decade before ~2016 and the decade after.
 
Last edited:
Sure. So when client and server disagree, what happens in-game? *complexity spiral intensifies*
The client updates to what the server state it. If you rubber band around get a better computer and/or stop cheating.
 
Thank you for demonstrating precisely how the complexity spiral I'm discussing looks like. If you don't grasp how this leads to more attack surface, the brain tumor is clearly inoperable.
well if you're talking about buffer overflow shit then yeah, but in the absence of that, the server not just saying "oh ok i guess you really did headshot that guy on the other side of the map with your pistol" is less secure than it double checking everything the player ever does
in fact most of the complexity of network prediction is in the client, the latency hiding, interpolation, and lag compensation has to be put there to make the game not feel like total shit over a medium-latency connection
the server mainly just independently verifies player actions and tells clients what's happening in the world and maybe rolls back a hitbox or two if you're feeling fancy
 
Windows still exist and will continue to exist but Microsoft is no longer putting any priority into it or making any significant investment. It has all been shifted over to India and is never coming back. All high-priority work and engineers are 100% invested in Azure and AI and that is basically 100% Linux.
This is what I fear is happening.
Some old experienced devs are stuck in maintenance mode for system internals, and Office, and everyone else got shifted to Azure, Office 360, Linux, and maybe AI. Leaving userspace for jeets and newly hired webshit devs. I think this is the reason why web-tech is used in the desktop. That is, because there are no devs who understand the Win API. And newly hired web devs turned system programmers would also explain why Rust is now in the kernel. It also explain shift from Visual Studio to Visual Code. I mean, VS barely runs these days.

Anycase, Win32 will outlast Windows by decades.
 
what the actual fuck is this retarded llm smoking, isn't man 2 write for files and to make a server you need the socket functions send and recv????????
Funny that, I was doing C programming for Windows awhile back to port Linux programs over.
Windows write() comes from msvcr* DLL, but send/recv is from winsock2, so Windows is special in that regard that it can't use write() on socket handles like BSD or Linux, even if it has a BSD-like network stack, but still easily fixable with wrapped/abstract calls.
 
Anycase, Win32 will outlast Windows by decades.
linux killed the big commercial unixes back in the 90s by doing the same thing they did but better
perhaps that will be the case for most windows programs one day? everything either gets ported, put on compatibility layers, or fades into irrelevance as nobody wants to run them since they need a crippled legacy system
Windows is special
and that's only just one of the ways it's special
it is perhaps one of the most special operating systems still in existence
 
Im too much of a retard to really follow or care about the above conversation, but I'll add my two cents anyway.

Server side is better cause it punishes the lossy fag with high ping more. Shooters were much better when the lag affected the person behind it and not everybody else.
 
Last edited:
__attribute__
Don't worry, I'm not judging, I do this a lot myself. I hate how the error message is worded, it makes me think the interior of the attribute is what's cooked
how did this even compile and why didn't -Wall tell me about this what the fuck
that's it i am never touching inline assembly again
note: i probably will when i want to play around with some avx instructions but not today
 
perhaps that will be the case for most windows programs one day? everything either gets ported, put on compatibility layers, or fades into irrelevance as nobody wants to run them since they need a crippled legacy system
Compatibility layer is probably the only way to go. Maintenance required to keep your programs working over time on Linux is such a fucking pain. I want an executable I can run today and in 20 years. If I switch from Win10 to Linux, I'll probably still write programs like they're for Windows and just run them in Wine.
 
Maintenance required to keep your programs working over time on Linux is such a fucking pain.
are you certain this is the case? it might be not be quite as bad as you expect
it's mainly a problem if you add tons of libraries and shit. a program with just libc will probably work until the cpu architecture dies
I want an executable I can run today and in 20 years.
stuff like nix and guix actually do this quite well (you could make a compatibility layer that emulates a gnu/linux userspace from one specific point in time and use that forever)
also the linux userspace abi never changes so if you statically link everything it will always at least sort of work as long as all the userspace daemons stay the same too (x11 (and therefore xwayland too) hasn't changed significantly since the 80s and alsa gets emulated somehow so i wouldn't worry too hard)
personally i don't have too much trouble since c niggers love keeping their abis stable for 27 years (i don't run that many 20 year old binaries though, because they're just better freshly compiled)
I'll probably still write programs like they're for Windows and just run them in Wine.
you could also try winelib which is like reverse cygwin (i.e. a weird library that carefully adds the windows api but not the abi)
definitely try the native interfaces first however
 
how did this even compile and why didn't -Wall tell me about this what the fuck
that's it i am never touching inline assembly again
note: i probably will when i want to play around with some avx instructions but not today
I compile everything with -Wall -Wextra -Werror, I'd rather disable warnings inline on a case by case basis than have it build tbh
 
Back
Top Bottom