819 karma · joined September 28, 2010
Just a note, I am working for the org, that sells enterprise software shipped as container images, publishes on Docker Hub and RedHat. No issues migrating to apple/container.
M5 announcement [1] says 4x the peak GPU compute performance for AI compared to M4. I guess in the lab?
Both iPad and MBP M5 [2][3] say "delivering up to 3.5x the AI performance". But all the examples of AI (in [3]), they are 1.2-2.3X faster than M4. So where this 3.5X is coming from? What tests did Apple do to show that?
---
1. https://www.apple.com/newsroom/2025/10/apple-unleashes-m5-th...
2. https://www.apple.com/newsroom/2025/10/apple-unveils-new-14-...
3. https://www.apple.com/newsroom/2025/10/apple-introduces-the-...
Compare to macOS 15 which exactly one year ago had 50% of the market share.
Obviously, it is just a subset. But the drop from 40 to 30% is pretty significant even for that subset. (Based on https://telemetrydeck.com/platforms/swift/ - 6,280 apps use it, but that includes macOS and iOS apps)
PS. I am a macOS indie app developer, but I personally do not use TelemetryDeck and I am not in any way related to them. Just found this data being really interesting, so decided to share.
I have not tried new fenix watches. And I would assume they are the same good as Apple Watches as well. But I do like my Apple Watch Ultra (2 or 3, whatever was released this year)
I was able to develop apps for Garmin Fenix 3, which was released in 2015 https://www.garmin.com/en-US/p/160512/#specs it already supported building apps for the watch. They also had a funny name for the language they built, something like "Gorilla language" or something similar.
EDIT: found it, they call it Monkey-C https://developer.garmin.com/connect-iq/monkey-c/
Is that a lie? What about Garmin Watches?
Sure Google/Samsung/Apple Watches are not "Long battery life", because they are not "Always on e-paper screen", but I feel like Garmin Watches are.
Obviously some Garmin Watches are pretty expensive, like Fenix (I have not used it since I switched to Apple Watch), but there are ~200USD watches as well https://www.garmin.com/en-US/p/741137/ with 2 weeks battery life, custom apps, screens, and even GPS.
As for your question. This issue exists forever. If you can build something in a few hours, somebody else can too. If your idea is unique, maybe spend a bit more time to actually ship a product, not MVP.
Just to explain, their app can be written in 24 hours, maybe in 4 hours with some vibe coding. This app does not provide more information than System Information app on macOS. And we are talking about it on HN. So yes, this is clearly to bring attention to the app, and get more installs.
I am surprised this submission has not been flagged.
It does suck, A LOT
I tried to contact Atuin authors to see if I could also integrate ShellHistory with their servers, but at that time it seemed like they did not support third-party clients, and the API was not documented.
I highly recommend using tools like Atuin and ShellHistory, at this point I have 136,000 records since 2017. My shell history is the best documentation for me. If I need to do a `kubectl --raw` API call, and don't remember exactly how to write it, I just search for `kubectl raw` and get some results from the history, don't remember some advanced `git rebase`, just search the history for it.
—-
- [1] https://www.outcoldman.com/en/archive/2017/07/19/dbhist/
- [2] https://loshadki.app/shellhistory/
- [3] https://support.apple.com/en-us/108756
Edit: fixed formatting
Docker for Mac builds it in 4 minutes.
container tool... 17 minutes. Maybe even more. And I did set the cpu and memory for the builder as well to higher number than defaults (similar what Docker for Mac is set for). And in reality it is not the build stage, but "=> exporting to oci image format" that takes forever.
Running containers - have not seen any issues yet.
I was ok with the system settings redesign, could get used to it. But this whole new design is a different level of bad.
I personally have another example. Own MM B2B.
So most companies/devs will be able to just publish on App Store, and apple can after that "verify" that the app confirms with their standards.
Developing without the knowledge what LLM writes is dangerous. For me having LLM as a tool is like having a few Junior Developers around, that I can advise and work with. If I have a complicated logic that I need to write - I write it. After I wrote it, I can ask LLM to review it, it might be good to find some corner cases in some places. When I need to "move things from one bucket to another", like call API and save to DB - that is a perfect task for LLM, that I can easily review after.
At the same time, LLM is able to write pretty good complicated logic as well for my side projects. I might need to give it a few hints, but the results are amazing.