I'm certain everything Textile does could be handled by bash scripts, or any other script flavors / languages / tools. So, yes, Textile is supposed to be a more convenient way to do it.
I'm not too familiar with Espanso, but Textile is not a text expander. Textile allows you to pre-define a sequence of steps that dynamically generate the text you want, by running commands on your computer, reading your clipboard, or using hard-coded text you provide.
Here's a quick example, and one that I often use with Textile to generate a preview URL based on my current branch:
(1) Start with the output of the command `git branch --show-current` in the `~/code` directory (yielding text like `JIRA-1234/some-feature`).
(2) Replace all `/` characters with `-` (now the text is `JIRA-1234-some-feature`).
(3) Prepend `[preview](https://staging-`, which is the start of a markdown link (now the text is `[preview](https://staging-JIRA-1234-some-feature`).
With those steps saved in Textile, I can now click a button to run them over and over again (or use a keyboard shortcut if I assigned one). So no matter which branch I'm on, I'll always get a proper preview link without having to construct it manually myself.
"...fewer than 4,000 jobs, representing less than 5 percent of our total employee base."
I cringe at this attempt to soften the numbers by saying "fewer than" and "less than" here. Conversely, and ironically, it also puts inflated numbers in your head.
I just got laid off by Pie Insurance, along with 64 other people (including staff software engineers, engineering managers, product managers, and other roles). I worked across the stack at Pie, building design systems and reusable UI components on the front end, as well as APIs and event-based systems on the back end.
Wow, the way Upwork is handling this seems really bad. They announced the layoffs today, but nobody will know who is being let go until next week! Sheesh.
Our first year on Vercel, the bill was $40,000. When our management went back to negotiate the second year, Vercel wanted $120,000! Vercel wasn't offering 3x the features, mind you, they just knew we were locked in. Our management got it down to $60,000 (still a 50% cost increase, year over year).
Our app is small beans, too. We don't even have that many users. To borrow a favorite term from DHH, Vercel are "merchants of complexity."
But they're only half the problem. Our management is the other half. They can't be bothered to grow a spine and move away from Vercel. So we'll just keep paying, and eventually some people will "be affected" by a "reduction in force."
I once had an external monitor with a maximum refresh rate of 30 Hz, and mouse movements were noticeably sluggish. It was part of a multi-monitor setup, so it was very obvious as I moved the mouse between monitors.
I'm not sure if this LG display will have the same issue, but I won't be an early adopter.
My wife and I canceled Netflix a while ago and went back to DVDs. An FYE store in our area recently had a store closing sale, so we bought three DVD players and snapped up all our favorite DVDs for a few bucks each.
No subscription, no mid-movie ads, and no worrying about this or that service losing the streaming rights to whatever.
I never actually type semicolons in my JavaScript / TypeScript. In work projects, my IDE adds them for me thanks to the linter. In personal projects, I just leave them out (I don't use a linter, so my IDE does not add them), and I've never had a problem. Not even once.
I'm seeing a 404 page. I assume this is unintentional, but it's making a funny point: How could AGI possibly be imminent and we still have 404 pages?
Regardless, I agree with this article whose body eludes me: AGI is not imminent, it's hype in the extreme. It's the next fusion. It's perpetually on the horizon (pun intended), and we've wasted trillions on machines that will never reach it.
We went from having new JavaScript frameworks every week to having new AI frameworks every week. I'm thinking I should build a HN clone that filters out all posts about AI topics...
I've created a new issue for this (it's similar to an idea I already had):
https://github.com/rob-johansen/textile/issues/75