readmodifywrite

7 ms·

1.
by readmodifywrite 8mo ago
The guy owns a rocket company and still hasn't even been to LEO. Katy Perry has spent more time in space than Elon. Mars isn't happening, at least not on his watch.
2.
by readmodifywrite 8mo ago
They are not. Turbine engines require much higher quality manufacturing and tolerances and operate at much higher speeds and pressures. There is more to it than the perceived number of moving parts.
3.
by readmodifywrite 9mo ago
If you were using TCP, then this is absolutely normal and expected behavior. It is a stream protocol, not packet/message based.
4.
by readmodifywrite 11mo ago
Finally, a use case for blockchain!
5.
by readmodifywrite 1y ago
Having used Unifi for 10+ years, they really have improved their firmware/software by quite a lot.
6.
by readmodifywrite 1y ago
One engineer's esoteric is another's daily driver. All 3 of those options are borderline mandatory in embedded firmware development.
7.
by readmodifywrite 1y ago
Katee Sackhoff did an interview with Ron Moore on her podcast, and one of the topics they discussed was how they would write the "technobabble" in Star Trek (and BSG). Moore said they would write the script and just say things li
8.
by readmodifywrite 1y ago
> Gibson is such a unique sci-fi author because his fundamental interest is fashion (he’s said this himself) Check out Pattern Recognition if you're interested in following him down this line of inquiry!
9.
by readmodifywrite 1y ago
My go to analogy is that conservatives will underfund the assembly of a car, deliver a car that only has two wheels that are both the wrong size, and then say "See? Cars will never work!" I think it is amazing that in a country as
10.
by readmodifywrite 1y ago
The PPK2 is one of the best pieces of kit I have and it'd be worth it at 5x the price. There's an unofficial Python library as well. I have power consumption tests running as part of my automated firmware test suite.
11.
by readmodifywrite 1y ago
It switches the detection range, but not the actual power supply. You can ramp from <5 uA up to 500 mA and back all you want. I haven't noticed any glitching on the actual supply. Schematics: https://www.nordicsemi.com&
12.
by readmodifywrite 2y ago
Not to mention the TX power ramps up in microseconds to quite a lot more than 80 mA. If your supply can't handle the modem sleep mode it definitely isn't going to transmit reliably either.
13.
by readmodifywrite 2y ago
Also, they are options . Basic pub/sub usage doesn't need any of them, though some are pretty nice to have.
14.
by readmodifywrite 2y ago
The lack of status bits on the auto-cal is really unfortunate. Turning it off during a UART transaction definitely "fixes" it. I'm somewhat tempted to do the manual calibration the HSI instead.
15.
by readmodifywrite 2y ago
Yup, it's the Hakko Omnivise. They might seem a little pricey, but they are worth every penny.
16.
by readmodifywrite 2y ago
It really seems like it has to be something like that. The problem is there is no detail in the docs and no status bits in the chip. There's no way to know when the auto-cal runs. One of the several things I did to eliminate the prob
17.
by readmodifywrite 2y ago
This is a good resource, however, it didn't apply in my situation because it describes the manual calibration process, not the auto-cal (which the F0 probably doesn't even have). I still haven't come across anything that expl
18.
by readmodifywrite 2y ago
My guess is that the receiver clock glitches in some way when the MSI auto calibration runs, but it never showed up on the transmitter (and the device on the other side of the connection has never had a reception issue). I ended up disablin
19.
The Latest and Greatest in Moats(blog.supermechanical.com)
2 points by readmodifywrite 3y ago|0 comments
20.
by readmodifywrite 6y ago
The GIL is not there to prevent data corruption on shared objects - it only protects the interpreter's internal state. The fact that sometimes you can get away with it is an accident of the GIL's implementation, not a feature any
21.
by readmodifywrite 6y ago
There are TNG episodes that specifically deal with that, and the problems it causes. I think ENT had a few as well, instances which led them to the creation of the Prime Directive.
22.
by readmodifywrite 6y ago
That's kind of ironic, considering they don't provide a scheduled reboot feature for their own gear (which often needs it for IoT usage).
23.
by readmodifywrite 6y ago
The CPU implementation is done by Qualcomm, Apple, and the like. The CPU design is done by ARM, predominantly in the UK. The fact that Softbank (Japan) owns ARM has no bearing on where and who is doing the actual technical work.
24.
by readmodifywrite 6y ago
I love that the example uses the exact same indentation format that Python already requires.
25.
by readmodifywrite 6y ago
The issue here is opportunity cost. It has nothing to do with difficulty. The time spent porting to Python 3 has to provide a better return on investment than the same time spent doing something else. For a lot of people for a very long
26.
by readmodifywrite 6y ago
It sounds like you had a project that really benefited from updating, and that's great! Some of mine have as well. It is not universally applicable, however. There's a lot of old code that, as I said before, is just fine . Add
27.
by readmodifywrite 6y ago
It is a completely different language - it is syntax incompatible. Human languages are a very poor comparison to computer languages. It's just a tough sell to manually update a huge pile of code that works just fine as-is. No new
28.
by readmodifywrite 6y ago
Do you have a link to the paper? I'd love to read it.
29.
by readmodifywrite 6y ago
The issue there is desalinating the water in an environmentally responsible way. It's hugely energy intensive.
30.
by readmodifywrite 6y ago
From my experience, and this is compared with AVR and most ARM parts I've worked with. 1) Generally poor documentation. Non-existent at the register level - you are entirely at the mercy of the SDK and what other people have reverse e

More ›