- cross-posted to:
- [email protected]
- phoronix
- [email protected]
- cross-posted to:
- [email protected]
- phoronix
- [email protected]
You must log in or register to comment.
This must be the most horrid type of programming work available.
First: You have to deal with Win32 APIs. Which, they’ve kept certain bugs because it break legacy programs.
Second: You have to deal with game programmers. Which, program things in such a way that GPU driver programmers, have to write SPECIAL drivers, so that your game is treated the way these programmers THOUGHT it was supposed to work…
It’s surprising anything works. Master Race my ass.
So many games work on Proton/Wine these days, it’s not really surprising anymore.
Nowadays you have a huge chunk of games being built on massively popular engines like Unity and Unreal, making it much easier to support/optimise for.
Another big point is that you’re not developing exclusively against DirectX. Vulkan is very popular, and both APIs are frequently supported by game engines. This introduces some “good habits”, in that it forces the devs to think about compatibility from the get go, instead of trying to come up with shady tricks to get one or two extra fps that only work in specific conditions and crash the game otherwise.
The fuck
PC master race I hope. Could be phrased better but yeah.
Yes, I’m referencing PCMR. And I think it’s a fucked up term, and gamers shouldn’t be proud of it.
Well, wasn’t it originally meant to make fun of them? Gamers ofc being dumb as bricks did not get it and adopted the term.
imho, who the fuck cares? How did we even get on this topic in the first damn place? Nobody mentioned it until the guy bitching mentioned it.
Constantly obsessing over the way things are worded is a game for crybullies who perpetually play victim so they can feel righteous about themselves. PCMR all the way.
Yeah, not sure when this trend started, but having to install a new driver to make a new game work seemed like the wrong way to go about it.
I feel this. That Valve guy talking about ‘Nvidia you’re doing lighting wrong’ because Nvidia adopted the same logarithmic formula for gamma as photography. Like holy shit I’m sorry Carmack got this wrong, but fr get your shit together Valve. Y’all didn’t just invent how the world models light.
They have the potential to take a serious bite out of Windows if it enshittifies further.
*when
I buy a license for Crossover every year to support Codeweavers. I know its not much but its what I can do to show my support for such an amazing software (talking about WINE).
It’s great to see they are hiring, but I do hope they arent being rash with these openings. Ive work my fair share of tech companies and some have a culture to open positions because of KPIs and then 6 months to a year later have a massive layoff because they were completely off with their projections so now they have to cut positions which include some of the people hired well before the hiring bananza.
i wonder what happens to the excess crossover licenses? do you feed them to the crossover failover dumpovermatron 2000… to fertilize the weeds of windows‽
When I say buy I should have said renew the same license/support. I get the idea that by supporting Crossover I’m reinforcing Windows dominace, but look at Valve with proton and the Steamdeck. Their success shows that Linux is gaming capable which can get people to try Linux that otherwise would have wrote it off.
Edit: swapped ‘capable’ and ‘gaming’
I think people who view Wine/Proton as a crutch is missing the point. Even disregarding the fact that it’s introducing more people to Linux (me included), I think the bigger point to make is that the future of software (or rather, the emerging meta of software) is cross-platform. Think about all the web apps and Electron apps. The solution to the Linux compatibility issue is not to make a Linux version of the software, it’s to set up a system such that one version works for every OS. Wine/Proton is just an unusual extension of that software philosophy.
The definition of “doing God’s work”.
Doesn’t look like they really want to pay 'em
Edit: there’s no salary listed, y’all. Don’t put up with that shit.
Damn. These kids need to wake up and stop getting ripped off. Salary range in the listing is the law in many states now and much of the world.
It’s basic self respect to expect it in the listing, and ask why it’s not there, when it’s missing.
We already know they pay 100-150k
How are we supposed to know this?
Removed by mod
My point is the fact that they aren’t willing to advertise their compensation is a red flag.
Then most companies have red flags. Not saying that shouldn’t be changed, but it is the norm at present for the majority of industries. And if it were to change, that certainly doesn’t negate an applicant’s responsibility to research the company (and honestly the industry as a whole, but that’s neither here nor there).
https://www.americanprogress.org/article/quick-facts-about-state-salary-range-transparency-laws/
It’s also a teensy bit illegal to play that explorative game.
But yeah, fuck most companies.
First sentence “… they are looking to hire multiple Wine developers to join their paid team…”.
And then proceed to list no salary.
deleted by creator
It was different before the dark times, and it’s different again. Several states, including CA, passed laws requiring salary ranges to be listed. Technically, CodeWeavers is in violation of a few state laws by advertising remote work.
Also, a $130k cap is hilariously low.
why do you say that lol the ads def seem to be for paid positions?
Is that a question?
They don’t list any pay rates.
What’s the technical diffence between CrossOver and just running Wine/Proton?
If there’s none, doesn’t it make more sense to support Wine directly?
CrossOver am pretty sure was designed to be easy and way more compatible to run Windows apps/games.
I think CrossOver is designed to have better compatibility with specific programs (MS office, adobe programs etc)
Crossover is a for profit organisation + software but their contributions to wine are open sourced/pushed upstream to the wine repo
I see, thanks!
You’re paying for someone to yell at when an update breaks your workflow, and they have to fix it instead of you.
I see the point! Thanks
