Ryan Day

@adam_baldwin What about water pie?

@ag_dubs This made me feel special. Ty!

work with ryan! and like, i guess, wasm, if you're into that

Hey all! My team is hiring. 😃 Come work on wasm at Google goo.gle/4dcyVCL

@MylesBorins Thanks Myles! Excited for you to keep doing you. Kittens and rainbows 🐱🌈

Today I stepped down from all existing Node.js and TC39 commitments. No drama, no blog post, just no time. So long, Thanks for All the Packages.

@caraesten I've been shopping for bay kayaking as well. Ty!

@caraesten What kind of kayak do you have? I may have missed the post. 😃

@evenstensberg "data at rest should match the access pattern" is great advice for this problem space.

@soldair Yea that works. Ideally I want to have the time series for a table in a column, not more tables for the relation.

How do you implement time series in a db? For instance, you store some variable, number of purchased in a month. It should be reset each month, but I want to store the previous month to have for stats

@adam_baldwin Haha absolutely. I think it's a copepod

Anyone know what this is? They ate all the algae in an experiment I was doing :)

@sebmck @wesleytodd EventEmitter is a decent thing to use if you want to compose requirements as you build it. 😀 It's a node process, so your async lock is probably already any variable in scope of the emitter. And the var could be a map for your cache! Anyway. Good luck! These are fun choices.

@soldair @wesleytodd Very true! I guess I'm not really sure what I want. I just know that a basic EventEmitter is not it.

@sebmck @wesleytodd Decent is carrying a really heavy load of otherwise unspecified requirements there 😅

@wesleytodd Yeah it's standard but I'd hardly call it decent. I think I just want an async store that I can subscribe to. Maybe some async locks or cache management too.

Monday I start working on wasm at google. Nice to start a new adventure.

@MagicznySzymek @matteocollina DI is just fancy arg passing haha. And the more automated the container the more you either depend on a build step or instantiation complexity. That complexity is harder and harder to test by nature and scales up. You need to track all the edges, the less magic it is the better.

@soldair @matteocollina so basically a dependency injection, but with manual work instead of an automated container

One of the primary reasons of spaghetti code & unmaintanable codebases are… SINGLETONS. They block future evolution of your codebase and make testing harder. STOP USING THEM NOW

@MagicznySzymek @matteocollina It doesn't. just make your state instantiatable. :shrug: this is about how you feel like passing arguments to the functions in your program. You pass state in as an arg, you make objects with a factory that injects state, or you put it in the vm somewhere where you can get it.

@soldair @matteocollina jesus christ it makes the state a singleton and you have the same problems

@matteocollina Export the state. Make your state mockable. Solve it in one spot. Making local changes in code bases like this is usually way easier than any other form of advanced di or additional positional arguments. Nike code ;)

@littledan Those tend to create the same problems if they contain state. Global state makes isolated testing hard/impossible. Example: setting the “db” of the process prevent that process to connect to two dbs.

@mountain_ghosts You can redirect it for everything in the whole script but that's often solving a different problem

@JPMajor @quephird My dad worked on this. I saw it take off at the cape, and was there in viewing at cal tech when they burned it up. Always makes me smile seeing through it's lens. Ty!

This is a view of Earth and the Moon captured from Saturn by the Cassini spacecraft on April 12, 2017 #OTD That's all of us from 1.43 billion kilometers away—specks of light inside the gap between two of Saturn's rings.📷🪐🌎🌕

@jfhbrook Seems like the only way is to make a sh wrapper for the node binary. Once something is a process it only really knows it's path env and args. Can snoop around in /proc/pid and see. Or just use "node" if it's resolved by which

Update, node is not designed to be embedded and it's totally not worth it - yuck.

I have a need to get at the equivalent of Bash's "$0" in Node: - `bash` -> $0 is "bash" - `$(which bash)` -> $0 is "/opt/homebrew/bin/bash" - "my-cli", located at "./node_modules/.bin/my-cli" -> process.argv is ["node", "/path/to/node_modules/.bin/my-cli"] Any ideas?