She actually made some specific recommendations on the microscopy sub-reddit but they're a bit pricier ($425+). (scroll to last comment by Jay211TF):
https://www.reddit.com/r/microscopy/comments/1dhagyr/entry_l...
2,435 karma · joined June 10, 2014
She actually made some specific recommendations on the microscopy sub-reddit but they're a bit pricier ($425+). (scroll to last comment by Jay211TF):
https://www.reddit.com/r/microscopy/comments/1dhagyr/entry_l...
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.
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?
-ESP32 based device that tries to detect bluetooth/MAC addresses of flock cameras and beeps when it does
- a Stingray detector that runs on a second-hand mobile hotspot
- a device that alerts you about things that are moving approximately with you (AirTags, SSIDs, etc).
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.
For the record, I like Odin.
(On homebrew it appears to have been downloaded 6,707 in the past year. Compare to:)
zig: 71,565
rust: 304,405
golang: 1,246,300
malbogle: 9
https://www.youtube.com/watch?v=wcp1BfPUeOc
The program is actually called "Predator Free 2050" and also aims to eliminate possums and stoats. No mention is made of Uruk-hai, orcs, or Balrogs.
Anyway, keep up the awesome work! I haven't used Jupyter at all since I started running marimo from uvx.
'''
Y.T's mom pulls up the new memo, checks the time, and starts reading it. The estimated reading time is 15.62 minutes. Later, when Marietta does her end-of-day statistical roundup, sitting in her private office at 9:00 P.M., she will see the name of each employee and next to it, the amount of time spent reading this memo, and her reaction, based on the time spent, will go something like this:
Less than 10 min. Time for an employee conference and possible attitude counseling.
10-14 min. Keep an eye on this employee; may be developing slipshod attitude.
14-15.61 min. Employee is an efficient worker, may sometimes miss important details.
Exactly 15.62 min. Smartass. Needs attitude counseling.
15.63-16 min. Asswipe. Not to be trusted.
16-18 min. Employee is a methodical worker, may sometimes get hung up on minor details.
More than 18 min. Check the security videotape, see just what this employee was up to (e.g., possible unauthorized restroom break).
Y.T.'s mom decides to spend between fourteen and fifteen minutes reading the memo. It's better for younger workers to spend too long, to show that they're careful, not cocky. It's better for older workers to go a little fast, to show good management potential. She's pushing forty. She scans through the memo, hitting the Page Down button at reasonably regular intervals, occasionally paging back up to pretend to reread some earlier section. The computer is going to notice all this. It approves of rereading. It's a small thing, but over a decade or so this stuff really shows up on your work-habits summary.
'''
It too puts the output of a cell above the code so if you're unable to adapt to things that are different it's also probably not for you.
FWIW, Observable's Notebooks (Javascript) work the same way: output above the code that produces it. [https://observablehq.com/]
I too did not like having the output above the code but got over it pretty quickly. For plots, it's arguably better: usually, I want to see the plot before I see the 15 line invocation of some plot command. The thing that bugs me the most about Pluto now is that it really wants you to only have a single evaluating statement per cell. You have to wrap stuff in "block......end" if you want to e.g. define more than one variable in a cell.
''' This technology is fundamentally different from the “rivulet (shark skin) process,” which is known as a typical aerodynamic drag reduction technology. The rivulet process mimics the fine longitudinal grooves in shark skin, and by carving grooves approximately 0.1 mm wide along the direction of airflow, it aligns the vortices that occur near the wall surface of turbulent airflow areas. DMR, on the other hand, delays the switch from laminar to turbulent flow by means of random and minute irregularities. The flow zones it affects and the mechanisms it employs are based on completely different concepts. '''
Here's a few:
Think Complexity
https://github.com/AllenDowney/ThinkComplexity2
Think DSP
https://github.com/AllenDowney/ThinkDSP
Think Stats
https://github.com/AllenDowney/ThinkStats/
Think Bayes
I and the public know
What all schoolchildren learn
Those to whom evil is done
Do evil in return.
W.H. Auden"The plug on this device represents the latest thinking of the electrical industry's Plug Mutation Group, which, in a continuing effort to prevent consumers from causing hazardous electrical current to flow through their appliances, developed the Three-Pronged Plug, then the Plug Where One Prong is Bigger Than the Other. Your device is equiped with the revolutionary new Plug Whose Prongs Consist of Six Small Religious Figurines Made of Chocolate. DO NOT TRY TO PLUG IT IN! Lay it gently on the floor near an outlet, but out of direct sunlight, and clean it weekly with a damp handkerchief."