Name a more stressful moment in tech

I have to check it like five times even if it's just a flash drive

I don't think it's badly designed, it's designed to allow the user to do whatever the fuck they want, unlike your favorite walled garden.

Oh you mean just like Microsoft who "accidentally" makes people's files deleted when they upgrade?

You'd think that could include concatenating the strings on rm to avoid this exact problem?

What do you mean? Windows always requires a reformat when installing

Attached: file.png (918x603, 100K)

>You'd think that could include concatenating the strings on rm to avoid this exact problem?
I don't think I understand what do you mean but whatever the case rm does what you tell it to do. No UNIX-like tools will hold your hand, even if you're doing something potentially stupid. Even so the only way you can break a system with rm is when being root or using sudo, so you have double responsibility.

Can't you delete important .dll files from system32 on Windows with an elevated cmd or Powershell? It's the same thing.

>Name a more stressful moment in tech. You can't
"now that we've gotten to know a bit more about your background, we'd like to ask you a few technical questions..."

Attached: whiteboard.jpg (500x500, 22K)

Attached: serveimage.jpg (197x256, 17K)

>A port is flapping

If they concatenated $0 $1 ... $n so it avoids a miss typed space being a problem?

>Can't you delete important .dll files from system32 on Windows with an elevated cmd or Powershell? It's the same thing.
You'd have to go out of your way to delete windows files, since they're in their own little folder, it's not going to happen by a mistyped space.
More importantly, powershell seems to do exactly what I said to avoid removing files by mistake, old cmd based versions did not however and would behave like rm on linux, pic related.

Attached: Untitled.png (877x402, 48K)

At least it's not as bad as having your entire system wiped out when even a big corporation can fuck up because your entire system is under a single directory.

At least on windows a different partition is under a different base directory, so you know, even if you wipe out an entire paritition, you haven't lost everything else in the other ones.

Attached: serveimage.png (788x378, 40K)

Runing patcher/patched/keygen.exe even when over half of the AV engines in virustotal claims it's safe.

I had to call Microsoft nearly every fucking day because Windows XP would never activate on a fresh install on certain OEM systems. It would fail saying invalid key and I'd have to talk to either pajeetdeep or robodialer to read out the key every fucking day.

I mean not exactly what I said, but putting a safeguard there.

>system too stupid to proofread user input

Happened before with Bungie, has happened before with other companies, for pretty much any operating system. It's not exclusive to Linux, nor is Windows 100% unaffected by such mistakes.

Well, obviously it isn't 100% unaffected, but it handles it far better.

How so? If you run an installer/uninstaller, Windows will ask for higher priveledges. Once you give the program that it can basically do whatever, so if it were to begin to delete things, the only advantage you have with Windows is that it wouldn't be able to delete files that are in use, and that's only because Windows can't open/edit/change already opened files.

Nightmare fuel

Ctrl + C

when you want to play some halo 3 but when you turn on the xbox you get three red flashy bois instead

>so if it were to begin to delete things, the only advantage you have with Windows is that it wouldn't be able to delete files that are in use
Sure, though I don't like that I can't delete files that are in use myself.
I'm not talking about ill intentioned programs, but accidents.

An accident on windows from similar causes as will at most result in a single partition being nuked, and the current safe guards on powershell
Means that it's even harder for mistyped spaces to cause a problem like pic, plus windows programs are under program files, so adding quotes to a windows command is a necessity in the first place, this should minimize developer mistakes.

All in all, better file organization.

Attached: Programming - 05.jpg (900x900, 97K)

You have never updated your BIOS or HDD firmware, have you?

I nuked a 5-disk SCSI stack with data from 20 years ago of all my old renders and stuff doing that. Family pictures, school pictures of my dead brother, all gone

Luckily I backed it all up before doing that

>dev made script run in quiet mode :^) or you got up to drink some coffee while installing or uninstalling a program
>your entire system is nuked from a mistyped space

>mfw found 5 dollar 3dfx Voodoo 5500 PCI MAC
>mfw flashing the BIOS to PC

It was successful btw

Attached: proxy.duckduckgo.com.jpg (474x432, 22K)

11:59pm GMT December 31, 1999

>You'd think that could include concatenating the strings on rm to avoid this exact problem?
Then how the fuck would you specify multiple arguments?
rm one /two
has a complely different meaning than
rm one/two

Well, you could have the path specified by a flag? Or throw an exception like on windows?

Throw an exception for what? Trying to delete two files at a time? Are you retarded?

>whiteboard interviews
nah I'm good

see
For how it looks on powershell and on cmd, on powershell, if you just shove a second file in there it throws an exception in your face.

So if I want to delete 5 files I should have to type out 5 different rm commands so that my OS can babysit me?

No, you use a better syntax, every file path in the powershell rm is separated by a comma so they get all put in the same array, if you try shoving one with a space in it will throw an exception in your face.

Attached: Untitled.png (877x402, 45K)

idiot
low test

Attached: high test.jpg (422x392, 28K)

You can do the exact same thing in bash by surrounding all your paths in quotes if you're that scared that you're going to accidentally press the spacebar.

You use quotes on windows too when your file path has spaces. But none of that changes the main point, that it still doesn't have any safeguards in case you don't put quotes.
And most people never use quotes, including devs (they may be more likely to on windows due to bullshit like program files being separated by a space, but that's not my point).
So safeguards are required, a simple improvement on the way the rm command works would solve a lot of the problems with it.

Every modern language uses at least a comma when separating arrays already anyways.

was itdev/sda1 or 2, shit

Windows power shell is ass cancer

Attached: omg.jpg (211x160, 5K)

>Keeps your files safe from mistakes by retarded coders and even yourself
>Still allows you full freedom
>Cancer
What?

>
>>Keeps your files safe from mistakes by retarded coders and even yourself
>>Still allows you full freedom
>>Cancer
>What?

It's called BASH, you mongoloid.

Attached: lemongrab.gif (320x223, 204K)

When you push the power button and nothing happens for a moment.

rm * needs to work, and * expands to a space separated list of files.

Well, powershell does have a lot of problem, I have to agree with that, but it handles rm in a far better way.

>RemoveWAT
>not Daz

waiting for first post on a new build
>tfw z270 asus mobo takes just shy of 10 seconds

Does not enable features tho, useless.

I format everything for LULZ and also im a badass and also I upload my important things to the cloud so the corporations can comb my data but they wont find anything fun to do with it so I'm getting free storage for my photoshop files and other generic garbage and also I like the feel of when you format a drive, it feels like heaven tbhdesu.

Well, I'm not a linux expert to be able to think of the best solution, but it should work as long as a comma for example is put between each file?

Deleting a table on prod

Well, I'm not a linux expert, but it should work as long as a comma is put between each file for example?

>What do you mean? Windows always requires a reformat when installing
it wasn't always like that, and there's no good reason it needs to be like that now, given that the file system isn't changing much if at all

When I was a kid installing Win95 and needing to find that old floppy disk that had a god damned cd-rom driver on it. You all 'members. You had to keep it somewhere safe in your messy ass room.

Attached: dos generic cd-rom driver.png (736x472, 41K)

Fuck that, that latch on LGA sockets are sketchy as such. I'm always worried I'll break something.

As fuck, rather.

That would be changing POSIX. * expands to a space separated list.

POSIX has the correct approach to FS hierarchy. Make a mistake, data is bake. If your OS holds your hand you'll learn it's OK to do dumb shit and will know you should do better next time.

will not know*

Can't it detect that the input is a wild card? If so it should be trivial to parse only the stuff sent in by the wildcard.

As if that was the approach of POSIX, if it was you'd be running everything on root with ring 0.

tfw winbabbies need hand holding to operate a command line because they scared to hit the space bar with their greasy mcdonalds fat fingers

imagine being at computers

IT'S EITHER ALL OR NOTHING, PRAISE KEK GUISE

>OS handholds him by not let him do anything important unless he runs as root
>preventing data loss?
>that's one step too far
And to think before windows vista people would point out how having a need for a root account was one of the advantages of linux since it improved security.

Get these fucking kiddies out of linux.

how hard is to understand that when you're root you're responsible of your own fat finger mistakes. the os shouldn't babysit the user babbyboi

You must be a great driver

>sudo cryptsetup luksformat /dev/sdb[2]
>YES
NO

>dump bios before flashing
oof, wow no problem now

I use to get if/of confused and made a horrible mistake one day and now I don't make that mistake anymore

Attached: 1527309976929.png (661x812, 991K)

What features

a working updater

It updates though
Literally no side effects

Because you never gave permission to a program to execute as root right? You don't even need to be root, you can have your home folder nuked just fine without that.

Like I pointed before with steam. Linux has plenty of good stuff, but the file system organization and the way it handles rm is not one of them.
Besides, throwing an exception or changing a single command is hardly hand holding.

Windows Update doesn't work if the OS is not activated, if yours is working the program you are using does more than just getting rid of the nag.

Works on my machine

Attached: counterfeit.gif (366x251, 11K)

You are using an activator, of course it works. But anyway, enjoy your russian backdoors if using the most common methods bothers you so much.

>applying for a recordkeeping position at a local hospital
>not even remotely related to tech
>no whiteboard in sight
>"Alright, and on to logistics. We heard you had a background in computer science..."
>some lackey-ass motherfucker furiously wheels a whiteboard into the office and locks the door behind him

Dude don't make me boot up my laptop.
It has no serial on Computer and Windows update works.
Are you talking about Windows 10? I'm talking about 7 since the activation image OP posted is from 7.

Well of course, you can delete the things your user owns and has write permissions, it's exactly like Windows. However, just because Powershell does it differently it doesn't mean any is better. I don't want any commands to make their own twisted interpretations of what I write

There is literally no activator for Windows that isn't a virus.

even the microsoft one?

Especially the Microsoft one

github.com/Wind4/vlmcsd

>Just got a netbook in the mail today
>BIOS is not last version available
>follow instructions to the letter
>BIOS flash based update program
>PLEASE WAIT WHILE BIOS UPDATES
>no change
>no change
>almost ten minutes later
>just about to force-turn off the machine by holding power button down
>press and hold button for like a minute
>stays on anyways
>just about to unplug it when BIOS update says finished successfully

Took a couple years off my life jesus fuck

Then it wasn't all gone

rm does not see the wildcard. Bash expands it into a list of files before rm is executed.

they have an artificial delay of about 60 seconds while it verifies to prevent mass attempts

Rebooting Windows server 200x

Kek. Brings back memories.
I had a falling apart K6-2 back in the day. Two out of three Windows 2000 boots resulted in some disaster (rolling bluescreens, missing hard disks, just hanging on startup). But once it was going, it would happily run perfectly for months. Always hairy if the power went out or something.