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.

love this, in a similar vein real heads will remember The Echo Nest https://en.wikipedia.org/wiki/The_Echo_Nest

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!

One of my favorite games when traveling is spotting the iconic horn antennas that are still in operation or the various towers that were a part of it. A good chunk of the site are still in active use with all kinds of new equipment bolted onto them, and you can sometimes see holes in the platforms where the original horn antennas used to be mounted.

Microwave is line-of-sight so here on the Colorado front range and deeper into the mountains there's a bunch of sites high up on mountain tops that connect more remote towns. It's always fun to stumble across them when hiking, and I've made a point now of visiting some of the ones that are trail accessible to take photos. The juxtaposition of industrial equipment with the scenery is very striking and it's been fun to take film photos and submit them to the gallery on long-lines.com. Sometimes I worry someone might mistake some of my B&W photos as being much older than they actually are!

There's a bunch of amazing videos from the era on the AT&T archives channel on youtube, they're a lot of fun. It's easy to forget how groundbreaking this was at the time! https://www.youtube.com/@ATTTechChannel

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.

Very similar in theory to Bob Widlar's legendary "hassler" circuit

https://en.wikipedia.org/wiki/Bob_Widlar#Personality

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!

Fond memories of a job circa 2013 on a very large Rails app where CI times were sped up by a factor of 10 when someone realized bcrypt was misconfigured when running tests and slowing things down every time a user was created through a factory.

This is exactly how I feel; I'd love a switch that performs like the modern apple keyboards. Anytime I've dipped my toe into mechanical keyboard waters I've lost speed and accuracy, even after weeks of practice. The extra key travel felt like it gave me more fatigue, even with low profile switches. Whenever I've researched alternatives I get the sense I'm in the minority, though, and most mechanical keyboard users are after a very different feel. It's a huge shame, because I'd love to move to something with a split for better shoulder/arm positioning.

I've always viewed computers as being an obvious complement. Of course we worked so hard to build machines that are good at the things our brains don't take to as naturally.

All of this and the only image linked is a collage clocking in at a whopping 512x218px...anyone know where we can see the full resolution? It looks spectacular from the thumbnail!

Labor is a factor but it helps to have the insane manufacturing synergies they have where almost all of the parts are made down the road from you.

Macs still have target disk mode but it requires rebooting. Highly recommend using thunderbolt to transfer over to a new computer!

To be fair, this is the case with any styling approach; if the style is applied to the element, it's there for you to toy with in the inspector.

But you have recourse! It’s not ideal, but it beats being at the mercy of a vendor in most cases. Trying to hack around a closed source format is an even bigger drain.

100%, there's weeks I just plug straight into an amp because that feels right! At the end of the day it's great to have options.

Just like real life I have a tidy put together functional board, then a disturbing spaghetti mess tucked away in a corner that few are allowed to see

> Like a few good sounding pedals that, ideally, each have just a knob or two.

It makes for a nice narrative but I haven't found it holds much water; musicians are all over the place on this spectrum. You'll find both extremes very well represented, and a good chunk of people who compartmentalize their "dayjob" music and tinkering. I've found a lot of successful musicians love to tinker and are always on the search for new inspiration. Like any good craftsperson they take some amount of pride in their tools and I've been blown away by how technical many can get on the electronics side! It's always funny to see Reverb auctions go up for famous musicians and finding out a bassist in a pop punk band owns a bunch of weird synthesizers :)

Simple one to two knob pedals are a big deal but you'll see a very large number of pros touring with extremely complicated modeling setups and all sorts of gadgets. At a certain point you really know what you want, and having the ability to dial that in is important! I tend to gravitate towards simplicity in a band setting but I know a lot of people who want dirt pedals with 10 knobs so they can dial in the sounds they hear in their heads.

Why stop there? Clearly any kind of medical intervention is against nature’s wisdom.

I'm glad that works for you. Ultimately I think different people will prefer different ways of working. Often when I'm starting a new project I have lots of boilerplate from previous ones I can bootstrap off of. If it's a new tool I'm unfamiliar with I prefer to stumble through it, otherwise I never fully get my head around it. This tends to not look like insane levels of productivity, but I've always found in the long run time spent scratching my head or writing awkward code over and over again (Rust did this to me a lot in the early days) ends up paying off huge dividends in the long run, especially when it's code I'm on the hook for.

What I've found frustrating about the narrative around these tools; I've watched them from afar with intrigue but ultimately found that method of working just isn't for me. Over the years I've trialed more tools than I can remember and adopted the ones I found useful, while casting aside ones that aren't a great fit. Sometimes I find myself wandering back to them once they're fully baked. Maybe that will be the case here, but is it not valid to say "eh...this isn't it for me"? Am I kidding myself?

This is where the disconnect is for me; mundane code can sometimes be nefarious, and I find the mental space I'm in when writing it is very different than reviewing, especially if my mind is elsewhere. The best analogy I can use is a self-driving car, where there's a chance at any point it could make an unpredictable and potentially fatal move. You as the driver cannot trust it but are not actively engaged in the act of driving and have a much higher likelihood of being complacent.

Code review is difficult to get right, especially if the goal is judging correctness. Maybe this is a personal failing, but I find being actively engaged to be a critical part of the process; the more time I spend with the code I'm maintaining (and usually on call for!) the better understanding I have. Tedium can sometimes be a great signal for an abstraction!

Hey both things can be true. It’s a long ways from the AI renaissances of the past. There’s areas LLMs make a lot of sense. I just don’t find them to be great pair programming partners yet.

I naively bought into the idea of a future where the computers do the stuff we’re bad at and we get to focus on the cool human stuff we enjoy. If these LLMs were truly incredible at doing my job I’d pack it up and find something else to do, but for now I’m wholly unimpressed, despite what management seems to see in it.

It’s totally valid to see a new piece of tech, try it, say it’s not for you, and move on. With LLMs it feels forced-fed, and simply saying “eh I’m good, no thanks” isn’t enough. Lots of hype and headlines on how it’s going to take our jobs and replace us, pressure from management to adopt it.

Some new trends make perfect sense to me and I’ll adopt them. I’ve let some pass me by and rarely regretted it. That doesn’t make me a luddite.