![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
Python 2.7 and iOS mobile programmers stuck on Objective-C could start a support group.
Python 2.7 and iOS mobile programmers stuck on Objective-C could start a support group.
I tried to hand-solder a Hirose .35-pitch connector onto a custom OSHPark board once. Let’s just say it was a humbling experience. Thanks to a generous friend, I learned the value of solder masks and owning a home reflow oven.
Respect to whoever can do this sort of thing, but life is too damn short and my eyesight and hands don’t need the abuse.
How you solder those without dropping a blob and causing a short is a mystery.
They’re propping each other up.
My needle on my BS-meter just snapped off.
Somebody starts streaming VR porn on the same cell network. Latency drops to a second. Patient flatlines.
The future is here.
All 418 error codes. We good.
Remembering ActiveX Controls, the Web’s Biggest Mistake: https://www.howtogeek.com/717016/remembering-activex-controls-the-webs-biggest-mistake/
That was amazing! Watched the video with my Trackmania-crazy kid. I’ve played it a few times but I’m total crap at it. We couldn’t peel our eyes off the action. The first external shot of the track shows how insanely difficult it was going to be.
If using pyenv to support multiple python versions, when creating venvs, make sure to pass --copies
to it.
% python3 -m venv venv --copies
Ordinarily, venv uses symbolic links back to the current version of the python binary. A lot of tools and IDEs don’t traverse symbolic links. That flag actually copies the real binaries over to the venv.
This avoids a metric ton of hard-to-diagnose misery later on.
That is actually kind of brilliant. Having to go through MFi and getting the Apple DRM chip into the manufacturing pipeline can be a real pain (and expensive).
With this scheme, they could also run all the wired on/off and volume control actions through Bluetooth AVRCP. Even have a Mic on the wire, so if a call comes in, switch to HFP to talk/manage the call.
Damn, that’s clever. Hats off to whoever came up with it.
Incidentally, there’s very little Apple can do to make this stop, unless they decide to break Bluetooth and third-party accessories.
There are browser userscripts out there now that do this automatically.
The year is 2245. The heirs finally locate a working, antique reader that can handle the ancient USB key, hoping to find great-great-grandpa’s crypto-wallet or the pin-code to a long-lost Maltese bank account.
Instead, they find a 4-bit, VGA-quality scan of Miss October.
One of the things they glided around was whether a lot of this on-device stuff needs a special processor chip with AI+security to work?
The Pixel phones (especially newer ones) made by Google have them, but the vast majority of Android phones don’t.
So either these features only work on latest Google phones (which will piss off licensees and partners), or they’re using plain old CPU/GPUs to do this sort of detection, in which case it will be sniffable by malicious third-parties.
And let’s not forget that if the phone can listen to your conversation to detect malicious intent, any country can legally compel Google to provide them with the data by claiming it is part of a law-enforcement investigation.
Things are going to get spicy in Android-land.
I’ve used it to make specific images for work proposals that stock sources may not have. Sometimes for fun, I vary it so it’s in the style of a cartoon or a Japanese woodcut.
Be fun to see the same M3Max with an ad and tracker blocker. See how much their top line improves.
Oh man, you would have loved a project I was working on ~15 years ago.
I have a project ready to try this out. It’s a software simulator, and each run (typically 10-10,000 iterations) can be done independently, with the results aggregated and shown at the end. It’s also instrumented to show CPU and memory usage, and on MacOS, you can watch how busy each core gets (hint: PEGGED in multicore mode).
Can run it single-threaded, then with multiprocessing, then with multi-core and time each one. Pretty happy with multicore, but as soon as the no-GIL/subinterpreter version is stable, will try it out and see if it makes any difference. Under the hood it uses numpy and scipy, so will have to wait for them.
Edit: on my todo list is to try it all out in Mojo. They make pretty big performance gain claims.