@airspeedswift@mastodon.social
@airspeedswift@mastodon.social avatar

airspeedswift

@airspeedswift@mastodon.social

thwart leader

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

airspeedswift, to random
@airspeedswift@mastodon.social avatar

There no bigger lie to tell yourself than “I’ll work on it on the plane”

Migueldeicaza, to random
@Migueldeicaza@mastodon.social avatar

My talk on “Swift Godot: Fixing the Multi-million dollar mistake” has been posted: https://streaming.media.ccc.de/godotcon2023/relive/57866

airspeedswift, (edited )
@airspeedswift@mastodon.social avatar

@Migueldeicaza very nice

re the reference cycle concern – the questioner sounds like they were using Swift when the main way to do async stuff was with callbacks and delegates, which force you to rely heavily on weak references in lots of places to avoid cycles. transitioning to async/await and structured concurrency makes this much better. you still need weak references occasionally, like for some data structures, but that's much more "this is the right tool for the job” kind of thing.

wikipedia, to random
@wikipedia@wikis.world avatar

On this day in 1910, a cow named Pauline arrived at the White House.

Photo via Library of Congress, text via https://en.wikipedia.org/wiki/Pauline_Wayne

airspeedswift,
@airspeedswift@mastodon.social avatar

@wikipedia @Gargron god bless Wikipedia. I thought “Last? Says who, it could happen again!” and then went to the page and saw someone fixed this just yesterday.

https://en.wikipedia.org/w/index.php?title=Pauline_Wayne&diff=prev&oldid=1183383312

airspeedswift, to random
@airspeedswift@mastodon.social avatar

Leaving my comfort zone to attend KubeCon in Chicago next week.

If you’ll be there and want to chat about Swift, let me know!

airspeedswift, to random
@airspeedswift@mastodon.social avatar

The pitch is up for extending Swift protocols and generics to work on non-copyable types.

https://forums.swift.org/t/pitch-noncopyable-generics/68180

Default behaviors are key here to preserve progressive disclosure – most operations will continue to rely on the default of copyability, with non-copyable behavior being opt-in when you want to support it.

danielpunkass, to random
@danielpunkass@mastodon.social avatar

I am so proud of myself and my society that my 15yo boy can come home and tell me nonchalantly about one of his best male friend's boyfriend. Like it's nothing. This is the future we want. Never would have flown in my childhood. And I'm sure it doesn't fly many places today.

airspeedswift,
@airspeedswift@mastodon.social avatar

@danielpunkass seriously, the kids are just so chill. We watched Office Space and their main complaint was people weren’t being nice to Milton.

airspeedswift, to random
@airspeedswift@mastodon.social avatar

The debugger team at Apple is looking for an intern to join them, to work on improving the handling debugging of optimized Swift code.

Would be a great opportunity for someone enthusiastic about learning more about how Swift is implemented, and improve the debugging experience for the community.

https://gist.github.com/adrian-prantl/488fe9c4abcb93be8ea113df2daa1b30

icanzilb, to random
@icanzilb@mastodon.social avatar

🚒 Do I know anyone on the Swift Standard Library team?

https://github.com/apple/swift/issues/69397

airspeedswift,
@airspeedswift@mastodon.social avatar

@icanzilb this is the expected behavior of SE-0213. If something is expressible by a literal, then it has an initializer that takes that literal

https://github.com/apple/swift-evolution/blob/main/proposals/0213-literal-init-via-coercion.md

airspeedswift,
@airspeedswift@mastodon.social avatar

@icanzilb good point – it’s tricky because this is a property of the language, so not something that’s necessarily appropriate to document on every protocol. But since only the language can provide literal protocols, probably that can just be handled manually on each one.

airspeedswift,
@airspeedswift@mastodon.social avatar

@ctietze to be fair, it’s really not appropriate to have an initializer that, when it takes a literal, yet does something different to what the literal initializer would do

airspeedswift,
@airspeedswift@mastodon.social avatar

@icanzilb I don’t think a diagnostic would be appropriate here. The initializer that takes an Int would still be called/needed in non-literal cases. But in the case where you supply a literal, it’s correct to call the literal initializer, which should trap on invalid input not produce nil.

airspeedswift,
@airspeedswift@mastodon.social avatar

@icanzilb exactly. If you are initializing with a literal it should be guaranteed at compile time to work or trap* so should not be failable. Whereas if you are supplying a variable at runtime failing is reasonable.

  • of course you can in theory write a literal init that relies on global runtime state or some other monstrosity but let’s ignore that :)
airspeedswift, to random
@airspeedswift@mastodon.social avatar

A seasonal question: what candy that is available globally has the worst-tasting American version?

My vote is for KitKat.

Rules: this is for things that are supposed to be the same thing in the US and globally. This isn’t related to naming i.e. smarties in the US are a different thing to in the UK. Milky Way in the US should be compared to a Mars Bar. Also “kinda the same thing” doesn’t count i.e. you can’t say Malteasers/Whoppers they’re different (otherwise that would be the runaway winner).

airspeedswift,
@airspeedswift@mastodon.social avatar

@layoutSubviews you’re not wrong but the rules are you gotta be more specific i.e. a bar of Cadbury’s (made in the US by Hersheys under license) is clearly not as good tasting but it’s not that bad. Regular Hershey’s is of course trash but only sold in the US for obvious reasons.

airspeedswift,
@airspeedswift@mastodon.social avatar

@layoutSubviews I should source some European Lindt and do a blind tasting, I don’t know it well enough to know when I try the US bars whether they are crap

dimillian, to random
@dimillian@mastodon.social avatar

So, are we bashing Marc Andreessen's techno-optimist manifesto here? This has been my belief for a while now.

I'll never buy whatever is the opposite of growth.

airspeedswift,
@airspeedswift@mastodon.social avatar

@dimillian Andreessen can be a clown and degrowth can be misguided BS. They aren’t mutually exclusive.

airspeedswift, to random
@airspeedswift@mastodon.social avatar

Oil of EULA

airspeedswift,
@airspeedswift@mastodon.social avatar

I should take the time to workshop that into a proper pun toot but I’ve got a lot on rn

kyleve, to random
@kyleve@mastodon.online avatar

Corporate compliance trainings be like “You have accidentally clicked on a phishing link which installed ransomware on your computer. Do you:"

A) Stop using your computer and tell IT
B) Pay the ransom
C) Throw your computer into the ocean
D) Quit and never speak of this again

airspeedswift,
@airspeedswift@mastodon.social avatar

@kyleve “pick the one that sounds the most exhausting” always served me well

airspeedswift,
@airspeedswift@mastodon.social avatar

@kyleve @layoutSubviews AML training be like “you know those other trainings you half assed? do that with this you goin to jail”

course, Trump thinks the FCPA is just a very unfair rule imposed by the deep state so at least we won’t have to do any of this for much longer

airspeedswift, to random
@airspeedswift@mastodon.social avatar

There's this increasing tendency to talk about memory safety as if, because it's the most pressing problem right now, solving it means you've won the battle. But that's not the end goal… it's the start. Literally the least you can do.

airspeedswift,
@airspeedswift@mastodon.social avatar

Percentages add up to 100. As segfaults and exploits due to buffer overruns or use-after-frees decrease, the proportion of bugs that come down to logic errors will increase.

If the way you achieved memory safety (or performance) means your code is so ceremony-heavy that it starts to impact correctness, because you can't so easily see what it is actually trying to do, this is unfortunate.

Think about this now, not once we get there.

harshil, to random
@harshil@mastodon.social avatar

Need this in SwiftUI https://mastodon.guerilla.studio/@tixie/111215467470196154

airspeedswift,
@airspeedswift@mastodon.social avatar

@jpsim @harshil

I’m duping
the radar
that you left
in the feedback

in which
you asked
for text
to be wrapped

Forgive me
it was more readable
so visually appealing
for headlines

airspeedswift, to random
@airspeedswift@mastodon.social avatar

The boy wanted to know what a SCART cable looked like. I checked my box of emotional support cables and was sorry to discover it doesn’t contain one.

He said a picture would do but it really won’t. You have to hold one, to try twisting it and feel the resistance and hear the crinkling of the inner wires, to stare at the giant plug and poke its sharp connector teeth, to truly understand it.

airspeedswift,
@airspeedswift@mastodon.social avatar

@heathborders

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