📄"St. Bonaventure's universal hylomorphism comes from Avicebron" is entirely false. St. Thomas contends against Avicebron (de Substant. separatis, 5-8), but that's neither St. Bonaventure's position (II Sent, d. 3, p. I, a. 1, q. 1) nor his main sourcetext/authority - St. Augustine.

At @Expo we now run TypeScript ESM in Node.js in production in a small user-facing service. There is no compilation step with Babel or tsc, just Node. It used to be a stretch to achieve this with Node.js TypeScript Jest but now it is viable. This is the setup: [Build] npm install --production This is the full build. We run tsc only during the test phase for type checking. The added cold start latency to parse TypeScript is about 1-2ms for a small codebase (de minimis in Kubernetes autoscaling). The Node.js runtime options are: --disable-warning=ExperimentalWarning --experimental-transform-types In development we add --watch and --inspect [TypeScript] tsconfig.json is mostly: "@tsconfig/node24" preset allowImportingTsExtensions noEmit Import specifiers use .ts file extensions. This works for services as opposed to published libraries where you should use .js import specifiers since you must publish JS. Imports are divided into "import" and "import type". Node.js will fail if it tries to import a type that has been stripped at runtime so you must distinguish static types vs. reified values. [Performance] Peak memory usage seems higher. Have not yet bisected to find whether this is due to Node.js 24 or TypeScript or ESM. I read awhile ago that CJS was measurably faster to load than ESM. That was for an older version of Node.js and may have been fixed. For a small service this doesn’t matter. For larger services we will keep a build step to save about 500ms of TypeScript parsing and will benchmark CJS vs. ESM and compile to CJS if it performs better (speed, memory). [Testing] The Jest config needs: "extensionsToTreatAsEsm": [".ts"], We still use a custom Jest transformer since "--experimental-transform-types" is not passed to workers. It’s small: import { stripTypeScriptTypes } from 'node:module'; export default { process(sourceText: string) { return { code: stripTypeScriptTypes( sourceText, { mode: 'transform', sourceMap: true } ) }; }, }; It would be better if Jest automatically ran workers with TypeScript enabled if the main process has it enabled. However, the custom transformer uses Node’s own API to process TypeScript so there should be high parity with production. jest.unstable_mockModule and dynamic imports replace the classic jest.mock calls. Manual mocks behave strangely (they aren’t loaded but seem to get registered). And sometimes imports from mocks lead to OOM errors. Make small changes and test continuously. [Lessons] This is directionally how we want to develop. High parity across development, testing, and production. Low runtime overhead and config maintenance in those three environments. I would like configs to asymptote zero. Node.js could auto-enable "--experimental-transform-types" when the entry point file ends in .ts. Jest could do similar. Today’s state is still good. Every year I would try to achieve this and would hit another roadblock at the intersection of technologies like Jest and ESM. Everything works now because of the hard work of people who work on V8 (ESM capabilities for Jest), Node.js (thank you for TypeScript parsing and being able to "require(ESM)"), TypeScript (keeping pace with Node.js/package.json) and Jest (making ESM work in a project that started with module mocking, TypeScript support). In a year or two perhaps this full setup will work out of the box.

スクリプトにするのは面倒なので私ならエクスプレッションで解決しますね テキストレイヤーにSlider Controlのエフェクトをかけてから テキストレイヤーのSourceTextに以下... 続き→marshmallow-qa.com/messages/… #マシュマロを投げ合おう

1. Psalm 50, of which St. Teresa of Avila prayed on her deathbed. 2. Some sourcetext and prooftext familiarity with St. Ephrem but that's all, unfortunately. 3. Escape, 50/50 for the Beatific Vision? I'll take those odds. 4. Cutepost

Made with Moglyph FX by @fremox59 aescripts.com/moglyph-fx #aescripts #aftereffects #moglyphfx Thanks to the new #aftereffects API's methods available in version 24.5.0x41 and after, we can now easily mix regular editable sourceText fonts with other specified fonts in a dynamic, "animator like", way thanks to some expressions! Here is a quick test achieved with a few MoglyphFX fonts MoglyphFX - with all its glyph fonts that you can use in any software- is available on my @aescripts store : aescripts.com/moglyph-fx/ (link in bio) More infos about upcoming version 4 soon ;)

After Effects V25 Text Styling set up - 4 Text Styles with multi-modal Text Selectors. The sourceText Expression has 396 lines - includes Commenting. But it performs very well - near real time in AE. Used AE's V25 Text Style features? Want me to test something?

Thanks to the new #aftereffects API's methods available in version 24.5.0x41 and after, we can now easily mix regular editable sourceText fonts with other specified fonts in a dynamic, "animator like", way! Here is a quick test with a few MoglyphFX fonts (aescripts.com/moglyph-fx/)

haha i agree mostly, i just find it funny how so many AUs are very very far from the sourcetext to the point i dont even recognize the ship beyond aesthetics. actor aus i find very interesting because like what is it that appeals about it ?? its not even the same characters

a part of fandom culture i think is interesting is AUs that just end up using the characters put in the AU as aesthetic rather than as believeable extensions of the characters as they exist in the sourcetext

6 years old so I’m not going to pretend it’s any good but here’s the sourcetext at least

Tbh, there is also a point to be made about how one should probably get help to understand the sourcetext before changing it anyways, even with jokes. The screenshotted event in the game has a randomness factor to it, most likely because it is about not understanding it.

Loop In out is a constant. That and Sourcetext = thislayer.name on type layers.

Poaching an argument, aping a style, subconsciously lifting a melody… more and less obvious… but direct reproduction of a sourcetext seems more intimate and daring — how could you not know that what you do??

I’d love to see more about how you’ve set this up under the hood. For example, you’re linking sourceText to the path length property, but I’d love to know what logic you’ve implemented to determine which characters get duplicated to fill the space when the path stretches, etc.

#13inh Tạo đồng hồ đếm giờ với #AEexpression 1. Tạo 1 comp mới 2. Tạo Solid layer mới làm nền 3. Tạo Text layer mới, chỉnh font, size và màu sáng cho text 4. Thêm Slider Control cho text layer, keyframe hoặc time 5. Trong thuộc tính SourceText gõ JS như hình.

* the removal of the legacy LSP server and SourceText implementations in favor of the Adaptive LSP Server and SourceText implementation from our friends over at the Roslyn project. Everyone go update, and happy #fsharp hacking!

expression showcase for the glitchy elements from my last tweet make sure "value" from the sourceText expression is just a singular pipe character :)

We're back! @a_ferrares @SilviaBernardin & their colleagues from UBologna propose an innovative & fascinating "comparallel" approach to #newstranslation They provide fascinating insights into the notions of #sourcetext & #targettext, and, ultimately, #translation #UCCTS2023

You only have patristics because athonites kept translating (into their own languages like georgian or bulgarian) and recopying them for centuries and never stopped doing so. And they didn't need no translation from papist, they had both the language mastery and the sourcetext