211–220 of 226 posts
Earlier quoted context omitted.
I meant it as an user.
If the developer has decided you are not allowed to, then you can’t really blame the tool he’s using…
Additionally, see: https://news.ycombinator.com/item?id=43215065
Earlier quoted context omitted.
Firefox will have WebGPU this year. Safari too probably.
Better wait while seating. Firefox is at the edge of irrelevance and Safari barely supports WebGL 2.0.
Earlier quoted context omitted.
Having things look the same makes everything easier to use. I know exactly what's clickable and what happens when I click them, instead of having to figure it out each time. I don't understand why you'd be annoyed at different checkboxes within an app but not at different checkboxes between apps. Do you only ever use a single app? I constantly switch between many apps. More importantly, having things behave the same…
I love it when someone's example makes it clear that they have no idea what they're talking about. OS Widgets don't implement undo. Undo is inherently tied to app state and the developer is responsible for managing it. At most, the OS will give you an undo button/icon and you can use it to fit in visually. Frankly, building a separate version of my app per platform to conform to your nativist standards is a huge wast…
Have you actually built any native macOS apps? I have.
Earlier quoted context omitted.
Better wait while seating. Firefox is at the edge of irrelevance and Safari barely supports WebGL 2.0.
Okay, let's have a race. I bet we'll see WebGPU released in Firefox and Safari before we see Flash becoming relevant again.
Earlier quoted context omitted.
Eh.. lots of projects targeted mobile app stores by authoring in Flash and using the GPU accelerated stuff. Starling was a semi-blessed framework. Worked perfectly well, no battery drain. Lots of "native" apps were authored that way (and still are, you see the same approach with Unity etc.) Browser plugins could have been fixed to catch up, the VM itself wasn't the problem in terms of drain
Not my recollection at all. Adobe invested almost 0 effort in getting their runtime working on non-x86 platforms. It was pathetic, honestly, how many years passed before they had any kind of passable implementation there. Adobe Flex was interesting and not awful. The problem was the runtime. And the company behind it. Who remains awful.
Earlier quoted context omitted.
What is the fundamental limitation that prevents AI from ever doing the maintenance tasks that you mentioned? Current AI cannot, of course, but the trajectory seems to be that it will be able to do such things better & faster than any human can.
Two things: This requires a language that a human can give the specs in. A language that is both precise and unambiguous and understandable by humans. A... programming language? And it requires AI to understand the effects of changes it makes. On many levels. "If I move this module behind an abstraction, will it make it easier to maintain? Does it touch performance? Would it open security issues?" Generative AI isn't…
From what I've seen, Grok 3 would be quite capable of inferring the effect of any change, at least at a high level. Have you used any of the recent models?
Earlier quoted context omitted.
What is the fundamental limitation that prevents AI from ever doing the maintenance tasks that you mentioned? Current AI cannot, of course, but the trajectory seems to be that it will be able to do such things better & faster than any human can.
The trajectory actually seems to be plateauing already. OAI is struggling mightily to improve GPT enough to call it 5.0 and te struggles will only get harder as the number gets higher
Earlier quoted context omitted.
I love it when someone's example makes it clear that they have no idea what they're talking about. OS Widgets don't implement undo. Undo is inherently tied to app state and the developer is responsible for managing it. At most, the OS will give you an undo button/icon and you can use it to fit in visually. Frankly, building a separate version of my app per platform to conform to your nativist standards is a huge wast…
Bullshit. Undo in a macOS text entry box is part of the widget’s implementation and you get it for free. It doesn’t need to be tied to the app’s state, since it’s just working on the text you put into the box. Have you actually built any native macOS apps? I have.
Sure, point taken. Native widgets might work differently than cross-platform ones. That said, there's no reason a cross-platform widget couldn't work identically to the native one.
Indeed, a platform's native widgets an effective way to give users a consistent style and functionality across apps from many developers.
Yet, as a one-man dev team, the cost of building a separate version for each platform is prohibitive. The choice is to disregard most platforms or disregard a small corner of the expectations each user has for apps on a given platform.
The choice was pretty obvious to me.