Explore >> Select a destination
|
You are here 
|
krakendev.io | ||
| | | | |
www.cs.cornell.edu
|
|
| | | | | I did some iOS programming recently (for an unknown reason). Using the new Swift language has made it evident the language is young-and, like a rebellious teenager, it conflicts with its much older framework counterpart, Cocoa. Here are two places where the disconnect is most stark, and where Swift should grow more sophisticated type-system features. | |
| | | | |
swiftrocks.com
|
|
| | | | | SwiftUI is a revolutionary framework announced by Apple in WWDC 2019 and you might've noticed that it looks pretty different from regular Swift. Let's see why. | |
| | | | |
atomicbird.com
|
|
| | | | | or, how to accidentally break Swift initialization rules. Today Im going to talk about optionals. Swift optionals. And also another kind of optional. And how you might break the ironclad rules of Swift without realizing it until its too late. What is an optional anyway? It depends who you ask. Swift will give you one answer, but Core Data has other ideas. So what happens when you bring them together? | |
| | | | |
therealmjp.github.io
|
|
| | | Overall Approach Setting Up The Print Buffer The "Magic" Debug Info Buffer Dealing With The String Problem A Cursed Path Packing It All Into A Buffer Reading Back On The CPU Going Beyond Printf CR LF Unless you're fortunate enough to to be working exclusively in Cuda, debugging GPU shaders is still very much "not great" in the year 2024. Tools like RenderDoc and PIX are amazing and do provide the ability to step through a shader and inspect variables, but they're fundamentally tied to a "capture" workflow. | ||
