Source strings

32 Strings 100%
Browse Translate
1,541 Words 100%
9,811 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
32 1,541 9,811
All strings Browse Translate Zen
32 1,541 9,811
Read-only strings Browse Translate Zen
1 63 378
Strings with any failing checks Browse Translate Zen
1 63 378
Failing check: Ellipsis Browse Translate Zen

Summary

Project website tuist.dev
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language can not be edited.
Source code repository https://github.com/tuist/tuist
Repository branch main
Last remote commit fix(server): fix CLA workflow for fork contributions (#8149) 0888ada44
Pedro Piñera Buendía authored 11 hours ago
Last commit in Weblate Update translation files ac014321e
Weblate authored 15 hours ago
Weblate repository https://translate.tuist.dev/git/tuist/documentation-pages/
File mask docs/docs/*/guides/features/projects/cost-of-convenience.md
Monolingual base language file docs/docs/en/guides/features/projects/cost-of-convenience.md
Translation file Download docs/docs/en/guides/features/projects/cost-of-convenience.md
Last change Sept. 8, 2025, 6:09 a.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,003,224
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
20 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 32 1,541 9,811
Translated 100% 32 100% 1,541 100% 9,811
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 32 100% 1,541 100% 9,811
Failing checks 3% 1 4% 63 3% 378
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 32 changes
SepOctNovDecJanFebMarAprMayJunJulAug

Quick numbers

1,501
Hosted words
31
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
+100%
Translated
—
—
Contributors
—
User avatar None

Source string added
---
{
"title": "The cost of convenience",
"titleTemplate": ":title · Projects · Features · Guides · Tuist",
"description": "Learn about the cost of convenience in Xcode and how Tuist helps you prevent the issues that come with it."
}
---
20 hours ago
User avatar None

Resource updated
File “docs/docs/en/guides/features/projects/cost-of-convenience.md” was added. 9 days ago
User avatar None

String added in the repository
Until that happens, you have to choose whether you want to embrace the convencience of Xcode and take on the debt that comes with it, or trust us on this journey to provide a better developer experience. We won't disappoint you.
Until that happens, you have to choose whether you want to embrace the convencience of Xcode and take on the debt that comes with it, or trust us on this journey to provide a better developer experience. We won't disappoint you.
9 days ago
User avatar None

String added in the repository
Ideally, **the build system was more extensible**, but wouldn't it be a bad idea to have plugins/extensions that contract with a world of implicitness? It doesn't seem like a good idea. So it seems like we'll need external tools like Tuist or [Bazel]{1} to provide a better developer experience. Or maybe Apple will surprise us all and make Xcode more extensible and explicit...
Ideally, **the build system was more extensible**, but wouldn't it be a bad idea to have plugins/extensions that contract with a world of implicitness? It doesn't seem like a good idea. So it seems like we'll need external tools like Tuist or [Bazel]{1} to provide a better developer experience. Or maybe Apple will surprise us all and make Xcode more extensible and explicit...
9 days ago
User avatar None

String added in the repository
Because the future is unknown, we try to **be as close as possible to the industry standards and Xcode projects**. We prevent the above issues, and leverage the knowledge that we have to provide a better developer experience. Ideally we wouldn't have to resort to project generation for that, but the lack of extensibility of Xcode and the Swift Package Manager make it the only viable option. And it's also a safe option because they'll have to break the Xcode projects to break Tuist projects.
Because the future is unknown, we try to **be as close as possible to the industry standards and Xcode projects**. We prevent the above issues, and leverage the knowledge that we have to provide a better developer experience. Ideally we wouldn't have to resort to project generation for that, but the lack of extensibility of Xcode and the Swift Package Manager make it the only viable option. And it's also a safe option because they'll have to break the Xcode projects to break Tuist projects.
9 days ago
User avatar None

String added in the repository
Apple finds itself in a bit of a chicken-and-egg problem. Convenience is what helps developers get started quickly and build more apps for their ecosystem. But their decisions to make the experience convenience at that scale, is making it hard for them to ensure some of the Xcode features work reliably.
Apple finds itself in a bit of a chicken-and-egg problem. Convenience is what helps developers get started quickly and build more apps for their ecosystem. But their decisions to make the experience convenience at that scale, is making it hard for them to ensure some of the Xcode features work reliably.
9 days ago
User avatar None

String added in the repository
Whether Apple will do something to prevent all the above issues is unknown. Their continuous decisions embedded into Xcode and the Swift Package Manager don't suggest that they will. Once you allow implicit configuration as a valid state, **it's hard to move from there without introducing breaking changes.** Going back to first principles and rethinking the design of the tools might lead to breaking many Xcode projects that accidentally compiled for years. Imagine the community uproar if that happened.
Whether Apple will do something to prevent all the above issues is unknown. Their continuous decisions embedded into Xcode and the Swift Package Manager don't suggest that they will. Once you allow implicit configuration as a valid state, **it's hard to move from there without introducing breaking changes.** Going back to first principles and rethinking the design of the tools might lead to breaking many Xcode projects that accidentally compiled for years. Imagine the community uproar if that happened.
9 days ago
User avatar None

String added in the repository
Future {#future}
Future {#future}
9 days ago
User avatar None

String added in the repository
If there's an important non-written principle that we recommend every developer or organization that wants their development with Xcode to scale, is that they should embrace explicitness. And if explicitness is hard to manage with raw Xcode projects, they should consider something else, either [Tuist]{1} or [Bazel]{2}. **Only then reliability, predicability, and optimizations will be possible.**
If there's an important non-written principle that we recommend every developer or organization that wants their development with Xcode to scale, is that they should embrace explicitness. And if explicitness is hard to manage with raw Xcode projects, they should consider something else, either [Tuist]{1} or [Bazel]{2}. **Only then reliability, predicability, and optimizations will be possible.**
9 days ago
User avatar None

String added in the repository
Explicit, explicit, and explicit {#explicit-explicit-and-explicit}
Explicit, explicit, and explicit {#explicit-explicit-and-explicit}
9 days ago
Browse all translation changes