"Completely different"? All of the new values listed are practically synonyms of the former (with the exception of the "AGI focus" addition).
This article is clickbait at best
248 karma · joined May 17, 2022
This article is clickbait at best
Serotonin (the moood-regulating neurotransmitter), for instance, is produced _primarily_ in the gut (up to 95% of it). https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6469458/#:~:tex....
Over the weekend, I was finding ChatGPT giving me incorrect answers for some things too. In one case, it would try to correct itself when I asked it to, similar to the article's author. However, it kept getting it wrong and then started to repeat previous incorrect answers. I finally said "you repeated an incorrect answer from before" and then it said suddenly "Session token expired" and logged me out lol
There's a fair bit of UIKit-parity that's still missing, which forces you to create a ViewRepresentable class and do the UIKit bridging yourself (this ranges in complexity, but can definitely present significant challenge depending on the task). This becomes more frequent too for lesser used Apple platforms (watchOS and tvOS).
Another place that's lacking that the author doesn't quite dig into is that SwiftUI has no concept of cell re-use at all. The Lazy UI components (stacks, grids) will _delay_ their initialization, however, nothing actually ever gets re-used. So if you're working with a layout similar to Netflix, every time you scroll left/right/up/down, new cells are being created and are loading more image data into memory. With UIKit, cell re-use is a foundational concept that all devs should be utilizing, so it's a bit of a headscratcher that something like this is still missing from SwiftUI by now.
To top it all off, as Apple does get SwiftUI up to spec, they are completely resistant to releasing support libraries (or anything along those lines) - so rudimentary UI features/modifiers/etc. that get added years later will only ever support the latest version of iOS and forward. This makes it much more restrictive to work with, as most apps are targeting at least 1 year back and not only the latest major version of the OS.
The banana duct-taped to the wall could be considered "art by a lazy person", yet at the same time, it was actually a very authentic expression (in this case, an expression that was more along the lines of satire). The "artist" was having an internal experience that he chose to express as a banana on the wall with a piece of duct tape. The artistic expression was a social statement, a joke, a protest. And that's ok.
Within cells interlinked.
Within cells interlinked.
I don't disagree with providing feedback, but to "hate on" something is very different than providing feedback or constructive criticism. And of all things, more so art than anything else. Art is someone's personal expression. To "hate on" it is implicitly an attempt to invalidate that person's expression, if that were even possible. Are you being a judge of what someone should or shouldn't be expressing?
Per the author's "not my cup of tea" comment, I do believe that is actually a better approach. Because you are simply expressing that it's not something that you connect with/enjoy/appreciate/etc. and making your comments about yourself. When you "hate on" someone's art, you're completely missing the fact that your strong feelings are _yours_ and that the artist's expression is completely independent of that (whether others share your sentiment towards the work or not).
Given their attention to detail in design (see the rabbithole of their Human Interface Guidelines - https://developer.apple.com/design/human-interface-guideline...), I agree with the author in that this was an intentional design choice that Apple made.
Sounds a lot like a problem that NFTs could fix
In a similar, yet different, set of circumstances, what are reasonable expectations when you're an indie developer? And instead of it being an OSS Homebrew solution, it is an OSS library on GitHub that accepts sponsoring (and you've sponsored them before, simply because you get value from the library and want to show your gratitude)?
It's easy to hate on the big tech corp who doesn't pay for what they use, but what about the indie dev (and especially if they have paid)?
Within 24 hours however, I was back at the Apple Store returning it. What was the issue? Nothing wrong with the device at all - it was everything I hoped it would be! Unfortunately, the issue was with the apps instead.
Developers have gotten so used to everyone being on bigger devices. Since the Mini _lowered_ the standard size of a device (and represented such a small audience), I found that most of my apps had various UI bugs as they were written to target a regular iPhone dimension or larger. In some cases, apps were unusable due to the UI bugs.
As an iOS engineer, I can also speak to the development side of things. At the various places that I've worked, I can't say that any testing was ever specifically done on a device smaller than the smallest _regular_ iPhone (like an iPhone XS). Even our team of QAs had all kinds of devices that they'd use and we had automated UI testing, but an iPhone Mini was consistently overlooked.
Maybe the device will be better in the future, but until then, the apps just aren't ready.
Granted this is my experience with iPhones and iOS apps. Android could very well be in a different place. I expect less out of the app development on that platform, however, developers are also more attuned to targeting smaller screen sizes, given how many Android devices exist, so it could indeed be a better experience if you find a device that you like.