<commit_before>---
layout: post
permalink: swift-evolution-without-swift-evolution
title:  "Swift Evolution without swift-evolution"
---

An interesting few tweets from the Swift team's [Slava Pestov](https://twitter.com/slava_pestov) confirmed something I have been thinking of pretty much since Swift was open sourced.

{% twitter https://twitter.com/BasThomas/status/845737912436228104 %}

`swift-evolution` is great, but takes *a lot* of time from both the Swift Core Team and developers writing a proposal.

And, according to Slava, it has already had quite an impact during the development of Swift 3.

To me, it seems like a temporary halt to `swift-evolution` would be very welcome. This gives the Swift Core Team more time and concentration to solve issues that they would've liked to address a long time ago: ABI (!), fixing crashes, improving error messaging and compile times.

Sure, halting `swift-evolution` doesn't magically solve all the "problems", but I think it can create some focus on deferred work.

Maybe there will even be time to look into [this Discourse thing](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170206/031657.html), which would improve the swift-evolution process in the future...<commit_msg>Remove Twitter plugin<commit_after>---
layout: post
permalink: swift-evolution-without-swift-evolution
title:  "Swift Evolution without swift-evolution"
---

An [interesting few tweets](https://twitter.com/BasThomas/status/845737912436228104) from the Swift team's [Slava Pestov](https://twitter.com/slava_pestov) confirmed something I have been thinking of pretty much since Swift was open sourced.

`swift-evolution` is great, but takes *a lot* of time for the Swift Core Team - or even too much.

To me, it seems like a temporary halt to `swift-evolution` would be very welcome. This gives the Swift Core Team more time and concentration to solve issues that they would've liked to address a long time ago: ABI stability (!), fixing crashes, improving error messaging, improving compile times, paying off technical debt...

Sure, halting `swift-evolution` doesn't magically solve all these "problems", but I think it can give more room and focus on deferred work.

Maybe there will even be time to look into [this Discourse thing](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170206/031657.html), which would improve the swift-evolution process in the future...
{'fraction_non_alphanumeric': 0.07976973684210527, 'fraction_numerical': 0.026726973684210526, 'mean_word_length': 4.738207547169812, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4439556', 'n_tokens_mistral': 728, 'n_tokens_neox': 619, 'n_words': 307}