217 karma · joined February 17, 2022
However, most churches don't have full bodies anymore, for obvious reasons. However, when the altar is stripped (for example on Good Friday). If you were invited into the sanctuary... you would be able to see a stone, on which there is inscribed several crosses. Under each cross is a relic, set into the stone. The priest consecrates bread / wine over the stone.
In terms of provenance... you can't sell a relic, but most monasteries, shrines, the Vatican, or other places that have burial records, will provide relics upon request, if available. Orders keep careful details of their martyrs and saints. So for example, a Dominican parish will often ask a Dominican priory with burials of a Dominican saint for a relic. We have indeed even entered the modern age where some monasteries / priories / convents even let priests request relics online!
Instead of learning a young, new language, I could just boot into Linux and used an established operating system?
I don't understand this mentality of 'Windows must be better'. PowerShell is alright, but as the article pointed out, the Windows terminal experience is terrible. Even the OG terminal interface on linux is better (supports copy paste with mouse for one thing).
I have made no argument that everyone needs to use the CLI. I like it, and it is a fair criticism of Windows to say that it makes things harder by not having it. That criticism rings true for me and many others. Some other people with different experiences probably think CLI is hard. That's fine. To each their own.
The comment I responded to accused the author of being disingenous. I pointed out that (1) technical users are still users and (2) there are things that if you're used to a unix shell are simply an absolute pain to do on windows.
> The way I see it, the issue here is that you don't know how to use Explorer features, but instead of looking it up and learning how to use it, you're pushing the narrative that somehow it's Explorer's fault for you not bothering to look up such solutions. It' not like you were born with the Linux command line in your head. You had to take the time to learn all those commands and practice. Same with Windows and MacOS and other OS. You need to re-learn certain mechanics whenever you switch OS and it's not the OS's fault you refuse to do that and choose to remain stuck wanting everything to work the Linux way.
Okay, now do any file with a number at the end?
Not everything uses SMB? Windows compatibility for anything not Microsoft is sporadic.
On linux, the 'normal' way to move files is using the terminal using 'mv'. On Windows, the terminal is available, but the main interface is the UI. It's easy to move one file. It's even easy to move several files 'next to' each other in the window. It's not easy to move files matching a particular name, or across multiple folders.
So usually what happens is I have to find (perhaps even purchase) a purpose-built utility to do exactly what I want. Or, sit there and move files. Like ctrl+click on them (that interface is terrible by the way, because one click makes the entire selection go away... who thought that up?) and then move them. What other way is there without delving into automation? Windows Explorer cannot even do the most basic selection of 'select all files with NNN in the name'. It's completely useless for anything but the most silly of operations.
Also, if you have to do actual work moving files between different filesystems or across network filesystems, it becomes even worse. You have to find something compatible with Windows, install it. It's probably some ad-containing shareware non-sense, so you pay for the license so you don't get bombarded with ads, a browser toolbar, and whatever other nonsense the MSI decided to install. Then, after about 30 minutes of downloading, installing and endless clicking on the 'do you want to allow this software to do blah' (which I never really read and click by default), it may or may not work.
On linux, it's just mount.
I don't really get the complaints about linux being hard to use. Different sure. But if you're used to it; if you grew up with it, it's mind-numbingly easy.
You criticize the author for lacking self awareness, but then turn around and do the same.
Many linux users (myself included) do not spend time 'tinkering'. I've had the same experience as the author. I've used linux almost exclusively since around 2000 and the few times I have to use windows, I'm completely stuck. It takes forever to get things done. Just helping my parents out with simple things like 'move these files', 'rename these photos', etc take hours and hours of work, whereas on linux it's like a minute.
> Linux is not really a viable alternative for most mainstream non technical users.
Perhaps that's true, but technical users are ... still users.
> They're spinning a lot of plates, which is why it feels and looks the way it does to some extent.
That's great, and while it may excuse their poor operating system, it doesn't suddenly make it a great OS.
Both money and family time are necessary for kids to thrive. If you have one and not the other, it's going to be a problem.
[1] As in... my parents had a curfew and didn't let me drink..., so totally normal rules for a high schooler, but I felt that the world was ending and everything was so unfair.
I mean... just reading about their life before the suicides already stressed me out.
EDIT: Also, the article spent very little time talking about the human impact of COVID lockdowns (it mentioned them, but did not dwell). Passages like this:
> I asked Angela if we could come by for a condolence call. She said yes, if we were vaccinated. Because vaccines were not yet available to children, she added, “Don’t bring George.” She paused, then explained, “It’s just—because of Agnes. She can’t get vaccinated yet, either. And she’s all I have left.” In the following weeks, Angela told her story over and over to any friend who asked, as though she could contain it through repetition. For Billy, even conversational boilerplate was a struggle.
Make me think the parents were a bit over the top with regards to covid lockdowns. Children not being able to see friends? Human companionship (physical presence) is a basic human need on par with food and water. No one's surprised when a child dies from lack of food. Lack of intimate friendship is the same.
EDIT 2:
> Trevor, the child of well-off, educated parents, had far better mental-health support than most American children, but was not saved by it
In my experience, it's better to come from a lower middle class family (so enough money to eat and have everything you need, but not too much), than to come from outright wealth. Money is not a solution to every problem, and too much money and luxury is the root cause of many mental illness.
[1] I wrote this comment before reading the article, but the article later goes on to talk about how we was abused. I don't want to say 'I told you so', but the signs were all there. It's interesting... the New Yorker doesn't even stop to question whether the rise in child suicide rates may be due to a rise in child sex abuse.
Same input -> same output is a nice property of referential integrity, which is a common thing we have in functional languages, but it is actually not due to the functional nature. Imperative languages can trivially be made to have this property by disallowing mutation of variables not in the immediate scope and restrict IO side effects (and maybe a few other straightforwards restrictions depending on the language in question).
With that out of the way. Same input -> same output holds for `orElse :: STM a -> STM a -> STM a`. However, you really have to expand out the types.
Here is the definition of STM (from https://hackage.haskell.org/package/base-4.15.0.0/docs/GHC-C...):
> newtype STM = STM (State# RealWorld -> (# State# RealWorld, a #))
So, `orElse` should behave the same as a function with this type:
> (State# RealWorld -> (# State# RealWorld, a #)) -> (State# RealWorld -> (# State# RealWorld, a #)) -> State# RealWorld -> (# State# RealWorld, a #)
Now, the definition of 'same input -> same output' is clear. Assuming the global state (State# RealWorld) is the same, then the output state will be the same. Actually, this is not a property of all languages, as most languages allow arbitrary side effects in any code. Haskell does not. This is the key property that makes STM easy in Haskell and difficult in other languages. Note that the 'State# RealWorld' is always handled linearly, so there is no possible way the same 'value' could be passed in twice. Again, hiding this behind a monad enforces that this value is handled linearly, since Haskell doesn't have linear types (or at least didn't when STM, ST, and IO were written).
As someone who has autoimmune diseases, you must be getting your information from a source I'm not familiar with. Auto-immune disease are a long game of guess, test, and adjust.
No surprise there given my ethnic background (which frankly should have been a dead giveaway, because thalassemias are not uncommon at all), but I saved myself from being put on iron supplementation which is already potentially dangerous for a man, but especially dangerous to someone with thalassemia.
In my experience, many people have a quasi-religious belief in the capability of modern medicine to perform what would otherwise be called a miracle. This belief is typically held without any evidence whatsoever.
In reality, there are a plethora of conditions, some very common and serious, that medicine simply has no idea how to treat. The set of completely treatable / curable conditions is much much much smaller than the set of all possible diseases, yet people act as if it's the opposite. This is why things like 'evidence based' medicine is so dangerous -- we don't have evidence for the vast majority of impactful conditions, simply ignoring patients with these conditions is not a workable solution.
No. I'm very clear with demands on my time that either companies have to provide resources to implement features (and I'll charge a consulting fee to train devs) or pay me directly to implement them (and I'll name the cost). Actually, several companies have paid me, and my project is significantly smaller than homebrew (niche Haskell library).
> We have seen how much the internet can vilify people who refuse to do this kind of free work
I don't really care about being vilified online. Have had my fair share. I'm old enough to not give a second thought to online trolls.
> Change the license and yank the rug out from under people, or pass it on to someone else
Or... don't change the license. Stop giving updates, and put up a notice that says you are not actively working on project X but for a fee you will be happy to make updates.
> Like most blasé statements, this statement doesn't help anyone. Not least because that's exactly what Tea seems to be trying to help people to do. Whether they succeed or not, no idea - but I wouldn't be bashing the concept this early on.
I wish them every success, and I may end up using it myself. However, I don't like the accusations of unfairness being levied against open source users (among which I would also include myself) for using freely available code for free.
So... while I don't get 100s of e-mails a day, I do get a good amount per year demanding I implement a feature. I point out that my personal contact details are there (as well as my corporate entity) and that we can be contacted for custom commercial work.
The way I see it... OSS is my past-time. The moment there are deadlines you need to pony up
I have a few open-source libraries, and I figure that... since I give them away explicitly for free... there is no expectation of being paid. If one expects to be paid, one should sell their product.