He made $12000 off each fired employee.

Yeah, you enjoy your day and your strawman arguement you ‘won’ against as well.

Also, c’mon, their criticism of this decision in the sentence just before it heavily implies that.

That’s literally not how that works, and you even agree in the paragraph above this one. Why are you even arguing about this?

As for twitch’s working conditions, it’s a company ran by amazon, with management by amazon, so it has a lot of the same problems. From what I understand, the hours are shit, everything is a metric that’s impossible to meet, you’re constantly at risk of being laid off, a lot of the management are jackasses, and it’s very much a bunch of little fiefdoms trying to flex their position and abuse any amount of power they can.

Like, I can sum it up as simply as “Know how terrible twitch mods are? Imagine working for one.”

Not quite as bad as the conditions working in an amazon warehouse, sure, but still not something anyone should have to put up with. Regular inhuman working conditions with a focus on gaslighting and abuse, as opposed to an amazon warehouse’s egregiously inhuman working conditions which are focused more on physical abuse.

They’re talking about the working conditions in general, which are indeed deplorable. They’re not saying this specific act is proof of it, or even an example of it.

Reading comprehension, dude.

Google is spending a lot of cash to make Firefox look bad so people are unmotivated to change away from Chrome when manifest v3 is fully rolled out.

Because it’s cheaper than actually implementing working anti heat instead of just stealing control of your computer and leaving gaping vulnerabilities on it.

After all, why would they care? It’s not their computer.

Google really wants to make sure you can’t escape their ad-riddled bullshit when they get rid of Manifest v2

Removed by mod

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.

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.

Man, there is a LOT of people in this thread hoping to normalize this, or pretend it will happen anyway, or that it’s ‘not really a PR disaster’, or that people will ignore it, or-

Go make your money elsewhere, christ.

That didn’t stop everyone from jumping on GPT, either.

The problem here is “reasonable court.” One party in the US has spent decades stacking the courts with unreasonable judges who will agree to anything a corporation hands them.

np

gdb gives you waaaaaaaaaaaaaaay more than a stack trace.

https://wiki.ubuntu.com/Apport

It intentionally acts as an intercept for such things, so that core dumps can be nicely packaged up and sent to maintainers in a GUI-friendly way so maintainers can get valuable debugging information even from non-tech-savvy users. If you’re running something on the terminal, it won’t be intercepted and the core dump will be put in the working directory of the binary, but if you executed it through the GUI it will.

Assuming, of course, you turn crash interception on- it’s off by default since it might contain sensitive info. Apport itself is always on and running to handle Ubuntu errors, but the crash interception needs enabled.

Imagine if you knew the most basic foundational features of the language you were using.

Next we’ll teach you about this neat thing called the compiler.

Correct, I agree you run it with an eye on it (which you should probably do anyway) instead of firing and forgetting (which, to nginx’s credit, is typically stable enough you can do that just fine).

That said, nginx treats experimental as something you explicitly run in production- when they announced they added it into experimental they actually specifically say to run it in prod in an A/B setup.

https://www.nginx.com/blog/our-roadmap-quic-http-3-support-nginx/

Because the entire design of it is to mathematically prevent you from having the option to hack or block the ads. THe way to get around it is to… not use chrome.

Really dude? I never once devolved to name calling, I stated that s/he lied when s/he made false statements. What else am I supposed to say there?

I also don’t understand how saying they doesn’t know what the subject matter s/he’s taking a stance on is ‘know-knowing’ either? S/He’s straight up said they doesn’t know what a CVE is, doesn’t know what experimental means, and while they claims to be in this field of work, they doesn’t know what a web worker is and confused a web transaction with a database transaction.

Sure, I could have been nicer about it when they started escalating, but I never made it personal, and have no intentions of doing so either.

EDIT: realized I was assuming their gender.