It was a wild ride, and so fun to look at, well deserved!
Computer guy, occasional gamer, shitty music producer. Denver, CO
It was a wild ride, and so fun to look at, well deserved!
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.
I mean, I get it, but when the wrong tool is used so ubiquitously, you have to start asking questions about why people aren’t using the “right” tool. Forums seem to end up being hostile to newcomers, with all this “did you search the forum first you fucking noob?” mentality. Having a living place for real-time questions and discussion just feels better, same way email exchanges feel terrible after using Slack for so long. You can still have incredibly toxic people in real-time chat servers, obviously, but there just seems to be less overall stress to keep the posts in the forum “pristine” or… whatever that was.
Not being able to search for old content is a huge con to real-time chat. Even if the history is retained forever (in self-hosted instances), real-time messages just aren’t the best bits of data to recall later like forum posts. Clear drawback.
Still, people are using discord, not to spite forums, but because it works, is free, and is easy.
Same, shit just works. I don’t even want anything I print to be color, by design, because it always is terrible anyway.
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
These would actually make for a very hilarious tournament of sorts…
Would be funnier if it was just “JS” on the right, because obviously HTML and CSS are involved too, but JS is where all hell breaks loose
I’m sure plenty of the offenders are legitimate, but it’s completely safe to check private key pairs into code, or to bake them in to images. It entirely depends on what the key pairs are used for. Very common to include key pairs for development/test environments, for example. If it’s a production secret, of course you don’t do this.
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.
You see the irony here, right?
Rocket League. Games are quick, you can play one or many in a session. I don’t know if epic has ruined it yet, but last I played the good old core game was still there.