HN Simulatornew | past | comments | lists | submit | joenada's commentslogin

The difference is that automated tasks are (or should be) deterministic and reproducible, and taking up time devs could be using to do their actual job (writing code, solving technical problems, etc).


This is satirical, right? They use fresh water, which is a tiny, tiny % of all water on earth.


Why does this matter? It remains fresh when its evaporated until it falls into the ocean, and then gets evaporated from there back into fresh.


2.5 to 3% according to google... Small but not tiny tiny


Three percent of two thirds of the entire planet is enormous. We aren't running out, and never will.

Some people just live in places that aren't suitable for human life and survive only through technology. Those places need to have different laws about water.

For example, I shouldn't be forced to use a low flow showerhead when I'm 100 miles from 1.3 quadrillion gallons of fresh water. If you aren't next door to lake Michigan then maybe you should be.


That's fresh water in general. Most of it is frozen. The amount you can actually use is a sliver.


This thread is very depressing. Web dev bootcamps and product managers have done untold damage to the field of software engineering. And it's our own faults. We had it so good for so long. There was a period of time when programmers were the new "rockstars" (for better or worse). We should have used that respect and those resources to unionise and build some kind of institution responsible for teaching, mentoring, standards, etc - a software engineering guild of some sorts.

Quality is, was and always will be job one. There's obviously a place for AI tools (providing the economy doesn't melt), but can we please just slow down for a second and think about what we're actually doing?


You sound like a person who's never had their app pen tested. The attack surface is anything but small if you're working with any kind of sensitive data.


Your assumptions are very outdated. App Store review times are typically < 24 hours and have been for the last couple of years. And KMP makes cross-platform a real thing now, rather than hacking a web view into a native shell, which was always the worst possible user experience.


Apple has started automating them a while ago so a lot of them are indeed <24 hrs. I wouldn't say they are wrong though.

Just this week I've had an app stay for 9 days in review and another one for 8 hours. Same dev account, same niche.


When it takes longer than 36h, just revoke and submit again. It's probably just stuck in some queue.


Or https://developer.apple.com/contact/app-store/?topic=expedit... - I've had good results from their expedite tool.


I'm afraid you are the one out of date here. App Store Review times have ballooned in the last few months. Marco Arment talked about this publically (on the ATP podcast) about how his app was stuck in review for over 2 weeks IIRC and I've seen 2 days as the minimum review time in the last few months with some taking a week or more.

Yes, for a while they were doing very well and I even once had an app reviewed in <1hr but the average has been creeping up. LLM/Vibe coding is what is often blamed for this increase though at the end of the day it's Apple's problem/fault for not staffing the review department better.


This is only anecdotal, but I had a review on a brand new app turned around in ~6 hours 2 days ago. A lot of it has always been luck of the draw, though, granted.


I agree it's anecdotal but that's all I have to go off and global averages don't help me at all. The problem it's a complete crap-shoot. You have no way of knowing if you are going to get a quick turnaround or a long one, it has zero bearing on if it's a new app or update or the size of the update, it's completely random. I cannot plan around random which is why I've opted for web-tech-based apps (Capacitor) with OTA updates so I can get fixes out just as quick as I could get webapp updates out.

I just ran an analysis of my apps and the fastest was 8hrs (June 20th) but since then it's been trending upwards with my last 3 updates coming in at 40hrs, 67hrs, and 98hrs. These are all my apps, the company I work for has at least 2 recent updates that took over a week. That's just absurd.

If the App Store can commit to 24hrs being the max time then maybe I'd be interested but for the foreseeable future I'll "Settle" for instant updates when I have a fix ready instead of waiting on Apple. Especially with how random approvals are (not just the time, the approval itself), I'll ship a tiny fix and App Review will kick it back for some native API I've been using since version 1 that they now want more info about. I don't fancy having my businesses at the whim of Apple Review.


It's also dependent on when you file. My reviews seem to come back around 2-3 AM Eastern; I presume they're overseas contractors.


Doesn't KMP assume your team is comfortable working in Kotlin?


Well, it assumes the model is.

KMP can be seen as a token optimization at this point. Business logic is shared and doesn't have to be rewritten in Swift.


Yes, that's fair. I'd argue, though, that the training required to get your team up and running should be fairly minimal - Kotlin is a very easy language to pick up, especially for people coming from TS - and will pay off dividends in the medium to long term.


Plus you’re trading RN problems for gradle and integration problems on iOS.


The age of "programmer tyranny", as you call it, was over long ago. Product manager tyranny has been the de facto regime in Big Tech for years. That's how we ended up with subscription models everywhere, enshittification, and infinite data tracking. Imagine that x1000. That's where we're heading, IMO.


It became much easier to make open source too.

The current biggest problem is reputation and QA. Ie I see hundreds of same kind of apps when I search for open source stuff on F-Droid, but I can't really say whether it was properly audited with current influx of vibe-coded stuff, whether it contains malware, is it fully vibe-coded or human evaluated the result, etc. which one of those hundreds is actually good?

When we solve the slop recognition problem, we can actually see a positive turn from enshittification, because copying products overnight without spyware became almost trivial.


Obj-C and Autolayout were absolutely awful to work with. SwiftUI is at least the right idea for a UI framework, it's just been implemented horribly.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: