I’m liking the transition, as I have less work now. My day is a lot more waiting on the AI to complete a task or waiting for a human reviewer to do a pass on the code so I can spend more of my time doing important things, like scrolling on lemmy.

Maybe it’s just me but this sounds like torture to me. I have enough progress bars to wait for in my work day and I would rather do something else with my life if waiting and reviewing generated code becomes the bulk of it. It’s good to see that some people do seem to enjoy doing it so maybe there’s a chance I don’t have to.

Not with that attitude.

Maybe they are trying to manifest its death by arranging its funeral over and over. Programming as an art form isn’t more dead than painting as an art form, as long as people want to do it. However, as the blog post hints at, what you produce for work wasn’t perhaps ever meant to be a work of art. You aren’t necessarily going to be able to write code in your favorite style for work anyway, unless you can influence it and decide the conventions. That has been true since forever in larger organisations.

Props to the blog author for seeking out new experiences in their free time but what they are mourning is either still there (just write your art code) or they have just had to adjust to their new trade-off. Don’t be surprised when it doesn’t feel artistic if you don’t spend any effort on the process.

That’s nice to hear! And the Ok* color spaces are indeed quite neat

ICC profiles are definitely part of the field, but that’s sort of a topic of its own. At least in terms of scope. The color space rabbit hole is so deep that I never got as far as including them. There are other crates that go into those parts and it should be easy to bridge between them and Palette.

I would say Palette is more for the “business logic” of working with colors, so converting, manipulating and analyzing. The difference from ICC profiles when converting with Palette is that you need to know more about the source and destination color spaces during compile time. ICC profiles use more runtime information.

Palette could be used for applications like image manipulation programs, 3D rendering, generative art, UI color theme generation, computer vision, and a lot more. A lot of people also use it for smaller tasks like converting HSL input to RGB output or making gradients.

My shower has its own favorite temperature and will slowly readjust itself to it.

I considered the smaller one at first, but decided to take the larger one and use the compression straps to keep it tight when packing a smaller volume. It doesn’t feel as bulky as I thought it would at first.

Got myself a proper hiking backpack. An Osprey Exos 58L. Shifting much of the weight to the hips makes a massive difference and my back was very happy!

Also the Swedish classic “glida in på en räkmacka” ((to) slide in on a shrimp sandwich), which basically means to end up somewhere (location, career, situation) without any difficulties. The shrimp sandwich symbolizes a life without difficulties or in some luxury.

Then there’s also “halka in på ett bananskal” ((to) slip in on a banana peel), which is similar to the above, but not always favorable and you don’t have any plan or preparation. You just winged it or it just happened by accident.

Absolutely, I didn’t mean to suggest otherwise. :) I’m just giving a bit of context and perspective from someone who has used it for a while.

Static types aside, the file system has a lot of failure cases, which every language is affected by, and Rust makes them very visible. This can indeed feel like a lot, but it’s an intentional feature and makes more sense in larger projects. I guess the feeling may get amplified by the author’s style of long form posts with a lot of details.

Error handling in practice contains a lot of “let the caller deal with it”, using the ? operator to pass errors up the call stack. The more verbose options are for when you need to actually handle it.

They interviewed multiple eye witnesses.

To make things worse, that teapot doesn’t have a bottom surface.

I’m of course only one single anecdotal sample, but the release cadence has probably been the least of my problems. My experience is that it’s fine to not update for quite some time. I have a crate with 1.60 (released about one and a half years ago) as MSRV, which means I run unit tests with that version, as well as stable, beta and nightly. The only pressure to upgrade is that some dependencies are starting to move on. Not that the newer compilers reject my code, not even anything deprecated.

Also, small, frequent releases usually takes away a lot of the drama around upgrading, in my experience. Not the opposite. A handful of changes are easier to deal with than a whole boatload. Both for the one releasing and for the users.

Do you want the background to have looped back to the start after one cycle? If so, you probably have to make it repeat N times more than the foreground, and move by a factor of 1/N in comparison to the foreground. Or put another way, have 1/N times the length. That means that after one cycle, the background has moved a distance of 1/N, but also repeated exactly once.

I hope this makes sense…

The HTC color system? I have been looking at it and was planning to give it a try after CAM16 support is in. HTC is partially based on CAM16, after all. CAM16 is kind of complicated to get right, so it’s taking a while…

Alright, but nice that it turned out to be what they were looking for 😁

That’s awesome to see! 👀 I actually found one or two of your repositories back when I was looking around at how people were using Palette (to not develop it in too much of a vacuum). I’m happy that you’re finding it useful! Do you remember if there was any specific feature, when picking the crate, that you found particularly nice or helpful?

Also, don’t hesitate to let me know if anything is missing or can be improved for your needs. 🙂 I try to keep the scope somewhat focused, but I’m always open to ideas and feedback.