I must have a different idea of what “deep dive” means; this is simply going through the (relatively simple) motions of implementing a builder. “Deep dive”, to me, would look at how the compiler translates statements using these builders, for example, or reverse-engineering Apple’s builders for juicy information. I’ve recently forayed into SwiftUI to see what all the fuss was. I have to say, I really feel for people…
A deep dive into Swift’s function builders
21–30 of 39 posts
Re: A deep dive into Swift’s function builders
#22I must have a different idea of what “deep dive” means; this is simply going through the (relatively simple) motions of implementing a builder. “Deep dive”, to me, would look at how the compiler translates statements using these builders, for example, or reverse-engineering Apple’s builders for juicy information. I’ve recently forayed into SwiftUI to see what all the fuss was. I have to say, I really feel for people…
Re: A deep dive into Swift’s function builders
#23I must have a different idea of what “deep dive” means; this is simply going through the (relatively simple) motions of implementing a builder. “Deep dive”, to me, would look at how the compiler translates statements using these builders, for example, or reverse-engineering Apple’s builders for juicy information. I’ve recently forayed into SwiftUI to see what all the fuss was. I have to say, I really feel for people…
Re: A deep dive into Swift’s function builders
#24I must have a different idea of what “deep dive” means; this is simply going through the (relatively simple) motions of implementing a builder. “Deep dive”, to me, would look at how the compiler translates statements using these builders, for example, or reverse-engineering Apple’s builders for juicy information. I’ve recently forayed into SwiftUI to see what all the fuss was. I have to say, I really feel for people…
Re: A deep dive into Swift’s function builders
#25I must have a different idea of what “deep dive” means; this is simply going through the (relatively simple) motions of implementing a builder. “Deep dive”, to me, would look at how the compiler translates statements using these builders, for example, or reverse-engineering Apple’s builders for juicy information. I’ve recently forayed into SwiftUI to see what all the fuss was. I have to say, I really feel for people…
And yes, I wish Apple had proper and up-to-date information on this somewhere.
Re: A deep dive into Swift’s function builders
#26I must have a different idea of what “deep dive” means; this is simply going through the (relatively simple) motions of implementing a builder. “Deep dive”, to me, would look at how the compiler translates statements using these builders, for example, or reverse-engineering Apple’s builders for juicy information. I’ve recently forayed into SwiftUI to see what all the fuss was. I have to say, I really feel for people…
Re: A deep dive into Swift’s function builders
#27I must have a different idea of what “deep dive” means; this is simply going through the (relatively simple) motions of implementing a builder. “Deep dive”, to me, would look at how the compiler translates statements using these builders, for example, or reverse-engineering Apple’s builders for juicy information. I’ve recently forayed into SwiftUI to see what all the fuss was. I have to say, I really feel for people…
And wiser.
Youth is wasted on the young. Unfortunately for the field of software development that means endless gyrations of over engineering and technobabel.
Re: A deep dive into Swift’s function builders
#28I must have a different idea of what “deep dive” means; this is simply going through the (relatively simple) motions of implementing a builder. “Deep dive”, to me, would look at how the compiler translates statements using these builders, for example, or reverse-engineering Apple’s builders for juicy information. I’ve recently forayed into SwiftUI to see what all the fuss was. I have to say, I really feel for people…
I also share this opinion. This hard-on that companies have of making coding easy for everyone will be the field's downfall. Just look how people are outraged whenever algorithm's are mentioned in interviews. I lost track of how many people with "senior" positions coming to interview at my company and showing that they know absolutely nothing about anything. My explanation for this is that you have a bunch of people from other areas coming to tech simply because it's easy money. They don't care about becoming the next legendary developer or something like that, they just wanna make easy money. The result is that everything gets dumbed down as a result. I really hate this and it probably means that a lot of important knowledge will be lost when the old dogs die.
Re: A deep dive into Swift’s function builders
#29I must have a different idea of what “deep dive” means; this is simply going through the (relatively simple) motions of implementing a builder. “Deep dive”, to me, would look at how the compiler translates statements using these builders, for example, or reverse-engineering Apple’s builders for juicy information. I’ve recently forayed into SwiftUI to see what all the fuss was. I have to say, I really feel for people…
Up until snow leopard lots of very old APIs had been kept around so actually pulling things apart was not only an interesting thing to do but even profitable (because the knowledge gained would be useful for years.) Contrast Apple's current generation of operating systems where the API churn is comparable to lots of JS frameworks. Not to mention how unfriendly the company has been to smaller developers
Re: A deep dive into Swift’s function builders
#30I must have a different idea of what “deep dive” means; this is simply going through the (relatively simple) motions of implementing a builder. “Deep dive”, to me, would look at how the compiler translates statements using these builders, for example, or reverse-engineering Apple’s builders for juicy information. I’ve recently forayed into SwiftUI to see what all the fuss was. I have to say, I really feel for people…
I don't consume his content (neither his website nor his podcast) but he sure knows his Swift. His recent code is probably some of the best Swift code I've seen and I have very high standards for that.
He creates amazing DSLs / abstractions / APIs by leveraging the type system which in my opinion is exactly what Swift should be about.