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.
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 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.
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.
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
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.