I spend an enormous amount of money on Apple products, and increasingly they lead to frustration and anger at the thoughtlessness and plain shittiness of them. I’m really wondering why I bother. They clearly don’t have my interests in mind.
3,208 karma · joined February 21, 2014
I spend an enormous amount of money on Apple products, and increasingly they lead to frustration and anger at the thoughtlessness and plain shittiness of them. I’m really wondering why I bother. They clearly don’t have my interests in mind.
I don’t see how this won’t disable a lot of people. It’s cruel.
The section where they talk about how it adapts to different situations so that it still shows the top layer information did not inspire hope. I’m autistic and I have a hard time picking out signal from a noisy background easily. In the demo, it’s as if the icons are constantly dancing (delightfully, no doubt) but the information is lost.
For those that say that Apple always has accessibility settings where you can lessen effects like this, that’s not enough. We’re techies. We know about fiddling with settings. A lot of people won’t know. A lot of people that will be affected by this won’t consider themselves disabled, so they don’t even know the word “accessibility”. It’ll just subtly make every interaction with their technology more difficult and more stressful.
The pain of shitty code doesn’t go away. They can ship your crappy MVP faster, but technical debt doesn’t magically go away.
This is an awesome opportunity for those people to start learning how to do software design instead of just “programming”. People that don’t are going to be left behind.
These tools have turned out to be great at this stuff. I don’t think I’ve turned over any interesting problems to an LLM and had it go well, but by using them to take care of drudgery, I have a lot more time to think about the interesting problems.
I would suggest that instead of asking people to post their work, try it out on whatever bullshit tasks you’ve been avoiding. And I specifically mean “tasks”. Stuff where the problem has already been solved a thousand times before.
I’m not just thinking of myself here. I’m concerned that a lot of people who don’t consider themselves disabled will be disabled by this.
To me, being socially awkward is kind of a secondary, less important trait, but that’s the one everyone seems to notice. We’re weird on the outside because inside, we’re dealing with overwhelming sensory input.
Translucent layers generally make software unusable for me. In the video, I saw several instances that would be really really bad for me, where I’d be straining to understand the text. Looks really cool and futuristic though. Just like a movie. Big whoop.
I’m autistic, but this won’t only affect autistic people. A lot of people are going to have problems with this. I hope there’s a very prominent way to turn it off.
Most research is still following a medical model that worked for infectious diseases in the 1950s but does not yield any meaningful information or treatments for chronic, complex disorders that have multiple interrelated factors.
And since doctors are trained primarily in the treatment of acute diseases, even the useful information that’s found by research is largely ignored in practice. The ignorance of the average MD about chronic illnesses is astounding.
I’ve been sick for the last two years and I’ve given up going to doctors. They are a waste of my time. I’ve done much better by doing my own research and treating myself. Much of what’s helped has been stuff that I’ve seen described as pseudoscience, even though it’s empirically based, because there aren’t enough RCTs for it to qualify as “evidence”. This makes me incredibly angry.
The system is utterly broken. I’d like to scrap the whole thing and start over. Hopefully, we’ll find a way to start over when the smoke clears.
I approach problems with curiosity because I know that this is the only way I’ll find a way to survive and thrive again.
Well, if you’re a novice, don’t do that. I learn things from LLMs all the time. I get them to solve a problem that I’m pretty sure can be solved using some API that I’m only vaguely aware of, and when they solve it, I read the code so I can understand it. Then, almost always, I pick it apart and refactor it.
Hell, just yesterday I was curious about how signals work under the hood, so I had an LLM give me a simple example, then we picked it apart. These things can be amazing tutors if you’re curious. I’m insatiably curious, so I’m learning a lot.
Junior engineers should not vibe code. They should use LLMs as pair programmers to learn. If they don’t, that’s on them. Is it a dicey situation? Yeah. But there’s no turning back the clock. This is the world we have. They still have a path if they want it and have curiosity.
Seriously, everyone should get good at fixing bugs. LLMs are terrible at it when it’s slightly non-obvious and since everyone is focusing on vibe coding, I doubt they’ll get any better.
Here’s a possible out: Senior engineers stop working huge corporations and use these tools to start their own businesses. (Given today’s hiring situation, this may not even be a choice.) As the business grows, hire junior developers as apprentices to handle day to day tasks while senior engineer works on bigger picture stuff. Junior engineer grows into a senior engineer who eventually uses AI to start their own business. This is a very abbreviated version of what I hope I can do, at least.
And you could mitigate that risk by publishing research that doesn’t really matter, so no one ever checks.
Here’s the kicker: They only had a few hundred MAUs. Not hundreds of thousands. Hundreds of users. So all this complexity was for nothing. They burned through $50M in VC money then went under. It’s a shame because their core product was very innovative and well architected, but it didn’t matter.
I think this need to bullshit is probably inherent in LLMs. It’s essentially what they are built to do: take a text input and transform it into a coherent text output. Truth is irrelevant. The surprising thing is that they can ever get the right answer at all, not that they bullshit so much.
As I wrote that, I realized there could be cumulative layout shift, so that’s an argument against. To avoid that, the browser would have to download all transcluded content before rendering. In the past, this would have been a dealbreaker, but maybe it’s more feasible now with http multiplexing.
[0] https://en.m.wikipedia.org/wiki/Transclusion#Client-side_HTM...
I’m using AI to increase my productivity, but whenever I’ve vibe coded (not intentionally, just by getting caught up in the dumb vibes) I’ve regretted it. I’ve ended up with a tangled mess.
We’ve built an industry around solving this problem. What if, for some basic web publishing use cases, we could replace a complex web framework with one new tag?
Yeah, we’ve been solving this over and over in different ways. For those saying that iframes are good enough, they’re not. Iframes don’t expand to fit content. And server side solutions require a server. Why not have a simple client side method for this? I think it’s a valid question. Now that we’re fixing a lot of the irritation in web development, it seems worth considering.
Often, I use LLMs to write the V1 of whatever module I’m working on. I try to get it to do the simplest thing that works and that’s it. Then I refactor it to be good. This is how I worked before LLMs already: do the simplest thing that works, even if it’s sloppy and dumb, then refactor. The LLM just lets me skip that first step (sometimes). Over time, I’m building up a file of coding standards for them to follow, so their V1 doesn’t require as much refactoring, but they never get it “right”.
Sometimes they’ll go off into lalaland with stuff that’s so over complicated that I ignore it. The key was noticing when it was going down some dumb rabbit hole and bailing out quick. They never turn back. They’ll always come up with another dumb solution to fix the problem they never should have created in the first place.
It’s not just node. They have Fresh, which depends on Preact, which is a compatibility layer over the React API. Why? To save a few K on bundle size? They have JSR. Why?
The sales pitch is great: Typescript that just works. But in my experience, it didn’t “just work”. I tried building something with Fresh and ran into issues immediately. I bailed out.
I agree with you. But what you or I think doesn't matter.
> This is how the whole system is supposed to work.
My point is that our current form of capitalism is designed to work this way, but there's no requirement that capitalism must work this way. This is just the toxic form of market economy that we ended up with.
I think capitalism is the best way to structure an economy, but it’s a terrible way to structure a society. Nowadays, we use capitalist values as the benchmark for what matters in almost every context, and then we wonder why our society is a dystopia.