Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/schwa/statuses/114382148327614502">Jonathan Wight (schwa@mastodon.social)'s status on Wednesday, 23-Apr-2025 00:38:59 JST</a><a href="https://mastodon.social/@schwa" title="schwa@mastodon.social"><img src="https://gnusocial.jp/avatar/14975-48-20221031025923.webp" width="48" height="48" alt="Jonathan Wight" style="position: absolute; left: 0; top: 0;">Jonathan Wight</a></section><article><p>Reminder that just because you can it doesn’t mean you should.</p><p> “Config as code” is a bug not a feature.</p><p>Config should be easy to reason with and understand. Being forced to run the code to understand what the configuration is, is a huge failure.</p><p>Package.swift should have been something like TOML (or whatever) with a suitably expressive schema instead…<br><a href="https://chaos.social/@ole/114381265023437618" rel="nofollow">https://chaos.social/@ole/114381265023437618</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4934433#notice-9667818">In conversation</a><time datetime="2025-04-23T00:38:59+09:00" title="Wednesday, 23-Apr-2025 00:38:59 JST">about 2 months ago</time> <span>from <span><a href="https://mastodon.social/@schwa/114382148327614502" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@schwa/114382148327614502">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: assets.chaos.social</div><h5><a href="https://chaos.social/@ole/114381265023437618">Ole Begemann (@ole@chaos.social)</a></h5><div> from <span>Ole Begemann</span></div></header><div>Attached: 1 imageReminder that SwiftPM package manifests are Swift code, so you can write loops etc. in them. I use this in some of my packages to enable the same upcoming language features for all targets. Example: https://gist.github.com/ole/c0f4de915a483edb5e6df5f1ad677fb5This isn’t particularly useful for complex projects where you might want to migrate to Swift 6 mode module-by-module, but for small and simple packages it’s usually easy to stay on the cutting edge of Swift. #SwiftLang</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Jonathan Wight (schwa@mastodon.social)'s status on Wednesday, 23-Apr-2025 00:38:59 JST Jonathan Wight
Reminder that just because you can it doesn’t mean you should.
“Config as code” is a bug not a feature.
Config should be easy to reason with and understand. Being forced to run the code to understand what the configuration is, is a huge failure.
Package.swift should have been something like TOML (or whatever) with a suitably expressive schema instead…
https://chaos.social/@ole/114381265023437618
In conversationabout 2 months ago from mastodon.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: assets.chaos.social
  Ole Begemann (@ole@chaos.social)
  from Ole Begemann
  Attached: 1 image Reminder that SwiftPM package manifests are Swift code, so you can write loops etc. in them. I use this in some of my packages to enable the same upcoming language features for all targets. Example: https://gist.github.com/ole/c0f4de915a483edb5e6df5f1ad677fb5 This isn’t particularly useful for complex projects where you might want to migrate to Swift 6 mode module-by-module, but for small and simple packages it’s usually easy to stay on the cutting edge of Swift. #SwiftLang

Public

Embed Notice

HTML Code

Corresponding Notice