occz

It plummets. Standardizing the building process and building at scale unlocks some major efficiencies.

Were you under the impression that it would be the opposite?

Radical concept: you could provide UBI in the form of housing, food and transportation

Municipalities have far-reaching power in deciding what gets built where. Getting things built can take quite a long time.

I think the reason behind using React and JavaScript is simpler - these tools are heavily vibecoded, and React/JavaScript is what was most present in the training data and as such is what the models excels the most at generating.

The crappy laggy UIs have the same root cause - heavy use of vibecoding with lackluster quality processes

Books3 is public data on the internet in the same way that the Claude code source code is public data on the internet.

Except Anthropic published the Claude code source code themselves, while Books3 was not published by their original authors.

Electric assist helps with the wind.

Or just building some fitness, which in my experience comes automatically when you bike

The 24 hour wait period is the largest of the annoyances in this list, but given that adb installs still work, I think this is a list of things I can ultimately live with.

That's not correct - the flow described in the post outlines the requirements to install any apps that haven't had their signature registered with Google.

That means those apps still keep on existing, they are just more of a hassle to install.

E-bike makers aren't going to volunteer for that it'd destroy their business.

Arguably, complete bans will be even worse for business.

And I just finished The Rise of Endymion a few days ago. Uncanny indeed.

This can be solved well enough by having the model invoke `--help`

I'm a bit jealous of those prices, there are no caps on Stockholm transit if paid for on single tickets, and the price of a single ticket is 43 SEK (£3.45). The best deal available for period tickets is the unlimited monthly pass for 1060 SEK (£85).

Public transit in Stockholm has in the last ten years done two things that make for a godlike ride payment UX:

1. Removed the concept of zones - everything is now covered by one single ticket 2. Introduced tap-to-pay support for debit/credit cards

This means that you as a user can always just show up with the overwhelmingly most common way to pay for things in Sweden - by card - tap once, and then you're done. No more actions required. Need to transfer? No problem, the virtual ticket you bought by tapping your card is valid for 75 minutes, no more money will be charged if you tap again within this window.

No fumbling with an app, no awkward QR code scanning, just one tap and go. Peak UX.

Easy, you reject it.

As it turns out, you regularly get a COP of >3 from heat pumps, as they don't need to generate the heat, they steal it from somewhere else (outside)

You'll be waiting for a long time then, probably. Making codecs is actually a hard problem, the type of thing that AI completely falls over when tasked with.

While funny, that's not really what I would call accurate. Users get reduced data consumption, potentially higher quality selection if the bandwidth now allows for a higher resolution to be streamed, and possibly lower disk usage should they decide to offline the videos.

Better codecs are an overall win for everyone involved.

It's not really a matter of just turning it on when it comes to the kind of scale that YouTube has on their catalogue. It's practically impossible to retranscode the whole catalogue, so you're more or less stuck with only doing it for newly ingested content, and even there the tradeoffs are quite large when it comes to actually having DRM.

I think we can safely assume that the only content under DRM at YouTube today is the content where it's absolutely legally necessary.

This doesn't really mean much on account of the iOS ecosystem only supporting the latest two OS versions in their apps as a general rule. Once you are behind 2 versions, your device becomes quite useless at that point

It's insignificant for day-to-day programming for experienced developers, but has importance for learners.

That's not a good move at all.

I guess that depends on how you get that ARR-figure. If more than all of it goes to paying your AI bills, then you can't really afford that much engineering investment.

One way to reduce deaths is just get everyone into cars.

A patently absurd claim that holds up to no scrutiny whatsoever. The whole nation of the U.S disproves it, for one.

Nor do you really need to comment on them, in that case.

I've noticed this as well.

I've also noticed that the effort to de-slop the shit-code is quite significant, and many times eats the productivity gains of having the LLM generate the code.

There's very few currencies in the world in which 1M isn't enough to retire. USD isn't one of them.

Unless you're planning on retiring as cheaply as humanly possible, 1M is not enough to retire for the large majority of the currencies in the world.

None of the claims in this comment are grounded in reality.

With less hindrance from congestion as well, meaning that they get to make more transactions and hence make more money.

You build the EOL plan in advance.

The things people will do to avoid putting up catenaries truly are wild.