By Hyrum's Law and the fact that there are 20M installs, we can infer that somewhere, some nitwit is probably using this bug as a handy function for removing 'a's from a string.
Rewriting a program in Rust (specifically) really only makes sense for a few reasons:
1) the existing implementation is in an unsafe, cumbersome language (C, C++).
2) the existing implementation language is too slow and that slowness cannot be worked around.
3) the implementation is enormous, in a dynamic language and you desperately need stricter types. But this doesn't really favor Rust specifically.
1 doesn't apply because Ruby is garbage collected. It's doubtful 2 applies just given what homebrew does: the long pole is always going to be I/O. The performance improvements in version 7 seem to mostly be due to doing more concurrently. I highly doubt the Ruby-ness gets meaningfully in the way.
I was kinda kidding because parent called it "blazing" fast lol. I didn't think it was Rust. Blazing fast software is reserved as a descriptor for Rust programs :)
i just tested and `mise bootstrap` is over twice as fast at installing when a bottle was in the cache. other commands like `status/check` are 20-30x faster. that's without spending much work at all on perf—i'm sure i could bring these numbers down much further.
That file doesn't seem like it would work for a number of reasons.
The gear with integrated hour hand wouldn't be able to rotate in the space that it's mounted. In order to tell the time against the ring, the hand would need to be much further away from the gear.
Secondly, the funnel bit seems to have no real purpose; if you have to pipe water to the funnel, why not just bring it directly to the cup at the bottom? In real water clocks there is usually a primary collector but it's built in such a way that it overflows at a certain level so that the pressure on the outgoing line stays constant. The funnel here does essentially nothing and there is nothing else in the clock that would provide any kind of flow rate calibration; you'd have to do that externally.
Lastly, it's not clear how you'd reset the clock. Can the collector be removed separately or do you need to turn the whole clock upside down to pour the water out and get the float back down to the bottom?
Is it just me or does the dark blob in the center of the decagon look like a Mandelbrot set? The resemblance appears more acute in the images lower down in the article.
I think the images in the article are mosaics created from multiple images and the dark blob in the center is where their was no imagery because Saturn's south pole is currently tilted somewhat away from us. It has a 30 year orbit, and you can see in the images we are able to see closer and closer to the south pole each of the three years images were taken. The rough edges are just an artifact of image processing, and where individual exposures cut off.
Cool, I like the esp idea but won't you have to walk fairly slowly with a default ESP antenna? High gain might be better.. If you're wearing a cap you may not care as much being seem from above vs from the front.
Maybe attach a little windspeed meter to the top of the antenna on your hat too ;)
Voting, and participating locally in policy discussions has far greater traction.
The fact is with satellite to cell service online, there is a far greater risk automotive and civilian telemetry meta-data is collected regardless of what people want or do on the ground.
It is credulous to believe individuals can affect political policy with gadgets. =3
Clocks like this are fun. I coded one but couldn’t decide how to handle the corner cases where the sun rises but does not set (and vice versa). You also have to decide if you’re showing the time that the sun rose today or if it should be tomorrow once you’ve already passed that time. Either way, at a certain point you’ll see the UI shift. At moderate latitudes it makes little difference but the effect can be quite extreme depending on the latitude and time of year.
> how to handle the corner cases where the sun rises but does not set (and vice versa)
In practice it doesn't matter: you get a thin sliver of twilight between solar midnight and sunrise or sunset, and a 'Sunset: Does not occur' message in the text info. In such cases the sunrise/sunset arc (sector?) is pretty broad anyway.
> or if it should be tomorrow once you’ve already passed that time
Yes. I chose to recalculate the times midnight.
> Either way, at a certain point you’ll see the UI shift
Yes, but it's usually not dramatic. A few minutes time and fractions of a degree each day. The biggest shift occurs when Daylight Saving time changes — you get a big 15° rotation in the display. Most people are asleep when that happens, but it's cool to watch it jump.
I'd want to make it continuous, but then it wouldn't actually show you proper sunset/sunrise times until the moment they are actually happening, which is probably sacrificing function for form. You could also hide the shift by making the whole thing "tick" rather than having some parts continuous and some quantised.
Summary: almost, but not quite entirely successful.
Launch successful. Booster separation and boost back burn looked good. Booster failed to relight some of its engines and hit the water hard. Successfully deployed the 20 starlink satellites. Successfully reignited an engine in flight to prove potential for de-orbit burn on future flight. Re-entry looked good and less spicy that some previous attempts (subjective). Such a soft landing that the ship flopped into the water without exploding and floated for a good long while (possibly still floating for all I know). Got some great drone footage flying over the heat-shield.
So the ship itself is looking increasingly good (so far) but they still seem to be having some issues with the booster.
Speaking of which, are there any fan theories on why the boosters seem to have persistent issues? Or is the plumbing still churning fast enough that we keep seeing N=1 issues for successive designs?
Until the past couple launches it was the ship that had the issues. Had to be blown up a couple times, failed to relight in vacuum, lost an engine and nearly failed to get to the suborbital trajectory last time. Meanwhile the booster had the most spectacular success in the catch, and has yet to result in a catastrophic failure.
The leading theory, from what I can tell, is slosh. The flip on separation is relatively violent, and while there's not much fuel left compared to the amount at launch, it's still heavy enough to do damage.
Oof, yeah, one good slosh at 11G is probably all it takes. On the bright side, there is probably a trajectory that works and I wish them luck in finding it!
I'm not sure I understand why even a truly obscure programming language article should ever be deleted; it's not like Wikipedia is running low on paper. If Odin ceased all development tomorrow it would be good to have some record of what it was.
For the record, I like Odin.
(On homebrew it appears to have been downloaded 6,707 in the past year. Compare to:)
The point of Wikipedia is to be accurate, not complete. Wikipedia does not want to just trust the developers of $ObscureLang to maintain their own wikipedia page. So, the existence of the $ObscureLang page (and, in the aggregate, many similar pages) imposes a maintenance burden on Wikipedia. Better to say nothing than to risk saying something inaccurate.
Ha! This set it designed to take 114 years to construct and for maximum verisimilitude, Lego will run over your foot with a Lego tram after only a few decades of trying to build it.
https://www.hyrumslaw.com/
https://xkcd.com/1172/
reply