

Friends don’t let friends buy ASUS unless the purchasing friend enjoys months of customer support or RMA nightmare.
Friends don’t let friends buy ASUS unless the purchasing friend enjoys months of customer support or RMA nightmare.
Dead Space (2008) ADS Cannon Puzzle. Epitome of game making. Guarantees 5 hours of your time whether you like it or not.
You know what an even better take is? “We hear you, we’ll take your feedback” or just as good, say nothing at all.
Arguing that you are smarter or wiser than your users / customers is paradoxical. You are by definition not smart if you attempt to do this.
Looks like Bethesda discovered ChatGPT.
Some of those replies are as bland, hunky-dory and sanitized as can be, with a dash of “you’re playing it wrong”.
First Nic Cage, then Chalamet? Death Stranding 2 cast is going to be stacked.
Baldur’s Gate because it’s not a “mainstream” big-name-company AAA release.
Bro why you sleeping on Alan Wake
wdym, pretty easy through Heroic Launcher. I have GoG, Epic and Amazon Games working great on it.
having to spend any money on game isn’t a good thing.
Can you explain? How do you expect devs to make a living? Getting rid of microtransactions I can understand, but not paying for games at all seems overboard.
It’s a fun game, but completely missed the tone of the first two games. If you consider it a shooter with Dead Space mechanics and gameplay then it’s just a lot of fun, not a serious Dead Space game.
make it available to anyone
To do what?
Both are good games. I would even argue that 2 is better than the original.
AI can be a great tool if used properly to enhance human work but companies seem hell-bent to instead have just AI do all the work, cutting human beings out completely and “saving costs”. Recipe for disaster.
He said “would you kindly play BioShock”?
Matthew Perry was Benny from FO: New Vegas
What happened to writing the “core” of an app that doesn’t rely on UI then simply writing the front ends for each platform you want to support?
What do you mean? I can’t speak for Slack but I’m sure some degree of business logic / client side logic separation exists.
By the way, what you just described is the essence of cross-platform development, rather than an argument for building apps natively.
simply writing the front ends for each platform you want to support?
But why would you rewrite the “front-end” for each platform if you have one you could just port over? Who is going to pay for those 2x developers and what would be the ROI on this effort?
That’s just three (if you don’t write for a million desktops on Linux).
Is it really so hard to support just three environments with only the UI being tailored for the OS it’s running on?
In Slack’s case I’d wager the answer to be a resounding YES. I don’t think you fully grasp the full scope Slack’s capabilities, and the amount of work involved to build native clients for not just one or two, but three different platforms - it’s definitely not just the “UI”.
Honestly, it just feels like poor tooling and a poor excuse.
Quite the opposite - frameworks like Electron let’s devs with your skillset build with the stack you already know, and abstracts away quite a bit of the cross-platform complexities, which strangely enough is what you are suggesting but also what you are arguing against
I prefer to call them FOSSholes.
It has all this support for native platforms yet it’s always a clunky memory hog
Maybe so but it has improved a lot over time. The app devs share some responsibility too so it’s not all on Electron.
zero effort to respect the design language of the OS it’s running on.
That’s the Dev’s design choice, not a limitation of Electron.
I’m on macOS, I want the app to be a native macOS app. If I wanted it to look like a webpage, or Windows, or Linux GTK then I’d switch to one of those and expect it to match those paradigms.
I don’t disagree but at the end of the day it doesn’t matter to enough people for it to become an issue. People are used to Slack and the way it works.
Moreover the cost of building the same app 2x or 3x simply doesn’t make business sense.
Flutter came to market much later. It wasn’t even a thing when Slack started building using Electron. I’m sure the same applies to Tauri as well.
It’s a business decision they made to go with Unity, there are risks that came along with it and they are dealing with it.
I’m sure FOSS options were considered at one point but it’s not really surprising that game devs are generally in the business of making games, and not in the business of spending money and resources to bootstrap FOSS tools or to please the community.
Not going to disagree with the tough world out there, I’m just going to suggest / ask a few things that are at least somewhat in your realm of control that might help.