masterspace

Oh yeah, you simultaneously live everywhere in Canada at the same time? How much time do you spend with Canadian-Caribbean people?

Canada? The British slang at least wouldn't be that out of place here

This is basically what No Man's Sky did. When Bethesda took their crappy RPG engine and mocked up interplanetary travel using loading screens and then started writing quests and storylines, NMS focused on building a very good engine that allowed you to go from surface to air to space to interplanet / stellar while mostly ignoring the rest of gameplay and storytelling.

And not to be too hard on No Man's Sky given the resource differential, but ultimately all it is is one really rock solid system thats not quite a full game surrounded by a lot of hollow feeling stuff to kinda flesh it out on paper. Ultimately Starfield has way sharper hooks almost immediately simpy because while it has a relatively crappy engine and at time frustrating amounts of loading screens and limitations, they spent more time writing content and dialogue that makes the universe feel actually alive and rich, and polishing each individual system until it's fun.

I think The Outer Worlds is also worth comparing to as Obsidian is even farther down the same route as Bethesda imho, making a much smaller universe that feels even less free than Starfield but having even better writing and I would argue it's possibly the best game of the three though I have to withhold my judgement on Starfield until I atleast finish the main quests.

Life? The fact that time is finite? The fact that if it wasn't finite they wouldn't have to compete for it?

You take BSc’s and make them create web pages, and hey, with Chromium they can also be your desktop app devs. No need to have costly MSc’s for backend or full-stack work.

?

In this situation you never needed MSc's...

No need to have costly MSc’s for backend or full-stack work.

Lmao where are you seeing backend shops just full of MSc's writing new sorting algorithm and arguing about the BigO notation of their problem?

I've worked at Fortune 500 and MAANG companies, and the overwhelming vast majority of backend engineers that I've seen have BScs at best.

It doesn't even make logical sense in the context of your argument given that Electron is purely a frontend technology. It has no bearing on your backend costs or how many backend engineers you need if you're building your frontend natively or with Electron.

Watch The Social Dilemma on netflix, it will give a better and more compelling argument than an online article explaining it, however, I worked at facebook and I've seen the internal market research around boosting "engagement". They're all playing a zero sum game and know that they're trying to maximize your engagement at the expense of everything else that might possibly be engaging (including other apps, games, media content, and incidentally useful stuff like work and school).

Yes, it absolutely does. We have a finite limit of attention / emotional energy / etc and most of the stuff on your phone is tailor made to try and monopolize it.

Not taking enough literature and humanities is how we end up with Elon. Every little wannabe engineer who thinks they shouldn't have to take a humanities course should be smacked in the face by a physics demonstration.

Lmao, need more title bars to match macOS' 90s aesthetic?

Options:

Native app for each platform:

• Pros: native code is going to be the fastest possible to run and have the smallest dependencies
• Cons: have to write all your code 3+ times in different languages, have less time to develop new features and optimize existing code.

Progressive Web App:

• Pros: single app, write once runs anywhere, no signing keys, no lock in, can be hosted anywhere, runs on everything
• Cons: artificially limited by Apple on iOS, doesn't have access to deep operating system resources, only what's exposed through the browser, limited multithreading capabilities

React Native:

• Pros: single app, write once, runs anywhere, similar enough to React Web that a lot of developers will have an easy time learning it
• Cons: still kinda finnicky, not super easy to make it work and perform well across all platforms, you'll probably still end up having to write some native code, not actually CSS / React Web so still a bit of a learning curve coming from there

Qt:

• Pros: single app, write once, runs anywhere, low level / compiled means that it will be small and performant
• Cons: written in C++, harder to find developers for, harder to implement modern out of the box niceties that CSS gives you for free, poor devX compared to react

.NET MAUI (formerly Xamarin):

• Pros: single app, write once, runs anywhere, low level / compiled enough to be more performant than most web apps out of the box, well documented
• Cons: written in C#, easier to find devs for but not many experts in it specifically, MVVM model is not as pleasant of a devX as React, again no css

Electron:

• Pros: single app, write once, runs anywhere, has full access to operating system resources and deep multithreading if needed, can be as simple as web app in a container or as complex as something like VSCode.
• Cons: takes up more storage and ram since you're bundling chromium with your app

You ever notice how everything installs and uninstalls super cleanly and easily these days and software gets consistent regular updates?

That's because developers stopped min/maxing storage and started bundling all of an application's dependencies with it instead of trying to rely on globally installed packages and frameworks that can break or be missing or lead to dependency hell.

No one likes larger download sizes and more storage being used but the tradeoff is by and large worth it.