• 1 Post
  • 451 Comments
Joined 11 months ago
cake
Cake day: August 15th, 2023

help-circle


  • Vlyn@lemmy.ziptoGames@lemmy.worldElden Ring – Patch Notes Version 1.12
    link
    fedilink
    English
    arrow-up
    21
    arrow-down
    5
    ·
    8 days ago

    No ultrawide support, no DLSS, no removed fps cap, no precompiled shaders to remove the stutter, …

    From makes good games, but when it comes to technology they either suck or are just lazy as hell.

    The biggest joke is that ultrawide already renders the full screen width, they just put black bars on top to not give the player an advantage, lol.


  • Well, there’s modern C++ and it looks reasonable, so you start to think: This isn’t so bad, I can work with that.

    Then you join a company and you find out: They do have modern C++ code, but also half a million lines of older code that’s not in the same style. So there’s 5 different ways to do things and just getting a simple string suddenly has you casting classes and calling functions you have no clue about. And there’s a ton of different ways to shoot your foot off without warning.

    After going to C# I haven’t looked back.


  • Agile is not about being quick, it’s about delivering what the customer actually wants. When you do Waterfall you gather all the requirements, then you sit down and code the thing. Only to find out months or years later that you delivered crap as the customer didn’t even know themselves what they wanted.

    With agile you take it one step at a time. What is important now? Get the requirements for this feature, deliver it in the next two weeks (or at least a part of it). Then the customer, which can be an actual customer, or your internal Product Owner, or a Product Manager looks it over. If the whole thing is perfect? Nice, carry on to the next thing.

    Often you find out some detail was overlooked, or a new requirement came up, or the design didn’t fully work out. So pack it into the next sprint and do it better. You’d never get this feedback if you gather “all” requirements first and then just try to go from start to finish.

    Agile certainly has its upsides when done right, unfortunately there’s not a lot of companies who manage to do so (like most I’ve been part of). Despite being messy at times, it’s still better than Waterfall. There’s too many meetings either way.





  • Hydrogen cars will never happen. Storing hydrogen is difficult, you also have to transport it on top. Which basically replicates the concept of gas stations with added difficulty.

    EVs make much more sense, transporting power is easy and the car doesn’t care where it comes from. Beides the possibility to produce your own.

    Upgrading the energy grid and adding a good mix of renewables is the way. But here we are with people crying that wind turbines are ugly and kill birds, while we burn coal and their outdoor cat is playing bird terminator.



  • There were 3 issues at once, so “trust & safety” is definitely part of it.

    1. Too much traffic use, this is purely a billing issue and CF probably wouldn’t even care (they haven’t for years) despite losing money
    2. Violating ToS with the domains, a minor infraction probably, but enough to cancel the contract
    3. This is the big one: CF uses one pool of IPs for all customers, the IP of a gambling site (like a casino) will get banned by ISPs of various countries (Gambling being illegal, strictly regulated and so on). This is the trust & safety issue, CF is actively hurting by keeping this customer. The enterprise plan they want to push them to has ByoIP (Bring your own IP), which would probably have been one condition of keeping them on. CF could have communicated better (if we got the full story here…), but for $250 a month they’d much rather kick the customer off their service

  • From the additional info I read, it sounds more like the traffic wasn’t the main issue.

    Gambling is forbidden in a lot of countries or heavily regulated. Cloudflare uses a common IP pool for all customers, so a casino customer would possibly get their IPs blacklisted (by various ISPs). The Enterprise tier of Cloudflare has “Bring your own IP (ByoIP)”, which they probably wanted to force onto this problematic customer to protect their business.

    So it’s actually a problem, not just them paying not enough (which is another reason to get rid of them as fast as possible).



  • As I said in another comment: The up-front payment is the only thing that makes sense for Cloudflare. You got a customer that’s costing you money each month. They broke ToS. You offer them a deal still to keep the services running. And their CEO/CFO tells you they are looking at other providers like Fastly.

    If Cloudflare gave them a monthly contract then the casino would simply pay for a month and switch over their services to a competitor in that time. So Cloudflare loses all the money from the past (where the casino used far too much traffic) and will barely recoup 10k (minus the running cost, so more likely 7k at the high end) for a single month. It’s just not worth it.

    So they offer: Stick with us for a full year at least or get fucked. Which is fair.


  • Is there? The casino is on a cheap $250 a month plan they don’t belong on and they broke ToS with the domains. While also costing Cloudflare money each month (as the casino admits themselves, their traffic alone is worth up to $2000 a month).

    It’s absolutely in the right of Cloudflare to drop a customer that’s bothersome. Casinos usually are (regulations, going around country restrictions), them costing them money on top is a massive issue.

    120k a year is a big slap of course, but it’s probably the amount Cloudflare would want to keep them on as a customer. If they leave, so be it.

    I’ve seen it several times before at companies I worked at. They cheaped out and went with a tiny service plan to coast by. Or even broke ToS because it would be cheaper. That usually got stopped by plans getting dropped (GitLab Bronze for example), cheap plans getting limited, or the sales team sending a ‘friendly’ message that we’re abusing their plan and how we’re going to fix it. If you don’t play along at that point you’re going to get the hammer dropped on you.

    It also wasn’t 24h as the title says, the first communication happened in April. At that point they should have started to scramble, either upgrading to a bigger tier immediately or switching providers. And it’s totally normal to go to the sales team when you break the ToS of your plan or you abuse a smaller plan. They’re going to discuss terms, it’s not a technical issue.

    Edit: And I should also say, the whole “paying for a whole year is extortion” is bullshit too. Their CFO or CEO told Cloudflare they are looking at switching providers (as they looked at Fastly). So of fucking course Cloudflare is going to demand a full year upfront. Otherwise the casino could pay for a single month and during that month they switch away to another provider. So Cloudflare would still be thousands in the red with that ex-customer after they used so much traffic the last few years.