Small clean-ups to mini history in get-started #17253
Open
+4
−4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
the em-dash error in the 2022 section caught my eye, also made couple other small improvements
thomas-te
requested review from
aaazzam,
kevingrismore,
daniel-prefect and
seanpwlms
as code owners
discdiver
reviewed
Feb 24, 2025
| Prefect 3.0 also unlocked a leap forward in performance, improving the runtime overhead of Prefect by up to 90%. | ||
|
|
||
|
|
||
| ## Join our community | ||
|
|
||
| Join Prefect's vibrant [community of nearly 30,000 engineers](/contribute/index/) to learn with others and share your knowledge! | ||
| Join Prefect's vibrant [Slack community](/contribute/index/) to learn with others and share your knowledge! |
There was a problem hiding this comment.
Do you want this to link to the Slack community inviter: https://prefect.io/slack ?
| Inspired by distributed tools like Dask, and building on the experience of our founder, Jeremiah Lowin (a PMC member of Apache Airflow), we created a system based on simple Python decorators for tasks and flows. | ||
| But what made Prefect truly special was our introduction of task mapping—a feature that would later become foundational to our dynamic execution capabilities (and eventually imitated by other orchestration SDKs). | ||
|
|
||
|
|
||
| **2022:** Prefect's 2.0 release became inevitable once we recognized that real-world workflows don't always fit into neat, pre-planned DAG structures: sometimes you need to update a job definition based on runtime information, for example by skipping a branch of your workflow. | ||
| So we removed a key constraint that workflows be written explicitly as DAGs, fully embracing native Python control flow—if/else conditionals, while loops-everything that makes Python…Python. | ||
| So we removed a key constraint that workflows be written explicitly as DAGs, fully embracing native Python control flow—if/else conditionals, while loops—everything that makes Python…*Python*. |
There was a problem hiding this comment.
Suggested change
| So we removed a key constraint that workflows be written explicitly as DAGs, fully embracing native Python control flow—if/else conditionals, while loops—everything that makes Python…*Python*. | |
| So we removed a key constraint that workflows be written explicitly as DAGs, fully embracing native Python control flow—if/else conditionals, while loops—everything that makes Python…*Python*. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
the em-dash error in the 2022 section caught my eye, also made couple other small improvements.
In the raw markdown I cannot see the rendering of a normal dash vs. an em dash. Might need some help from you @discdiver