- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 29 for historia (0.09 sec)
-
docs/es/docs/history-design-future.md
# Historia, Diseño y Futuro Hace algún tiempo, <a href="https://github.com/fastapi/fastapi/issues/3#issuecomment-454956920" class="external-link" target="_blank">un usuario de **FastAPI** preguntó</a>: > ¿Cuál es la historia de este proyecto? Parece haber surgido de la nada y ser increíble en pocas semanas [...] Aquí hay un poquito de esa historia. ## Alternativas
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Dec 30 18:26:57 UTC 2024 - 4.6K bytes - Viewed (0) -
docs/es/docs/tutorial/schema-extra-example.md
### Resumen Solía decir que no me gustaba mucho la historia... y mírame ahora dando lecciones de "historia tecnológica". 😅
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Dec 30 18:26:57 UTC 2024 - 9.8K bytes - Viewed (0) -
docs/pt/docs/async.md
### Concorrência é melhor que paralelismo? Não! Essa não é a moral da história. Concorrência é diferente de paralelismo. E é melhor em cenários **específicos** que envolvam um monte de espera. Por isso, geralmente é muito melhor do que paralelismo para desenvolvimento de aplicações web. Mas não para tudo. Então, para equilibrar tudo, imagine a seguinte historinha: > Você tem que limpar uma casa grande e suja.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:56:21 UTC 2025 - 23.6K bytes - Viewed (0) -
docs/es/docs/async.md
¡No! Esa no es la moraleja de la historia. La concurrencia es diferente del paralelismo. Y es mejor en escenarios **específicos** que implican mucha espera. Debido a eso, generalmente es mucho mejor que el paralelismo para el desarrollo de aplicaciones web. Pero no para todo. Así que, para equilibrar eso, imagina la siguiente historia corta: > Tienes que limpiar una casa grande y sucia.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:56:21 UTC 2025 - 24.7K bytes - Viewed (0) -
docs/en/docs/history-design-future.md
# History, Design and Future { #history-design-and-future } Some time ago, <a href="https://github.com/fastapi/fastapi/issues/3#issuecomment-454956920" class="external-link" target="_blank">a **FastAPI** user asked</a>: > What’s the history of this project? It seems to have come from nowhere to awesome in a few weeks [...] Here's a little bit of that history. ## Alternatives { #alternatives }
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 4.2K bytes - Viewed (0) -
docs/en/docs/tutorial/schema-extra-example.md
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 9.6K bytes - Viewed (0) -
cmd/config.go
CreateTime: obj.ModTime, // ModTime is createTime for config history entries. } if withData { data, err := readConfig(ctx, objAPI, obj.Name) if err != nil { // ignore history file if not readable. continue } data, err = decryptData(data, obj.Name) if err != nil { // ignore history file that cannot be loaded. continue }
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 5.9K bytes - Viewed (0) -
compat/maven-compat/src/main/java/org/apache/maven/artifact/ArtifactScopeEnum.java
* @return true is supplied scope is an inclusive sub-scope of current one. */ public boolean encloses(ArtifactScopeEnum scope) { final ArtifactScopeEnum s = checkScope(scope); // system scope is historic only - and simple if (id == system.id) { return scope.id == system.id; } for (ArtifactScopeEnum[][] set : COMPLIANCY_SETS) { if (id == set[0][0].id) {
Registered: Sun Sep 07 03:35:12 UTC 2025 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 3.2K bytes - Viewed (0) -
docs/ko/docs/history-design-future.md
Saeye Lee <******@****.***> 1731012374 +0900
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Thu Nov 07 20:46:14 UTC 2024 - 4.4K bytes - Viewed (0) -
PULL_REQUESTS_ETIQUETTE.md
# MinIO Pull Request Guidelines These guidelines ensure high-quality commits in MinIO’s GitHub repositories, maintaining a clear, valuable commit history for our open-source projects. They apply to all contributors, fostering efficient reviews and robust code. ## Why Pull Requests? Pull Requests (PRs) drive quality in MinIO’s codebase by: - Enabling peer review without pair programming. - Documenting changes for future reference.
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Sun May 25 16:32:03 UTC 2025 - 4.7K bytes - Viewed (0)