I would agree and also suggest that initiatives like this play a large role in doing so. While there's a lot of bullshit arguments coming from the "yes" camp they do make some reasonable points and it's important that we discuss them to show what the trade-offs are.

I cannot speak for all Swiss but knowing that it was a democratic decision to continue with some, high skilled, immigration makes it far easier to accept than if some government employee in Bern would've made that decision single handed.

That is, pretty damn impressive and very useable. When it comes to architecture or complex problems it does noticeable worse but I don't think anyone expected anything else.

One particular interesting strong point seems to be design and user interfaces. It does seem to punch above it's weight there but that might just be personal preference.

What happens to the (slightly warmer) water after it has been used? Is there a way we could return it in a way to minimise impact? I.e if we extract ground water should we inject it back into the ground? Would that even matter?

In the end I have a feeling that the most efficient solution will most likely be to just increase the price of water during a drought. People will complain but it won't be long before the big consumers will happily adjust their consumption or move to an area with abundant water.

China doesn't access to any of the latest chips technology but Huawei seems to have a roadmap to work around this by focussing on "3D chips" (vertical stacked). It's unclear if they can pull this off but if they can it might be a huge boost and allow them to further drive down inference prices.

GPUs that can run everything from Crysis to CUDA are a harder engineering problem to solve than creating a chip that's optimized for inference. Not to mention that inference is an excellent first step towards a full, competitive GPU as well.

Ofcourse you don't want users to lose the feature once they exceeded your revenue threshold or cross the border so you'll need to implement some kind of tracking. Your analytics and error tracking also needs to communicate with the feature flag service.

Definitely not rocket science but more complex than a environment variable.

It's not good enough to fully replace any of the frontier models yet but it's definitely great to have as a backup!

For everything that's wrong in society the answer seems to be more and more regulations. The negative effects (such as the lack of European AI companies) are then waved away (it's because Europe spends their money on American AI instead of investing in EU AI).

It's honestly scary.

The poverty rate in Switzerland has increased (source:https://www.bfs.admin.ch/bfs/en/home/statistics/economic-soc...) but is defined as:

The poverty line is derived from the guidelines of the Conference for Social Welfare (SKOS). In 2024, it was on average CHF 2388 per month for a single person and CHF 4159 for two adults with two children.

I live in Zurich (by far the most expensive city) and while 2388 (or 4159) would be tight (depending on housing) it would still afford you a fairly comfortable life with access to top quality healthcare and public transport. Life quality wise one could argue that poverty in CH is a better option than a middle income in a lot of European countries.

I spent some time figuring out how to disable the default language server after installing Ty.

I love the concept but I've never hosted such a terrible piece of software. Every update breaks something new or introduces another "anti-feature" that's enabled by default.

The documentation is often lagging behind and the changelog has such a low signal to noise ratio that you need a LLM to figure out what upgrading will break this time. For now I've just given up on updates and I've been patching bugs directly in the JS when they bother me enough.

If OpenClaw is the future of software I'm honestly a bit scared for the industry.

I'm open to suggestions, I tried Zeroclaw and Nullclaw but they're bad in their own way. I would like something that's easy to run on Kubernetes with WhatsApp integration and most important, stable releases.

For the price this is a pretty damn impressive model.

On the other hand I did get a chewing out from an older guy for having a conversation with friends on a train once, so some people take it perhaps a bit too serious.

For them there're far worse things than giving up some freedoms.

One can agree or disagree with this but Europe's actions are far more understandable if you see where they're coming from.

From what it's worth, the younger generation doesn't seem to see this the same way so whatever censure Europe introduces today will most likely be temporary.

Some update broke the OpenRouter integration and I haven't been able to fix the issue. I took a quick look at the code, hoping to narrow it down and it's pretty much exactly what you would expect, there's hidden configuration files everywhere and in general it's just a lot of code for what's effectively a for loop with Whatsapp integration (in my case :)).

Not to mention that their security model doesn't match my deployment (rootless and locked down Kubernetes container) so every Openclaw update seemed to introduce some "fix" for a security issue that broke something else to solve a problem I do not have in the first place :)

I've switched to https://github.com/nullclaw/nullclaw instead. Mostly because Zig seems very interesting so if I have to debug any issues with Nullclaw at least I'll be learning something new :)

There's probably a better source somewhere but this is the one I had at hand.