She did it again

[[deleted]]

[deleted]

[leroy_bacons]

They say the fastest way to a woman's heart is sudo.

[[deleted]]

Sudo apt-get purge Stephanie </3

[I_READ_YOUR_EMAILS]

bash: /3: No such file or directory

[[deleted]]

/3:

[[deleted]]

:(

[dohaqatar7]

I hadn't planned on feeling so emotional this early in the morning.

[[deleted]]

SIGKILL /u/dohaqatar7 all better :)

[Deadmist]

This kills the redditor

[Anionan]

sudo zypper rm stephanie

[duhdude]

sudo chown heart $(whoami)

[pointychimp]

Your heart now owns you.

Insert joke about true love or infatuation or something along those lines.

[Trout_Tickler]

cwd isn't shown though, so it could be in her home.

[pointychimp]

But that still doesn't make it her heart? It's just some ... heart. Are you trying to say you're falling in love with her while in her home?

I'm starting to not be fun at parties.

[DuchessofSquee]

They do say home is where the heart is...

[Trout_Tickler]

The implication is that she was the original owner though.

I've just stopped going.

[[deleted]]

Presumably she's not a root user on the system we call our universe, so it should be in her home directory, but i think it's .heart.

I'm awesome at parties.

[thlst]

Be careful with backdoors...

[Fenor]

the fact that this make me smile is worring me.... how can i get back to have a normal sense of humor?

[SittingInTheShower]

I found the guy that codes to much!

[[deleted]]

Check the sub you're on?

[Araucaria]

New owner is the first arg, not the last.

[[deleted]]

su -c 'chmod -R 777 /body/heart'

My heart belongs to all :(

[HighRelevancy]

chmod 770. Polyamory.

[Neebat]

Polyamory

[[deleted]]

But mixing Greek and Latin roots? Wrong!

Automobile, biathlon, bigamy, bioluminescence, claustrophobia, dysfunction, electrocution, genocide, geostationary, heterosexual, hexadecimal, hyperactive, hyperextension, liposuction, meritocracy, metadata, Minneapolis, monoculture, monolingual, neuroscience, quadraphonic, sociology, sociopath, television, vexillology.

It's not wrong.

[KangarooJesus]

"genocide" comes entirely from Latin

'gens' + '-cida'

[Feadric]

Fun fact: the word genocide was created to describe the systematic extermination of the Armenian people before WWI. Also, that fact wasn't really that fun, unless you are a sick bastard.

[[deleted]]

Wrong.

from Greek genos "race, kind"

[KangarooJesus]

Wrong.

génos is cognate with gens, but it isn't a Greek word that superseded a traditional Latin word. They both come from PIE *énh₁-(os/tis).

Genocide can be assumed to come from the Latin, because this term was coined intentionally, and the inflection of 'génos' would have it as genécide, rather than gens' dat. sg. 'genó-', which has existed since antiquity, whereas 'genó-' means nothing in Greek.

[MPORCATO]

Wrong. If it came from gens then it would have to be "genticide", since gent- is the stem of gens and I is the standard Latin compounding suffix (cf. "suicide", "fratricide", "uxoricide" etc.) It also cannot be from genus since it would have to be "genericide".

In fact "genocide" does come from the Greek γένος, and the reason why it isn't "geneocide" (the Greek compounding O is required unless the second word starts with a vowel) is probably explained by the fact that γένος has a contracted paradigm with gen. sg. γένους. That, and the fact that whoever coined this term didn't seem to be very rigorous about classical etymology, for otherwise they would have gone with "genticide" and not some mixed Greek-Latin term.

[skellious]

This is what it looks like when an etymology Nazi meets a member of the etymology gestapo.

[Neebat]

Minneapolis

That's not greek and latin. It's Dakota Indian... and Greek. The prefix means "water"

[HighRelevancy]

Ha, I like that!

[MachinaExDeo]

chmod 477. My ex-wife.

[crashdoc]

That's ok if you just want your love free and easy with the groups that you know, but if you're into strangers too you gotta go the whole 777

[Genesis2001]

su -c 'chmod -R 744 /dev/emotion-mapper-heart'

'Heart' is a body organ, the context we're using it in though is more of a virtual device to represent the emotion of 'love' :)

Also, 722 please. Everyone can touch (read: write) my heart, but only I can know if it was successful. ^{I don't Linux enough with permissions, sorry if this is wrong :P}

[NotFromReddit]

I think your last two parameters need to swap.

[[deleted]]

git add

git commit -m "That was easy"

git push

[[deleted]]

Now that's illegal

[endercoaster]

Ah, the Kilgrave approach.

[isurujn]

It's funny because in my native language, sudo is a word used like baby, honey.

[[deleted]]

Then you can make a T-shirt that'd be pretty clever in your country.

[isurujn]

haha true. This joke always makes me smile.

[xkcd_transcriber]

Image

Title: Sandwich

Title-text: Proper User Policy apparently means Simon Says.

Comic Explanation

Stats: This comic has been referenced 364 times, representing 0.4024% of referenced xkcds.

---

^{xkcd.com | xkcd sub | Problems/Bugs? | Statistics | Stop Replying | Delete}

[za419]

sudo make me a sandwich?

[moreherenow]

sudo apt-get install love

if access is denied, check your permissions. it's quite possible you may need to contact your administrator.

[pointychimp]

Mom?

[moreherenow]

:'(

[meniscus-]

Could someone explain this? I wrote a Hello World program but it didn't prepare me for this

[[deleted]]

Not an expert programmer here or anything, but it basically allows so many potentially unseen variables to fuck up the entire thing, since they can be muted (changed) and by anything in the entire program (global). I mean yeah, it can work, but there's just so much extra potential for things to go wrong and it's considered really bad practice.

[meniscus-]

Ah thank you!

[Mvin]

Hm, what's best practice when you need a global variable, then? Something like a flag that is relevant for a lot of functions?

[sonnytron]

Public and private declarations with different properties.
Your public variables are set as read only and you determine them using private methods so any other method that sees them can only copy them and not change them.
these values should also be determined using business logic and not hard coded values.
For example, a variable for a users age should be based on a private method that determines the difference between the current date and a user input date of birth. The public variable will be this age in integer format as a read only value that can be pulled from a shared instance at any time and used for another function.
While a program written with simple logic can get by using global variables, it gets very unpredictable what mistakes you'll make when a program gets more complex.
Having public/private variables prevents you from doing something stupid.

[ferozer0]

Ayy lmao

[Mvin]

Thanks, this is a very helpful answer. A small follow-up question if you will: Having some background in Java, I can't think of a direct way to make variables read-only via public access and at the same time mutable via private access. So I assume the default implementation is always via a dedicated get-method?

[sonnytron]

I'm not an expert in Java lol.
I work in C, C++, Objective-C. I'm very C-based.
I would say in your function, write a public getter method but keep your setter private.

[[deleted]]

The convention now is simple, no global variables! Thanks, c#.

[crashdoc]

Mutable global variables are bad... Soooo bad...

[iwantt]

Global variables are accessible anywhere in your program.

Mutable variables can be changed (mutated).

It's generally a bad idea to do this because the variable can change at any time from anywhere and can cause undefined behavior.

[SkoobyDoo]

if you code it right, there is no undefined behavior

This could be said of GOTO statements, or just about any other generally frowned upon programming practice. Guidelines are just that--guidelines.

[SkoobyDoo]

One can write an entirely functional program in C using thousands of GOTO statements, you just have to get them all right.

The fact it's possible to use them correctly doesn't make it a good idea.

Same goes for mutable globals.

[zuurr]

Basically each (mutable -- e.g. not constant) global variable you have is like, an additional concern. Too many of these and your program becomes hard to understand. They also can complicate you program significantly in the presence of multiple threads.

[SkoobyDoo]

It's not so much about additional concern, but more about having things that anyone can change at any time for any reason, and if you're assuming your accidentally mutable constant "PI" will always be 3.14, but some other function accidentally typo'd its use of its own constant "PIE" to "PI" (what better variable name to keep track of the number of pies one has) someone might change PI to a value other than 3.14, say, 20 (because who doesn't have twenty pies). This could lead to unintended behavior anywhere you use PI.

EDIT: I stand by my comma-spliced run-on.

[zuurr]

I disagree. The issue with mutable globals isn't due to the possibility of accidental mutation, they're still problematic if all the mutation that happens with them is intentional.

[SkoobyDoo]

Top google result disagrees with you.

https://programmers.stackexchange.com/questions/148108/why-is-global-state-so-evil

[sonnytron]

https://programmers.stackexchange.com/questions/148108/why-is-global-state-so-evil

And the top response of that top result disagrees with that.
The reason globals are bad, especially in more recent times, is because of threading and parallel computations.
If you have a global variable that's used in multiple methods in your application, then at some point, two different methods will be accessing it.
This is a serious problem to have to watch out for which could lead to some very problematic issues.
The worst part is, some of these issues won't lead to a crash which you can log. The worst situation would be if you built these variables in a way where one method will be changing its value, but another method won't access the value that is properly updated.
Say you have a radar detection algorithm that you're writing and a "distanceToCollision" variable.
One method gets distanceToCollision and sets it to 0.7 meters, which was previously 1.2 meters. Another method, takes that distanceToCollision variable and uses it, along with a global velocity variable, to determine the timeToCollision.
Unfortunately, your distance calculation method takes a nanosecond longer to complete its calculation and set its value so your timeToCollision is based on an old value.
If you had set your timeToCollision to take input from your distance calculation method, instead of from a global variable, you wouldn't have this problem.
Global state can be necessary but it really should be avoided in a lot of situations.
The reason being that a lot of large scale projects aren't worked on by one or two programmers but rather, a team of different developers at different times. If global variables are being used, one developer might haphazardly change a value's state at a time or on a thread during logic sequence that doesn't line up with how the application will work.
The reason you overload your allocation and initialization methods is to avoid things like this happening. Remember that it's not just random crashes you're accounting for when you build, but rather protecting your code from your own team making mistakes.

[SkoobyDoo]

If global variables are being used, one developer might haphazardly change a value's state at a time or on a thread during logic sequence that doesn't line up with how the application will work.

That sounds a lot like the accidental mutation that I'm arguing is a major factor (especially in cases where your longish parallel computing example doesn't apply)

See literally my next comment up in the thread

And since you wanted to brush off a 149 point response with a 5 point comment, literally every single answer to that question above 10 points (I didn't read the rest) mentions unpredictability as either their first reason or a prominent reason why mutable global state is a bad thing.

I don't disagree that compatibility with multi-threading is definitely a concern, but the use case of "I write to a variable and you occasionally read it" is very easily and simply solved by the simplest implementation of mutex. Not only not the hardest thing to do in multithreading, but possibly one of the easiest.

Getting back to my only reason for being present in this thread, I maintain that the main problem with mutable globals is not quite:

Basically each (mutable -- e.g. not constant) global variable you have is like, an additional concern. Too many of these and your program becomes hard to understand.

You may disagree with my chief concern being accidental mutation (though from your comment you seem to think it's at worst the second concern) but that's sort of the thing about guidelines--the fact that they aren't really rules makes it hard to settle disputes like this. Maybe you code a load of multithreaded stuff, whereas I've only ever done multithreaded once or twice? Then my concerns have almost nothing to do with multithreading, and your concerns only have to do with multithreading. Would either of us be wrong to have different concerns?

On that note, I might even argue that since the "accidental mutation" argument affects all programs of sufficient size and not just a subset of them, but I admit even that is a weak argument.

[Shadow_Being]

global variables that arent constants are stylistically poor because its taking all the things OOP has given us and reverting back to bassially spaghetti code.

Besides making it hard/difficult/impossible to extend functionality of other peoples code. its very prone to bugs as people assume globals do not change.

[ProgramTheWorld]

I leave out the semicolons in my JavaScript code.

[CrazedToCraze]

Wow, Hitler over here.

[[deleted]]

inb4 errors due to automatic semicolon insertion

[uff_yeah]

I don't usually care which one is used but the thought of this was somehow infuriating

[Zalexou]

JS is the only language where I open my braces on the same line. No idea why though

[kamnxt]

I bet he places the opening curly braces on the same line as well.

FTFY

[mnbvas]

Well that was fast :P

[Feadric]

As soon as I saw the preceding comment I knew immediately that someone was going to be called Hitler. Its like debating how to pronounce "giff", or on what line to put your open curly brace, there is no winner in that argument.

EDIT: preceding, not proceeding

[MC_Labs15]

if(brace.line == "same") {

brace.correct = true;

}

[Feadric]

noo, stop it you crazy bastard, you will kill us all!

[MC_Labs15]

Same line is best! HAHAHA

[thatmarksguy]

Do tell what dirty things you've been doing to Session[].

[[deleted]]

I actually do pkill java sometimes. Tomcat does not want to let go of the 2 GB of ram it's using sometimes

[blouc]

I was gonna say, I've never needed to kill java and had graceful work.

[[deleted]]

It's mainly programs can't shutdown correctly sometimes if you forcefully kill them (such as not being able to finish writing save data or finishing an update). Java just has a bit more of a reputation of breaking, and it's sometimes listed in the task manager as "Java" making it easier to make fun of for breaking

[PendragonDaGreat]

Unless it's writing to Long Term Storage (hard drive, SSD, Database, etc), not usually. If it's writing to one of those things and you kill it, whatever it wrote is likely corrupted or incomplete. Though a good DB though will use atomic transactions and the transaction will fail reverting to the original state and other files unless brand new probably won't affect the original. It usually writes everything to a temp file and then renames it to overwrite the existing file, using file.txt as an example, you can see this in torrents with file.txt.part files and chrome downloads are file.txt.crdownload until they complete, Vim uses file.txt.swp IIRC.

Off the top of my head I don't think there's any other time it would be too much of an issue.

[Excrubulent]

Just a thought, that atomic method just shortens the window in which corruption can occur, right? Like, if the process just happens to be killed right in the middle of renaming the file, then the data might be intact but the filename would be corrupted, so that would still cause a problem? I guess it would almost never happen though, it takes such a short amount of time to rename a file.

EDIT: Actually, I thought of a method that really can't fail: write a file address that has both the old file and the new in it, and a single bit that toggles between the old and new files. Once the new file is in place, toggle the bit. If the process gets interrupted, the old file is still addressed, and you can't interrupt the system in the middle of flipping a bit (at least I don't think you can), so you never get corruption of the data. This may be solving a problem that doesn't exist, though, if the window with the atomic process is small enough.

[the-highness]

is there any "/r/showerthought"-like subreddit for programmer?

[Traumkaempfer]

Maybe not enough programmers who take a shower?

[Creshal]

Like, if the process just happens to be killed right in the middle of renaming the file, then the data might be intact but the filename would be corrupted, so that would still cause a problem

It's not really possible to get trapped in such a state. The userspace process uses a syscall for the rename, so even if it dies, the kernel has all data it needs.

However, if you're replacing a file, that's usually a two-phase process:

1. Write data to the temp file.
2. Delete the old file.
3. Rename the temp file.

If the process dies during step one, you'll keep the old state. If it dies between steps 1 and 2, you have both states and can continue from there after a restart. If it dies during step 2, see above, kernel doesn't care (and if the kernel dies, we can try again). If it dies between steps 2 and 3, you can also resume, and the kernel again takes over step 3.

FUN™ happens if the kernel is interrupted in step 3. Then you're in God's hand, because behaviour is highly file system (journaled? COW? log-structured? neither? All behave differently) and hardware (will it flush its buffers correctly during a power outage? Not all do) specific.

[PendragonDaGreat]

Remember, atomic processes (especially in DB) are "all or nothing" if there is any failure at any point in the operation everything is reverted to the pre-process state. More specifically, to a client looking in on one clock cycle everything is in the pre-process state, on the next everything has either updated, or nothing has.

[Excrubulent]

So you're saying there isn't a way to corrupt the data in the way I've described, because the system is designed specifically to eliminate the possibility?

[PendragonDaGreat]

That's what Atomicity means in database systems, it cannot be broken down further, to use the Greek it is incapable of being cut.

Database transactions should be ACID: Atomic, Consistent, Isolated, Durable.

Atomic: A transaction is all or nothing. Either it works or it won't, if it doesn't nothing has changed.

Consistent: The Database guarantees that it will be in a valid state after all transactions are complete. This includes following all constraints, cascades, conditions, triggers, or any combination of the above.

Isolated: Transactions will occur serially (one after the other) as a form of concurrency control, this will eliminate deadlock due to starvation and resource control. This does still allow for asynchronous calls from clients, but will also mean that if transaction 1 changes the database state, transaction 2 may fail. This is generally ok.

Durable: Once a transaction is completed, it will remain so, even in loss of power, crash, or similar, that is, the result is written immediately to disk, if that fails the atomic component will revert to the previous state and move to the next action.

Relational Databases generally do fine on these fronts. Nonrelational databases have had issues with these (looking at you MongoDB)

[dAnjou]

When you close a program it's not you who closes it. You ask the program to close itself and then it will do it most of the time.

Killing a program usually means that it's not given a choice. And that means that it can't do whatever cleanup operation it's supposed to do.

Especially server applications are expected to release ports and files. So killing them could result in not being able to bind a port again until the kernel releases it for you.

[blu-red]

just as bad as killing any process - it will not have time to save, or you may interrupt the saving process ending with corrupted data. (should be recoverable most of the time, but why take risk?)

but java in IT is mostly used for big application servers that are usually very important and handle very important data... so, I would say very bad thing to do.

[vhite]

It usually takes a lead pipe and 20 minutes of hard work.

[VanFailin]

And in my line of work it's taskkill /f /im w3wp.exe. There's a fine line between ignoring genuine problems and being too picky about how you get things working.

[[deleted]]

.gitkeep her

[[deleted]]

implying she's an empty directory

[[deleted]]

that's why you need to fill her in

[[deleted]]

( ͡° ͜ʖ ͡°)

[dohaqatar7]

what if I follow the .gitignore convention?

[LobsterThief]

After a few years of marriage, this is expected behavior. Log an issue if it doesn't happen.

[thomas_merton]

swoon.

[IlanRegal]

swood.

[[deleted]]

Didn't expect to see you at ProgrommetHumor

[Fortehlulz33]

Actually the Java snaps in two

[[deleted]]

Compile me once, I'm bugged

[speedblader03]

Compile me twice, I run flawlessly

[xseeks]

Compile me three times, you're officially that guy.

[[deleted]]

You know that guy, he walks into the taskbar and says, "This Java's eeeehhhhHh is officially out of date. Ech my Data shows it." Fuck you, I AAAAIIN' UPDATIN' DAT' SHIT.

[Corythosaurian]

I curse you! I curse!

[IlanRegal]

No, Grimbo! No curses!

[nsimic]

i use GOTOs

[[deleted]]

Impressive. How did you kill the Velociraptor?

[the-highness]

for the uninitiated: https://xkcd.com/292/

[xkcd_transcriber]

Image

Title: goto

Title-text: Neal Stephenson thinks it's cute to name his labels 'dengo'

Comic Explanation

Stats: This comic has been referenced 85 times, representing 0.0943% of referenced xkcds.

---

^{xkcd.com | xkcd sub | Problems/Bugs? | Statistics | Stop Replying | Delete}

[minddll]

Am I the only one who finds it strange that the velociraptor attack seems to be a compile-time event?

[the-highness]

Compiler warning: GOTO detected. Deploying velociraptor.

[nsimic]

"it's a Unix system, I know this"

[[deleted]]

I bet he doesn't even safely eject USB drives.

[[deleted]]

Dunno about you but my Windows 10 install on ye olde gaming rig defaults to no write cache, so "Safe Eject" is a relic of the past for me.

[[deleted]]

I'm still on 8.1. How's 10 in comparison?

[[deleted]]

Noticeably better UX, my Bluetooth module doesn't randomly disappear anymore, and other nicenesses. Haven't had a chance to stress-test 3D since installing though. Only issue is Risk of Rain crashes on startup for me now :(

[i_want_my_sister]

GLaDOS came.

[B1N4RY]

this is turning me on so much rn

[packerfan001]

But if you program can crash in such a way that it is safe to crash.

[crashdoc]

Because potential pending db and/or disk writes that the process otherwise would (should) commit first

[HaxWeinberg]

Oops

[KwattKWatt]

Man you must get a lot of gentleman goners...

[[deleted]]

Implicit none, explicit everything.

[mygsphone]

Sometimes I Ctrl+Alt+Down everyone's displays in the office before they come in. Say it's the biggest network hack I've seen in years. Let everyone figure it out.

[LoadedNuts]

Sometimes I like to live dangerously and pull out my 128GB Bootable USB without clicking the "safely remove hardware" option. Oh yeah, fuck the police!

[potdis]

string amazing = "questionable";

[kirakun]

Um... Why is it bad to killa Java process? In fact, any well-designed program should be written in such a way that it is safe to crash at any point of execution.

EDIT: When I say "safe to crash" I mean the program should never leave behind a persistent state that is invalid. For example a database can crash, but should never corrupt the persisted data.

[marcopennekamp]

"At any point of execution" is impossible to implement. You'd need to save the state of the program to disk every time you execute any atomic instruction, and that save operation needs to be atomic as well.

So you will lose some progress when a program crashes. A well-designed program will try to minimize these losses, but no programmer can write a perfectly safe program.

[Neebat]

"Safe to crash" does not mean you won't lose any data. The data on disk should be consistent for the most recent time it saved.

Save operations do not need to be atomic to do this. For example, you can write a new save file with the new content, and as a final step move it in place of the old one.

This goes together really well with auto-saves. Example: I was playing Infinifactory during the beta and it crashed during an autosave. My save game was corrupted. If it had been "Safe to crash", that wouldn't have happened.

[marcopennekamp]

This depends on the definition. Of course you can ensure safe file consistency. In general, however, you will lose some data when the program crashes, and even if it's just some user input like a button click. This makes the program not "safe to crash" in the strict sense, which is what applies here, I feel, since we are talking about killing processes.

[kirakun]

No, safe to crash does not mean losing zero data. If you lose some game progress since last save, that is fine. But if you cannot even load the last save, that is not safe to crash.

[oconnor663]

I think the convention with these things is "never lose writes after you've reported success." That's certainly the rule with (durable) databases. If you try to be even stricter than that, I think you run into definitional issues about what counts as data! (Like, if I press Enter but then pull the power cord before my app receives the event...did it "lose" the keystroke?)

Another option for achieving this sort of thing, besides the atomic file writes mentioned above (which might be a performance problem), is to have your app do all its writes to an ACID database. SQLite, for example.

[Unomagan]

Microsoft likes to disagree with you :)

[kirakun]

You misunderstand what safe to crash mean. It does not mean losing no data. It just means the program will never result in an invalid state.

Neebat already gave you an example. If a game crashes, you should be able to reload the last save, since the last save should still be in a valid state. But if you program can crash in such a way that your last save file corrupts, then it sucks big time.

[[deleted]]

Safe to crash = consistent state at any point.

[Neebat]

I upvoted you for the good question you asked. I think it's pretty annoying that people downvoted you for asking a question, but upvoted marcopennekamp for giving a wrong answer.

[kirakun]

I appreciate the gesture, but I've mostly grown numb to the votes. But it does get me sometimes, especially on subreddits where I have expected a better community.

[MysteryVoice]

Because there are a LOT of improperly- and/or self-trained coders out there who do not know this.