RL Anger
-
@Ganymede said:
I'm sorry to hear you're going through a rough time. My advice is probably not something you should follow, but, having removed any semblance of empathy or a soul in exchange for a profession, I generally have nothing good to say about or to any person that has meaningless injured another.
You may want to remind your brother that families, unlike marriages, are not contracts.
You are a better person than I. I love my family, but I remember how they neglected to tell me that my cousin, with whom I grew up and went to school with, committed suicide until after the funeral.
WHUT. Just. Whut. That's.......I dunno, maybe they thought they were keeping the person's memory pure or something until after the funeral? I don't even anymore.
-
That is just so tasteless. Even as a gesture of grief, it's inappropriate, selfish and blind.
I cannot fathom a reasoning that would justify that.
I have a waggish sense of humor.
-
@Sunny said:
@WTFE said:
Why do the son and the daughter-in-law think they have a claim on the wedding ring over the husband who actually fucking bought the thing and was wed with the woman? These people need 9mm parabellum of pain relief straight into the brainpan.
Oh, it gets way better than this.
My dad PHYSICALLY MADE THE RING for her.
OK, this convinces me. Burn the fuckers slowly with a blowtorch. @Ganymede is right.
-
@Misadventure said:
That is just so tasteless. Even as a gesture of grief, it's inappropriate, selfish and blind.
I cannot fathom a reasoning that would justify that.
I can fathom a reason, and it's a really bad one. Like ghoulishly bad. They (likely the wife putting pressure on her husband, the son) can't wait for the mother to bequeath it, and are afraid Sunny will eventually get it instead when that time comes.
-
@Three-Eyed-Crow said:
@HelloRaptor said:
There comes a point where you need to bite the fucking bullet and move up. The number of times I've talked to companies that have perfectly viable (maybe not perfectly, but still viable) modern alternatives but don't want to spend the money or time to train people to use them, is just infuriating.
My first job was at a weekly newspaper that still used dial-up Internet service. I used to beg to go back to my apartment to do anything online, where I could use my cable modem.
I don't have the heart to tell you how long my father used the really old school modems that looked like giant phone suction cups to send stories in when he was working for our local paper.
It was longer than one would ever have imagined; safely into the mid/late-90s.
When he saw my first laptop, his first words were: "HA! That thing is pathetic! It's so small!" And then I opened it, and the screen was bigger than the one he was working on with his briefcase-sized monster.
And then he saw it was in color, and I swear I saw that man die a little inside.
I didn't have the heart to tell him about the modem for at least a year after that, I just couldn't.
-
@Sunny said:
@WTFE said:
Why do the son and the daughter-in-law think they have a claim on the wedding ring over the husband who actually fucking bought the thing and was wed with the woman? These people need 9mm parabellum of pain relief straight into the brainpan.
Oh, it gets way better than this.
My dad PHYSICALLY MADE THE RING for her.
Just... oh my god. I am so sorry.
My cousins were very much like this when my grandmother (who I lived with most of my life) passed, and... oh, do I ever understand.
There is an extra special circle of hell for people like this. Just... wow. That's just so utterly awful.
-
@Sunny said:
So, the whole blow-up with my sibling and his wife was over my mom's wedding ring. They wanted it -- apparently took it off of her just after she passed -- and my dad said 'no, give it back', and explosion. The reasoning behind my being an awful person is that I apparently did not make my dad give it to them nao.
Christ. I would have been an awful person for calling them a pack of vultures.
-
Spoken like someone who's never watched a dozen "modern" replacements come in at ten times budget (in both time and money) and still not actually managed to replace the system that it was intended to replace.
Spoken like someone who's never dealt with budgets (in both time and money) based on unrealistic expectations for what things should cost or how long they should take, or situations where 'not actually manage' is just code for 'awkward due to unfamiliarity'.
A decade? That's what you think is old and decrepit?
Read for comprehension, you curmudgeonly fuck. I was pretty clearly speaking about software systems built for functioning within an OS with a modern counterpart, not embedded systems probably built in the 50s.
Further, 'shit that became common 10 years ago' is not the same thing as 'a decade old makes something old and decrepit' by any reasonable standard of understanding what the fuck someone is saying, especially when speaking about technology.
In either case, examples of shit like code written before Unix was even a thing were clearly well outside the realm of what I was talking about in that quote.
I know techies love to use the latest hotness, but only a dumb businessman listens to techies breathlessly talking up their grand future vision of modern hardware and modern software. If you have a system that works and does what you need, you don't replace it. You introduce a new system iff you have clearly-identified business needs that are not being met by your existing system. And even then, you probably start by having the new system only augment what you've got until it has proven itself and can be expanded to replace.
All of which completely ignores the fact that I flat out said that what you had said was true, so why you thought you had to rehash that shit here I have no idea.
What I was talking about, and why @Shebakoby's gripe is still perfectly valid, are companies running old ass programs that are so far past no longer supported and quickly reaching the point where they aren't going to be compatible with a modern OS in any reliable way while still needing to use a modern OS for everything else. And specifically, as I already said, when there are viable modern alternatives even if they aren't perfect.
This is especially a problem when the industry you're a part of is moving forward with that modern alternative regardless of its imperfection. It doesn't really matter if what you're trying to do was best done on an original Macintosh or Windows 3.0 machine, on Version 1 of whatever program you're using, when the people you're in business with are on Windows 7 using Version 8 of whatever that program is, and those versions are incompatible due to changes in how the program works and organizes data. At some point you're going to have to suck it up and move forward.
If you've seriously, for real, in all honesty never run into one of the many examples of organizations running wildly outdated software that they can and should have moved on from, but haven't due to a combination of fearing the unfamiliarity of the new and being unwilling to pay employees to learn a new system before it gets implemented and a million other examples of them just clinging to the past 'because it works' even when it is clearly not going to keep working for much longer? Then really, you have lived a charmed fucking life.
But they do exist, and it is pretty common to run across, and it is pretty fucking frustrating. Especially when they want all the bells and whistles and advancements a modern OS provides but don't want to let go of some shit that came out the same decade as the original version of the OS.
HERE IS SOME BOLD TEXT TO INDICATE YOU SHOULD PAY CAREFUL ATTENTION TO THE FOLLOWING:
Much like I said before, everything you described is true, from the catastrophic results of trying to update embedded systems by companies more interested in showing off those bells and whistles than creating a functional replacement (they often get paid regardless), to the techheads who will want to replace everything with the most cutting edge modern version of itself even when it's not necessary or even detrimental to the process.
But what I said, and what @Shebakoby was griping about, are also true. We're just talking about different aspects of the same general issue, and none of us are wrong. Aside from the bits where you were wrong about what you quoted.
-
@HelloRaptor said:
Spoken like someone who's never watched a dozen "modern" replacements come in at ten times budget (in both time and money) and still not actually managed to replace the system that it was intended to replace.
Spoken like someone who's never dealt with budgets (in both time and money) based on unrealistic expectations for what things should cost or how long they should take, or situations where 'not actually manage' is just code for 'awkward due to unfamiliarity'.
A decade? That's what you think is old and decrepit?
Read for comprehension, you curmudgeonly fuck. I was pretty clearly speaking about software systems built for functioning within an OS with a modern counterpart, not embedded systems probably built in the 50s.
Further, 'shit that became common 10 years ago' is not the same thing as 'a decade old makes something old and decrepit' by any reasonable standard of understanding what the fuck someone is saying, especially when speaking about technology.
In either case, examples of shit like code written before Unix was even a thing were clearly well outside the realm of what I was talking about in that quote.
I know techies love to use the latest hotness, but only a dumb businessman listens to techies breathlessly talking up their grand future vision of modern hardware and modern software. If you have a system that works and does what you need, you don't replace it. You introduce a new system iff you have clearly-identified business needs that are not being met by your existing system. And even then, you probably start by having the new system only augment what you've got until it has proven itself and can be expanded to replace.
All of which completely ignores the fact that I flat out said that what you had said was true, so why you thought you had to rehash that shit here I have no idea.
What I was talking about, and why @Shebakoby's gripe is still perfectly valid, are companies running old ass programs that are so far past no longer supported and quickly reaching the point where they aren't going to be compatible with a modern OS in any reliable way while still needing to use a modern OS for everything else. And specifically, as I already said, when there are viable modern alternatives even if they aren't perfect.
This is especially a problem when the industry you're a part of is moving forward with that modern alternative regardless of its imperfection. It doesn't really matter if what you're trying to do was best done on an original Macintosh or Windows 3.0 machine, on Version 1 of whatever program you're using, when the people you're in business with are on Windows 7 using Version 8 of whatever that program is, and those versions are incompatible due to changes in how the program works and organizes data. At some point you're going to have to suck it up and move forward.
If you've seriously, for real, in all honesty never run into one of the many examples of organizations running wildly outdated software that they can and should have moved on from, but haven't due to a combination of fearing the unfamiliarity of the new and being unwilling to pay employees to learn a new system before it gets implemented and a million other examples of them just clinging to the past 'because it works' even when it is clearly not going to keep working for much longer? Then really, you have lived a charmed fucking life.
But they do exist, and it is pretty common to run across, and it is pretty fucking frustrating. Especially when they want all the bells and whistles and advancements a modern OS provides but don't want to let go of some shit that came out the same decade as the original version of the OS.
HERE IS SOME BOLD TEXT TO INDICATE YOU SHOULD PAY CAREFUL ATTENTION TO THE FOLLOWING:
Much like I said before, everything you described is true, from the catastrophic results of trying to update embedded systems by companies more interested in showing off those bells and whistles than creating a functional replacement (they often get paid regardless), to the techheads who will want to replace everything with the most cutting edge modern version of itself even when it's not necessary or even detrimental to the process.
But what I said, and what @Shebakoby was griping about, are also true. We're just talking about different aspects of the same general issue, and none of us are wrong. Aside from the bits where you were wrong about what you quoted.
I see you got some sleep.
"Excuse the hell out of you. He's a bag of dicks. I'm a carefully curated box of cocks." -- to @GirlCalledBlu upon being misrepresented.
-
@Coin said:
I see you got some sleep.
Managed to stay up till 12:30, then slept like a log till 9. Hurray!
-
You aren't allowed to get old.
-
I love you guys, thanks. I know it's just a signal of where I am right now, but reading all y'all saying horrible things about them is rather cathartic, and CERTAINLY makes me feel vindicated. I totally got a laugh out of it, too.
It sucks, it's awful, they're pretty wretched people, but like I used to tell my mom before she passed? At least I don't have to wake up and be them every morning. They have to live with themselves, and they are always going to be awful people. They'll miss out on SO MUCH good, being that way.
-
@HelloRaptor said:
Spoken like someone who's never watched a dozen "modern" replacements come in at ten times budget (in both time and money) and still not actually managed to replace the system that it was intended to replace.
Spoken like someone who's never dealt with budgets (in both time and money) based on unrealistic expectations for what things should cost or how long they should take, or situations where 'not actually manage' is just code for 'awkward due to unfamiliarity'.
A decade? That's what you think is old and decrepit?
Read for comprehension, you curmudgeonly fuck. I was pretty clearly speaking about software systems built for functioning within an OS with a modern counterpart, not embedded systems probably built in the 50s.
Further, 'shit that became common 10 years ago' is not the same thing as 'a decade old makes something old and decrepit' by any reasonable standard of understanding what the fuck someone is saying, especially when speaking about technology.
In either case, examples of shit like code written before Unix was even a thing were clearly well outside the realm of what I was talking about in that quote.
I know techies love to use the latest hotness, but only a dumb businessman listens to techies breathlessly talking up their grand future vision of modern hardware and modern software. If you have a system that works and does what you need, you don't replace it. You introduce a new system iff you have clearly-identified business needs that are not being met by your existing system. And even then, you probably start by having the new system only augment what you've got until it has proven itself and can be expanded to replace.
All of which completely ignores the fact that I flat out said that what you had said was true, so why you thought you had to rehash that shit here I have no idea.
What I was talking about, and why @Shebakoby's gripe is still perfectly valid, are companies running old ass programs that are so far past no longer supported and quickly reaching the point where they aren't going to be compatible with a modern OS in any reliable way while still needing to use a modern OS for everything else. And specifically, as I already said, when there are viable modern alternatives even if they aren't perfect.
This is especially a problem when the industry you're a part of is moving forward with that modern alternative regardless of its imperfection. It doesn't really matter if what you're trying to do was best done on an original Macintosh or Windows 3.0 machine, on Version 1 of whatever program you're using, when the people you're in business with are on Windows 7 using Version 8 of whatever that program is, and those versions are incompatible due to changes in how the program works and organizes data. At some point you're going to have to suck it up and move forward.
If you've seriously, for real, in all honesty never run into one of the many examples of organizations running wildly outdated software that they can and should have moved on from, but haven't due to a combination of fearing the unfamiliarity of the new and being unwilling to pay employees to learn a new system before it gets implemented and a million other examples of them just clinging to the past 'because it works' even when it is clearly not going to keep working for much longer? Then really, you have lived a charmed fucking life.
But they do exist, and it is pretty common to run across, and it is pretty fucking frustrating. Especially when they want all the bells and whistles and advancements a modern OS provides but don't want to let go of some shit that came out the same decade as the original version of the OS.
HERE IS SOME BOLD TEXT TO INDICATE YOU SHOULD PAY CAREFUL ATTENTION TO THE FOLLOWING:
Much like I said before, everything you described is true, from the catastrophic results of trying to update embedded systems by companies more interested in showing off those bells and whistles than creating a functional replacement (they often get paid regardless), to the techheads who will want to replace everything with the most cutting edge modern version of itself even when it's not necessary or even detrimental to the process.
But what I said, and what @Shebakoby was griping about, are also true. We're just talking about different aspects of the same general issue, and none of us are wrong. Aside from the bits where you were wrong about what you quoted.
I know someone who works for the government, who was still using old ass computer cassette tapes and the old ass types of computers that use them, at least up until maybe 2-3 years ago (idk if that's changed since then, since they changed workplace)!
-
@Sunny Yeah but even though they have to live with themselves, it doesn't really matter because they will never think of themselves in a way that living with themselves would matter, unfortunately.
-
@Sunny said:
I love you guys, thanks. I know it's just a signal of where I am right now, but reading all y'all saying horrible things about them is rather cathartic, and CERTAINLY makes me feel vindicated. I totally got a laugh out of it, too.
See, we can all be mean for you in this instance.
Many of us are quite good at it!Fresh peeve: Whyyyyyyyyyyyyyy does everything seem to break at once? Seriously, I think my bathroom just decided to disassemble itself practically overnight.
First the shelf with the bajillion makeup pencils collapsed in an explosion of chaos, then the tub rack whined in that oh-so-special metallic way before collapsing on me (in the tub, grr-clonk), and the roomie decided to start shuffling things randomly from the hall into the (tiny! house built in the 40s...) marginal floor space.Obstacle courses can be fun, but not in bathrooms.
Oh fucking well.
-
@surreality said:
Fresh peeve: Whyyyyyyyyyyyyyy does everything seem to break at once?
Sorry. I was practicing cursing on you.
-
@surreality said:
@Sunny said:
I love you guys, thanks. I know it's just a signal of where I am right now, but reading all y'all saying horrible things about them is rather cathartic, and CERTAINLY makes me feel vindicated. I totally got a laugh out of it, too.
See, we can all be mean for you in this instance.
Many of us are quite good at it!Fresh peeve: Whyyyyyyyyyyyyyy does everything seem to break at once? Seriously, I think my bathroom just decided to disassemble itself practically overnight.
First the shelf with the bajillion makeup pencils collapsed in an explosion of chaos, then the tub rack whined in that oh-so-special metallic way before collapsing on me (in the tub, grr-clonk), and the roomie decided to start shuffling things randomly from the hall into the (tiny! house built in the 40s...) marginal floor space.Obstacle courses can be fun, but not in bathrooms.
My eyes skipped over the 'makeup' part of that and I was like "Why does she have a shelf with a bajillion pencils in her bathroom?" for a good minute or so before I caught it.
-
My office air conditioning has died for the third time in two weeks. This is literally worse than all previous evils in human history.
I'm a rodeo clown.
-
Our AC at work is busted.
I work in a bakery. Standing next to ovens.
Fml.
I hate today and everything/one in it.If you get your AC fixed, send some this way. Stupid summer.
-
Extra salty bread, mmm.,
