andix

99% of developers should just ignore SIMD. Most projects have a lot of low hanging fruit to increase performance, and still nobody finds the time to solve them.

That would be the reasonable thing to do.

As an European I would laugh so hard, if China out-competes US based AI companies before the European car manufacturers.

(it would be a very cynical laugh, no happiness, don't worry)

I guess the US can freely request data on any citizen. The home countries don't know if you are actually traveling into the US. Direct flights are not the only option to reach the US.

Exactly my experience. I would even draw the border at 100-150k. Long contexts would be nice, but they just don't work well, even if the models support them.

I didn't try long coding sessions for a while. I had really noticeable performance degradation with all models above 100-150k and always try to stay below those numbers.

A lot of things people do on smartphones have very similar effects as gambling. It's only not as catastrophic, because most users don't lose all their money on it.

Sadly a lot of tech is potentially harmful for kids. And also adults, but they should be able to handle it better.

But it extends to many other common items. Kitchen knifes, cars, lawn mowers, ...

soon F-Droid and any unattested open source Android app distribution will be gone

This is not connected to age restrictions. It might've been used as an excuse.

I don't think age restriction will impact FOSS in the long term. If there are some regulations that threaten FOSS now, they are going to be adopted in the long term.

Regulations for age restriction are understandable. A lot of modern technology is harming kids (and I don't mean dirty videos, social media seems to be much more harmful).

A sensible regulator would leave some responsibility to the parents, but require restrictions for consumer devices (smartphones, laptops). Maybe even enable age restrictions by default, block replacing the OS or the firmware, and only allow it once the age was confirmed.

I don't see a point of including all kind of OS or software into this regulation. Just the ones that are preinstalled on consumer devices, and commercially distributed to consumers. Once the age of the user was confirmed, the devices should be able to become as open as we know them now.

Next Costco is approximately 7.000km away and would require some serious swimming skills.

I get that they make it hard to find, so we also buy different stuff. But if I can't find what I'm looking for too often, I won't come back anymore.

Sometimes I really want/need something, and I have all the stores close by. But I still decide to buy it online, and accept waiting a few days, because stores/malls are such a bad experience.

Supermarkets are maybe a bit different, they are hard to avoid.

But I dislike malls so much, that I only get new clothes for example once it's really necessary. If it was more pleasant to shop there, I would probably buy more stuff.

I guess there are some people who fit into that environment, their tactics work well on them, and the shops/malls just ignore customers like me.

I really hate shops, malls and supermarkets. I'm not easily overwhelmed and can handle being there fine. But it's just horrible there. Way too loud, bright and often too warm. Completely full of chaos and way too many useless products.

When I have to go I try to be out there as quickly as possible. I always thought that's weird, shouldn't those shops be designed in a way that makes me want to explore them, look at all the things they have, instead of just hunting down exactly what I need and leave as quickly as possible.

I probably didn’t read it. But I also had to read it twice to understand what it meant.

I’m still not sure if this is the mentioned issue or a different one.

Keycloak is awesome, but whenever I used it the documentation gave me too little guidance. On how to use it in the right way, without having to customize it too much.

Is it about the license? I see less and less new projects using GPL, and a lot of MIT(ish) licenses.

Most complex open source projects like Linux for example have a lot of contributions by corporations. The GPL kind of forces them to participate in open source, instead of just creating internal forks.

GPL and even LGPL are tricky for libraries though.

Impressive, but on iOS 27 even one of the examples don't work. Seems like it has an issue with spaces. https://imgur.com/a/tZGqtjR

The message is written to the outbox table in the same transaction as the database changes. Only if the transaction completes, the message is actually created, and other tables are updated.

In a second step the message is taken from the outbox and gets sent to the queue/broker. Only after it was sent out, the message is removed from the outbox. If the sending fails, it stays in the outbox and is retried. If the deletion of the message from the outbox fails after sending, it's getting re-sent later. So you can get a duplicated out-message.

Message brokers usually don't de-duplicate messages, they don't have a database that keeps messages, the receivers need to do that. Either with idempotency, or by tracking message ids. Event sourcing brokers can de-duplicate, because it can stores all messages.

If you never delete messages from the outbox, then they are re-sent all the time. You are going to notice such a bug really quickly.

Inbox pattern works very similarly, but the other way around.

With an inbox/outbox pattern it's possible. The incoming message might be processed more than once, and an outgoing message might be sent more than once. That's the limitation, and the system needs to be able to handle it.

If you can't de-duplicate messages it's not possible, that's true.

I don't drive the best car available on the market. I don't own the fastest and best PC/Laptop/Smartphones available. I don't live in the best house in my city. I made reasonable choices that balance my needs and my available budget.

But it's still a Democrat.

https://trakkr.ai/bias/worldview

I had that idea too. Maybe that's the future of OSS development.

Because that's the only meaningful interpretation of your suggestion.

Big corp accounts are pre-vouched. And it will be mostly their responsibility to vouch for other accounts.

I never ran into that. I always ask the recruiters to include my GitHub account in the summaries they submit to the technical teams reviewing applications. But they never do.

I see one big difference: with email it was always about sender reputation based on email servers (IPs), maybe about domains. But never about individual users. It's the organizations running the email server, who make sure users behave. So they don't get blacklisted and lose sending privileges for hundreds or thousands of users.

For PRs/issues this is not applicable.

I still feel a bit dizzy a minute after closing the page.

Duplication is often less harmful than abstraction.

Duplications can often be cleaned up over time, bad abstractions can quickly become a bottleneck, that severely slow down everyone working on the project.

I always try to design in a way, that using abstractions/shared logic is optional.

I've worked in too many projects, where every new feature needs to be built on top of existing abstractions, that often lead to severe restrictions if something slightly different is required. I always try to create reusable units/components, that can either be used as intended or replaced by something that behaves slightly different if needed.

Components are not necessarily frontend components, this extends also to backend logic.

I guess you can test that on hypotheticals. Ask about things after the knowledge cut off that never happened. Or ask things that are genuinely unsolvable.