NorwegianDude

While Google does a good job with language support in their models, GPT-5.5 can't write proper Norwegian. It's even making up words that does not exist.

Considering the fact that the US is complaining about Norway putting too much money into the US market, imagine what would happen if all that money was spent in Norway. It would be chaos.

Noctua wants their fans to last for many years, spinning at 2K rpm, with heat.

Being able to produce something with lower tolerance is one thing. Making it work long term at ~10 m/s and ~200G is another thing. Have you ever been in a car that brakes really hard? You'll move. Now, multiply that force by 100 and you'll get around what the fans must sustain over time.

A simple LAMP stack can give you <1ms page loads for most applications. Even 15 years ago you could serve over 100k/rps of lightweight PHP pages from a low end server.

Just to point it out, Cursor has not made any good models themselves. Composer 2 is Kimi K2.5, and they tried to pass it as their own until people noticed that the api specified it as Kimi.

It's especially bad considering the US had already taken out 100 % of Iran's military capabilities, according to the official statements.

What a clown show...

> I worked at a startup, they built their API in PHP because it was easy and fast. Now they're successful, app doesn't scale, high latency etc. What does their php code do? 95% of it is calling a DB.

So PHP worked perfectly, but the DB is slow? Your DB isn't going any faster by switching to something else, if that's what you think.

PHP is the future, where React has been heading for years.

Qwen3.5 27B works very well, to the point that if you use money on Claude 4.5 Haiku you could save hundreds of USD each day by running it yourself on a consumer GPU at home.

At least for me, it's cheap. Even Claude Haiku 4.5 would cost over $60 each day for the same token amount, after accounting for electricity costs. I have the hardware for other reasons anyway, so why not use it, avoid privacy issues and save money.

Are the LLMs very useful? That is a whole other discussion...

I guess this might be a decent way to farm data? Those with larger OSS projects usually have better code quality, making it easier to create a dataset with maybe higher quality for training. Considering how often people leak data to the LLM services it's also an amazing way to get backdoors into many OSS projects.

Fun challenge, but running the benchmark on Apple hardware is a weird decision as Apple doesn't even have server hardware. Would make much more sense to run it on a dedicated Linux box as that is more accessible and more realistic.

I guess people are just a few days from starting to earn $30k/yr on their model 3s, as musk said it years ago? lol

To be fair, he's completely right. I have a lot of experience with IE6 and safari on iOS, and while IE6 was bad and did weird shit, Safari is much worse. It's amazing that things can work in any browser, without ever even thinking about it, but then on Safari you get weird behaviour, straight up rendering bugs because of some weird race conditions with the engine or even crashes.

The latest issue that I've noticed yesterday is the button nav bar on the screen when running PWAs. The button is over the bottom navbar of the PWA, and despite apple themselves coming up with the API to inform the browser about safe display areas, it doesn't work in PWAs on iOS. PWA mode on iOS != non PWA on iOS. They often behave completely different and you often have to use JS for basic things to work, like clicking a link(yup, this was a thing for years).

If you're looking up values from a 3 GB DB, most would have to hit RAM. Lookups form a hash map can be fast, but SQLite does quite a bit more than just a hash map lookup, and it would usually hit RAM, not L3 cache.

> You could always allow users to choose the amount and just include the transaction fee.

I'd be happy to do that, but it's not really as simple as it seems. Multiple of my payment providers have fees I'm not allowed to disclose, and the same Norwegian Consumer Council has also repeatedly stated that they do not want payment fees to be passed on to the consumer as that might be unfair to those who can't use specific payment options. They are passed on to the consumer either way, so... That's the only reason I don't provide tiny purchases, as the fees will result in negative value of the sale. But again, I'd be happy if I could just add fees to the price so that people could just buy exactly the amount they want.

> If card networks are operating in the country, they'd have to abide by the country's rules too. Yes, but currently the laws are not compatible. You can't follow one without breaking the other.

The problem isn't displaying a price, but how to do it in a way that makes sense. It doesn't really make anything more clear when it's called the same thing as the currency in game and has no fixed conversion because of fees making up a larger cut for small purchases. The Norwegian Consumer Council want's users to be able to buy the smalles unit of currency if thwy want, but that must be relatively very expensive because of the fees. They alsy want prices to reflect the most expensive method of acquisition of the currency. This will 100 % result in totally unrealistic prices, that are easy to confuse with the in game currency. It's clearly easier if you buy a fixed bundle of 1000 "gold coins" for $10, and the price is listed as "Buy a $500 paiting for 100 gold coins" instead of "Buy a $500 paiting for 100 gold coins($50 real money)".

You do have some weird takes on why I'm doing things. The game is free. Not because I'm trying to exploit someone, but because it's much harder and more expensive to market a paid game. I don't have DLCs, cause all content is free for everyone, and forcing players to pay to play by putting content behind paywalls is not something I want to do, and also something the same Norwegian Consumer Council says should not be allowed in games.

A one time payment for an ongoing service is not sustainable. Infrastructure and content isn't free, the same way you don't pay a one time payment for netflix.

It's not solved if you're not allowed to bill for fees seperatly. The end result is the same, so it's a dumb rule. It just makes it less clear what you're actually paying for.

Didn't I just say that it wasn't part of some evil plan? Prices of things have no relattion to that the different bundle sizes are. In-game prices are constant to ensure that people get what they pay for. The price in real money for the in-game currency is adjusted for inflation every now and then.

40 million reads per second, on a single core? 40 million reads/s is 25 ns per read, that is faster than any RAM I know of.

I've been using GitLab since the early days, but a week ago I switched to Forgejo. Power usage on the server dropped by 10%, despite both being idle most of the time.

As the author says, GitLab feels sluggish, and is bloated with 1001 thing I'd never use that just makes the UI a pain. Despite all the features I don't need, some that I would benefit from are disabled in the free version.

Forgejo is simpler. It allows me to hide features per project that I don't need. Bit there are some tradeoffs. Updates on GitLab was great. I've been letting it self update for years with no issues. This does not work on Forgejo. Forgejo is also a lot less polished, and some features just doesn't seem to work like they should.

I do t have time to test myself now, but it would be interesting to see a proper benchmark. We all know it's not suitable for high write concurrency, but SQLite should be a very good amount faster for reads because of the lack of overhead. But how much faster is it really?

SEK, not EUR.

As a game developer myself, I think young kids should not be able to make purchases on their own.

But some of the ideas on what needs to be done is just silly.

Here is some of the ideas the Norwegian Consumer Council suggested: - All things in games should be shown in real money value, not in game currency that you have to but for real money, and the price should reflect the most expensive way to get the currency. - All transactions in games should have the same rights as in real life(if you buy an item in game, you could use your right of withdrawal). - Users should be able to choose how much the want to buy of premium currency/spend.

While it might have good intentions, they have serious issues. I sell bundles of in game currency. I don't allow users to select just how much they want to buy. I don't do this as part of an evil plan, but because it makes sense. Bigger purchases give more, because the percentage lost to fees are lower. Tiny amount can not be bought, as it would not make sense considering the per transaction cost.

I don't price things in real currencies, cause after the purchase is made, it's not real money, and if it were, I'd be a financial institution and break the rules of all major card networks. It also would cause issues when it comes to inflation adjustment. If an user buys 100 "coins", they can buy something for 100 coins. If I adjust for inflation then I adjust the price of coins, not how many coins are needed to buy something in game. That would not work with real money.

Regulation is welcome, but don't do something dumb. Let most thing be as they are, but put strict rules in place on kids making purchases, that way a grown up who hopefully understands money can approve or deny the purchase.

How freaking expensive do you think infrastructure is? It's not that expensive, and certainly not anywhere close to the point where it would make a noticeable impact on GDP.

It's not a wrong solution. It's been commonly used since forever, tens of years before the sec-fetch-site header existed, and it stops CSRF. Sec-fetch-site is not supported in old browsers, so relying on that is unsafe without any fallbacks.

The simplest way to prevent CSRF is to use the Referer header, and that has been used since forever. If the header is missing, you no-op the post. Origin is similar, and can be used with referer as fallback, but it's not needed for most sites.

To be fair, Gmail asks for a phone number, but you dont have to add one.

This is very misleading. The secure defaults for sqlite is changed, so commits are not actually written to the disk. Running sqlite like this will cause data loss on os crash or power loss.

It is an option. You can run without cloudflare, and if you ever need filtering then you just swap over with little downtime.