ericwood

Browsers intentionally add jitter to timing methods like setTimeout and setInterval to avoid fingerprinting and other side channel style attacks. When I've messed with building in-browser sequencers in the past you had to use a webworker with the clock that sends messages back to the main event loop, although I'm sure there's reasons that won't work these days either.

CSS suffers from one of its original design tenants in that it's very easy to throw some shit at the wall and kind of get it working without fully understanding it. This is especially true for people who have dabbled in it from time to time in their career when absolutely needed. It's rare to see someone sit down and learn it from first principles. It doesn't take long and knowing the basic theory goes a long ways!

Those are pretty wild accusations from someone who doesn't know me or my beliefs. I definitely have not been calling for those things, especially not through the lens of religion.

Everything I said here in regards to his beliefs can be easily verified. It's crazy to me to respond "well you're doing the same to them" as a retort. I'm not?

They would be liars, then.

There's disagreement then there's being an outspoken supporter of systematically trying to strip rights away from others because of your religious beliefs. It's much deeper than having differing views on fiscal policy.

These are super cool and I've never seen one before! I'd imagine most of the passes I'm in are within spitting distance of at least one town so powering a substation isn't out of the question. It seems like most of the installations are very much "middle of nowhere" situations. I hope to run across one of these in person!

It is so disappointing; I started getting into photography over the past few years, shooting rolls of film here and there and need some basic library management tools to track my shots and add EXIF data for film stock, camera, etc. Photos.app kind of does what I need, but there's baffling decisions like all photo data being uneditable, even through APIs. You can edit EXIF data on the original image but the app's internal database is completely immutable. I have a handful of photos with inconsistent metadata I'd love to fix and the only option appears to be removing them from the library and re-adding them.

I really don't need many features! I'm not a pro and while I wouldn't mind shelling out a one-time fee for good software I'm not paying a subscription for cloud storage I'm not going to use. The OSS options here are not awesome, either.

It's honestly incredible they're bringing this to market! This style of incubator tends to work on a lofty goal and the research and ideas explored on the way trickle down into other parts of the company and find their way into more accessible products. Really similar in theory to the over the top concept cars manufacturers build that never see the light of day.

If speaking strictly in terms of audio effects this is a delay, with "echo" usually implying feedback so the delayed signal is attenuated and fed back into the delay line, getting quieter each iteration and fading naturally.

Yes and no, and the answer will depend a little bit on your background. It's Rust, and the learning curve around that still exists. The HAL does a very good job at papering over some annoying details, e.g. if you're working on STM32s you'll be able to get things working without having to dig into the monstrous clock trees and timer peripherals. I found one of the biggest learning curves to be dealing with shared mutable state; embassy offers lots of primitives and tools for dealing with this that are more approachable than you'd encounter with a vanilla embedded Rust project, but there's a little bit of a time investment to learn them and you'll find yourself reading a lot of example code.

Once you get the basics, though, it's very productive and I've found it surprisingly easy to write building blocks I can reuse across a wide range of hardware projects and MCUs!