How about replaceable batteries?

EU regulation on that should come into force in Feb 2027.

You sure? I only heard of laws about repairability, not swappable batteries. You can already replace the battery of any phone, the only question is if it'll take you 1 minute (Fairphone) or several hours (every other vendor I'm aware of). The legislation might make it take maybe 1 hour instead of 2, and requires (iirc) that you can obtain legit replacement parts for a few years, but that's about it

Seeing how Motorola is trying to bypass the regulation for software updates, I don't have any hopes. https://www.androidauthority.com/motorola-eu-software-update...

That regulation doesn't apply to mobile devices at this point afaik.

Next victims of "AI productivity gains"

What worried me is that LLMs are becoming a crutches for overworked engineers. But instead of reducing the workload it has also increased the expectation and consequently more aggressive deadlines, making it all worst overall

Correct the url has 2026, probably a typo

Seizon Senryaku!

Sorry but this seems like vibe coded slop

You cant search or change language

Idk what is the goal here, but maybe some analysis with graph would be better, like who has the most territory or something like that? You also might need to disclosure how you got this data

Hey there I made the site about a year ago or so because I noticed around my apartment is only Lawson's, so I got curious to see and find how common those types of places are. I used ai for CSS since I can't stand it. But this was a project mostly to learn and play with leaflet

I thought you were being unfair, but I don’t think you’re wrong anymore.

https://github.com/kikkia/ConbiniWars/commit/b8ea5e5a9351c23...

If you are referencing the size of the initial commit that's 99.9% geojson. 56k conbinis takes a lot of lines. Since I was using this as a project to learn leaflet, there is also code I copy pasted from plugin getting started sections and what not. Also some plugins were old and unmaintained so I opted to just put them statically in my assets so I could also modify them easily as needed.

No it’s the single large commit of, not just the data, but the rest of the logic in conjunction with it. You did not appear to use any version control in the development of your app, yet you use it to maintain the app. That’s a AI “smell”.

As an aside, we used to use the term “code smell” back in the day when trying to trace the source of problems in an app. The “smell” would tend to lead you to the bad code.

It doesn’t guarantee this is purely AI generated. It’s just weird, and when held up to the rest of the git repos of the last two years, it gives the appearance of AI generated.

The “slop” part is debatably unfair still, but having an app be AI generated tends to mean little effort was put into the up front requirements analysis before a selection of functionality made.

Again, just generalizations on my part. If it makes you feel better, I’m working on an AI generated app to quantify the amount of times someone’s work is dismissed as “AI slop” so I can present a case to the moderation team to get the HN guidelines updated to discourage ONLY calling something slop without any evidence of it.

Wut, how does that look like AI?

Agreed! The problem is that some 'seniors' never cared to learn patterns in the first place. That’s a huge problem for frontend, where we have increasingly complex architectures and people with very little experience with design.

Even some principles aren't known. I always recommend the book Head First: Design Patterns. It's in Java, but the lessons can be applied in every language.

Unfortunately, we are in a 'post-knowledge' era... I don't know how we can keep things up at this pace.

> It's in Java, but the lessons can be applied in every language.

I can only discourage anyone from applying Java patterns all over the place. One example in JavaScript: There was a functionality that required some parameters with default values. The plain solution would have been:

    function doStuff({ x = 9, y = 10 } = {}) {  ... }

Instead, they created a class with private properties and used the builder pattern to set them. Totally unnecessary.

I've read that book, and it felt very childish and condescending.

Design patterns cannot be applied in every language. While some patterns are applicable everywhere, many of them provide replacements for missing language features. For example, the Builder pattern is not very useful in languages with default parameters and named arguments.

I'm not sure what Builder would have to do with default parameters and named arguments.

Builder is extremely useful to pair with a parser, e.g. SAX. The parser parses the input, and the builder then decides what to do with it.

Here is an example of the Builder pattern that illustrates my point: https://www.baeldung.com/java-builder-pattern#bd-classic-bui...

Let’s remove the category argument and you get this:

    Post post = new Post.Builder()
      .title("Java Builder Pattern")
      .text("Explaining how to implement the Builder Pattern in Java")
      .build();

This builder is a more readable alternative to this:

    Post post = new Post("Java Builder Pattern", "Explaining how to implement the Builder Pattern in Java", null);

But if Java supported named arguments and default values (the default would be null), this could just be:

    Post post = new Post(title: "Java Builder Pattern", text: "Explaining how to implement the Builder Pattern in Java");

Funny part is that Java does have named parameters, but only for annotations!

What's interesting about frontend is that there are two ways to evaluate it: by how it looks and how it's written.

It definitely biases how people evaluate llms. Many cite Claude as their favorite llm for generating frontend code, but I suspect that many people prefer it because the output is prettier, rather than better composed.

Two words: Disco Elysium

Maybe you need VA too

Storage seems small to how crazy big some games have bee EDIT: Maybe it needs a combo ssd for system + hdd for storage

I have been thinking on dropping Windows, that I use only for gaming, but the issue is that I got a Nvidia graphics card and didn't have time to check if the support for it in Linux got better

But after experiencing the new Windows 11 "always-online" model it might make me stick to AMD in the future

While I would like to champion AMD a bit more because Nvidia has been doing some anti consumer shenanigans, I have to say that at this point, the Linux support is good. It is a bit of a myth or perhaps just outdated info that if you want to have a headache-less experience, you need to use AMD. For new hardware, it may even be a bit better than AMD to be honest.

The only difference is that updating is a bit easier on AMD, after all, mesa just updates with your OS. But this is merely a note on convenience.