Sorry to those that took the time to share their experiences and then were told "no, you're wrong, here's why". Nothing will change here, good luck.
429 karma · joined December 5, 2022
Sorry to those that took the time to share their experiences and then were told "no, you're wrong, here's why". Nothing will change here, good luck.
Feel free to google the word, then the behavior I described, then look at the peer comment where someone literally goes "idk what that long-since killed-off-thing was but you must be exaggerating".
Thanks for ironically proving my point and demonstrating just how ignorant the criticism was.
I can't get my head around this. I describe a feature, that has long since been ret-conned from the community because it became such a thorn in everyone's side.
And you're just like "nah it probably wasn't that bad even though it was excised and is no longer talked about *and I can't even remember what it was for*" (despite being the exclusive only way to do local dep management). Stun-ning.
What is was "sold as a fix for"? Man, the hubris of people commenting on things literally completely ignorantly.
LOL, really didn't think I'd be gaslit about GOPATH in 2023. Brilliant, keep it up Gophers!
The entire premise is absurd. What application spends more time on SSR than data fetch, or other? Exactly freaking zero that ive ever operated.
/me remembers years of being gaslit by Gophers, of all stripes, for asserting that, no, unlike the cult of personality around Go, i did actually know what i was talking about when I said GOPATH was a nightmare in real world use (even better, it was plainly obvious even with pre-1.0 kubernetes). Just cringey.
For all the handwavey whinging about Rust, Gophers have treated me far more poorly over things that have been retconned and forgotten years later.
Lol! Its like this site having more pity for consumerist tech workers that pissed away hundreds of thousands a year versus rhe empathy displayed for otherwise actually poor, disenfranchised folks.
Regarding concurrent stream plans, I'm afraid you're going to have a very bad not great day if you get mad about every tech-y company over-selling to unsuspecting consumers...
Or are we keeping with the feigned-ignorance thing and acting like a company growth-hacking and rug-pulling customers is anything but absolutely run-of-the-mill.
`xplr` and `joshuto` are clearly thought-out non-trivial TUI file explorers that seem to scale to the naive and a certain power-user type.
`difftastic` is a very cool replacement `diff`.
`jj` is compatible with git, and like git-branchless, but I'll bet on `jj` for a number of reasons. It's also awesome and in 3 years there's going to be some amazing tools built with `jj` and...
(not a daily/semi-daily use, at all, but special mention:) `git-oxide`, I mean, you can guess from the name, the monthly reports show just how incredibly thoughtful the author is and just how incredibly viable and already-usable this project is (especially given the complexity which I really would not have understood without the thorough monthly updates).
followup, there's no reason for this to really mean anything, or for anyone to "believe" me, but I just opened this post on reddit:
https://old.reddit.com/r/zfs/comments/10pdspe/take_your_zfsb...
and wow, what a smart tool, and a smart way to release it. I know how to mount a snapshot, and ripgrep/fd through it, could script that, but making that resilient would suck. The way this is presented is smart. It's a new OSS project, shows example usage in the reddit post. Anyway, I thought of my comment earlier, and of course, there it is, `Cargo.lock`, bias confirmed. And a tagged release. And has a `LICENSE`. And has committed `Cargo.lock`.
For the sake of not replying too much I'll say I'd echo everything spoiler wrote in this posts' sibling comment. And at the risk of coming across poorly, there's something that's a cross of stockholm-syndrome and sunk cost fallacy and it seems like when certain potentially displacing technologies gain more and more steam, there's a louder and louder minority that claim that this new paradigm is just too disruptive and what are they teaching our kids. (oops)
Uutils, helix, zellij, ripgrep, and countless others.
Ive stopped caring (mostly) to convince others of it, but many, many Rust projects are clearly started by very experienced folks that know how to release and foster a community.
The logic here of "just leave it unlocked, no one ever tried the door" it's... not logic.
But maybe I should be more careful in how I speak. Class consciousness is key and I didnt know any better until I did.
But also I know whats it like to live in a nice, newly built 2br apt in the second most expensive tech city. And I know how to make that work, coasting, on ~60k/yr, without free meals, without free orca cards, without free shuttles across town. So when i see 5year xooglers that i know made 300k+ the entire time, my head starts to pulsate.
When I think about how i can draw what i draw off my (big tech co) stock, and then I think about those same xooglers, and their stock benefits...
It just feels like these conversations are borderline dishonest with the handwaving and intentional lack of discussion of specifics, and any consideration of the meta of how this tragic, unthinkable event is discussed here compared to other topics related to labor.
But for those reading this who are "crying in bathrooms", what does it say about your lifestyle thst you likely made 2-3x my salary, and yet i walked away from tech for years while youre somehow fearful of making ends meet?
I eat what i want, i have money for more weed and booze and casual friendships than i can dream of. I am fucking disgusted with this "trying to make it seem like fired tech workers are as pitiable as average americans".
No. No more. You want me to cry for your lost Google salary, i wanna see numbers.
This entire shit conversation is privileged and absurd and ignorant of what the left has advocated for for decades ... to a point i pull at my hair.
Seriously, this fucking website is gonna cry over fired tech workers when hundreds of thousands of americans who make less than 5% of google salary experience this, regularly, without severance, health care and a halfway decent shot at findinf a new job. Really? Ive seen the attitudes that are popular here. BUT GOD FORBID SOMEONE QUESTION THE SPENDING HABITS OF THE SELF-IMAGINED-AS-WEALTHY TECH CLASS?!
Oh and they repeatedly drive away the few ppl who care enough to have a comprehensive view of the OSS/real world and internal systems. Gaslighting and behind-your-back conversations is what you can expect even if youre a mild-mannered shy quiet boy that just happens to have a fucking clue about where GCP and AWS still mop the floor.
(No silverspoon here, stock matches and living conservatively)
Hi, welcome to the left, or class solidarity if thats more palatable. Every time yall rolled your eyes at unions and labor protections?
Protip, a buncha people need to really internalize this -- your boss and management don't give a shit about you (certainly not in any tangible, meaningful way). You're not family and never were any more than my deadbeat dad was family because he made me do yardwork.
Yo, your boss totally is gonna "value you" more if you downvote me to satiate the cognitive dissonance! Lol I can't, I really can't.)
I've 100% accepted that AI will displace tons of jobs and lead to the near dissolution of meaning and discourse "online" (as if as anything else will exist). And Im just trying to be happy day to day until that and its secondary effects come to pass or until one of other countless seemingly incoming disasters happens.
lol, maybe accidentally brutally honesty and ordering in that list of roles. Maybe I was the idiot for ever thinking the huge, lavishly lavishly paid DevRel team at Azure would result in the platform being less of a nightmare for users.
Maybe the book is just "AD brings in the money" but wow, they sure bring it down as well. Global outages like that always stink of AD.
All to say, I agree wholeheartedly with every word.
Okay, here we go, let me be explicit: there's a Venn diagram I imagine in my head of two circles - first is "password managers that require a web ui and browser integration", second is "password managers written in a language and with an overall complexity that I'm comfortable with".
For certainly-informed users, there's ZERO overlap in 2023. what's super fun is that this comment would get entirely different scores in yah, every 2 years for the past decade+ now. (think abour Rust circa 2021, 2019, 2017, I feel confident saying... for well most, opinion has been shifting in a certain direction).
luckily recently there is a tool which is,
1. rust-written
2. pass, pass-totp, and pass-tomb compatible
3. hasn't yet broken the CLI UX in nearly every release like another prominent "safe-lang" re-write of pass. that's all I'll say because it turned into a many-paragraph rant otherwise.
I'm trying so hard to watch myself here, but it's just not that hard. Let's imagine what needs to break for me to compromise your WV account versus what you'd need to compromise my public-hosted git-repo-backed yubikey-hardended-gpg-encrypted pass accounts. "I'll post mine if you post yours?"
If you're writing go though, you can probably leverage docker-machine which i would have to guess has such abstraction internally.