I don't like the term "AI psychosis" because I think it's the incorrect way to describe what's happening here. I think "cognitive surrender" is a much better term. Because it's not that people are getting "crazy" due to AI, but rather that somehow these people are totally fine with having zero critical thinking and blindly trusting whatever junk the AI decides to regurgitate. A lot of my colleagues don't even have opinions of their own anymore, they are just meat proxies to whatever AI they happen to be using at the moment. Which is really purely about laziness and / or ignorance rather than a medical condition.
The problem here is that the paradigm is AI-assisted development, but a LOT of people are treating it as "AI-independent" development instead, a.k.a "just send it to the agent and blindly trust whatever comes out of it", *including* deferring all responsibility / blame to the AI itself which is absolutely ridiculous.
Realizing? Will be very happy if that is the case, but in my view all big company execs are still balls deep into the notion that you will be able to just ask it for the facebook clone and everything sucks as a result
This extension is for "pure" Swift development, not iOS development. I doubt the latter will ever officially happen. It's possible to make it work for iOS at an unofficial capacity though by hooking into the extension's LSP support. We did this at Spotify to enable iOS development in Cursor for Bazel iOS projects: https://github.com/spotify/sourcekit-bazel-bsp
This is a very welcome improvement but I should note the title is a bit clickbaity: using Swift on e.g. Cursor was always possible, it's just that after Microsoft banned forks from accessing the official VSCode marketplace last year you started having to workaround it by downloading and installing the .vsix file manually. Having the extension on the Open VSX Registry sorts this out so you can now install it via the proper way once more. Very happy this finally happened!
Problems that require deep knowledge of multiple repositories, e.g. when trying to debug issues involving dependencies. The models get confused very fast even with all code available locally, due to the size of the problem. But in my experience any kind of deep integration already messes up the models, even within a single repo.
Oh yeah I forgot to mention that, it was the first option I considered but getting it shipped to Sweden was super expensive. So it didn't make sense considering I just wanted the camera dump feature. Buying the pcb and port on the other hand only costed me about 10 bucks since I already had an Arduino laying around, and also served as some necessary soldering practice :)
When the AI companies run out of money, I predict tokens will stop being dirt cheap and such setups will become extremely expensive (even for regular software engineering to some extent). Then it's become clear how over-engineered most things we do with AI are
While true, my personal fear is that the higher-ups will overlook this fact and just assume that AI can do everything because of some cherry-pick simple examples, leading to one of those situations where a bunch of people get fired for no reason and then re-hired again after some time.
I think the "well defined prompt" is precisely what the person you responded to is alluring to. They are saying they don't get worried because AI doesn't get the job done without someone behind it that knows exactly what to prompt.
I made an account there to use my Home Assistant as a media server and it's already the second time they reported that they messed up something. I heard you can install VLC on the Apple TV and stream through that, so I'll definitely do that and skip these weird middle companies.
I think Swift Concurrency is a great idea that unfortunately wasn't executed very well. The motivation behind it is that concurrency is difficult to understand and tricky to get right, but Swift Concurrency is at times even more difficult to understand and has even more pitfalls and gotchas compared to old-school synchronization primitives. I don't know where exactly it went wrong but it does feel that they really overcomplicated this feature.
The most hilarious yet infuriating thing for me is when you point out a mistake, get a "You're absolutely right!" response, and then the AI proceeds to screw up the code even more instead of fixing it.
You can have aliases on Gmail if you use Google Workspace (for custom domains), but there's a limit and no support for wildcards. Wish they had those, because then it's very easy to find out who sold your data
Aren't credit cards nowadays basically physical private keys? IIRC transactions are one-time payloads signed specifically for that operations, so intercepting that won't help you if I'm not mistaken about how cards work nowadays.
I think you are mixing some different concepts here. It's not that this is a layer on top of Xcode/xcodebuild, it's just that Apple today happens to package everything iOS/Swift-related together with Xcode releases. So even if you couldn't care less about the Xcode IDE itself or the xcodebuild build system, you still need to have it because this is the only way for you to download / install those toolchains. Apple could provide these separately, but they just don't.
Agree on Paul Hudson being great, but not so much on the guiding around the pitfalls. One big issue with the Swift community in general in my opinion is that a lot of the community content is incredibly shallow. Most of them are fine with "there's this feature and you can do X with it, cool right?" style-content, meaning very few people actually take the time to explain what the trade-offs are / performance considerations / how things work under the hood, and IMO this took a huge negative hit in the average skill level of Swift developers.
I find Cursor (or any LLM in general) to be amazing at doing very simple and concrete tasks for me. It really saves me a lot of time.
But the keyword here is "simple and concrete". I do not understand why people expect those tools to be good at tasks that involve having years of context on something. It really makes you think that the people that say that AI will replace SWEs have never actually used any of these tools.
Paired with Home Assistant and the Hue emulator, Alexa gets a lot more useful as you become able to expose to her whatever crazy script you'd like her to toggle via voice