6,563 karma · joined January 10, 2012
name Michael Bradley
code https://github.com/michaelsbradleyjr
tech <3 https://www.gnu.org/software/emacs
https://nim-lang.org
https://clojure.org
https://racket-lang.org
https://developer.mozilla.org/en-US/docs/Web/JavaScript
https://libp2p.io
https://ethereum.org
faith https://j.mp/Catechism
https://j.mp/CatechismOfTrent
https://www.latinmass.live
https://institute-christ-king.org/videostream
https://divinumofficium.com/cgi-bin/horas/officium.pl
https://universalis.com/readings.htm
https://savior.org
& reason https://j.mp/FidesEtRatioEn
https://www.magiscenter.com
https://www.feynmanlectures.caltech.edu
https://mathworld.wolfram.com
https://www.plasmauniverse.info
perspective "The true wisdom on which we ought to set our eyes is
perfection, which consists in union with God by love,
according to the saying of the Apostle St. Paul:
'Above all I commend to you charity, which is the bond
of perfection', and joins and unites us with God."
~ Alphonsus Rodriguez
https://archive.org/download/PPCV-Manresa/PPCV-Manresa.html
center Jesus Christ, King of Mercy and Justice, teach us how
to love the cross and the poor, and to humbly build
your Father's kingdom with faith, hope, and charity.
https://j.mp/LaudeturJesusChristusTotally agree, that is how it should be.
Let’s compare an average daily Mass (e.g. 8 AM on a ferial day at St. Joe’s, no music) in the Novus Ordo with a TLM Low Mass. Let’s assume that in either form it lasts about 45 minutes.
In the N.O., from start to finish, the priest is in a kind of dialogue with the people, accentuated by the versus populum arrangement that has become the universal norm. In between the responses of the laity and for a stretch of time surrounding the consecration, there is time for interior/silent prayer by the laity. The laity’s posture changes from sitting, to standing, to kneeling many times throughout. On the whole, the flow of the liturgy is marked by outward verbal and postural activity of the laity punctuating the span of 45 minutes. That is by design, and is supposed to be conducive to so called “active participation”. Now, and this is important, if that N.O. Mass was offered entirely in Latin and the laity in attendance knew and spoke all the responses in Latin, it really wouldn’t change “the way it goes”.
At TLM Low Mass for the same ferial day, the laity would kneel after the priest begins the prayers at the foot of the altar, and some might change their posture to/from sitting a couple of times over the next 45 minutes, while others would kneel the entire time per their preference. No responses are offered by the laity, only by the altar server/s assisting the priest. The priest faces the same direction as the people the entire time, except when distributing Holy Communion to them, that is toward the altar, a.k.a. ad orientem because classically that would be eastward. Much of the text of the Mass is prayed sotto voce by the priest, i.e. it’s inaudible or barely audible by those in attendance. On the whole, the liturgy is marked by near silence and the laity in attendance joining their silent prayers to the quiet actions of the priest at the altar.
Nobody can really blame you for the impression you got/get from the Novus Ordo Missae.
However, that’s not really what Mass was like for the laity for most of the past 1,000 years (much longer actually, but the history of Western Catholic liturgy is complex so I’ll leave it at that). It was mostly a context for silent mental prayer that, ideally, (1) is informed by the sanctoral/seasonal calendar, (2) prepares the worshippers to join themselves spiritually to the sacrifice offered on the altar by the priest, (3) prepares them to receive Jesus in Holy Communion.
You can experience the same today at the Traditional Latin Mass. The difference in atmosphere can be rather shocking if all you’ve ever experienced is the N.O. A lot of newcomers, who are also lifelong Catholics, relate a feeling of not knowing what to do with themselves throughout the liturgy — well, you’re supposed to cultivate your interior life, spend the 60-90 minutes actually praying instead of just rattling off verbal responses and warbling out bad hymns.
In practice, it's turned out to be an "expert's tool" that's more expressive-convenient than C/++ to do all manner of things in the realm of systems programming, from embedded to HPC. And it's got great C/++ interop, so you can continue to leverage those software ecosystems.
In that respect, I'd say the biggest boon, rather than a killer project, would be for a famous programmer or shop to publicly and loudly adopt it as their everyday language, shouting its name for several years and saying things like "Wish we had started using this years ago, would have been so much better, look at all of these great apps and libraries we've been able to create and maintain more easily than if we'd stuck with C/++/Go/Rust/Swift!"
There’s a rule of thumb: write a macro as a last resort.
It’s not hard to stick to it. In general, you can go a long, long way with HOFs, transducers, and standard macros before a hand-rolled macro would serve you better.
Man available to the woman effectively around the clock every day, setting majority of the time is private and comfortable enough that sex can just happen, in compressed and sometimes exciting timeframe, i.e. even if busy with WFH and childcare.
I am aware of couples who struggled or are struggling with fertility, and using the various tools and techniques to increase the odds. I am not discounting their experiences and hardships. I am saying that, on average, if more couples of child bearing age are sexually accessible to one another effectively 24/7, then there are natural instincts that can and do play a role in them coming together sexually at the critical time for conceiving a child, and so more children would be conceived.
If earth is about 4 billion years old, but it takes say 400 trillion years for natural processes to produce this chemistry, then it happened out there not here.
This was a key reason why Hoyle preferred a steady state model of the universe — the part of the universe we inhabit needs to be very, very old for this stuff to work out, according to his thinking. A minority opinion, for sure, his rejection of the Big Bang model and timelines lost him a lot of respect among his peers. And his ideas could be wrong, I’m just pointing out that historically panspermia proponents have taken this position as to “why not here”.
You can use words however you like, of course, but others may struggle to understand your perspective if your usage is novel and/or strained. General consensus is the early modern period of theological development in Christian history began in the 1500s.
> To an outsider there is little if any difference
Fine, but… two people could be sitting at similar looking computers, one playing Minesweeper while the other is doing chemical engineering in MATLAB. There are objective differences in those human activities. If someone insisted they are doing pseudo-same-thing, it would be fair to say that’s a stretch and tends toward missing the point. But I do (maybe) understand what you mean: inculturation was a real phenomenon as Christianity spread Eastward and Westward.
The theological language of hypostases in relation to the divine persons of the Trinity was worked out in the late 300s but proto-Trinitarian language is found in Christian writings nearly 200 years before that, i.e. butting up against the close of the apostolic age. So, how is it you propose it’s a modern invention? That is, what timeframe constitutes “modern”? Even 300s is considered early Christian history.
Likewise, from the early Church onward, Christians were careful to distinguish reverence for and intercessory invocation of martyrs, saints, and angels, who are all just creatures, from worship of God.
https://www.ecatholic2000.com/lagrange/interior1/interior.sh...
https://www.ecatholic2000.com/lagrange/interior2/interior2.s...
There may be a 24/7, or frequently open, adoration chapel nearby to you. Maybe you could make a daily trip to spend a little time (a “holy hour”) with Christ present with us on earth in the Blessed Sacrament?
For me, Kitty still has the edge:
https://sw.kovidgoyal.net/kitty/
WezTerm is also a strong contender:
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.
I'm certain I haven't misunderstood the point of MSYS2's CLANG64 and other environments.
> These binaries themselves are built to run in the MSYS2 environment
I'm not sure if you're referring to the toolchain binaries or the binaries one produce's with them.
The CLANG64, etc. environments are 100% absolutely for certain for building software that can run outside of any MSYS2 environment!
You can, of course, build executables specifically intended to run inside those environments, but that’s not the primary use case.
> (gci Env:PATH).Value.Split(';') | sort
I don't want to use PowerShell or Cmd.exe when doing dev stuff on Windows. I want to do CLI work and author scripts in and for modern Bash, just like I would for Linux and macOS. I want to write Makefiles for GNU make, just like...
Now, sometimes there are bumps and sharp edges you have to deal with via `if [[ -v MSYSTEM ]]; then`, similar in Makefile, cygpath conversion, template/conditional code in sources, and so on. But that's a small price to pay, from my perspective, for staying in the same mental model for how to build software.
I built a network daemon using the MSYS2 CLANG64 environment and llvm toolchain on Windows 10.
Windows 7 x64 users could download the compiled single-file executable and run it just fine, so long as they installed Microsoft’s Universal C Runtime, which is a free download from Microsoft’s website.
It gives you a *nix-like shell/dev environment and tools, but you build native software that runs on Windows systems that don’t have or need to have all/parts of MSYS2/Cygwin installed.
The Windows-native software you build with MSYS2 can be shipped to and run by users that don’t have anything of MSYS2 installed.
I don’t want to even hazard a guess how many times folks new to Nim would ask “How do I work with ref across threads without running into SIGSEGV?”, and the answer might as well have been to become a Jedi master unless the use case fit very well with one/more (let’s be honest, experimental) structured concurrency libraries. Sometimes that would turn out to be the case, or could be the case if they would pretzel their mental model for the business logic, but generally it was a big turnoff.