• 7 Posts
  • 52 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle



  • I was thinking long and hard about this to form an opinion, but my answer is no.

    The final decission point was: I’m from Slovakia, it’s no secret that Russia would love to take us under their sphere of influence. You and your instance is not only supporting this, you’re actively propagating this. In fact, I’m pretty sure if Russian soldiers would be at my doorstep, threatening my family, you and your instance would be cheering. And when I would realize, that I actively supported this, that would break me.

    If you’re about to publish your work for free, I gladly use it as long as it’s run by good people like lemmy.world. This way you get no support from me. If I’d pay you, I don’t know what part of my support would end up in .ml instance which I see as a propaganda machine against countries like mine. And even if you say that none of my money would end up there, I kind of don’t want to support you as a human being. I won’t pay your salary so you have energy to do what you do on .ml instance.

    If Lemmy as a project dies, so be it. Foss world can always spark successful forks (see OpenElec vs LibreElec) and alternatives like PieFed already exist


  • I wouldn’t say you made a mistake. Lemmy is still a great place and instances like lemmy.world you’re on, are run by down to earth people like you and me.

    It’s just that Lemmy’s core code is (primarily) developed by people who … well, have some opinions. However, that probably shouldn’t even matter. Developers’ opinions are just that - opinions. They don’t put any of their opinions into the code. And that code is then taken by people of lemmy.world to run the instance.

    And up until now it wasn’t a big issue, it was more like a curiosity “Hah, this great piece of software is developed by those guys. Well I strongly disagree with them and want to have nothing with their instance and their opinions”. But now it starts to be an issue when they ask for money. People are naturally reluctant









  • I see the next BF will be developed by Dice and 4 other teams? Well I wish them luck on good cooperation but that sounds really scary team-wise.

    But who knows, maybe it’ll help. Because Dice is … ok well I’m old so I don’t know if this is still true but I remember them as one of those studios that just keeps fucking things up. Bugs on bugs. Them and Creative Asembly (Total War). But as I said, I’m old, not sure how things look now

    Bonus rant: But boy, I remember one bug they introduced in BF3 with one patch. The bug was that the under-barrel shotgun attachement didn’t have its own damage, but took the damage from main weapon i.e. 12 pellets x 25 HP = 300 HP. I mean, shit happens but how much of a mess there’s in the code that this happens? I’d genuinely love to see that code. And! And! That testers don’t catch it during testing! How? That it flows through all the stages up to the production. Do you even have some tests? Is there a QA team? And I know I’m not crazy because as a follow up, the EA tried to step in to put things in order. Rant over


  • In my opinion yes, unfortunately. It’ll suffer from Gartner hype cycle soon but it’ll recover and will slowly get better every year to the point it’s really good.

    The worst thing is that I don’t see any “stop sign”. Like f.e. with self driving cars it was kind of obvious that it’ll get ridiculously complex in real life situations, thus having a problem with legislation and mass adoption. But with AI? I don’t know, I don’t see any stop sign … Maybe that it never reaches this high mark we all expect?



  • small tasks that you don’t expect to grow in complexity

    On one conference I heard saying: “There is no such thing as temporary solution and there is no such thing as proof of concept”. It’s an overexaguration of course but it has some truth to it - there’s a high chance that your “small change” or PoC will be used for the next 20 years so write it as robust and resilient as possible and document it. In other words everything will be extended, everything will be maintained, everything will change hands.

    So to your point - is bash production ready? Well, depends. Do you have it in git? Is it part of some automation pipeline? Is it properly documented? Do you by chance have some tests for it? Then yes, it’s production ready.

    If you just “write this quick script and run it in cron” then no. Because in 10 years people will pull their hair screaming “what the hell is hapenning?!”

    Edit: or worse, they’ll scream it during the next incident that’ll happen at 2 AM on Sunday