It was a wild ride, and so fun to look at, well deserved!

Also, how do I verify that this fork isn’t malware wrapped in emulator code?

The code is open source, you read it all, ensure that you download exactly the code you read, and you compile it yourself. That’s the only way, in general, to accomplish this.

I enjoy it, started playing recently! All the fun for me is in trying to find good loadouts completely on my own. I don’t want to watch some YouTuber show me the absolute maxed out best loadout, because that’s the entertainment to me. Progress is slow, I still haven’t cleared the game lol, but when I do, I know it will be my own choices that got me there. No shame in researching how to win if that’s your thing, I just love diving into games like this blind.

Do meeee
Talk about the burns

The JetBrains AI plugin wants to be activated so badly, but legal says we can only use GitHub copilot. The copilot plugin is really good so I don’t mind, but we all know the data is going to OpenAI regardless of the plugin. Data sovereignty will only be achieved by running these services locally.

You have to listen to your heart, at least once in your career, to learn that grass on the other side is covered in just as much dog shit as it is over here.

deleted by creator

Will be interesting to see the new “verification” methods that people come up with. AI won’t be good at “weird” things, like, I dunno, putting your shirt over your head and doing a jumping jack. At least until millions of those videos exist, then time for a new move? It’s not like people will just give up because this tech exists, we have the entirety of human history to tell us that much.

Hardly surprising, the point of building a cookie cutter is to mass produce cookies

I think it is fantastic. Great level design, some of the wonder flowers had me laughing and some had me crying, though I have yet to 100% it (getting close). It’s 2D Mario done well! It’s not supposed to be baldurs gate level deep, it’s Mario wahooo

Isn’t it that horrid ugly fucking foot

Read… instructions? I love teaching people that git very often prints out what you should do next.

git: “to continue, resolve conflicts, add files, and run rebase —continue”
dev: …time to search stack overflow

All that said… just use lazygit. It does help to know CLI git first to put things in context, but if you do, no need to punish yourself every day by not using a UI.

fzf? https://github.com/junegunn/fzf

Out of the box, would only help searching shell commands that have been run, so for files, things like “vim file.txt”, which is obviously not usually how files are edited (you’d use the file browser in a text editor or IDE)

However if you find a way to list all files on your system by modified time, you can pipe it to fzf for a slick fuzzy find search.

Maybe ag would work here too: https://github.com/ggreer/the_silver_searcher

Debugger good for microscopic surgery, log stream good for real time macro view. Both perspectives needed.

Aw gee guys we are soooo sowwyyyy that we hurt your feefees

deleted by creator

Well, the intent behind adding DRM at first is to maximize profit by making piracy more difficult. Trust me I hate DRM too, but it’s not like they add it for no reason.

I feel like this is just a new cash grab technique, and it’s actually pretty smart. The audience of people who will buy immediately despite DRM will do their thing, first wave of money complete. Over the next few years, trickle in more cash through steam sales. Once that well dries, get one more wave of cash by removing DRM, which appeases the audience that abstained the whole time, collecting their cash.

Edit: my half baked conspiracy theory got some attention. the argument that companies remove DRM like Denuvo because of cost makes way more sense, Occam’s razor holds true. Both can be true, they save money by removing the DRM, which has the nice side-effect of creating a small new wave of sales. Win/win. I’m sure Denuvo hates this and will one day make it more difficult for studios to just remove their software, because money.

Christ, do this many people really find iso8601 hard to read? It’s the date and the time with a T in the middle.

It’s here, it’s there, it’s everywhere. The problem with replacing things that work with something “better” is that “better” is subjective, so you end up with a new “better” way every few years, and maintaining existing systems becomes a god awful slog. See the JavaScript ecosystem.

The bash I wrote 10 years ago still works today, and it will still work in 10 more years. The same bash will very likely work on your computer, on a remote server, etc. This is the power of not chasing “better” all the time.

Try running a Ruby or Node program from 10 years ago today on your computer. Now, try running it on a random Linux server.

Please do not take this as a slight against Ruby or Node, or any other high level programming language. Bash compared to those is simply apples and oranges, they are not the same thing.

By all means, if you have a project that requires a Ruby runtime anyway, write operational scripts with Ruby, run them with Rake, etc.

Want a portable script that doesn’t depend on a complex runtime? Use bash.

If bash is too limiting, use Perl. No, seriously. Perl is fine. It is about as ubiquitously available as bash, and the standard library likely has what you need to get the job done. People blindly dismiss Perl because some blog post told them to, usually in the context of writing application code. You’re not writing application code, you’re writing scripts. Would you write an application with bash? No.