Congratulations on shipping this, I’m sure folks will find it useful!
The rails native way to do this is to track state in a db row and queuing “next step” jobs as the data changes. This can get verbose especially for smaller pass/fail workflows. However, I find this works better (not worse imo) in more complex workflows as the state is tracked, queryable, can be surfaced in UIs, and resumed “manually” in the event of an outage.
All of this sucks, and it’s time for the community to move on.
It’s a bad look for the ruby ecosystem. Continuing to rehash, throw mud, and speculate at this point likely harms the greater community more than any “side” would “win”.
It would have been a better angle to title it "gem.coop - the new homebrew-like place to get your gems" and then talk of the advantages for users and the simplicity of the file change to use it.
It pains me how this comment illustrates how ignorant most folks are of the consequences of installing software off the internet is (even technically inclined folks that hang out on HN). How many of us have non-security software installed on our computers today that do exactly these things... but sell the information? Definitely a non-zero number!
If folks understood this better, there would be less reason for software like Huntress' EDR to exist.
I don't think anyone is unfamiliar with the consequences of installing potential malware. I think people are surprised that a seemingly? legit company is going off and having a little pokeabout on arbitrary computers based on nothing more than a hostname match. Then sharing screenshots on HN. I guess they're Canadian but wow does this seem to have CFAA written all over it?
Unless you were moving a full 18-wheeler worth of stuff you overpaid. For a 240 mile move you can rent the truck and drive it yourself, and pay local movers to pack/unpack at each location.
New Glen is their orbital rocket but it is not ready yet. Hopefully it will be ready for some of the launches, but it must hurt owning a rocket company and having to use another companies to launch your satellites.
From the project web page
"Project Kuiper has secured 80 launches from Arianespace, Blue Origin, SpaceX, and United Launch Alliance, and we have options for additional launches with Blue Origin, providing enough capacity to deploy the majority of our satellite constellation. The agreements comprise the largest commercial procurement of launch capacity in history, and support thousands of suppliers and highly skilled jobs across the U.S. and Europe."
It's worth mentioning too that BO is following the same strategy as SpaceX (and others), in becoming their own customers. Lesson learned from the 90's launch vehicle boom. Companies couldn't scale without customers, it's a vicious feedback loop. No customers because prices are too high, can't bring prices down without more customers. Either you have to become your own customer or you have to bootstrap. It's a long way to bootstrap and an expensive industry.
Though using ULA is kinda a bridge to the looking deadline[0]. So if they can't get satellites up now they won't have this means for being their own customer in the future.
They need to launch fast with as many launchers as they can, due to their looming FCC deadline. The more they launch, the better their odds for getting an extension to their deadline as more launches demonstrates their seriousness.
They're even going to launch on Falcon 9 (albeit after a shareholder lawsuit..)
Did shareholders not want them launching on a Falcon 9 because it was helping a competitor, or did they actively want them to use the F9 because it's the most affordable option but Bezos (or other higher ups) didn't want to support a competitor?
The latter. SpaceX isn't an Amazon competitor if Amazon doesn't have their constellation in the first place, and the loss of a handful of launch contracts from Amazon isn't going to slow SpaceX down (while on the other hand, it would slow Amazon down considerably.)
Bezos didn't want to launch with SpaceX because SpaceX is a Blue Origin competitor. Shareholders sued over this, saying that Amazon was putting Bezos' personal interests before Amazon's own.
New Shepard has limited payload delivery capacity. It's mostly for crew and experiments held in lockers in the crew compartment.
New Glenn has a 100,000lb to LEO payload capacity which makes it absurdly oversized for this mission.
Atlas V has a 18,000 to 42,000lb to LEO payload capacity. The variable solid rocket booster configuration really gives this platform the most flexibility for customer needs.
You are suggesting that they should design a brand new upper stage to get the thing to put 50 kg into orbit, as an alternative launch platform for their 600 kg satellite? Instead of investing that engineering effort into finishing their New Glenn rocket which delivers 40,000 - 100,000 kg at a time to LEO?
For those who don’t understand why you might want something like this: if you’re doing high enough throughput where eventual consistency is effectively the same as atomic consistency and IO hurts (i.e. redis calls) you may want to cache in memory with something like this.
My implementation above was born out of the need to adjust global state on-the-fly in a system processing hundreds of thousands of requests per second.
I’ve seen cofounder departures go down a few times second hand/tangentially.
Not a single company survived afterwards.
Are you the CEO? If so, gain the buy-in from your cofounder to follow your direction. If not, find a way to get onboard… or probably damage the company with a departure.
The rails native way to do this is to track state in a db row and queuing “next step” jobs as the data changes. This can get verbose especially for smaller pass/fail workflows. However, I find this works better (not worse imo) in more complex workflows as the state is tracked, queryable, can be surfaced in UIs, and resumed “manually” in the event of an outage.
reply