I love the argument about c having type safety with the little side-swipe at rust. “AcTuAlLy C does have type safety! You just have to jump through the following 50 hoops to get it!”. I’m an outsider to both C and Rust but it’s still funny.
Only heard a couple people talk about it online (that I trust to be reasonable) and they basically said it was fine but didn’t blow them away. And that’s fine but it makes for boring “cOnTeNt”.
Ok hear me out. I’m a book author, I write a book and try to sell it for £100 while all my peers are selling books at 60 or 70. I spend the most money imaginable making my book. It’s quite possibly the largest book in existence thanks to the effort of me and 5000 other people. I lie awake at night worrying that we’ll never make back the money we’ve spent on it.
Wait what’s this? Some team of less than 10 people has written a 3-page book and sold it for 2.50? And people are… Buying it?! But why? Look at the size of my book, clearly it must be better because it’s so big, so fancy, so expensive! Every letter cost me millions! I read the 3-page book. It doesn’t have money dropping from each letter like mine. It has a beginning, middle and end but mine has 500 acts each more expensive than the last. Surely it’s not that good… It’s pretty great actually. I have learned nothing from this experience, even though it’s happened a hundred times. I will still make more money than entire countries, somehow.
The ELI5 version is that developers can make a lot of assumptions about what a Windows pc means and what features are available. A while ago if you had videos as part of a game (for example a cutscene) it was actually played through Windows Media Player, which was virtually guaranteed to be present on the user’s computer. Sure you can play that video with other tools like VLC or Quicktime, but you couldn’t guarantee they were installed, so Windows Media Player was a safe bet. Nowadays that’s not how video is handled but the point remains for a few other things. For example if I need to load an image, maybe a background, I would look it up using the windows filesystem, so probably something like C:\Program Files\Steam\common\mygame\images\background.png. That’s not the same in the Linux or another os. Also the piece of software that handles loading images might be different, which means how we execute that load operation is probably different, and so our Windows-focused version of our game just doesn’t work.
Fortunately nowadays that’s a mostly solved problem with Steam investing a lot of time into Proton, what they call a “compatibility layer” that basically translates all of the windows-specific stuff to work in Linux. That’s a very simplified explanation but you get the idea. The games that still won’t run have kernel-level anticheat (Valorant, Helldivers 2) or are so dependent on things only available on Windows that even Proton can’t fix it. Some anti-cheat software doesn’t run properly so then you can’t go online, like Warhammer: Vermintide 2. That’s mostly a commercial decision rather than technical, they could make it work they just choose not to.
The fact Microsoft isn’t mentioned astounds me.
We have rules?
The main draw to the CLI for me is portability. I’ve been a dev for ten years now and used tons of different editors on different platforms and while each one had a different way to describe the changes, how to commit, or how to “sync” (shudder), the CLI hasn’t changed. I didn’t have to relearn a vital part of my workflow just because I wanted to try a different editor.
The self-contained electron app works better for most people I think.
I believe it’s 1% for access to the “entire post-open ecosystem”, rather than 1% per project which would be unreasonable. So you could use one or thousands of projects under the Post-open banner, but still pay 1%.
It will take years to develop the post-open ecosystem to be something worth spending that much on.
I would be curious how this actually works in practice. What counts as “in progress”? Encounters? Plot points? Knowledge that a goblin has? If all of those things are “in progress” and you can only have so many things in the “in progress” column, I feel like you’d very quickly have to break that rule and then everything becomes “in progress”.
Literally just bought what I believe to be last generation’s X13 on ebay for half the price of the new one. It’s been great so far, especially with the power efficiency of Ryzen CPUs. My one complaint is the soldered RAM, which judging by the new lineup is getting phased out, thankfully.
My specific point here was about how this friend doesn’t trust the results AND still goes to Google/others to verify, so he’s effectively doubled his workload for every search.
I’ve had this argument with friends a lot recently.
Them: it’s so cool that I can just ask chatgpt to summarise something and I can get a concise answer rather than googling a lot for the same thing.
Me: But it gets things wrong all the time.
Them: Oh I know so I Google it anyway.
Doesn’t make sense to me.
I’ve been programming for too long, my brain just autocorrected the typo so initially didn’t get the joke…
Again, this existed before AI. Typo squatting, supply chain attacks, automated package uploads, CI pipeline infection, they’re all known attack vectors. That’s not to say this isn’t a concern, just that it’s a known risk and the addition of “AI” doesn’t, to my eyes, increase that risk. If your SSH keys don’t require a password, you have taken the decision to make those keys less secure but more convenient to use. That’s pretty much always the tradeoff in security.
The risk here is slightly overblown or misrepresented. Just because a fork exists doesn’t mean that anyone has even read it, let alone run it on their system. For this to be a real threat they would have to publish packages with identical or similar names (ie typo-squatting) to public package repositories which this article didn’t have any information on but which is a known problem long before AI. The level of obfuscation and number of repos affected is impressive but ultimately unlikely to have widespread impact to anyone besides GitHub.
Personally I rename them to something meaningful and they get merged if there are no other references. PayPal is especially bad for completely meaningless rubbish in the payee field and they tend to be ad-hoc purchases so I don’t fiddle with them much. The category is the most relevant bit for me.
Bit of an alarmist headline here. The vulnerability has been patched in the most common clients (openssh) and it was because the protocol wasn’t being implemented correctly. To say that the SSH protocol “just got a lot weaker” is just not true.
Why are people weaving social media and the internet into a single thread? The internet is so vast, social media makes up a tiny sliver of it.
Because to most people outside Lemmy the “internet” (by which they mean the world wide web but that’s me being a pedant) IS social media. There might as well not be anything outside the walled gardens of social media to them because they’ve been conditioned to only stay on one, maybe two platforms for years at this point. The old “what’s a browser?” question these days gets answered with “I don’t need a browser I have Facebook”. Completely nonsensical to us but to them it’s totally natural. Not being derogatory about them or anything but the 60k lemmy users and however many million on Reddit are not the majority. Facebook with it’s 3 billion (with a b) users, IS the majority of the internet.
I booked a flight recently, the translation engine was obviously having issues so instead of giving helpful labels for form fields it was stuff like: “{{ name.first }}”, which I could figure out for the most part, but then on submission I got an error with no description at all. I opened the dev tools and resubmitted the form to find the API response which gave me the actual error. 2 pages previously a form field hadn’t been set correctly by the web page (it was a drop-down, I selected an option, the error said it was null). I managed to force the field to populate properly and hey presto, submission works. Ridiculous.