Seems like an unusually boring Resolve release. There's nothing there I particularly want to try out. Nothing wrong with that, I've just got used to every release having a ton of shiny new stuff in it.
I guess the agentic stuff is probably exciting to somebody.
For the people who are sad about the high prices of the Pi range, I want to mention that I'm having a lot of fun with the Pi Pico 2. It's obviously not quite the same thing (ie. not a regular desktop computer), but it's ridiculously capable for its few-dollars price point. There's a lot you can do with it.
If you just want a cheap computer the Pi's don't seem so great these days, but the Picos are where the fun is now.
This is a weird conversation. Python was a strange choice back then, but is now probably the most popular programming language in existence. If anything the choice of Python (and C++) was remarkable foresight / luck.
If Eve were green-fielded today, there is a 0% chance they would choose Python anywhere in the service layer for an online game. Zero chance.
Python is a fantastic "glue" programming language. A duct-tape language. It's awesome for little scripts, or for gluing together some AI scripts, where you're basically atomically gluing a series of calls to giant native C/C++ libraries like pytorch that are then doing a series of calls to giant native C/C++ libraries like CUDA. Where the overhead of python is negligible compared to some heavy lifting being done by a better language/system.
The simple fact that we're talking about a service that was stuck on Python 2 two decades after it was replaced, half a decade after it was fully deprecated, reveals this to be 100% just debt. The fact that they talk about millions of lines of Python code, and that Python 3 represents a big speedup for their operations, again betrays it to be nothing but debt. They have Python code in the critical flow, not just as a light glue over intensive code, and they have almost certainly spent untold dollars on extra hardware, delivering a worse experience for their users, because they had a "python enthusiast" in a critical position decades ago.
Dolly wrote the lick herself, and when she was in the studio with the session players, they wanted her to show them how to play it [0].
She ended up having Chip Young lay it down on the record since her long fingernails made it difficult to nail consistently. This is also why if you watch videos of her playing guitar she plays in open tunings [1].
I still carry the rather 20th century idea that a performer of almost any kind also ought to have some sort of other talent in addition to their main one. The versatility of that sort of thing is one of the things that should separate a pro from the rest. I generally count "professional level musician" on more than one instrument as fulfilling that contract... perhaps one of the easier of the options, but it still carries that versatility advantage. Another example that I'm quite fond of is famous comedian Steve Martin performing Dueling Banjos with Kermit the Frog. The combo of two professional entertainers playing off of each other combined with the music skills creates the opportunity for a creative routine.
> I use it to add text to a family photo. The primary storage medium is jpeg. I don't want or need anything else.
So you open your photo, add your text, press Ctrl+E, choose a filename or press Enter to overwrite your old version, and press Enter to accept the default jpeg settings.
I guess it could save a couple of keypresses by auto-overwriting your original file without asking, or not asking about jpeg settings. But it doesn't seem like an outrageous workflow, considering that other people will want those options.
I do feel the same way as you about Photoshop muscle memory, having got quite good at it in the '90s and never really having caught up in Gimp.
I'm a fairly casual / infrequent user, but they've already addressed most of the things I found infuriating in the past.
The big remaining thing I can think of is the "layer boundary" thing, which (it seems to me) is very confusing for new users and inconvenient for all users.
I also have a vibes-based feeling that when I used to use Photoshop twenty-five years ago I was a lot more productive than I'm able to be in GIMP, but I can't be sure if that's just because I used to do more graphic stuff back then and I've never picked it up to the same degree. I find myself having to hunt for things in menus a lot, but that might be a me problem. Photoshop also took a while to get used to.
Edit: I basically agree with the people complaining about Save and Export being unexpectedly separate, although also it's not that hard to press Ctrl+E instead of Ctrl+S.
After the first run (where it has to evaluate plugins etc) it starts in under 4s on 26.04 on my Lenovo P53 (laptop from 2019). Which is admittedly not exactly snappy, but it's OK IMO.
If you use the friends or "all" feeds, you just get stuff about what your friends are up to and things from pages you've subscribed to. Or I do anyway. Also good for discovering events locally.
Even the main feed isn't that bad for me. I guess it depends who your friends are and what you click on.
I think the closest thing to an actual "standard" is AES5-2018, "Recommended practice for professional digital audio".
Abstract:
> A sampling frequency of 48 kHz is recommended for the origination, processing, and interchange of audio programs employing pulse-code modulation. Recognition is also given to the use of a 44.1-kHz sampling frequency related to certain consumer digital applications, the use of a 32-kHz sampling frequency for transmission-related applications, and the use of a 96-kHz sampling frequency for applications requiring a higher bandwidth or more relaxed anti-alias filtering. This revision further quantifies the preferred choices for higher sampling frequencies.
Edit: From my personal perspective, 44.1kHz is a legacy minor annoyance
I guess the agentic stuff is probably exciting to somebody.
reply