If I’m a company and want to bring something to production quickly, what should i choose:
A relatively new tool that has seen barely any production use and thus could have a bunch of unanticipated problems. Also nobody uses it so every new engineer you bring onto the project has to learn something entirely new before they can start really contributing. You also have no idea how long it will be supported by its developers into the long term future.
A battle hardened, production tested tool that has a huge community, has been around for a long time, and that a lot more developers already know how to use.
Sure #2 might be slower by a few fractions of a second, but if I’m in charge of the business i know which option I’m going to choose 100% of the time.
Look, I’m not a fan of early adoption either… but Tauri is not a one-person project that appeared yesterday. It’s been around for a while now and has important industry endorsements.
Also, every company should have an objective and rigorous set of technical requirements for the frameworks they use. If Tauri passes those there’s no reason not to use it.
As much as technologists like us wish we could prioritize efficiency and use the latest and flashiest tools all the time, that’s just not practical. When you say you want each company to have an objective set of technical requirements when choosing a toolset, you also have to have a set of practical requirements. What is the cost of friction of adding a new tech stack to the company?
Adding electron means just learning electron. Adding Tauri means learning Tauri and Rust.
It’s like the saying goes, “the best camera is the one you have with you”. It’s true with any business decision.
You have to upgrade sometime, you can’t stick to the “good old thing” forever.
That’s the kind of thinking that makes a business miss the boat by a decade or two until they’re no longer competitive and the cost of refurbishing has become so ridiculous that they’re forced to liquidate and sell whatever’s left of value (mostly customers and assets).
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
If I’m a company and want to bring something to production quickly, what should i choose:
A relatively new tool that has seen barely any production use and thus could have a bunch of unanticipated problems. Also nobody uses it so every new engineer you bring onto the project has to learn something entirely new before they can start really contributing. You also have no idea how long it will be supported by its developers into the long term future.
A battle hardened, production tested tool that has a huge community, has been around for a long time, and that a lot more developers already know how to use.
Sure #2 might be slower by a few fractions of a second, but if I’m in charge of the business i know which option I’m going to choose 100% of the time.
Look, I’m not a fan of early adoption either… but Tauri is not a one-person project that appeared yesterday. It’s been around for a while now and has important industry endorsements.
Also, every company should have an objective and rigorous set of technical requirements for the frameworks they use. If Tauri passes those there’s no reason not to use it.
As much as technologists like us wish we could prioritize efficiency and use the latest and flashiest tools all the time, that’s just not practical. When you say you want each company to have an objective set of technical requirements when choosing a toolset, you also have to have a set of practical requirements. What is the cost of friction of adding a new tech stack to the company?
Adding electron means just learning electron. Adding Tauri means learning Tauri and Rust.
It’s like the saying goes, “the best camera is the one you have with you”. It’s true with any business decision.
You have to upgrade sometime, you can’t stick to the “good old thing” forever.
That’s the kind of thinking that makes a business miss the boat by a decade or two until they’re no longer competitive and the cost of refurbishing has become so ridiculous that they’re forced to liquidate and sell whatever’s left of value (mostly customers and assets).