nepthar

Heh. Extremely accurate.

Pangolin! Gateway to everything else.

Woah. I’ve been meaning to check out zed but that’s a huge problem. I’ve fixed this problem before in rust, there’s just a library you can use to update file trees with a combination of batching fs notifications and a periodic rescan. Wtf guys! Maybe I’ll submit a PR… oh wait! I mean delta. :(

I have been working on literally this exact project for the past 6 months, down to the nomenclature used. Running into this on HN is… strange.

Location: Denver, CO Remote: Open to remote, would prefer at least some in person time Willing to Relocation: No Technologies: Rust, Scala + JVM ecosystem, python, rails, c++, (basically anything with AI now)

Resume/CV: Available upon request Email: Jordan@parker.sh

15 years of experience developing software at many scales from the frameworks that ran all of twitters services to nimble startups, to large scale data collection pipelines. Most recently, I was the head of engineering for a ~25 person engineering org, and have done consulting in the areas of providing technical due diligence. I'm currently working on projects that make self-hosted computing more accessible to anyone.

I wouldn't say complicated, and I agree with you that the proof is in the pudding. I looked at the gameplay and if it was something akin to.. let's say "minecraft before minecraft existed", I'd be amazed and see the value right away.

Looking at the game, it doesn't seem like a game that would require as much money to build as he's claiming he uses in credits (although via a loophole that allows him cheaper access). It doesn't look BAD, it just doesn't seem to warrant that much spend.

(Asking sincerely in good faith - I read this note along with skimming a few of the linked ones, and I'm familiar with gastown)

Can someone explain the value calculation to me? This seems like someone has truly let AI VASTLY expand the codebase of what seems to be a medium sized hobby game to ~10-100x the amount of engineering required. Especially with statements about how wheelhouse, his software factory, has grown to nearly the size of the actual software he's writing. He also mentions several times that wheelhouse is specific to developing the game. Then, he discusses "pulling in beads" which itself seems on my read to be enormously engineered. (note that he also says that you burn a lot of tokens with agents "keeping your beads in sync" and I didn't have the time to figure out what that meant, but it looks like as complicated as it is, beads can't reconcile itself without burning $$$).

It seems like if you answer "yes" at every time you have the question of "can I make AI do this", you end up burning $120k/month in tokens on your side project.

Again, I am not disparaging this- but I feel like I am genuinely missing something and would welcome help understanding it.

This is a perfect use case for AI, no?

Thank you. Thank you.

I agree. Take what ya can, give nothing back!

I just took a look a both (thanks for the pointer to seastar! cool project). I'd say "sort of but not exactly". It seems like two approaches to solving the same problem.

Silk seems like mostly a scheduler that uses C++'s native coroutines. Seastar is a future-based framework. Both contain a scheduler and enable async coding patterns.

“No way to prevent this” says only package manager where this regularly happens.

Well, I too, don't have anything against a company selling a "good but not open printer", and I don't care if my fridge is open.

However, I hope you see that the behavior reported by Jeff here is just bad. They are either not understanding open source licenses or are acting in bad faith.

I think this might be rage bait.

Friendly reminder to take a look at our posting guidelines, found at the bottom of the page.

What specifically did you find dumb about this?

I had one of these. My account ended up eventually being reinstated. No reason was given for the initial account freeze or reinstating.

One thing I did - in response to them saying I could no longer do business, I told them that they also could no longer do business with me, requested a copy of all of the user data they had on me under CCPA, and told them to then delete all of my personal information. They did not actually comply and I didn't pursue. I probably should, though.

Yeah, this is the single biggest reason I avoid go - I just don't want to clutter my "happy path" logic. It makes things harder to reason about.

"Errors are values", sure. Numbers are values and Lists are values. I use them differently, though.

I wonder if there could be "stupid" preprocessing step where I could unclutter go code, where you'd make a new token like "?=", that got replaced before compile time. For instance, "x ?= function.call();" would expand to "x, err := function.call(); if (err != nil) return err;"

Is there really such a large crossover that climbing.com makes it to hacker news? Sure, this is interesting, but I love that this site is focused on tech.

That’s an excellent point

I think a simple redacted name would address that concern

I'm also hoping for something like this! Bonus points if it had a "little snitch" type of operation where I could manually approve a matrix of (device x domain)

I've just hopped on. I agree completely and I've had the distinct pleasure of avoiding the past year's worth of churn as the tooling & best practices were changing frequently.

I cannot believe this is unknown to so many people that it's news

Your counter analogy is also a bit cherry picked. Guns and vehicles used for committing crimes are seized, but the vehicle makers and gunsmiths are not ordered to go substantially out of their way to prevent criminals from using them, although they do stamp serial numbers. Also, ore and parts suppliers are not required to ensure that the buyers of their material comply with all legalities with the use of their materials. There’s a line of absurdity that this crosses

Sources?

That’s a good question. A cryptographic hash must not leak any information other than “yes” or “no”. A checksum-type hash might have an additional property where data that only has a single bit flipped might hash to something close to the original hash, allowing you to refine your collision attack by knowing if you’re hot or cold.

For a checksum, this isnt a bad thing and actually could be good.

I think this is a really good point. A logging system could theoretically toggle "text" mode on and off, giving human readable logs in development and small scale deployments.

In fact, I'm going to build a toy one in python!

We used a deterministic aperture load balancing to solve this at twitter - https://blog.x.com/engineering/en_us/topics/infrastructure/2....

Cool to see some other approaches, although I believe they've complicated theirs a bit more than necessary.

Oh wow, I actually had no idea that was the case. That definitely throws a wrinkle into things

Well, one thought about your pricing model - you’re thinking that it might need work in the future, but you’re charging each month without delivering any additional value to customers. How about charging additional money for each new major version, corresponding to either new feature development or support for new versions of the OS?