@fabianfett@chaos.social
@fabianfett@chaos.social avatar

fabianfett

@fabianfett@chaos.social

Swift on server aficionado | Berlin | he/him/his

This profile is from a federated server and may be incomplete. Browse more on the original instance.

finestructure, to random
@finestructure@mastodon.social avatar

Folks who squash their merges, I’m curious why you are making that trade-off. I’m guessing the pro argument is a cleaner merge graph?

The big argument against it for me is that you lose granularity for git bisect. I've often been able to narrow down breakage (sometimes long past the merge) due to individual commits in the merge. If I'd merged in a giant blob all I'd have had to go by is that giant blob. (1/2)

fabianfett,
@fabianfett@chaos.social avatar

@finestructure I think reverting a change out becomes simpler. Also I want to point out that squashed commits do not necessarily mean larger commits. It mostly means that you focus to get a complete feature/bugfix into one commit. That has the benefit that all the small commits in between (“ooops”, “oh god please ci”, “pr review”) are not part of the final history. This way you have a 1:1 relationship between feature and commit.

fabianfett,
@fabianfett@chaos.social avatar

@finestructure Oh you use a ton of libs that do that everyday. 😀 The swift-nio family (incl. AHC, gRPC) uses squash commit in exactly this way.

fabianfett,
@fabianfett@chaos.social avatar

@finestructure Would you mind pointing to examples where we just commited big blobs and smaller commits would improve maintainability?

fabianfett,
@fabianfett@chaos.social avatar

@dgregor79 @finestructure I get your point that: If squash isn’t expected, squash can feel weird and destroy care that you put into separate commits. However the same is true the other way as well. ☺️ I often put lots of care into my pr description but yolo my commit messages, expecting commits to be squashed in the end and the message to be taken from my pr description.

If you were aware, of the squash behavior in SwiftPM, would it have been possible to put the temp fix in a separate PR?

fabianfett, to swift
@fabianfett@chaos.social avatar

Pretty cool to see that there is an client in .

https://github.com/m-barthelemy/AcmeSwift

fabianfett, to swift
@fabianfett@chaos.social avatar

👀 Good news for observability: Yesterday we released a first Swift version 2 alpha. Please check it out and report any issues that you might encounter:

https://github.com/swift-server/swift-prometheus/releases/tag/2.0.0-alpha.1

fabianfett, to swift
@fabianfett@chaos.social avatar

🚀 This is great news for the ecosystem. code artifact is now a compatible Swift package registry. The underlying APIs are defined in SE0292, SE0321, SE0378 and SE0391.

Besides the benefit mentioned in the article, this might also make your ‘swift package resolve’ faster, as spm doesn’t need to checkout your dependencies git repo anymore and instead can just download the specified version.

https://aws.amazon.com/blogs/aws/new-add-your-swift-packages-to-aws-codeartifact/

fabianfett,
@fabianfett@chaos.social avatar

@tonyarnold @sebsto Do you know the answer to this?

fabianfett, to swift
@fabianfett@chaos.social avatar

🧑‍💻⁉️ Please make your voice heard in the Server Working Group developer survey. Please do so, even if you don‘t use today. We would love to understand your reasons.

https://forums.swift.org/t/sswg-community-survey-2023/67084

fabianfett, to swift
@fabianfett@chaos.social avatar

🚀 Very excited about today’s PostgresNIO release. It has so much stuff that brings us closer to embrace a fully structured concurrency world:

  1. async/await support for prepared statement
  2. async/await support for Postgres listen/notify
  3. no need to provide EventLoops when creating a connection

Plus a ton of bug and behavior fixes.

https://github.com/vapor/postgres-nio/releases/tag/1.18.0

fabianfett, to swift
@fabianfett@chaos.social avatar

I’m excited to help move , a client build on top of , forward.

Read about @joannis and my plans:
https://forums.swift.org/t/redistack-future-plans/65703

fabianfett, to random
@fabianfett@chaos.social avatar

: So cool to see my on server colleague, Si Beaumont, give an intro into the awesome Swift OpenAPI Generator:
https://developer.apple.com/wwdc23/10171

fabianfett, to random
@fabianfett@chaos.social avatar

If you want to understand the benefits of using structured concurrency (taskGroups and async let) over unstructured concurrency (spawning new Tasks) in I highly recommend the session: “Beyond the basics of structured concurrency”.

👩‍🍳🧄🥕🥔

https://developer.apple.com/wwdc23/10170

Important Swift server note:
AsyncHTTPClient and PostgresNIO support cancellation today.

fabianfett, to random
@fabianfett@chaos.social avatar

It's so cool to see how the new Parameter Packs will allow us to get rid of our decode() overloads in PostgresNIO.

https://github.com/vapor/postgres-nio/pull/341

simonbs, to random
@simonbs@mastodon.social avatar

Apple hosts the official documentation for their new Swift OpenAPI Generator on Swift Package Index. Cool stuff, @finestructure and @daveverwer! 🙌 https://swiftpackageindex.com/apple/swift-openapi-generator/0.1.0/documentation/swift-openapi-generator

fabianfett,
@fabianfett@chaos.social avatar

@simonbs @finestructure @daveverwer Most swift-server libraries are hosted using the SPI. Including the nio family of libraries, AsyncHTTPClient and the AWS Lambda Runtime.

fabianfett, to random
@fabianfett@chaos.social avatar

🚀🎉 Swift Distributed Tracing has reached 1.0.

Huge shoutout to @slashmo and @ktoso for shipping a great library that is an essential building block for the instrumentation story in the on server ecosystem!

I highly recommend reading the release notes, that go into more detail:

https://github.com/apple/swift-distributed-tracing/releases/tag/1.0.0

finestructure, to swift
@finestructure@mastodon.social avatar

I had a hunch that I could take on tasks that I used to do with Python + matplotlib + Jupyter with Swift Charts + SwiftUI + Playgrounds instead. But I had no idea it’d be this nice and easy. Plus I find the default result better looking and I have much more control over everything around the chart, like labels, titles etc.

This will change everything for me when working with charts.

fabianfett,
@fabianfett@chaos.social avatar

@finestructure Awesome. Of course I would prefer if you went straight from PostgresNIO to SwiftCharts. 😜

fabianfett,
@fabianfett@chaos.social avatar

@finestructure Hot standby for the win…

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • megavids
  • kavyap
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • InstantRegret
  • GTA5RPClips
  • Youngstown
  • everett
  • slotface
  • rosin
  • osvaldo12
  • mdbf
  • ngwrru68w68
  • JUstTest
  • cubers
  • modclub
  • normalnudes
  • tester
  • khanakhh
  • Durango
  • ethstaker
  • tacticalgear
  • Leos
  • provamag3
  • anitta
  • cisconetworking
  • lostlight
  • All magazines
    •