Android tooling is cross-platform and easily executed in your choice of CI provider with cheap Linux ARM minutes. Simulator-based UI tests are headless (there are headless tests for iOS but not macOS). It's not even remotely a close comparison.
No, the apple ecosystem will always hold a monopoly over stupid upper class people to fleece. Apple will say "jump" and Developers will ask how high (if they know what's good for their wallet)
It's going to be interesting to see how this plays out with their "no unapproved code" stance. The old excuse was that normal users don't know how to write code and so don't need to be able to run their own code.
But now normal users can have some AI thing write single-use code for them, and for relatively simple code like "show me all my pictures between these two dates that are in landscape rather than portrait" they'll usually get it right.
And now who wants a phone where you can't do anything like that?
You absolutely can. You just have to pay Apple their $99/yr for the privilege. I have an app I vibecoded running on my phone to do regexps against a phone copy of /usr/share/dict/words because I find the regexp practice to be more fun when faced with a word game compared to getting stumped. There's some restrictions, like no running your own JIT on user specified JavaScript, aka no making a web browser, but for most apps I dare say you won't run into the limitations trying to scratch an itch.
It depends on the goal. Right now, one thing I definitely wouldn't want to do is write js bullshit by hand - absolutely not.
But if we are talking about personal projects where the aim is to learn complex interesting things, then of course writing code by hand is the only way to actually learn.
Kmett is a legend in Haskell. He writes and maintains tens of libraries - since the 2000s. Even before LLMs, Kmett had an output like most of us can do only with LLMs. Seriously, the guy is a coding machine.
i see, but my statement does not become false because of it. his agent pushes several commits an hour in a continuous loop, meaning this respected developer is not involved in the process at all.
The article gives a link to the discussion on Reddit. In it, Edward says
"I actually did pretty much gave up sleep for a week. That said there are a few hour stretches here and there where I leave it on mostly cleanup tasks and doze off. you can find a couple of 2-3 hour breaks where it got hung up on approval while I was lights out. "
He wore out the vim movement keys on a mac laptop keyboard in four months.
By "wore out" I mean he had worn the plastic down to the keyswitches, in FOUR MONTHS.
We once had an emergency production outage and Kmett got more productive as he stayed up later. At about 36 hours he fixed the problem. I fell over asleep, he fixed other problems he'd found during the investigation.
I have lots more Ed stories, but this output you question does not surprise me.
I briefly worked with him personally. He is 1. a perfectionist and 2. equipped with the intellectual and programming firepower to not get stuck in the resulting paralysis that a lot of people get stuck in but blast through tasks that should be impossible to do at all, let alone with a high degree of quality, successfully, through sheer intellectual firepower. The end result is that he is well known for already having not just one incredible Haskell library, but a number of them.
I can promise you he will not produce and release "slop". He would be an order of magnitude more offended at the idea than you are, I'd imagine.
In the original commenter's defense, I _did_ let the agents I have working on this get a more than a bit test harness crazy back when I was able to use GHC itself as a behavioral oracle. That worked fine through the initial build out, but then it rushed ahead with a broken CI due to misalignment in priorities, and then kept piling fixtures on top of fixtures and didn't properly track their cross-dependencies. My work on this in the last 48 hours has mostly been about getting that part under control and stable across my target platforms so I have better bedrock to build atop.
> not just one incredible Haskell library, but a number of them
...and this still understates his impact on Haskell, he helped shape how a lot of programs are written in Haskell through some of the stuff he worked on (see e.g. https://stackoverflow.com/a/2769840 as evidence of his influence on core functionality).
in that case it is truly amazing, because I have never seen anyone even with current ai capable of being so productive and truly understanding what they are putting out.
Ed Kmett is one of the smartest people I have ever met in my life. He is quite literally built different.
He completed undergrad and graduate programs in math, computer science, and a special program in ai all simultaneously in 3 years. I believe he was finishing programs before his scholarships could kick in.
As a 17 year old, I agree with this. Ofc I'm against all the hate directed at PG, I believe that all knowledge has value regardless of its economic utility, but I understand where the hate is coming from. Personally, I find LLMs boring for now, and I'm more focused on CS and electrical engineering.
LeetCode problems are usually added after each contest, and as far as I know their statements generally don't change afterward at least the actual problem itself doesn't.
As for test cases, there are occasionally solutions that are technically incorrect but still pass because a particular edge case isn't covered. We maintain our own test cases, including a DSL for writing large stress tests, and try to cover all possible cases.
In the worst case, a solution might pass our local tests but fail on LeetCode. I expect such cases to be rare and one of the benefits of having the tests open is that when someone finds a missing case, it can be added so nobody else runs into the same issue.
I love open source and open systems in general. Popular competitive programming platforms aren't like that: not only is their source code closed, but they also don't publish the test cases used to evaluate submissions.
There are already projects that can submit your solutions through the LeetCode API and return the results. But I don't really like that approach, so I decided to build an open set of tests that aims to match the quality of LeetCode's tests as closely as possible. This way, you can run everything locally, without needing for example, an internet connection.
I see the project being useful for its most straightforward purpose: testing your solutions locally on your own hardware, without any submission delays and even completely offline. Since the tests are open, people can also build different tools around them. For example vim extensions and other integrations. Ofc it's not that simple, we currently support about 1400 problems (out of 4000~, including premium), and not all topics are covered.
reply