tempest_

The point is that the incentives are not pointing towards "make better phone" they are pointing towards "sell more phones"

Sometimes "better phone" drives "sell more phones"

Sometimes it doesn't.

> If you could, iPhones would already have removable batteries.

A crazy take since apple has very clearly made anti-consumer moves in the past.

If having a baked in battery caused there to be 1% more iphones sales which would they choose.

You were likely nodding along when Jobs was out there telling people they were holding the phone wrong.

Citation needed.

All of those can be achieved with replaceable batteries.

It really really really depends on how you are using it and what you are using it for.

I can get LLMs to write most CSS I need by treating it like a slot machine and pulling the handle till it spits out what I need, this doesnt cause me to learn CSS at all.

We are lucky in that we can choose our machines (within reason, and no real support if things get broken) and run an arch flavour.

I use thinkpad x1 carbons and have nearly 0 issues. The hardware is not quite as nice as a macbook but it does the job and is nice enough.

Yeah, they were that, and for the last 20 years they have been the iphone company.

That is fair but in my experience most devs are targeting linux servers not BSD(or any other flavour) which is helped by OSX. If OSX was linux derived it would suit them just as well.

edit: I suppose I should also note the vast majority of people developing on mac books (in my experience anyway) are actually targeting chrome.

I am aware.

However having used Xcode at some point 10 years ago my belief is that the app ecosystem exists in spite of that and that people would never choose this given the choice.

Has apple been a serious development platform in the last 20 years?

I know a lot of devs like apple hardware because it is premium but OSX has always been "almost linux" controlled by a company that cares more about itunes then it does the people using their hardware to develop.

If you get enough of them they can start to look like cattle.

Still, they are all the same breed.

There is a large subset of devs who have worked their entire career on abstracted hardware which is fine I guess, just different domains.

The size of your L1/L2/L3 cache or the number of TLB misses doesn't matter too much if your python web service is just waiting for packets.

> fault tolerant distributed systems

I mean there were mainframes which could be described as that. IBM just fixed it in hardware instead of software so its not like it was an unknown field.

I build on the exact hardware I intend to deploy my software to and ship it to another machine with the same specs as the one it was built on.

I am willing to hear arguments for other approaches.

Because might makes right and any entity with the power to legally put up a fight is in on the game (or wants to be)

It isnt that weird. Just look at the gemini-cli repo. Its a gong show. The issue is that LLMs can be wrong sometimes sure but more that all the existing SDL were never meant to iterate this quickly.

If the system (code base in this case) is changing rapidly it increases the probability that any given change will interact poorly with any other given change. No single person in those code bases can have a working understanding of them because they change so quickly. Thus when someone LGTM the PR was the LLM generated they likely do not have a great understanding of the impact it is going to have.

Google is not incentivized to show you good results. You don't pay them, advertisers do and that is who they are working for.

Their job is provide you just enough "results" that you don't or cant go any where else.

No more, no less.

Why would you assume that to be?

They might charge you less, but they don't have to and wont if the market allows it

Cell was PS3 and the Will used a Power cpu.

IBM had a hand in both however

The Pi isnt a loss leader for user acquisition nor do they get to enjoy Apples economy of scale. Apple can take a small loss on this and it will still be worth it if they retain the users in their ecosystem.

JavaScript in the late 90s was doing a hell of a lot less than it is today.

DDR4 is also crazy expensive right now so this just depends on you having some around from a previous build

Those will dry up soon enough. Corporate laptop refreshes will be drawn out as they try and cost save on the increased price.

You also better hope the aliexpress dont figure out a way to get the RAM out of those things because they will start harvesting it for sure if there is money to made.

It isnt lost but it also isnt a common skill set in programmers any more.

Most programmers are JS web devs writing client side code or server side CRUD.

I would guess < 10% of programmers writing code today get perf / valgrind out on the regular. I know I dont.

We just had a vendor tell us none of the HDDs we were looking for were available unless we also committed to a full NAS offering.

Look at the gemini-cli.

Pretty sure it will look like that

My opinion is I think that there is a massive gulf between 'wrote the spec' and 'validated the output'.

I think if the answer to "could I do this again without claude" is no then it is difficult to claim ownership.

If you're just adding endpoints to some web project and doing feature work then whatever, if you are "rewriting tree sitter in rust" which a lot of these posts seem to be I think it deserves some skepticism.

Every "I created <xyz>" or "I rewrote x (y lang) into z lang" should really read "I prompted Claude Code to <insert thing>"

"I" create stuff all the time with AI Agents but am real uncomfortable claiming ownership over them. Others don't seem to have this problem though so /shrug

p.s. - in this case the commits are claude commits, even if they tell it not attribute itself you can tell because good commit messages were incredibly rare (even my own) until the last year or so when they started to look like entire pull requests

I mean they are not wrong.

For all the whinging about bugs and errors around here the software industry in general (some niche sub-fields excepted) long ago decided 80% is good enough to ship and we will figure the rest out later. This entire site is based on startup culture which largely prided itself on MVP moonshots.

Plus plenty of places are perfectly fine with tech dept and the AI fire hose is effectively tech debt on steroids but while it creates it at scale it can also help in understanding it.

It is is own panacea in a way.

I think it is gonna be a while before the industry figures out how to handle this better so might as well just ride the wave and not worry too much about it in software.

Still software is not medicine even if software is required in basically every industry now. It should more conservative and wait till things settle down before jumping in.

Running on Azure is not the same as migrating to Azure.

Making big changes like the tech that underpins your product while still actively developing that product means a lot of things in a complicated system changing at once which is usually a recipe for problems.

Incidentally I think that is part of the current problem with AI generated code. Its a fire hose of changes in systems that were never designed or barely holding together at their existing rate of change. AI is able to produce perfectly acceptable code at times but the churn is high and the more code the more churn.

I mean that was a thing at one point but I feel like it is baked into github/gitlab etc now