As I said in my reply to Kent: frankly, if you store important data on an experimental file system and don’t have backups, you deserve to lose it.
1,121 karma · joined July 5, 2017
And I have to imagine that those that are technical enough to not only use Linux, but use an experimental non-default file system, and those that don’t have backups of their data, is a vanishingly small group.
So no, I actually disagree —- it’s not part of the job.
So again we arrive at the same place: this data recovery tool is not worth the drama.
It’s a feature, not a bug fix, and an incredibly unimportant one at that _at this stage of development_. If bcachefs weren’t experimental and were widely used, it would be a different story —- I’d probably be in favor of bending the rules to get it in there faster. But that just isn’t where we are right now.
Err, what? While you're right about Intel integrated GPUs being a safe choice, AMD has long since been the GPU of choice for Linux -- it just works. Whereas Nvidia on Linux has been flaky for as long as I can remember.
You’re acting like bcachefs systems are storing Critical Data That Absolutely Cannot Be Lost. And yet at the same time it’s experimental. I’m just one user, but I can tell you that, even as excited as I am about bcachefs, I’m not touching it with a ten foot pole for anything beyond playing around until at least the experimental label is removed.
I imagine my position is not uncommon.
Please stop trying to die on this hill. Your project is really great and really important. I want it to succeed.
Just chill and let bug fixes be bug fixes and features be features.
What @surgical_fire is describing is the "minimum viable product" for a career. It's the thing that serves the basics on Maslow's Hierarchy.
What @hshshshshsh is describing is anything past that. We briefly exist sandwiched between two eternities -- shouldn't we care about the quality of our time during the thing that takes up the largest quantity of our time?
The problem is that, the issue that @hshshshshsh is pointing out is precisely what makes the minimum @surgical_fire is describing damn near impossible to find.
Because no one gives a shit about users, values, mission, etc, the company suffers and turns into a shit-show, incentivizing people to become more selfish so that they don't get sucked into the vortex of shit.
In order to reach the minimum of a "tolerable" job that doesn't suck up all your free time or make your time there a living hell, the company _must_ engage with at least some of what @hshshshshsh is describing.
This requires some amount of good faith from the majority involved. This is a tricky and fragile thing. It's easy to lose. And thus the cycle begins anew.
Ultimately, we need more people thinking like @hshshshshsh so that we can get what @surgical_fire is describing.
This right here. The perverse incentives integral to public companies are at the core of so much that is wrong with the world.
Side-note: what theme are you using in the linked gif? It's right in the middle of my two favorite themes, onedark and gruvbox.
Anything less than lightweight glasses is a non-starter outside of gaming and other enthusiasts. The Vision Pro is just too bulky for it to sell serious numbers.
But the whole "but actually you only like what you like for superficial reasons" thing lost me. I really dislike essays that create false dichotomies just so that they can purport to know why what you do is bad or wrong.
Can't someone choose a tool for _both_ rational and aesthetic reasons? In fact, isn't that basically the definition of "best?" And by "best" I (hopefully obviously) mean "best for me/you," not "objectively best."
I'm sure the author would take a dig at me: I have a love of Thinkpads of command lines. Regarding the CLI, I won't deny that I love the aesthetic. That's genuinely why I was originally drawn to them. Vain? Silly? Maybe. But I own it, won't deny it, and will never stop loving the aesthetic of a cool ass looking terminal.
However.
Seeing as the author chose to focus on editors, I'll do the same: I have never found an editor that is all together _better_ than neovim. Sure, this is probably still subjective, whatever, but putting aesthetics and feelings and whatever else aside, neovim still always wins for me and it's not even close. The speed, the stability, the power of a well-configured LSP, the navigation afforded by things like fzf and treesitter, the unbelievably rich and forward-thinking plugin community, and so on and so forth, make it come out on top time and time again for me. Many, if not most, of these reasons are rational.
I could say similar things about most of the other apps (cli-based and otherwise, though most are cli-based) that I use, as well.
The author also seems to misunderstand that the so-called "cult" of Emacs might exist for more than just superficial reasons. Perhaps a "cult" formed around it because it's actually really good, or at least addressed a lot of people's problems at a particular time, and groups of people tend to form their own aesthetic? I myself have never jived with Emacs, but I can certainly recognize the power of it -- and, yes, the aesthetic, community, etc -- and I certainly wouldn't dream of shitting on someone's joy of it, especially in a condescending "you actually only like this because you think it looks cool" or "it confirms some aspect of yourself" way.
It's simple: we can, and probably even should, choose tools for both rational and "superficial" reasons. It's perfectly fine, and one aspect does not negate the other.
- Protocols are descriptive, APIs are prescriptive
- Protocols are implemented, APIs implement
Rather than giving in to it, I've taken it as a signal that something needs to change -- I'm surrounded by the wrong people, in a business with bad market fit (a root cause of this kind of toxic culture that isn't talked about enough IMO), etc. Sometimes a good place has just rotted. Like entropy, I don't think this sort of thing can be reversed once it's set in.
I recently interviewed with a great company full of great folks, and I was given the chance to frankly but firmly (and slightly humorously in a gallows humor sort of way) state precisely why I was leaving my last company; in fact, I used it as part of the interview where I interview them. This section of the interview went well, because as far as I could tell, these people are smart, down-to-earth, no bullshit, and appreciate living in the truth. They're a small company, so people can't hide behind bullshit as easily. I much prefer that.
The cognitive dissonance displayed all over this thread and tendency to hand-wave it away by painting anything that isn't playing along as not understanding social cues, lacking tact, etc, makes me sick. The whole culture is childish, literally -- it reeks of the particular brand of lack of accountability, tendency to gaslight, and so on that is displayed by children. When coming out of a 4-year-old's mouth, it's easy to disarm and work around and excuse, almost cute in its ineffectiveness; when coming out of a company, as a matter of policy, it's authoritarian and frightening.
I really, really can't stand it. The good people are out there, however.
A couple purely superficial suggestions (echoing some other comments here):
- Lose the Brew terminology, especially if the name of the project isn't a synonym of "brew." - Change the name in general. "Sapphire" makes me think of "Ruby." IMO the obvious name is MacPac :p
I settled for Cmd+Ctrl+[h|j|k|l] window snapping via Hammerspoon, and let my Arch/Hyprland box keep the tiling window manager.
And yet far too many apps dare to put their files there. Drives me absolutely insane.
What? Go is one of the most stable languages I can think of. What churn are you referring to?
Literally laughed out loud at this, it’s so accurate.
This. Right. Here.
Looking at my Python before I began using type hints and data structures such as dataclasses, typevars, etc I was still type-checking a function's argument, but it was very manual and messy. Nowadays, my code is so much cleaner, concise, less error-prone, and much easier to revisit after a long period away. IMO there isn't a single downside to leaning heavily into types, even if they're sorta "fake" like they are in Python.
That is clearly, clearly not my argument, but I have a feeling that you're one of those bad faith "and yet you participate in society, curious!" guys, so I'm done here.