notnmeyer

you can write bash but run the scripts on systems that may not have bash, is my first thought. packaging “shell” scripts into a scratch container or similar sounds pretty nice for certain use cases.

clippy is one of the pets and mentioned at the top of the readme

no specific scale request, but id focus on getting the 7 main modes covered to start.

then id suggest taking a look at what other sites suggest for, "10 most useful guitar scales" or whatever for some fun variants you haven't covered yet.

oh, and it might be cool to have a mute button too — maybe i want the visual reference of the site but to put on my own music in a different genre or something.

love it. ive played for about 30 years and this is one of the better shut-up-and-play practice apps ive come across. couple suggestions to get me to come back:

- more scales. i know this is already the plan, but i suspect most users won't be wanting to jam on pentatonic or blues scales. there's already endless content devoted to practicing them since theyre usually the first scales people learn. imo the primary utility of your app is being able to practice scales or positions you dont use frequently. and to that point...

- let me choose which positions to practice. id love to exclude open-position scales, or focus on a particular part of the fretboard.

- when switching positions, show a hint where we're moving. saying that the position will switch but not indicating where isn't all that useful. i want to practice the shift as much as the position, so give me a heads up. it would be particularly cool to temporarily expand the fretboard and highlight the next position.

…i’m sorry, what? k8s can be as simple or complex as you make it.

i pay for orbstack. makes life better.

pretty interesting. i think i fall on the blunt end of the communication spectrum, so this gave me some things to think about.

looks great. similarly this is why i love ‘go mod tidy’. just use the thing and let the package manager sort it out after the fact.

a task runner/build tool thing, https://github.com/notnmeyer/tsk

exercise-monetize your users! even it’s a pay-what-you-want with a minimum of say $10 or $20usd per year.

your service is loved.

i agree with this take

aside from this being appalling, “notorious for rats and explosions” is pretty funny

i really am a fan of what the pico.sh folks are doing. their ssh, cli-centric tools really speak to me.

article says it’s optional

> Preorders at $349 start today for beta units, and Elemind expects to start general sales later this year. The company will offer customers an optional membership at $7 to $13 monthly that will allow cloud storage of sleep data and access to new apps as they are released.

exactly—well said

isn’t it though?

this is… somewhat horrific, right? would anyone do this without explicit version pinning?

loosely pinned deps installed on execution sounds fucking awful.

i’d wager this becomes increasingly less likely. everything that isn’t the cheapest is 1x or 2x these days.

in some number of years, 3x parts will become less available and less common on cheap bikes.

derailleurs are easy to adjust once you understand how. 99% of the time you only need the high and low limit adjustments.

decent bikes derailleur hangers.

they’re simple and they work reliably enough. why do we need something more complicated?

building a touring bike for remote areas? reliability wins, internal transmission and belt drive sounds smart.

otherwise, your money is better spent on nicer brakes, lighter weight wheels, nice hubs, etc.

totally agree. it was revolutionary at the time for the number of enemies on the screen. even at the time the vibe was very much, “croteam knows what they’re doing”.

really neat to be reading about this so many years later.

all my run books use this

hrm, smoke peat cigarettes instead?

whoa, autostash is brilliant

i doubt it. i would imagine any single ip address would get rate-limited/throttle before doing much. the situation the article is describing is much more like a botnet — there were hundreds or thousands (or more?) of unique instances making requests.

could you solve this with a "requester pays" bucket?

not viable for a public bucket, but seems like it'd do the trick on private buckets.

edit: hahaha, i'm wrong https://docs.aws.amazon.com/AmazonS3/latest/userguide/Reques...

this will be the subject line of my next resignation email!

booooooooooo hiss

from nearly 2 years ago. where are the ads?

> It’s a complete 360 on their stance last year,

whoops. who’s reading these before pressing publish in wordpress?

totally, your approach is the right one and anything reasonable is going to focus on collocating the cache as close as possible to where the build runs.