I think it's atypical but natural. Statistically speaking there is just going to be some asexual people in the population, so you are what you are. The more important question is if you are okay with it and are you happy? Do you want more?
habanhero
joined 1 year ago
According to the other comments on this post, it definitely does not seem like Godot is ready for prime time.
What do they say about "waiting for Godot" again?
Wow, what a long and meta meme it would be if the engine is simply created to never be ready on purpose, hence waiting for Godot.
The business is about making good games and making money. If Godot can actually support that don't you think devs would've switched to it in droves?
Since it's FOSS I would assume it's got no crazy financial legalese to bleed the devs dry. So it stands to reason that the Godot product is simply not ready. Devs are not stupid, if there is a tech that is better and free they'd switch to it in a heartbeat, or at least put it on the table for the next game.
The fact that they haven't done so says things about Godot itself.
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
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 not the ONLY conversation topic.
Because X gon' give it to ya and I do not consent.
It makes sense, people connect through shared experiences, and TV is an easy way to do that.
TV shows are just an easy conversational topic... that's all it is.
Karen. You know