What a weird combination of suggestions.

“Enjoy nature! Volunteer! Support local projects! Litter.your community with graffiti!”

Honestly, these days it’s pretty simple. The thing you need to remember is that you do not need to know EVERYTHING all at once. Learn a little bit, use it, keep what you use, discard what you don’t, get it in muscle memory, and learn a bit more. Very quickly you’ll be zooming through vim.

You can learn the basics, and go from there- the basics of vim (which imo everyone should know- vi is often the fallback editor), and then you can just casually learn stuff as you go.

Here’s the basics for modern default/standard vim: Arrow keys move you around like you expect in all ‘modes’ (there’s some arguments about if you should be using arrow keys in the vim community- for now, consider them a crutch that lets you learn other things). There’s two ‘modes’- command mode, and edit mode.

Edit mode acts like a standard, traditional text editor, though a lot of your keybinds (e.g. ctrl-c/ctrl-v) don’t work.

Press escape to go back into command mode (in command mode, esc does nothing- esc is always safe to use. If you get lost/trapped/are confused, just keep hitting escape and you’ll drop into command mode). You start vim in command mode. Press i to go into edit mode at your current cursor position.

To exit vim entirely, go to command mode (esc), and type :wq<enter>.

‘:’ is ‘issue command string’,

‘w’ is ‘write’, aka save,

‘q’ is quit.

In other words, ‘:wq’ is ‘save and quit’

‘:q’ is quit without saving, ‘:w’ is save and don’t quit. Logical.

Depending on your terminal, you can probably select text with your mouse and have it be copied and then pasted with shift-ins in edit mode, which is a terminal thing and not a vim thing, because vim ties into it natively.

That gets you started with basically all the same features as nano, except they work in a minimal environment and you can build them up to start taking advantage of command mode, which is where the power and speed of vim start coming into play.

For example ‘i’ puts you in edit mode on the spot- capital i puts you in command mode at the beginning of the line. a is edit mode after your spot- capital A is edit mode at the end of the current line.

Do you need these to use vim? Nope. Once you learn them, start using them, and have them as muscle memory, is it vastly faster to use? Yes. And there’s hundreds of keybinds like that, all of which are fairly logical once you know the logic behind them- ‘insert’ and ‘after’ for i/a, for example.

Fair warning, vim is old enough that the logic may seem arcane sometimes- e.g. instead of ‘copy and paste’ vim has ‘yank and put,’ because copy/paste didn’t exist yet, so the keybinds for copy/paste are y and p.

Violence is never the answer, but sometimes it’s a damn good way to cancel like terms so you can find the answer.

I’d you want immutability and things that just works, snaps are the exact opposite of what he needs. I’m gearing up to swap away from Ubuntu for the same reasons as him, and the snap ecosystem is utterly fucked and accelerating my timetable daily.

I’ve never seen something so damn broken, and it gets more so every update. It’s gotten to the point of where snap store will just straight up log me out of my session out of the blue when it finds an update so it can install it, losing all of my work.

He’s checking the bollard for scratches after a nazi drove a u-haul into it

Now it can make shit up and gaslight you with MULTIPLE senses!

That’s a really terrible misrepresentation of what happened.You should probably investigate this matter more. This article is supremely biased and basically outright wrong.

The quote you gave, for example, is an almost cartoonist level of distortion of the facts.

This just in, corporate apologist media thinks Internet Archive should go away.

Why is this trash here?

In the case of Discourse, a hardware engineer is an embarrassment not deserving of a job if they can’t hit 90% of the performance of an all-time-great performance team but, as a software engineer, delivering 3% the performance of a non-highly-optimized application like MyBB is no problem. In Knuth’s case, hardware engineers gave programmers a 100x performance increase every decade for decades with little to no work on the part of programmers. The moment this slowed down and programmers had to adapt to take advantage of new hardware, hardware engineers were “all out of ideas”, but learning a few “new” (1970s and 1980s era) ideas to take advantage of current hardware would be a waste of time.

You can really tell this guy is some hardware design engineer at nvidia that has absolutely no fucking clue about how real-world user space programming works. Also I like how 74% slowly kept getting inflated until it became 90%.

Like, this dude is trying to claim that fucking Donald Knuth himfuckingself cannot figure out some new computer hardware.

Multiple processors working in concert is not, and never has been, a cure-all. It’s highly situational and generally not useful.

What’s dumb is that, as a Systems Design Engineer at NVIDIA, Dan Luu should know that. After all, how has SLI been doing recently?

That said, yes, of course, web dev bloat is absolutely out of control, and slow websites absolutely have nothing to do with hardware or network. That’s a culprit of bad frameworks, horrific amounts of ads/trackers/bullshit, and honestly just general lack of programming fundamentals in the web dev space. Might as well call them web technicians and really ruffle some feathers. :P

I don’t think you are appreciating just how completely absurdly broken an unshackled FPS bot is. A chess bot will beat you. An FPS bot will not even allow you to play.

I’m not even kidding, an FPS bot will literally kill you from across the entire map, through a wall, with a perfect headshot, long before it would even be possible for you to know where the bot even is.

An unshackled FPS bot knows where you are at all times, how you’re moving, and can execute tick-perfect headshots the very second it can kill you, and it will never miss, even on full auto. It will fire a shot that goes through three sub-pixel-wide gaps and through a wall to instantly kill you, because it can calculate every single angle to get that kill faster than the server can even do a game update.

Humans may not stand a chance against a chess bot, but at least they can play a match against one. Against an FPS bot, you don’t even get to play the match, you just lose.

This is actually pretty funny- bots are INTENTIONALLY dumbed down in FPSs, because they would be unstoppable, unkillable gods otherwise. An unshackled FPS bot would make a chess bot look like a rank amateur in how hard it would dominate the top tier of professionals compared to the chess bot.

Samir Dinesh, you’re breaking the car!

Use Firefox. Add-ons that work for desktop on Firefox also work on mobile.

In very short- they did a lot.of shit to him, treated him like garbage the entire way, and then at the very end they literally tried to bribe him into being the scapegoat for the backlash they intentionally caused.

It’s not unreasonable to expect a game to be, to the publisher’s knowledge, bug free. In fact, it’s not just reasonable, as a programmer, it’s fucking baseline.

Most game devs are a fucking embarrassment, and they deserve to be dragged.

Depending on the skin color of the person living in your attic, you can.

They prefer to be called cops though.