No priest will feed sufficient context about their community into the context window - even if they were skilled enough to do so, unless the model was locally hosted, doing so would be a violation of their vows of silence.
Good homilies are written with the particular community in mind. If it were more effective to write a homily for a generic public, the Vatican would have started publishing standard homilies long ago.
Not sure what this is implying, but aspiring priests are required to have a Bachelor’s degree before entering Seminary, or it tacks at least two years onto a very rigorous six-year seminary program. The seminary program is on par with getting a Master’s degree in Philosophy and Theology. Further, only 30-50% of seminarians ultimately become ordained as priests, due to the rigorous vetting program and “discerning out.”
I know little about theology and philosophy but I’ve interviewed enough people with master’s degrees to be able to say that there a very large differences between skilled degree holders and average degree holders, at least in my field.
The selection process for Seminary and becoming Ordained is much more rigorous and difficult than a credentialing exercise that you pay for. I share your cynicism about masters programs, but I don't think it's applicable here. Funnily enough, my favorite professor in college was one of my math professors who was also a Catholic Priest and would say Mass on the weekends at the nearby chapel. Extremely hostile to using technology to teach us, except in very narrow circumstances, and I am all the better for it and so is everyone who had him. We have a much firmer grasp of the theory because he made us write it down (a lot). There are few things more rewarding in life than feeling that "click" in your brain that unlocks a new permanent level of understanding.
The crux of all religions. The only comparatevely harmless religions are the ones who don't claim that gods demand absolute obedience, but their orders are spoken through a chosen few; otherwise they're just a form of primitive government.
There is a difference however, of faith based on evidence vs. faith based in no evidence. Without getting into too much details here since it is not the avenue, Islamic faith is strictly based on evidence.
Naturalistic religions, so called "paganism", also worshipped living beings or natural phenomena like a particularly big tree, a mountain, a forest, the Sun, etc. Some of these didn't demand obedience nor spoke through a ruling elite. Bonus points for worshipping things that could be verified as real.
No, "faith" is actually an integral component of "the Christian faith".
Go read the first part of Acts 4, where a section closes with: "Now when they saw the boldness of Peter and John, and perceived that they were uneducated, common men, they were astonished. And they recognized that they had been with Jesus." So...yes! We do believe in a God that can empower average people to speak in above-average ways.
> You have a lot of faith in the qualities of average priests.
>> To be fair, faith is the crux of Catholicism.
So, in context (which the downvoters seem to have missed), "faith" is being used equivocally here. There a difference between having faith in Christ and his promises and faith in his claims of divinity on the one hand, and having "faith" in a priest or whatever else on the other. Hence, my question whether this was some kind of a bad attempt at humor or whether something was meant by it.
(FWIW, authentic Christian faith is not an arbitrary faith in anything you please. This is blind faith which is irrational. This is why we can speak of preambula fidei. There must be reasons for faith. When a friend tells you something about his inner life that you cannot know directly, you may believe him given an ensemble of evidence and reasons that cannot prove his claim definitively, but are nonetheless very supportive of it. Furthermore, the claim makes sense of what you do know about him.)
But part of the faith is faith that God can communicate through imperfect mortal vessels.
> Moses said to the Lord, “Pardon your servant, Lord. I have never been eloquent, neither in the past nor since you have spoken to your servant. I am slow of speech and tongue.”
> The Lord said to him, “Who gave human beings their mouths? Who makes them deaf or mute? Who gives them sight or makes them blind? Is it not I, the Lord? Now go; I will help you speak and will teach you what to say.”
Like, that's the whole deal about all of the prophets, popes, priesthood in general. They are all mortal and imperfect, but God still speaks through them.
> authentic Christian faith is not an arbitrary faith in anything you please
But he's not talking about an arbitrary faith. He's talking about faith in the capacity of priests -- clearly a relevant subject. And there are, indeed, _preambula fidei_ here: that the priest was taught in seminary, that the priest was approved by the Church, that the priest (through the bishop who ordained them) participates in a line of apostolic succession going back to Jesus, etc.
What you've written is simply an intellectual jumble. What does faith (the theological virtue) and acceptance of the apostolic succession have to do with "faith" in the capacity of priests, here, as competent homilists?
99% of the jokes I've made throughout my life don't land. For better or worse, if I find something amusing I impulsively share it.
In this case, I thought it should be obvious that OP must have faith in priests, given that they're Catholic, which requires faith as a prereq.
If you read my comment as a slight against Catholicism, I can understand, but I wouldn't feel comfortable publicly joking about any religion other than my own. If that's the case, you're in good company, with the multitude of nuns who've admonished me for similar offhand comments spanning 20 years of Catholic education from pre-k to college, this is old hat for me.
God willing, I'll mature or start telling better jokes some day.
Not much faith required on this one: either a given priest will have both strong familiarity with congregational context and the ability to articulate it as instructions to an LLM or they’ll be missing one of those two. If they’re missing the context themselves, well, they can’t feed it to the LLM and best case scenario is probably that they engage the process closely enough the whole way to learn something from it. If they lack the ability to articulate the whole context that they know but can intuitively work with it, then they’re more likely to meet needs than the LLM — and I’d guess this is a common case.
Forgive me father for I have sinned. It has been three minutes since I shit posted on HN, and my greentext stories are famous on 4chan. Also, after lunch today I send 300 emails to Jeffrey Epstein using my work email and signed with my real name. What a great guy!
all the homilies i've heard were pre-written but ended with current events... like telling the congregation to not vote for Obama heh. My wife was Catholic until that moment, she never went back after that. This was St. Rita's in Dallas TX.
Honestly she should have changed parishes. St Rita’s is in an affluent part of Dallas. One of the priests is a former Anglican(?) with wife and children who obtained a special dispensation.
I heard a lot of bad phone it in homilies too. Today one of my favorite priests is from Benin. He serves the Francophone community but also celebrates mass in English and Spanish. He is at Mary Immaculate in Farmers Branch. He is more traditional and gives the Catholic interpretation of the day’s readings and how it applies today.
American religions are supposed to stay out of politics, or they risk their tax-exempt status.
For me, the disturbing event was shortly before the 2016 event when a Catholic Church in Lowell MA had posters urging people to vote no on marijuana legalization.
(In my case, I smelt the politization when I was a teenager so I never continued being Catholic as an adult.)
The separation of church and state in the US was for the state to stay out of religion.
(the US was founded by religious exiles from a state which didn't stay out)
Religions are explicitly political but politics shouldn't interfere with religions. To follow your religion means interacting with the outside world. It's not some personally private thing like a harmless badge you wear (although there are American faith communities that advocate for that).
The cases in the past where political have interfered with religions are often, ironically enough, by other religious politicians. Hence the good idea to separate church and state.
> In 1954, Congress approved an amendment by Sen. Lyndon Johnson to prohibit 501(c)(3) organizations, which includes charities and churches, from engaging in any political campaign activity. To the extent Congress has revisited the ban over the years, it has in fact strengthened the ban. The most recent change came in 1987 when Congress amended the language to clarify that the prohibition also applies to statements opposing candidates.
> Currently, the law prohibits political campaign activity by charities and churches by defining a 501(c)(3) organization as one "which does not participate in, or intervene in (including the publishing or distributing of statements), any political campaign on behalf of (or in opposition to) any candidate for public office."
There's a subtle irony of this rule, which is that in order to stay in compliance with this law a savvy Priest tends to weave more sophisticated moral teachings into their Homilies that make it very obvious what or who they are advocating for or against without explicitly naming them.
Unfortunately, those laws are not currently enforced.
I see another reply is arguing that religion is inherently political. I disagree. Modern politics did not exist at the time the world's major religions were being formed. Attempting to twist them to fit with a particular party or candidate is a terrible idea all around in my book, for many reasons.
The state can cause a lot of damage by endorsing religion, the historical record is overflowing with examples. I'd argue that a religious body endorsing a state is every bit as potentially destructive. The government is at its best when it is neutral on the subject of faith and crafts policy in evidence-based ways that people of all (or at least most) faiths can agree upon. In this situation, there is no reason for a religious organization to promote such a government because their interests are orthogonal. They can cooperate, but there is a clear line between that and acting subservient, or declaring some sort of 'divine mandate' has been bequeathed upon a government institution or official.
The modern period where we take great pains to excise religion from the public sphere is not the historical norm. The norm is that many - if not most - political, and indeed geopolitical, events throughout history had religion woven into them. It is not difficult to find examples of this throughout European history and pre-history. I know you are making a statement on what you feel "ought to be", but I assure you this "ought" is not the usual course of business in world history. A solid quarter of people today live under regimes where politics and religion are deliberately intertwined, a historical aberration.
American religions are more like American Indian tribal nations. They have independent jurisdiction and their income is not subject to taxation. Whether or not they engage in politics is completely their prerogative and has no bearing on their tax exempt status. It’s like saying the Navajo nation can’t engage in politics or else they would lose their tax exemption.
Further, the core reason for freedom of speech in a democracy is to have freedom for political speech. The need is to have different factions discuss ideas related to the governing of society. Any legal regime that restricts the rights of religion to engage in political speech is one that rejects the separation of church and state. The purpose of the separation is to prevent the government from interfering with the rights of disfavored religious groups or granting special privileges to favored religions. If an individual has a right to political speech, then an association of individuals also has that right whether or not it is religious in nature.
When my state was debating creating a state-run lottery to fund education projects, my preacher gave a sermon on the evils of gambling. Religions can't realistically stay out of politics because every law can be reinterpreted as a moral argument.
That's fine. It's different when it's telling people how to vote.
Some people buy lottery tickets specifically because of who they benefit, which is very different than going to Vegas or certain forms of investment. (IE, uneducated investment is often just gambling.)
I was raised Catholic and even though the last time I've been to a church could have been in 2019, I don't remember any priest who wouldn't just gloss over the religious content for the day (copied from an online source), itching to share his politics and the most recent ragebait he's got from Facebook at the end.
That's a bit harsh! I go to mass every Sunday (in France) and rarely have political stuff.
When there, it's most often about abortion or euthanasia (of course in a pro-life (or anti-choice) direction, "you shall not kill")
But dull, empty homilies are (alas) very frequent.
Catholicism is different in every country, I would imagine that a church in a secular place such as France would contain itself a bit, because there's no societal expectation that anyone should follow its religion, and therefore the priests have to put in effort into making people stay.
In Poland, where I grew up, the Church still holds a lot of power and prestige, and priests consider themselves to have authority over people's lives. Leaving the church is seen as more of a childish rebellion, and I would often hear mocking remarks about non-believers in homilies.
It also varies inside countries. Some priests are simply more demure than others. The church as an institution certainly prefers the more radical conservatives as you go higher up the chain, but many low level employees that still talk to commoners do realize that these views are going to put off more people than they attract in developed countries. So in the long term they will only be left with a bunch of crazy radicalists and a silent majority that wants absolutely nothing to do with them.
Have you seen the current pope? He's a big step back from the last one. And the reason for this is the cardinals who wanted back, because they were never fully on board anyway. Then again what would you expect from a group where average age is significantly older than even US congress.
I would say that the burden of proof is yours first.
But since you asked...
> The church as an institution certainly prefers the more radical conservatives as you go higher up the chain
Where are these "radical conservative" bishops? They're anything but "radical". If anything, they tend toward a soft middle that is very slow to act. Indeed, that's one of the gripes "radtrad" types tend to have. They would prefer more bishops were made in their own image.
Instead, we see bishops aggressively curtailing more traditional expressions of the faith, while permitting plenty of liturgical abuse of, shall we say, a decidedly "untraditional" stripe.
> So in the long term they will only be left with a bunch of crazy radicalists and a silent majority that wants absolutely nothing to do with them.
You can't be serious. If anything characterizes the post-Vatican II Church, it has been the greater influence of "progressive" and "modernist" elements, some of them quite radical. Only in relatively recent times are we seeing a growing, younger crop returning to traditional forms. You can expect that the Church will look more traditional within a generation or two.
Your claim reminds me of those who clamored to make the Church more "relevant". They claimed that if the Church didn't do so, it would lose the youth and imperil the future of the Church.
Instead, what we saw was the reverse. As the Church became more "relevant" - which is to say, more concerned with the temporal and the temporary, conforming to the times instead of shaping men and the times - it became less appealing to the youth. It should be obvious in retrospect. What people desire from the Church is the eternal and the transcendent, not more of the same that you can get elsewhere and in bulk.
So, all that "relevance" produces is a large exit of the youth from the Church. Attend a "progressive" parish and you'll see plenty of empty pews with a few aging boomers. Go to a more traditional parish, and you see the pews brimming with families. These are not isolated cases. These are broad trends.
If you do see a swing toward the traditional, it is not because "crazy radicalist conservative" bishops are concentrating those elements, but because of a process of natural selection. "Relevance", it turns out, is dysgenic. And as the traditional element increases and becomes more visible, so does the visibility of its substance, which is what attracts converts and reverts.
So.. you basically agree, you just don't like the wording because you somehow felt personally attacked? Given your reasoning I suspect you work(ed) for the church in some capacity or are at least deeply involved. But it'll be quite obvious to anyone reading this that it is not exactly an objective opinion.
The last time I attended a mass (Spain) it was about some people in the village that were not helping the church enough (with an activity they had to do but also I think there was some money involved) but it was a bit cryptic, so only the ones that were directed the message to could fully understand it.
Catholics have more then just one book. They have whole libraries of theology and tradition way larger then just a bible. And large lists of saints to refer to.
Evangelical would be closer to one book thing, altrought it would still ve a stretch.
I have heard phoned in homilies from some priests but this is not accurate in the United States based on my travels and weekly local attendance. Sorry that you had a bad experience.
I can assure you that their experience wasn't in any way exceptional. It may be different in the US as Catholicism is in the minority in there (~20%), while GP's experience is from a place absolutely dominated by it (>90%).
European Protestantism and American Protestantism differ in substantial ways. Crudely, European Protestantism went the way of Hegelian dialectics and evolving beyond the Christianity of the Bible. American (conservative) Protestantism largely reacted against that. I think both groups are largely held together by politics today though their politics differ in the expected ways.
When I was in formation a couple of years ago, I showed our homiletics instructor a ChatGPT-generated homily for our assigned text. He read through it and put his head on the desk. Then he handed it back to me and said it was as good as good as anything you'd hear from the ambo that Sunday.
By this, he meant that it was ok-but-not-great, and there's a lot of weak preaching out there. And your point is dead on: the text and the assembly are the primary considerations. I preach on the same readings to 4 different masses, but the 4:30 Saturday Vigil folks are a different group than the 11:30 Sunday Morning crowd, so the message is tuned accordingly. Different emphases, different touchstones, differing exhortations, etc.
Homilies are not the core of Catholic mass, the Eucharist is. Protestant churches put more emphasis on the sermon, not sure if it’s all Protestant churches or just “Evangelical” ones
the context-specificity problem you're describing is exactly why the draft/execute divide is so persistent across AI use cases.
it's not a model capability problem. it's an architecture problem: the relevant context is distributed across systems (the priest's knowledge of their parish, history, relationships) that nobody has wired into the workflow. a homily generator without that context produces generic output. a priest who knows their community produces something unreplicable.
same pattern shows up in ops work. every ops request looks like a generic task -- 'update contract status,' 'respond to renewal question' -- but the context required to do it well is scattered across CRM, email threads, slack history, billing records. automate the task without the context and you get confident, generic output that's often wrong. the hard problem isn't drafting, it's knowing which context matters for this specific request before you act on it.
Side note, but I've definitely gotten annoyed with "context".
There's context in the strict technical sense - the AI is stateless, you need to get the right tokens to it in the right way, allow it to use tooling calls, etc. I get that. That, is cool. I use agentic coding a lot.
Then there's the sense of what you're saying - you have to feed the AI "enough context". In your case it's critical, but I've seen way too many pro-AI people just dismiss everything and say "context context you didn't give it proper context, have you tried this prompt etc." as a justification for the "lack" of intelligence.
At some point you have to wonder when it becomes unfalsifiable.
At some point, at least if businesses want to have AI “Agents” act as employees, then it needs to cease being stateless.
There’s a lot of hidden context in day to day work that a human often times wouldn’t even know to explain to the AI or even think that they’d have to include it, things that are just “known” by default of working somewhere for a long time.
With coding, there’s at least the entire codebase as context. With more creative tasks, it becomes murky. Even something as “simple” as sending a price increase notification to customers. There’s a lot of nuance in that, and customer relationship history you’d have to feed to the AI as context to get it right, yet a good CSR would just factor that context into their writing without a second thought.
There is a point, and it is reached very early, where it’s more costly and less productive to feed the AI as much context as you can try to imagine you’d need to give it vs. just doing it yourself. If I’m at the point of writing an entire document of history and context, into what’s effectively a full page prompt, then why bother with AI at that point.
You’re right that a priest can’t (and shouldn’t) dump private pastoral context into a prompt. But context doesn’t have to mean identifiable confession details.
I’m building BibleGuided, and one thing we’re adding is a church feature where congregants can opt in to sharing prayer themes, and leaders can see aggregated and anonymized trends over time rather than identities. That’s enough to shape a homily toward what people are actually struggling with, without violating confidentiality.
If anyone has experience with privacy thresholds (minimum group sizes, differential privacy), I’d love pointers.
I agree with the Pope’s point. Priests should not hand pastoral judgment to a model. BibleGuided has church management tools plus optional AI help for drafting and organizing, with the priest making the final call.
For community context, we avoid confessional and private pastoral data. It is opt-in from congregants, then aggregated and anonymized into themes and trends.
We think AI can be a helpful tool across many areas, including faith, and over time many church leaders (of many denominations) will get comfortable using it in bounded, and responsible ways. If a church does not want AI used for homilies, those features can be toggled off and the rest of our tools still work.
The pope, ostensibly the person you believe to be the representative of god on earth, has said that your product is garbage and here you are rationalizing it.
Its more than a nit. It only applies to confession so putting in other private information would not break a vow, but it would still be a very bad thing to do.
Sermon manuals were popular among Catholic priests from the time the printing press started to spread in Europe, and remained so into the middle of the 20th Century.
A parish priest might not deliver a “canned sermon” verbatim, but still rely on one/more sermon manuals heavily when preparing his words for Sunday.
The Roman Catechism (Catechism of the Council of Trent), published by the Vatican and ordered for use in seminaries for core formation of candidates for the priesthood, included a list of specific topics to address for each Sunday of the year. While not a sermon manual as such, those “bullet points” informed Catholic sermons around the world for 300+ years.
Very few priests take vows of silence. The standard vows are chastity, obedience and poverty. Even highly contemplative orders like Trappists don’t make a vow of silence - they practice something called monastic silence but it’s not a vow.
The closest thing is that a priest cannot share anything told during the sacrament of reconciliation. But that’s not so much a vow as just the other side of what Catholics believe is a direct connection to god.
Confession was originally often made in public. Confessional secrecy is more about making it easier for people to freely confess their sins, free of the fear of retribution or shame, very much like why we have doctor-patient confidentiality enshrined in law today. I would imagine confessional secrecy arose very quickly, even if the norm wasn't private confession.
The first reference I could find for confessional secrecy was from a 4th century book written by the 3rd/4th century Persian bishop, Aphraates. In Demonstration VII, On Penance, he councils priests to keep a penitent's confessions secret, "lest he be exposed by his enemies and those who know him. .... If they reveal them to anyone, the whole army will suffer an adverse reputation."
Source: https://archive.org/details/bub_gb_Sy0vAAAAMAAJ/page/n251/mo... That's a Syriac to Latin translation. I used Google Translate for Latin to English. There's at least one partial English translation of that book online, but I found their translation more confusing.
> doing so would be a violation of their vows of silence
I don’t know what this means. There is no formal “vow of silence”. The closest things I can think of are the discipline of avoiding unnecessary speech in some monastic communities, or perhaps the seal of confession, but this doesn’t apply as priests can speak in generalities or anonymously about the kinds of moral issues people struggle with.
> Good homilies are written with the particular community in mind.
That’s a bit of a generalization. Many, if not most, readings simply benefit from clear explanation. Tying in local or cultural context can be helpful, but they can also be a distraction, and mostly, homilies should be about the essential meaning of the readings. By having to write the homily, the celebrant benefits from writing the homily as well, a benefit he would lose if he simply drew from a corpus of prewritten homilies.
Catholic priests are forbidden from revealing anything they learn in confession under ANY circumstances. If someone comes in and confesses to a crime or that they are planning a crime, the priest can advise them to go to the police, they can counsel them that they may be in danger of hellfire if they do not, but they absolutely cannot tell anyone. The Catholic Church takes this very seriously. It is fully expected that a priest would die rather than break the confidentiality of confessions.
The Catholic Church is made up of people and people do all kinds of things and make all kinds of choices in life. As others have pointed out, it's very possible to talk about the struggles of your community without calling out Bob in the third row.
Let me be more clear then. Not only will there be many priests sharing private information about their local congregation, there will also be priests who continue to directly abuse people in their communities. Sharing private information is extremely mild in comparison.
How is it off topic? The entire basis of solatic's comment is the assumption that priests would not break the rules. A track record of breaking the rules is reason to not make that assumption.
Bro as a kid I used to go to church every Sunday and I guarantee that not a single person from my entire village understood what the priest was saying, including the priest himself, who was simply reading whatever higher-ups had given him. It was perfect slop because literally nobody cared about the content, it was all form - it needed to sound important and complicated enough to be able to be used in religious rituals. This is an excellent use case for LLMs because they excel at exactly that.
Imagine a bunch of bushmen trying to perform the spell of rain. It doesn't matter what they sing, as long as it sounds like something that could pass as the spell of rain, because the goal here isn't to make rain happen, it's to strengthen the community through shared rituals. 99% of religious activities are exactly this.
>>Bro as a kid I used to go to church every Sunday
I mean, not to dismiss your experience, but in my weekly Sunday going to church in Poland the priest would write an actual homily that felt relevant to the community. But then our small town had 3 churches, and each one had a different style - people would talk about preferring one over the other because they had more interesting "content".
But yeah, there was the message from the regional Bishop or the Archbishop of Poland or sometimes directly from the Vatican, then the reading from the old testament, then the homily which I'm 99% was written by the priest giving the mass.
>> I guarantee that not a single person from my entire village understood what the priest was saying
Well, I wouldn't say not a single person did, but yeah, we had those 3 churches, probably 10k seats each, every one was rammed on the sunday, but I'd say 90% of people there were only there to tick it off and snoozed through the whole thing. But it's not because the homily was boring, it's because going to church on sunday was(maybe still is?) a thing you have to do or people will make fun out of you.
OpenAI is dependent on same hyperscalers (most specifically Microsoft/Azure) as everyone else, and even have access to preferential pricing due to their partnership.
A better explanation is to point out that ChatGPT is still far and away the most popular AI product on the planet right now. When ChatGPT has so many more users, multi-tenant economic effects are stronger, taking advantage of a larger number of GPUs. Think of S3: requests for a million files may load them from literally a million drives due to the sheer size of S3, and even a huge spike from a single customer fades into relatively stable overall load due to the sheer number of tenants. OpenAI likely has similar hardware efficiencies at play and thus can afford to be more generous with spikes from individual customers using OpenCode etc.
I would guess the biggest AI product on the planet is Google's Search AI. Although even that might not be the case, unless your definition of AI is just "LLMs" and not any sort of ML that requires a GPU.
Is suspect large trucks may eventually move to hydrogen, but smaller passenger vehicles will stay on batteries. The nature of hydrogen containment favors larger capacity, on account of better volume to surface area ratios.
Many jurisdictions require that commercial drivers take a 30 minute break every 4 hours. Those that don't should. Those stops make battery trucking feasible.
And if you want to stop for 5 minutes instead of 30 you can use battery swapping solutions like the one Janus uses.
Batteries are feasible for long distance trucking today.
Green Hydrogen trucking uses 3X as much electricity as using it directly. Trucking's biggest expense is fuel, so that will be the killer factor ensuring battery will beat hydrogen for long distance trucking.
Using mandated breaks for recharging heavy trucks isn't actually helpful in much of the world. Maybe it is in parts of Western Europe.
The problem is that those mandated breaks are mandated and happen (with a small amount of wiggle room) wherever the truck happens to be at that moment. Rolling out enough charging infrastructure to make that work is an even more immense challenge than the already massive challenge of adding sufficient charging infrastructure to places like existing truck stops.
Imagine the cost of installing 1MW chargers on, say, half the wide spots on every highway.
Imagine the cost of installing massive diesel depots at half the wide spots on every highway. And yet, there they are. And we already have car chargers every few dozen miles on the highways. A larger number of smaller chargers adding up to likely a larger wattage than what the trucks need.
> Imagine the cost of installing 1MW chargers on, say, half the wide spots on every highway.
Do those spots have lighting? If so, a significant portion of the work has already been done. Even if the electrical wiring must be supplemented or replaced, just having already the subinfrastructure to snake high voltage wiring up there is the major hurdle.
Perhaps, but the larger question is whether the price of hydrogen itself can be sufficiently reduced. $36/kg is not justifiable for distance trucking or planes. If the price of hydrogen dropped sufficiently, then there's more demand to build hydrogen infrastructure, which increases demand for hydrogen in smaller vehicles, etc. in a positive feedback loop.
That theory didn't play out, mostly because the price of electrics kept dropping year after year, undercutting any appeal in early investment in hydrogen.
>Is suspect large trucks may eventually move to hydrogen [...]
They won't, why would they? The number of hydrogen gas stations is going down and the price is going up. Batteries are good enough already - the Mercedes eActros 600 with its 600 kWh battery has a range of 500 km.
Life expectancy. A hydrogen tank can be refilled forever. A battery is normally limited to a few thousand cycles. A truck, or airplane, is expected to be fueled/recharged daily for decades. A car is designed to survive the length of a standard lease. Those running fleets of trucks/aircraft will always care more than car owners about long-term ownership costs.
Yeah, Li-ion batteries already have comparable life cycles to hydrogen tanks 1-2k fills/recharges, _but_ batteries are improving rapidly and tanks are already a mature technology.
This isn't necessarily true. Most cylinders storing compressed gasses need to be hydrostatically tested in regular intervals to ensure continued safety and will need replacement when they fail. Other kinds of composite cylinders have fixed ages where they should be replaced.
Inspection is expected. In the transport industry, all sorts of parts need regular inspection. Batteries are different. Performance loss over time leading to replacement decisions is unussual. Virtually no other part degrades in performance the moment you use it. Lots of parts have time limits, especially in aerospace, but few degrade. Those running fleets see this as unussual and unpredictable which, at scale, means extra expense. A tank that needs inspection every decade is a known problem. A battery that looses 1% to 5% capacity every year, depending on weather/use factors, is harder math.
I'm not in the transport industry, I just want to go to the grocery store.
> Performance loss over time leading to replacement decisions is unussual. Virtually no other part degrades in performance the moment you use it.
Tires? Brake pads? Lubricants? Belts? Springs? Bearings? Bushings? Seals? There's tons of parts on my cars that have expected wear intervals that will need replacing after x number of miles with performance that changes with the wear of the part, there's a whole service manual of when to replace certain parts.
Nope. All those parts work at basically 100% until failure or replacement. Some even improve with a bit of use (tires, brake pads, seals). They wear, they dont degrade. Batteries drop in performance from day one.
So tires with 2/32nds will have better grip in the rain than warmed up fresh ones? They just get better until they pop? That must be the reason why race cars only use heavily worn tires instead of fresh ones when they race. Engine lubricant is better at 5,000mi than 1mi?
You only bother buying heavily used motor oil and tires right? After all they perform so much better.
And springs and shocks are perfect examples of things that start to lose their effectiveness on a curve instead of necessarily just all at once. You can tell the dampening effects get worse and worse, the car might start sagging more, etc. They have a whole range of performance before they need to be replaced.
Even the motor itself will often slowly have reduced compression due to slowly looser fitting parts before actual failure, fuel injectors will slowly get more gummed up over time, valves might get gunked up having reduced airflow, spark plugs are slowly vaporizing themselves and can have worse spark characteristics throughout their life, etc. Its not like everything just continues working 100% until they snap. Everything that's moving or reacting is slowly wearing itself out.
Mold release needs to be rubbed off. And the bead needs a few weeks to harden. That's why the tire people tell you to go easy on new tires. As for other stuff, work on cars for few decades and you will learn which parts are more reliable once proven than when brand new, which need time before being pushed to limits.
> As for other stuff, work on cars for few decades
That's the experience I'm drawing from when I point out that "virtually no other part degrades in performance the moment you use it" isn't based in reality. Everything is constantly wearing out. Anything rubbing on another thing, any fluid being pushed through a hole, anything that might be reacting with another thing, its all slowly getting more and more out of spec. And when it gets more and more out of spec, its performance gets worse. You might not immediately notice it, that performance might not be in the go go kind of performance, but it isn't working as well as it used to.
Are you really going to tell me a car with a couple hundred thousand miles on it running all original parts (assuming they didn't literally break apart yet) is likely to be anywhere near the same performance as when the car had 200 miles on it? Its not. Its almost like there's a reason why mileage is considered when people price cars. The suspension isn't going to keep the wheels as well planted, the cylinders likely don't have the same compression, those fuel injectors are likely tired and aren't spraying optimally, that coolant pump is worn down and barely able to pump coolant anymore, your timings are likely not optimal anymore due to slack in the timing chain or belt, your spark plugs aren't making as full or reliable of spark, etc.
If your response is "well you would have replaced those by now"...well, why would you have to do that? Because they...had their performance reduce over the life of the part?
And even then, a part of that break-in period of those parts is the part's performance actively changing over the life of the part with pieces of the part literally degrading, just pretty quickly and positively for performance as opposed to negatively. That positive slope of performance change is a pretty early hump though, otherwise as I mentioned you'd be taking me up for ensuring all your tires are near-bald (but not quite, they haven't actually failed yet!) all the time and you'd be dumpster diving for the good stuff out behind your auto parts store.
Around where I live, we have electric car ferries.
To avoid having to upgrade the grid massively, we use large battery banks shoreside which are being charged at a sustainable (to the grid) rate, then the ferry charges rapidly by depleting the battery bank, leaving the grid alone.
Electrifying all transport in the nation would increase electricity load by 20%.
But even if 100% of all vehicles sold today was electric, it would still take ~20 years before almost 100% of vehicles on the road were electric. And it's not, so we're probably looking at > 30 years to increase electricity load by 20%.
That annual increase is far less than the increase caused by data centers. It's about the same as the annual increase in load caused by increased use of air conditioning.
I worked in one of the top 5 logistics companies in the world and I can recall them investing in electric trucks and charging infrastructure. Idea was to have strategically placed overhead lines that could recharge trucks without need for them to stop. Can't recall any mentions of hydrogen.
I have seen at least one stretch of highway in Germany that has overhead power lines for trucks. I think it's a very interesting concept: the big downside of batteries is slow charging (compared to diesel) and limited range. Charging while driving on highways would largely solve these downsides.
I sympathize with the author, and in principle I find myself nodding along with his prescriptions, but one of the benefits of Dependabot (and Renovate) are that they are language-agnostic. Depending on how many repositories, and how many languages, and upon whom the maintenance burden falls, there's a lot of value to be had. It may not really be feasible to add "the correct" CI workflows to every repository, and the alternative (nothing) inevitably ends up in repositories where dependencies have not been updated in years.
It's good optimization advice, if you have the time, or suffer enough from the described pain points, to apply it.
A lot of people are often surprised at how non-frugal their lifestyles are. I'm not suggesting that people living on $50k/year aren't already frugal, but yeah, there's definitely people who take out car loans, take out mortgages for the full amount they were approved for, and all sorts of random things like buying chicken parts instead of whole chickens, buying small grocery store containers instead of bulk pricing for shelf-stable items, keeping your speed down to save gas, etc.
You really just need to build an innate understanding that the hedonic treadmill doesn't make you happier long-term and develop a resolution to get your expenses down and stay disciplined about it.
There are three things you can do with your money - save it (e.g. investments), give it away (e.g. charity), or spend it (e.g. housing, vacations). Whether or not somebody's investment strategy (i.e. saving) is optimal for their income level has nothing to do with the frugality of their lifestyle (i.e. spending).
So you are saying when I first graduated from college in 1996 I should have been able to max out my 401K - then it was $10K I believe. I was making $22K.
If the median income is $70k a year, after taxes they should be able to save $23500 a year and have an HSA compatible healthcare plan and max out their HSA?
I have no idea how you got that from my comment. How much you make, how much you save, how much you spend, and how much you give away are all independent, and neither is it a zero-sum pie (for example, sometimes investments go down in value, and sometimes the line between giving away and spending is blurry).
To answer your question directly, $70k income is independent of the cost of living in high cost of living cities (like NYC or SF) vs. low cost of living areas. If you make $70k/year in NYC, no you don't have the spare income to max out 401k/HSA. If you make $70k/year working for Walmart in Bentonville, Arkansas, then yeah, I expect that you ought to be able to max them out.
I'm surprised that this doesn't require DNSSEC or at the very least actively encourage configuring DNSSEC. While I used to be fully in the camp that DNSSEC was way more trouble than it was worth, in particular when access was de-facto secured by trusted CA certificates, more and more DNS record types (CAA, CERT, SSHFP, these TXT records) are responsible for storing information that can be manipulated in MITM attacks to seize control of a root of trust.
Of course, this has little applicability to anyone who is small enough not to have nation-state level actors in their threat model. But when I look behind the curtain of even Fortune 100 companies that really ought to have nation-state level actors in their threat model, too often you find people who are just not operating at that level or are swamped with unrelated work. So I'm starting to become of the opinion that guidance should change here and at the very least be documented recommendations - if it's not encouraged down the organizational size scale, too often it's not applied further up where it's needed.
The RFC wording is a little weird. If the zone has DNSSEC configured, then the wording should be stronger and use MUST wording, and not imply that CAs will be compliant if they choose to avoid verifying signatures despite the presence of signstures. Likewise, these TXT records for dns-persist-01 ideally "SHOULD NOT" be deployed when DNSSEC is not configured.
An open PR on the draft (#35) adds exactly this language: if a CA performs DNSSEC validation and it fails (expired signatures, broken chain of trust), the CA MUST treat it as a challenge failure and MUST NOT use the record. The rationale is that dns-persist-01 records are long-lived, so a DNSSEC failure has more severe consequences than it would for a transient challenge.
DNS has always been a single-point-of-failure for TLS cert issuance. The threat is real, but not at all unique to this validation method.
(For example, an attacker with control of DNS could switch the A record to their server and use that to pass HTTP-01 or TLS-ALPN-01 validation, or update the _acme-challenge TXT record and use that to pass DNS-01.)
While this is true, improvements in the TLS issuance process should also improve security. When the eventual deprecation of TLS-ALPN-01 and DNS-01 comes, this new method would be completely secure.
Here, the record could for example contain a signature from the same key pair used to authenticate the account. The alternative is DNSSEC, but that's avoided by a lot of domains.
> tents don't need to be strong in compression - there's no weight on the roof
But there is on the floor, unless you expect the inhabitants to sleep more or less directly on the ground, including themselves, whatever is used as a mattress, belongings, small appliances, etc. Emergency habitation is not the same as a camping tent, it needs to be able to service populations that have difficulty with camping's limitations, like the elderly.
> Paper is not a material that scales up
Citation needed? It's made from a renewable resource (wood) and there's some 400+ million metric tons of paper production yearly (source: Gemini, so feel free to take with a grain of salt).
> Or would be practical for outdoor use
If exposed directly to the elements, sure. But what if the paper is laminated or otherwise enclosed within plastic, rubber, or other synthetic material well-recognized as hydrophobic?
The ground can already support the weight. Anything whatsoever in between the ground and the occupants is sufficient if your goal is to separate their feet from it.
> It's made from a renewable resource (wood) and there's some 400+ million metric tons of paper production yearly
They don’t mean production volume, they mean physically. You can’t increase the thickness of paper by 1000x to just make thicker, stronger, paper. It’s a different material entirely.
>Citation needed? It's made from a renewable resource (wood) and there's some 400+ million metric tons of paper production yearly (source: Gemini, so feel free to take with a grain of salt).
Sorry, I meant in the sense of physical scale - I wouldn't imagine the properties of paper at 50cm scale translate directly to say 5 or 10 metre scale.
To each his own, but while I can certainly understand the hesitancy of an architect to pick Zig for a project that is projected to hit 100k+ lines of code, I really think you're missing out. There is a business case to using Zig today.
True in general but in the cloud especially, saving server resources can make a significant impact on the bottom line. There are not nearly enough performance engineers who understand how to take inefficient systems and make improvements to move towards theoretical maximum efficiency. When the system is written in an inefficient language like Python or Node, fundamentally, you have no choice but to start to move the hotpath behind FFI and drop down to a systems language. At that point your choices are basically C, C++, Rust, or Zig. Of the four choices, Zig today is already simplest to learn, with fewer footguns, easier to work with, easier to read and write, and easier to test. And you're not going to write 100k LOC of optimized hotpath code. And when you understand the cost savings involved in reducing your compute needs by sometimes more than 90% by getting the hotpath optimized, you understand that there is very much indeed a business case to learning Zig today.
As a counter argument to this. I was able to replicate the subset of zig that I wanted, using c23. And in the end I have absolute stability unless I break things to “improve”.
Personally, it is a huge pain to rewrite things and update dependencies because the code I am depending on is moving out from under me. I also found this to be a big problem in Rust.
And another huge upside is you have access to best of everything. As an example, I am heavily using fuzz testing and I can very easily use honggfuzz which is the best fuzzer according to all research I could find, and also according to my experience so far.
From this perspective, it doesn’t make sense to use zig over c for professional work. If I am writing a lot of code then I don’t want to rewrite it. If am writing a very small amount of code with no dependencies, then it doesn’t matter what I use and this is the only case where I think zig might make sense.
To add another point to this. W/e people write online isn’t correct all the time. I was thinking zig compiles super fast but found that c with a good build system and well split header/implementation files is basically instant to compile. You can use thin-lto with cache to have instant recompilation for release builds.
Real example: I had to wait some seconds to compile and run benchmarks for a library and it re-compiles instantly (<100ms) with c.
Zig does have a single compilation unit and that might have some advantages but in practice it is a hard disadvantage. And I didn’t ever see someone pointing this out online.
I would really recommend trying to learn c with modernC book and try to do it with c for people like me building something from scratch
Also I was also thinking that breaking doesn’t matter that much, but my opinion changed around 10k lines of code very quickly. At some point I really stopped caring about every piece and wanted to forget about it and move on really
>with fewer footguns, easier to work with, easier to read and write, and easier to test.
With the exception of fewer foot guns, which Rust definitely takes the cake and Zig is up in second, I'd say Zig is in last place in all of these. This really screams that you aren't aware of C/C++ testing/tooling ecosystem.
> ...in the cloud especially, saving server resources can make a significant impact on the bottom line. There are not nearly enough performance engineers who understand how to take inefficient systems and make improvements to move towards theoretical maximum efficiency.
That's a very good point, actually. However...
> with fewer footguns
..the Crab People[0] would definitely quibble with that particular claim of yours.
Coming from Go, I'm really disappointed in Rust compiler times. I realize they're comparable to C++, and you can structure your crates to minimize compile times, but I don't care. I want instant compilation.
Zig is trying to get me instant compilation and I see that as a huge advantage for Zig (even past the first 2 weeks).
I'll probably stick with Rust as my "low level language" due to its safety, type system, maturity, library ecosystem, and career opportunities.
But I remain jealous of Zig's willingness to do extreme things to make compilation faster.
The key with C++ is to learn how to use the build system, make use of binary libraries, and if one can afford to use the very latest compiler versions, modules.
And avoid header libraries, C++ isn't a scripting language.
Eh, I'd say that Rust has a different set of footguns. You're correct that you won't run into use-after-free footguns, but Rust doesn't protect you from memory leaks, unsafe code is still unsafe, and the borrow checker and Rust's language complexity are their own kind of footguns.
But I digress. I was thinking of Zig in comparison to C when I wrote that. I don't have a problem conceding that point, but I still believe the overall argument is correct to point to Zig specifically in the case of writing code to optimize a hotpath behind FFI; it is much easier to get to more optimal code and cross-compilation is easier to boot (i.e. to support Darwin/AppleSilicon for dev laptops, and both Linux/x64 and Linux/arm64 for cloud servers).
Ok, but most rust code is not unsafe while all zig code is unsafe.
> and the borrow checker and Rust's language complexity are their own kind of footguns
Please elaborate. They are something to learn but I don’t see the footgun. A footgun is a surprisingly defect that’s pointed at your foot and easy to trigger (ie doing something wrong and your foot blows off). I can’t think how the borrow checker causes that when it’s the exact opposite - you can’t ever create a footgun without doing unsafe because it won’t even compile.
> but I still believe the overall argument is correct to point to Zig specifically in the case of writing code to optimize a hotpath behind FFI; it is much easier to get to more optimal code and cross-compilation is easier to boot (i.e. to support Darwin/AppleSilicon for dev laptops, and both Linux/x64 and Linux/arm64 for cloud servers).
I agree cross compilation with zig is significantly easier but Rust isn’t that hard, especially with the cross-rs crate making it significantly simpler. Performance, Rust is going to be better - zig makes you choose between safety and performance and even in unsafe mode there’s various things that cause better codegen. For example zig follows the C path of manual noalias annotations which has been proven to be non scalable and difficult to make operational. Rust does this for all variables automatically because it’s not allowed in the language.
> a footgun is a surprising defect that's pointed at your foot and easy to trigger
Close, but not the way I think of a footgun. A footgun is code that was written in a naive way, looks correct, submitted, and you find out after submitting it that it was erroneous. Good design makes it easy for people to do the right thing and difficult to do the wrong thing.
In Rust it is extremely easy to hit the borrow checker including for code which is otherwise safe and which you know is safe. You walk on eggshells around the borrow checker hoping that it won't fire and shoot you in the foot and force you to rewrite. It is not a runtime footgun, it is a devtime footgun.
Which, to be fair, is sometimes desired. When you have a 1m+ LOC codebase and dozens of junior engineers working on it and requirements for memory safety and low latency requirements. Fair enough trade-off in that case.
But in Zig, you can just call defer on a deinit function. Complexity is the eternal enemy, and this is just a much simpler approach. The price of that simplicity is that you need to behave like an adult, which if the codebase (hotpath optimization) is <1k LOC I think is eminently reasonable.
> A footgun is code that was written in a naive way, looks correct, submitted, and you find out after submitting it that it was erroneous.
You’re contradicting yourself a bit here I think. Erroneous code generally won’t compile whereas in Zig it will happily do so. Also, Zig has plenty of foot guns (eg forgetting to call defer on a deinit but even misusing noalias or having an out of bounds result in memory corruption). IMHO the zig footgun story with respect to UB behavior is largely unchanged relative to C/C++. It’s mildly better but it’s closer to C/C++ than being a safe language and UB is a huge ass footgun in any moderate complexity codebase.
Depends how you compile it. If you’re compiling ReleaseFast/ReleaseSmall, it’s not very different from C (modulo as you said it has some language features to make it less likely you do it):
* Double free
* Out of bounds array access
* Dereferencing null pointers
* Misaligned pointer dereference
* Accessing uninitialized memory
* Signed integer overflow
* Accessing a union field for which the active tag is something else.
(Btw: you can't null pointer dereference in zig without using the navigation operator which will panic on null; you can't misalign a pointer unless you use @alignCast which will also create a panic)
Neat. Why isn’t this in the main compiler / will it be? I’m happy to retract my statement if this becomes actually how zig compiles but it’s not a serious thing as it’s more a PoC of what’s possible today and may break later
It will never be in the main compiler, since it was written by Claude. I think that's ok. The general concept is sound and won't break (modulo names of instructions changing etc). In fact it will get better. With the new io, concurrency checks will be possible
But also, there is no reason why it should have to be in the main compiler. I've architected it as a dlload plugin. It's even crazier! The output is a zig program which you must compile and run to get the final result.
I the sentence "I can also analyse C and C++ code for such issues, while keeping using a mature languages ecosystem." it is implied there are many tools that perform analysis of C and C++ code.
Some of those tools are static, others are dynamic, some require a special build, others are hybrid, others exist on all modern IDEs.
So it can be a mix of lint, clang tidy, VS analysis, Clion, ASan, USBsan, hardned runtimes, contracts (Frama-C), PVS, PurifyPlus, Insure++,....
This is pretty close to saying Rust is not very different than C because it has the unsafe keyword. That is, either an ignorant (of Zig) or disingenuous statement.
I’m not going to write a detailed response to something that’s extremely close to what an LLM responds to “what UB does zig have?”
Arguing about whether certain static analysis should be opt in or opt out is just extremely uninteresting. It’s not like folks are auditing the unsafe blocks in their dependencies anyways.
If you want to talk about actual type system issues that’s more interesting.
So the Fermat defense? “I have the proof but the margin is too small”.
The proof is in the pudding. TigerBeetle despite having a quite opinionated style still almost hit by UB and basically got lucky it wasn’t a worse failure. By contrast, even though unsafe isn’t audited for all dependencies, it does in practice seem to make UB extremely unlikely. And there’s work ongoing in the ecosystem to create safe abstractions to remove existing unsafe into well tested and centralized things
As an example to this, I was using polars in rust as a dependency in a fairly large project.
It has issues like panicking or segfaulting when using some data types (arrow array types) in the wrong place.
It is extremely difficult to write an arrow implementation in Rust.
It is much easier to do it in zig or c(without strict aliasing).
I also had the same experience with glommio in Rust.
Also the binary that we produce compiles in several minutes and is above 30mb. This is an insane amount of bloat. And unfortunately I don’t think there is another feasible way of doing this kind of work in rust, because it is so hard to write proper low level code.
I don’t agree with noalias being bad personally. I fuond it is the only way to do it. It is much harder to write code with pointers with implicit aliasing like c has by default and rust has as the only option. And you don’t ever need to use noalias except some rare places.
To make it clear, I mean the huge footgun in rust is producing a ton of bloat and subpar code because you can’t write much and you end up depending on too many libraries
> To make it clear, I mean the huge footgun in rust is producing a ton of bloat and subpar code because you can’t write much and you end up depending on too many libraries
Nothing is forcing you to do that other than it’s easy to add dependencies. I don’t see how zig is much different
I find it easier to write all the code I want in zig or c since it is easy to write low level code.
Hashmap is a good example to this. I was able to fairly easily port some parts of hashbrown to c but I’m pretty sure I can’t write that code in Rust in a reasonable amount of time.
Not the GP, but I've noticed that because if you don't anticipate how you might need to mutate or share state in the future, you can have a "footgun" that forces large-scale code changes for relatively small "feature-level" changes, because of the rust strictness. Its not a footgun in the sense that your code does what you don't expect, its a footgun in that your maintenance and ability to change code is not what you expect (and its easy to do). I'm sure if you are really expert with rust, you see it coming and don't use patterns that will cause waves of changes (but if you're expert at any language you avoid the footguns).
That’s not a footgun and happens in any language. I have not observed rust code to be more prone to it. Certainly less so than c++ for various reasons around the build time and code organization.
I remember when learning Zig, the documentation for the language itself was extensive, complete, and easily greppable due to being all on one page.
The standard library was a lot less intuitive, but I suspect that has more to do with the amount of churn it's still going through.
The build system also needs more extensive documentation in the same way that the stdlib does, but it has a guide that got me reasonably far with what came out of the box.
People do under estimate how nice it is that the language ref or framework/tool documentation is all on one web page i can easily pdf print it and push it to my ipad for reading.
People who have difficulty on dating apps want to find a scapegoat, so they scapegoat the app.
The truth is that dating markets are lemon markets. People who are "dateable" tend to find success quickly, and people who are "not dateable" tend to stay on the market. Hence over time, the market will be dominated by "not dateable" people. No dating app on the planet will magically make you a "dateable" person.
To find success on dating apps, you have to work on yourself first, and only afterwards make sure that work shows through both in your profile and in your texting.
Source: was on the apps, undateable for eight years (depression and low self esteem), went to therapy, after making huge changes to my life and getting to a point where I felt like things were going well in everything but being single, a month later I found my girlfriend (now two years together).
I hate this phrase because it's a generic catch-all that says nothing but shuts down any discussion. If I'm friendly, responsible, honest, not poor, do sports, learn new things, keep the house clean, then the fuck more you want. Can we admit that social dynamics have completely changed and the value of "a relationship" dropped through the floor? 200 years ago bad relationship was better than no relationship because have fun trying to farm land on your own, but nowadays it's literally more convenient to live single than to deal with the inconvenience of living with another person.
Also, personally, I'm a minority within a minority, and I'm not going to cheat the statistics even if I shower twenty times a day.
> If I'm friendly, responsible, honest, not poor, do sports, learn new things, keep the house clean, then the fuck more you want.
I think you are describing a person who has worked on himself. Like doing sports, that's good. I think too many guys continue with their teenage hobbies like playing computer games, and that's generally not attractive to women.
Of course, there are no guarantees. There's no magic checklist that you can fulfill and be guaranteed to find a partner. But I think there's always more you can do to make yourself more attractive.
I'm gay, so I don't care about impressing women. But besides this... I don't understand what's wrong with incorporating teenage hobbies into adult lifestyle. Sure, nobody wants to marry a mental teenager, but if I do have adult self-development hobbies, then I see no problem that next to that I'd also have teenage hobbies. I find it very sad when guys completely discard their personality just to keep wife happy.
It's just that, at current point of my life I think I'm ready for a relationship. My daily life loop is satisfactory for me, the only thing I'm missing is someone to be with.
> If I'm friendly, responsible, honest, not poor, do sports, learn new things, keep the house clean, then the fuck more you want.
I know people like this, but they also are unlucky in love because they also have negative attitudes about women and life that they refuse to become more enlightened about.
> friendly, responsible, honest, not poor... keep the house clean
Even assuming I take you at your word, this describes a good roommate, not a good romantic partner.
> do sports, learn new things
Has negligible if any effect on romantic relationships. Both fat and stupid people still find romantic partners (and sometimes end up happy with them nonetheless).
> Then the fuck more you want
Somebody who is fun to be with, who makes me feel good, warm, and fuzzy inside, who at times makes me feel safe and at other times dares me to go farther. Somebody who is willing to go to new depths of vulnerability together, so that I can trust that they see me, the whole me, even the crummy parts, and I can see them, the whole them, even the crummy parts, and be loved and accepted nonetheless.
> The value of "a relationship" has dropped through the floor
This is transactional language. Strong, fulfilling romantic relationships are not transactional. Part of working on yourself is learning how to develop non-transactional relationships without getting hurt / getting exploited in your attempts to do so (i.e. by lemons on the market).
> more convenient to live single than to deal with the inconvenience of living with another person
I highly disagree, assuming that you find the right person to live with, which is the whole challenge. Living with another person who you enjoy living with, economically speaking, means splitting at least rent and electric bills (water bills are more linear with the number of people in the house), sometimes splitting a car payment (if you are a one-car household); when you split rent, you split the rent of the kitchen, the bathroom, the living room, and at least one bedroom, that are all shared. You eat better by cooking for two and sharing. The absolutely most economical arrangement is usually Dual-Income No Kids (DINK).
> Somebody who is fun to be with, who makes me feel good, warm, and fuzzy inside, who at times makes me feel safe and at other times dares me to go farther. Somebody who is willing to go to new depths of vulnerability together, so that I can trust that they see me, the whole me, even the crummy parts, and I can see them, the whole them, even the crummy parts, and be loved and accepted nonetheless.
Cool. If I had stated that I am like this, then someone else would've complained that this is overly romantic view and in reality a relationship is built with someone who can help with boring everyday tasks like doing the laundry or watching the kids. The point is, even if I were Jesus Christ himself, someone would find a flaw that makes me undateable in their opinion.
> This is transactional language.
Because all relationships are transactional. Welcome to adulthood. I don't really have time to argue with someone who still believes in Santa Claus.
> Living with another person who you enjoy living with, economically speaking, means splitting at least rent and electric bills (water bills are more linear with the number of people in the house), sometimes splitting a car payment (if you are a one-car household); when you split rent, you split the rent of the kitchen, the bathroom, the living room, and at least one bedroom, that are all shared. You eat better by cooking for two and sharing.
It's strange to me that you tell me not to be transactional, but then you point to money as an example of an advantage of being in a relationship, not emotional support. Also, there's a huge difference between "without a relationship, I'll literally starve to death" and "without a relationship, I'll go on holiday once a year instead of twice a year".
Something tells me that your view of relationships is incoherent at best.
> The point is, even if I were Jesus Christ himself, someone would find a flaw that makes me undateable in their opinion.
Well yeah, Christ isn't really dateable because he would never be able to be vulnerable with you (after all, if he died for your sins, you can't really repay the favor, can you?). People want to take celebrities to bed, they don't want to date them. It's a different kind of relationship - more shallow.
But more to the point, a flaw is not what makes somebody undateable. We all have flaws. I have flaws. My partner has flaws. Some kinds of flaws make people undateable, others do not.
> Someone who still believes in Santa Claus
I mean, my partner makes me happier than Santa Claus ever did, and I don't have to wait until Christmas for her to pay me a visit, so....
> point to money as an example of an advantage of being in a relationship, not emotional support
Emotional support was literally the first example I gave ("feel good, warm, and fuzzy inside"). I added the economic argument to address your framing. The emotional aspect is the #1 most important reason and I would be in my relationship for that reason alone, even without any economic benefits; the economic benefits are a silver lining and insufficient on their own to justify a relationship. But no, I'm not going to pretend that the silver lining doesn't exist.
If employees get stock options and decide to exercise on exit, they count against the 500 unaccredited investor limit that would trigger reporting requirements. So companies that issue stock options do have an outside risk that enough employees will exit, exercise their stock options, and trigger a reporting requirement.
Good homilies are written with the particular community in mind. If it were more effective to write a homily for a generic public, the Vatican would have started publishing standard homilies long ago.
reply