I think the point is that, perhaps, ios and osx developers' biggest pain point was not objective c, but rather the regressions and missin...
I think the point is that, perhaps, ios and osx developers' biggest pain point was not objective c, but rather the regressions and missing features of the development environment. Taking on a whole new closed source (at least for now) language seems like it spreads resources a little thin -- even at Apple. Since it's already done I don't want swift to go away at this point. However, if given a choice between keeping objc and having a much better development environment or getting a totally new language (and the division it will bring) and a buggy IDE, I would've picked the former.
Posted by boundsj on Jul 21, 2014, 3:49 AM
Tags
Related issues
- Not sure what you suggest to do.
- Why is this not yet published on the official website and why is there no CVE?
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
Raise real-world problems, find people facing the same issue, and discuss solutions.9,500 issues0 comments
hackernews (Other)
Not sure what you suggest to do.
NewWhy is this not yet published on the official website and why is there no CVE?
NewThe biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
I think the point is that, perhaps, ios and osx developers' biggest pain point was not objective c, but rather the regressions and missin...
I think the point is that, perhaps, ios and osx developers' biggest pain point was not objective c, but rather the regressions and missing features of the development environment. Taking on a whole new closed source (at least for now) language seems like it spreads resources a little thin -- even at Apple. Since it's already done I don't want swift to go away at this point. However, if given a choice between keeping objc and having a much better development environment or getting a totally new language (and the division it will bring) and a buggy IDE, I would've picked the former.
Comments (0)
No comments yet. Start the discussion.