#objc — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #objc, aggregated by home.social.
-
This extract from AI Morning Live demonstrates the "centaur effect": we aren't outsourcing our understanding of our work to the LLM, we're using it to enrich our own knowledge and experience and to create a better outcome.
The _Stop and Plan_ pattern is part of the Chiron Codex patterns catalog for AI-augmented software engineering. Find more information, and join a community of software centaurs, over at the Patreon: https://patreon.com/chironcodex
-
This extract from AI Morning Live demonstrates the "centaur effect": we aren't outsourcing our understanding of our work to the LLM, we're using it to enrich our own knowledge and experience and to create a better outcome.
The _Stop and Plan_ pattern is part of the Chiron Codex patterns catalog for AI-augmented software engineering. Find more information, and join a community of software centaurs, over at the Patreon: https://patreon.com/chironcodex
-
This extract from AI Morning Live demonstrates the "centaur effect": we aren't outsourcing our understanding of our work to the LLM, we're using it to enrich our own knowledge and experience and to create a better outcome.
The _Stop and Plan_ pattern is part of the Chiron Codex patterns catalog for AI-augmented software engineering. Find more information, and join a community of software centaurs, over at the Patreon: https://patreon.com/chironcodex
-
This extract from AI Morning Live demonstrates the "centaur effect": we aren't outsourcing our understanding of our work to the LLM, we're using it to enrich our own knowledge and experience and to create a better outcome.
The _Stop and Plan_ pattern is part of the Chiron Codex patterns catalog for AI-augmented software engineering. Find more information, and join a community of software centaurs, over at the Patreon: https://patreon.com/chironcodex
-
This extract from AI Morning Live demonstrates the "centaur effect": we aren't outsourcing our understanding of our work to the LLM, we're using it to enrich our own knowledge and experience and to create a better outcome.
The _Stop and Plan_ pattern is part of the Chiron Codex patterns catalog for AI-augmented software engineering. Find more information, and join a community of software centaurs, over at the Patreon: https://patreon.com/chironcodex
-
I recently saw someone post, I think here that they were working on an #ObjC #ObjectiveC #Mastodon Mac client as a side project. Any pointers as to who that was?
-
I recently saw someone post, I think here that they were working on an #ObjC #ObjectiveC #Mastodon Mac client as a side project. Any pointers as to who that was?
-
I recently saw someone post, I think here that they were working on an #ObjC #ObjectiveC #Mastodon Mac client as a side project. Any pointers as to who that was?
-
I recently saw someone post, I think here that they were working on an #ObjC #ObjectiveC #Mastodon Mac client as a side project. Any pointers as to who that was?
-
I recently saw someone post, I think here that they were working on an #ObjC #ObjectiveC #Mastodon Mac client as a side project. Any pointers as to who that was?
-
I'm happy the old vibes of the internet are still alive: https://fuckingblocksyntax.com #objc
-
I'm happy the old vibes of the internet are still alive: https://fuckingblocksyntax.com #objc
-
I'm happy the old vibes of the internet are still alive: https://fuckingblocksyntax.com #objc
-
I'm happy the old vibes of the internet are still alive: https://fuckingblocksyntax.com #objc
-
The old dude was famously verbose, but this is getting a bit much:
[self.imageView addSymbolEffect:[NSSymbolRotateEffect effect] options:[NSSymbolEffectOptions optionsWithRepeatBehavior:[NSSymbolEffectOptionsRepeatBehavior behaviorPeriodicWithCount:1]]];
-
The old dude was famously verbose, but this is getting a bit much:
[self.imageView addSymbolEffect:[NSSymbolRotateEffect effect] options:[NSSymbolEffectOptions optionsWithRepeatBehavior:[NSSymbolEffectOptionsRepeatBehavior behaviorPeriodicWithCount:1]]];
-
The old dude was famously verbose, but this is getting a bit much:
[self.imageView addSymbolEffect:[NSSymbolRotateEffect effect] options:[NSSymbolEffectOptions optionsWithRepeatBehavior:[NSSymbolEffectOptionsRepeatBehavior behaviorPeriodicWithCount:1]]];
-
The old dude was famously verbose, but this is getting a bit much:
[self.imageView addSymbolEffect:[NSSymbolRotateEffect effect] options:[NSSymbolEffectOptions optionsWithRepeatBehavior:[NSSymbolEffectOptionsRepeatBehavior behaviorPeriodicWithCount:1]]];
-
The old dude was famously verbose, but this is getting a bit much:
[self.imageView addSymbolEffect:[NSSymbolRotateEffect effect] options:[NSSymbolEffectOptions optionsWithRepeatBehavior:[NSSymbolEffectOptionsRepeatBehavior behaviorPeriodicWithCount:1]]];
-
back in my early industry days when i was porting the adventure game studio (AGS) engine and games to mac/ios, i developed a healthy hatred of Objective-C which was used as interface glue between the engine code and macOS/ios
i had been working with C/C++ for a long time, and had made the mistake of assuming all programming syntax was essentially C-like in structure
suddenly having to deal with obj-c syntax was like stepping into an alien spaceship:
@interface ClassName : SuperclassName {
// instance variables
}
+ classMethod1;
(param1_type)param1_varName;- (return_type)instanceMethod1With1Parameter:(param1_type)param1_varName;
@endi could sort of grok out what i needed to do by changing a few variables and ctrl-c ctrl-v the methods i needed, but the overall experience was so difficult that i was glad when i never had to touch it again
over a decade later, i am *so* impressed by what obj-C was attempting. after doing a lot of NeXTStep reading, i finally understand what it was trying to do: add smalltalk-80 message-passing and object orientedness to C. the changes to the syntax (like using the + and - to indicate class vs. instance methods) are actually pretty cool!
sad that i dismissed something so fascinating in the early days just because i was more worried about getting a project done on time than actually learning how it worked
-
back in my early industry days when i was porting the adventure game studio (AGS) engine and games to mac/ios, i developed a healthy hatred of Objective-C which was used as interface glue between the engine code and macOS/ios
i had been working with C/C++ for a long time, and had made the mistake of assuming all programming syntax was essentially C-like in structure
suddenly having to deal with obj-c syntax was like stepping into an alien spaceship:
@interface ClassName : SuperclassName {
// instance variables
}
+ classMethod1;
(param1_type)param1_varName;- (return_type)instanceMethod1With1Parameter:(param1_type)param1_varName;
@endi could sort of grok out what i needed to do by changing a few variables and ctrl-c ctrl-v the methods i needed, but the overall experience was so difficult that i was glad when i never had to touch it again
over a decade later, i am *so* impressed by what obj-C was attempting. after doing a lot of NeXTStep reading, i finally understand what it was trying to do: add smalltalk-80 message-passing and object orientedness to C. the changes to the syntax (like using the + and - to indicate class vs. instance methods) are actually pretty cool!
sad that i dismissed something so fascinating in the early days just because i was more worried about getting a project done on time than actually learning how it worked
-
back in my early industry days when i was porting the adventure game studio (AGS) engine and games to mac/ios, i developed a healthy hatred of Objective-C which was used as interface glue between the engine code and macOS/ios
i had been working with C/C++ for a long time, and had made the mistake of assuming all programming syntax was essentially C-like in structure
suddenly having to deal with obj-c syntax was like stepping into an alien spaceship:
@interface ClassName : SuperclassName {
// instance variables
}
+ classMethod1;
(param1_type)param1_varName;- (return_type)instanceMethod1With1Parameter:(param1_type)param1_varName;
@endi could sort of grok out what i needed to do by changing a few variables and ctrl-c ctrl-v the methods i needed, but the overall experience was so difficult that i was glad when i never had to touch it again
over a decade later, i am *so* impressed by what obj-C was attempting. after doing a lot of NeXTStep reading, i finally understand what it was trying to do: add smalltalk-80 message-passing and object orientedness to C. the changes to the syntax (like using the + and - to indicate class vs. instance methods) are actually pretty cool!
sad that i dismissed something so fascinating in the early days just because i was more worried about getting a project done on time than actually learning how it worked
-
back in my early industry days when i was porting the adventure game studio (AGS) engine and games to mac/ios, i developed a healthy hatred of Objective-C which was used as interface glue between the engine code and macOS/ios
i had been working with C/C++ for a long time, and had made the mistake of assuming all programming syntax was essentially C-like in structure
suddenly having to deal with obj-c syntax was like stepping into an alien spaceship:
@interface ClassName : SuperclassName {
// instance variables
}
+ classMethod1;
(param1_type)param1_varName;- (return_type)instanceMethod1With1Parameter:(param1_type)param1_varName;
@endi could sort of grok out what i needed to do by changing a few variables and ctrl-c ctrl-v the methods i needed, but the overall experience was so difficult that i was glad when i never had to touch it again
over a decade later, i am *so* impressed by what obj-C was attempting. after doing a lot of NeXTStep reading, i finally understand what it was trying to do: add smalltalk-80 message-passing and object orientedness to C. the changes to the syntax (like using the + and - to indicate class vs. instance methods) are actually pretty cool!
sad that i dismissed something so fascinating in the early days just because i was more worried about getting a project done on time than actually learning how it worked
-
back in my early industry days when i was porting the adventure game studio (AGS) engine and games to mac/ios, i developed a healthy hatred of Objective-C which was used as interface glue between the engine code and macOS/ios
i had been working with C/C++ for a long time, and had made the mistake of assuming all programming syntax was essentially C-like in structure
suddenly having to deal with obj-c syntax was like stepping into an alien spaceship:
@interface ClassName : SuperclassName {
// instance variables
}
+ classMethod1;
(param1_type)param1_varName;- (return_type)instanceMethod1With1Parameter:(param1_type)param1_varName;
@endi could sort of grok out what i needed to do by changing a few variables and ctrl-c ctrl-v the methods i needed, but the overall experience was so difficult that i was glad when i never had to touch it again
over a decade later, i am *so* impressed by what obj-C was attempting. after doing a lot of NeXTStep reading, i finally understand what it was trying to do: add smalltalk-80 message-passing and object orientedness to C. the changes to the syntax (like using the + and - to indicate class vs. instance methods) are actually pretty cool!
sad that i dismissed something so fascinating in the early days just because i was more worried about getting a project done on time than actually learning how it worked
-
@sgharms Apple still develops #macOS more than #GNUstep ever evolved. Problem is I don't like the direction it's going. I don't want a network request for every app that I open.
But GNUstep won't help. It's just a POC, not able to deliver meaningful software anymore.
In case you want to develop #ObjC on living systems, try @objfw on literally any OS out there. In case you want a system where ObjC really is used to develop current applications, try #MorphOS. -
@sgharms Apple still develops #macOS more than #GNUstep ever evolved. Problem is I don't like the direction it's going. I don't want a network request for every app that I open.
But GNUstep won't help. It's just a POC, not able to deliver meaningful software anymore.
In case you want to develop #ObjC on living systems, try @objfw on literally any OS out there. In case you want a system where ObjC really is used to develop current applications, try #MorphOS. -
@sgharms Apple still develops #macOS more than #GNUstep ever evolved. Problem is I don't like the direction it's going. I don't want a network request for every app that I open.
But GNUstep won't help. It's just a POC, not able to deliver meaningful software anymore.
In case you want to develop #ObjC on living systems, try @objfw on literally any OS out there. In case you want a system where ObjC really is used to develop current applications, try #MorphOS. -
@sgharms Apple still develops #macOS more than #GNUstep ever evolved. Problem is I don't like the direction it's going. I don't want a network request for every app that I open.
But GNUstep won't help. It's just a POC, not able to deliver meaningful software anymore.
In case you want to develop #ObjC on living systems, try @objfw on literally any OS out there. In case you want a system where ObjC really is used to develop current applications, try #MorphOS. -
@sgharms Apple still develops #macOS more than #GNUstep ever evolved. Problem is I don't like the direction it's going. I don't want a network request for every app that I open.
But GNUstep won't help. It's just a POC, not able to deliver meaningful software anymore.
In case you want to develop #ObjC on living systems, try @objfw on literally any OS out there. In case you want a system where ObjC really is used to develop current applications, try #MorphOS. -
:mac: 🤘🏻🔻
#Metal :metal: + #glfw with #cpp code only.
Had to avoid #objc because my custom build system can't deal with that yet (and I didn't feel like changing that).What a pain to get it to compile.
BUT
It's using the exact same shader as my #Vulkan :vulkan: #HelloTriangle thanks to #Slang ❤️
AND
```
$ wc -l src/main.cpp src/shaders/hello_triangle.slang
134 src/main.cpp
40 src/shaders/hello_triangle.slang
164 total
``` -
:mac: 🤘🏻🔻
#Metal :metal: + #glfw with #cpp code only.
Had to avoid #objc because my custom build system can't deal with that yet (and I didn't feel like changing that).What a pain to get it to compile.
BUT
It's using the exact same shader as my #Vulkan :vulkan: #HelloTriangle thanks to #Slang ❤️
AND
```
$ wc -l src/main.cpp src/shaders/hello_triangle.slang
134 src/main.cpp
40 src/shaders/hello_triangle.slang
164 total
``` -
🧹 DYSNI — Do Ya Still Need It?
We deleted >800 lines of old Objective-C by asking one simple question: Do Ya Still Need It?
Simpler code. Less confusion. More clarity.
👉 https://paul-samuels.com/blog/2025/10/29/do-ya-still-need-it/
-
🧹 DYSNI — Do Ya Still Need It?
We deleted >800 lines of old Objective-C by asking one simple question: Do Ya Still Need It?
Simpler code. Less confusion. More clarity.
👉 https://paul-samuels.com/blog/2025/10/29/do-ya-still-need-it/
-
🧹 DYSNI — Do Ya Still Need It?
We deleted >800 lines of old Objective-C by asking one simple question: Do Ya Still Need It?
Simpler code. Less confusion. More clarity.
👉 https://paul-samuels.com/blog/2025/10/29/do-ya-still-need-it/
-
(At a later point I'm going to generate #ObjC bindings for #libpurple 3 using #ObjGTK and then use #ObjFW to integrate libpurple into #Adium. But I never said that, because probably it will never happen.)
-
(At a later point I'm going to generate #ObjC bindings for #libpurple 3 using #ObjGTK and then use #ObjFW to integrate libpurple into #Adium. But I never said that, because probably it will never happen.)
-
(At a later point I'm going to generate #ObjC bindings for #libpurple 3 using #ObjGTK and then use #ObjFW to integrate libpurple into #Adium. But I never said that, because probably it will never happen.)
-
(At a later point I'm going to generate #ObjC bindings for #libpurple 3 using #ObjGTK and then use #ObjFW to integrate libpurple into #Adium. But I never said that, because probably it will never happen.)
-
(At a later point I'm going to generate #ObjC bindings for #libpurple 3 using #ObjGTK and then use #ObjFW to integrate libpurple into #Adium. But I never said that, because probably it will never happen.)
-
Ok, as gorgeous as #Mavericks is, but the list of Software I need to backport becomes longer. Maybe it's easier to bite the bullet and update to 10.14. It's not as beautiful, but at least I wouldn't need to backport software written in #ObjC and 32 bit application still work. 😉
-
Ok, as gorgeous as #Mavericks is, but the list of Software I need to backport becomes longer. Maybe it's easier to bite the bullet and update to 10.14. It's not as beautiful, but at least I wouldn't need to backport software written in #ObjC and 32 bit application still work. 😉
-
Ok, as gorgeous as #Mavericks is, but the list of Software I need to backport becomes longer. Maybe it's easier to bite the bullet and update to 10.14. It's not as beautiful, but at least I wouldn't need to backport software written in #ObjC and 32 bit application still work. 😉
-
Ok, as gorgeous as #Mavericks is, but the list of Software I need to backport becomes longer. Maybe it's easier to bite the bullet and update to 10.14. It's not as beautiful, but at least I wouldn't need to backport software written in #ObjC and 32 bit application still work. 😉
-
Ok, as gorgeous as #Mavericks is, but the list of Software I need to backport becomes longer. Maybe it's easier to bite the bullet and update to 10.14. It's not as beautiful, but at least I wouldn't need to backport software written in #ObjC and 32 bit application still work. 😉
-
Eventually (which may be many years ahead) I'm going to have a cross-platform #ObjC app featuring both a native GTK and native Cocoa (Touch) interfaces.
