gempir

Unironically it's easier through third parties. Cursor has had Argon available, but in our enterprise we cannot get argon from the gemini subscription because they have some weird license split going on.

Namecheap is not some random cheapo provider. They've been around for a long time and used to have a pretty solid reputation. They didn't have overly inflated prices, they had a okay customer support and good dashboard.

In the last few years they managed to destroy that reputation though.

The last time I tried an API Key in Cursor they limited it to the very basic Ask mode. No Agent Mode. So this is very much useless if still the case

I can't even read specific public transport updates in my city because they only post those to Twitter, only vague messages on their own website.

> The National Trust, which owns the land, has previously warned pilgrims not to do so, as the area is ecologically sensitive, but it seems that people still do so.

Ah okay, laying a few stones is ecologically sensitive, but if a billion dollar company wants to dig up the entire beach for a cable, that's not a problem.

I am also referring to regular 70mm, not IMAX, so is that part of the article.

> 70mm film uses DTS audio, which is supplied to the cinema on either CD-ROMs, or (more recently) via USB sticks.

I'm curious about the opinions on 70mm (non-IMAX) vs Digital IMAX.

What do you prefer if you have tried both. Because those are the only mostly accessible options around the world.

Sound is also something to consider, because depending on the Theater they might have wildy different sound setups even different audio standards.

It doesn't have a lot of style guides or linting though. You have to install and configure quite a lot of tooling for that

I've been using golangci-lint for years, it's okay but it's slow even with a cache, as soon as you have good amount of lints enabled your ci can suddendly take minutes.

That's not the fault of golangci-lint, it's just the concept of bringing together a bunch of different linters and keeping it fast is impossible. And the configuration is a bit wild too, because every linter obviously has their own decisions on how it wants to be configured.

Ruff can lint in seconds or even sub second.

That sounds amazing! I do hope golangci-lint and the likes pick it up, I'm a big fan of the strict by default approach that Ruff and other linters have taken.

Gofmt is great but it's still not very strict, the amount of times my colleagues have argued about formatting in Go is still too great, stuff like consts, types, funcs, methods order, struct initialziation newlines and other details that do matter, but they should be decided one and then applied everywhere like that.