Skip to content

Copy edit and slightly tone down front page #1065

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

finagolfin
Copy link
Member

Light edit of new front page copy, some of it matter of taste.

@@ -53,11 +53,11 @@ atom: true
<section id="pillar-1" class="section pillar">
<div class="pillar-wrapper content-wrapper">
<p class="pillar-intro">
Swift is the only language that scales from embedded devices and kernels to apps and cloud infrastructure. It’s simple, and expressive, with incredible performance and safety. And it has unmatched interoperability with C and C++.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mainly got rid of "only language" because the first sentence above already establishes that it is a programming language- no need to restate it- but some people also felt "only" was an exaggeration.

@alexandersandberg
Copy link
Member

cc: @timsneath

Copy link

@Lancelotbronner Lancelotbronner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we can both sell the language and stay honest.

@finagolfin
Copy link
Member Author

@Lancelotbronner, I'd rather keep this focused on copy editing. As I noted above, I only made content changes to read better, and incidentally to tone it down in two places.

If you want to make adjustments based on toning it down in other places, I suggest you open your own pull for that, as I'd rather not expand this pull further.

@finagolfin
Copy link
Member Author

@federicobucchi, I don't know who has to sign off on these copy edits, mind reviewing?

Copy link
Contributor

@davelester davelester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contributions, @finagolfin! I left several comments -- happy to discuss further.

@@ -14,7 +14,7 @@
}

- title: Expressive
subtitle: Concise code. Powerful results.
subtitle: Concise code, powerful results.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stylistically could we leave this subtitle as-is?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My correction is how it would've been written in the past, but there has certainly been a modern trend towards this style. Up to the authors, just giving my suggestion.

@@ -39,7 +39,7 @@

- title: Safe
subtitle: Protect memory safety.
text: Swift prioritizes safety and eliminates entire classes of bugs and vulnerabilities by its design. Memory safety and data race safety are core features of the language, making them straightforward to integrate into your codebase. Safety is required at compile time, before your applications are ever run.
text: Swift prioritizes safety and eliminates entire classes of bugs and vulnerabilities by its design. Memory and data race safety are core features of the language, making them straightforward to integrate into your codebase. Safety is required at compile time, before your applications are ever run.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend we leave this as-is so we maintain "memory safety" as a keyword.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is that the word safety is used five times in the original, which is excessive. Memory safety is already in the subtitle, so I figured we could hammer it home one less in this ungrammatical way.

subtitle: Adopt in existing code incrementally.
text: Swift provides unmatched interoperability with its combination of natively understanding C and C++ types without the need for foreign function interfaces, and by providing bridging for bi-directional access. Swift’s interoperability features allow you to incrementally adopt the language into existing codebases without requiring a full code rewrite.
subtitle: Adopt Swift in existing code incrementally.
text: Swift provides unmatched interoperability, with its combination of natively understanding C and C++ types, without the need for foreign function interfaces, and providing bridging for bi-directional access. Swift’s interoperability features allow you to incrementally insert the language into existing codebases without requiring a full code rewrite.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend we stick with the original version, including "adopt" which aligns with the incremental adoption story of the language.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than the grammatical improvements, I added those two words to emphasize that this is about inserting Swift into existing C/C++ codebases, not the other way around.

</p>
<br />
<p class="pillar-intro">
It's the combination of approachability, speed, safety, and all of<br class="hide-small"/> Swift’s strengths that make it so unique.
It's the combination of approachability, speed, safety, and all of<br class="hide-small"/> Swift’s strengths that make it unique.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The so is added emphasis, but I can see how saying something is "so unique" may not land. How about we move "unique" earlier in the statement, and change unique to powerful?

I recommend this revision: "It's the unique combination of approachability, speed, safety, and all of Swift's strengths that make it so powerful.

Let me know if you'd like to incorporate the change, otherwise I'm happy to open an additional PR.

@@ -71,7 +71,7 @@

- title: Adaptable
subtitle: From microcontrollers to servers.
text: "The only language that can span from embedded and kernel, to server and apps. Swift excels no matter where it’s used: from constrained environments like firmware where every byte counts, to cloud services handling billions of requests a day."
text: "The only language that can span from embedded and kernel to server and apps. Swift excels no matter where it’s used, from constrained environments like firmware, where every byte counts, to cloud services handling billions of requests a day."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd recommend that we remove "only language" here as well. Perhaps changing it to "Swift spans from"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants