228 karma · joined January 13, 2010
For those wanting to hack their own tracker, for slightly more money ($5), you can get one with a Nordic nrf52832 which has lots more documentation and support, including Micropython:
Transpiles SwiftUI over to Kotlin/JetPack Compose. Native all the way down. Haven't used it in production, but the demos work and are native after going through XCode and Android Studio.
Toggled back and forth maybe 5-6 times. Finally settled on Parallels and stopped upgrading Fusion. Haven't had problems since.
Glad it's free now, but that sometimes means the company is going to stop investing in it.
Wondering if CM5 will offer enough of a boost to allow on-device LLM processing on a Home Assistant Yellow.
Guessing the answer is no, but it might be worth trying.
1. Allowing such apps to handle their own payment processing across multiple applications. This means Apple doesn't get to force everyone through the in-app purchasing funnel and collect a transaction fee. There could be an exception made that the fee is waived for purchasing physical goods and services through the super-app. This shouldn't be a hard change. The big fight will be over selling digital content and what is a fair percentage.
2. Allow users to install binary plugins or extensions into a single app without going through an AppStore review. Apple does not currently allow this unless the plugins or extensions are web-based and can run inside the webkit sandbox.
They'll have a strong argument that forcing them to allow running arbitrary, unreviewed code will open up big security holes.
- Gravity's Rainbow (which I did enjoy, but so many people raged against)
- Infinite Jest
- Finnegan's Wake
- War and Peace
- Divine Comedy
- Remembrance of Things Past
Didn't feel the same way about Catch-22. Really solid humor mixed with absolute tragedy.
- Connect my phone via CarPlay (as only user).
- Adjust AC depending on outside temperature and passengers.
- Plug car in at home to charge after midnight (cheaper rates).
In all three cases, the car forgets previous settings, requires multiple taps (up to 5-6 at a time), or makes it hard to find the screen to make the adjustment.
My last car ran fine for 20+ years. This is the third VW I've ever driven; the first two were a long time ago. I intentionally leased this one since I figured EV technology would evolve, so best to hold off before purchasing outright.
Unless they figure out how to make those features be 0-touch (or even 1-touch) operations, this will be the last VW for me. The EV part works fine, but I grit my teeth every time I get in or out of the car.
This way, everyone knew what to expect. Customers, co-workers, contractors, and management knew where things stood.
If every programming language and API/ABI did this from the get-go, there would be so much less angst and hair-pulling each time some old, bad design was deprecated.
So many of the websites raised red flags that I just stopped looking.
It's like showing how much faster you can get your handcrafted assembly code to run vs a bash script.
- Empty Planet: The Shock of Global Population Decline.
Regular Magsafe can start charging at 40-50mm. Power has to go through a lot of packaging layers. If they make an extra-strong in-store charger cradle to boost that distance, it would be possible to reach the phone, and trigger a power-up session without opening the box.
The power detection chip can take very little energy so everything else (other than maybe power-button-press detector) is in super-dormant mode.
On power bootup, the phones can connect to Apple store wifi (preset in wifi defaults), then use key exchange to authorize wifi. Then they can use mDNS/DNS-SD to scan for an update service running on the store network. If found, they can do a key exchange, then download the update, validate, and install.
The whole time, the custom cradle could also be topping up the phones so when the user opens their box, it's charged and they're happy.
Just a guess. Very clever, if true. Also, eminently doable.
"Was signed." Nice use of the passive voice, there.
The tech sounds a bit dodgy, though. Could well end up in Wisconsin/Foxconn territory.
Let's hope they're legit. It's good to diversify local manufacturing and rural Kansas could use the jobs.
My wife stuck a burrito to warm up in the microwave a room away (30-40 ft). This was with a brand-name model, so presumably properly shielded, etc.
Nope. The entire spectrum just went white with noise on all channels.
Once the microwave cycle ended, it still took a good 15-30 seconds before the airwaves calmed down and went back to normal traffic.
It was inconvenient by conventional standards (had to vacate and rotate rooms every few days) but he enjoyed the lifestyle. In the winter time, he went up to Tahoe and became a ski instructor while still freelancing tech projects.
With all the extra money he sent home, he ended up buying a house there while in his 20s. I lost touch but heard through mutual friends he was doing well.
You can sniff at pod housing, but when you're young, footloose, and chasing a dream, it's a pretty good deal.
All they have to do is add color commentary (post-game shows, direct interviews with players and coaches) and the value of local TV sports networks and intermediaries like ESPN will drop off to zero.
Only thing ESPN will have going for it is cross-sports content, like SportsCenter. Not sure that's enough to keep them going.
Once the cable and local network deals expire, the league streamers would be smart to do away with local blackouts, and then there would be no reason for fans to just buy the league streaming service directly.
Read somewhere the land acquired was 2x the size of the City of San Francisco.
No-GIL is a much smaller shift. It can follow the same transition path without radically breaking things. And if some things do break, there would be a well-defined way to handle those cases.
We all somehow survived those. Glad to see forward motion on this. It will open up a lot more terrain that has been marked off as untenable.
One of the things about early Swift that they got right was building breaking changes into the promise. Everyone knew where they stood and adjusted just fine. Sometimes I wish Python would take the same path.
Also, wouldn't something like MessagePack, ION, RION, or CBOR give you payload compression over JSON?
A few thoughts:
- Every project is at its most exciting right in the beginning when it's new, and toward the end where the end is in sight. The trick is staying engaged and interested in the long, flat middle where progress comes in small dribs and there are frequent setbacks.
- Another point I wish the essay made is that many projects reach a point at which it is best to reveal it to others. That is one of the most scary parts, of exposing oneself to criticism and doubt. It's what petrifies so many people from even starting. But if you embrace it not as the end, but as part of the process and a natural part of the evolution of the idea, it can itself be turned into a motivator. It's your first milestone. You WANT to get to that point, as a checkpoint. Seek out the feedback, adjust, and press on.
- In fact, more should be said about the emotional part of doing projects. The love (or lust), the fear, the frustration, the doubt, and yes, the joy. All those human emotions are part of doing any work. We can run away from it and try to avoid it, or realize it comes with the territory.
- Another thing that comes with experience and age is knowing what to say NO to, and avoid getting pulled away into the tributaries. It's easy to get distracted by side quests and to engage in bike-shedding. In fact, sometimes it's necessary for one's mental health. But it is best to keep an eye on the main goal that got us excited about the idea in the first place. Knowing when the break is over and it is time to get back to main path is a trick that seems to only come with age.
- Lastly, there is great value in brevity (this is not a critique of PG's excellent essay :-) Imagine meeting a friend and they ask what you are working on. You tell them a long, complicated story, and their eyes glaze over. Next person, you learn to shorten it. Same result. You iterate. Soon, you've boiled it down to a short sentence you can rattle off without thinking. That's the nugget of the idea. The through-line. It's the blurb on the back of the book, the opening line of the website, and the executive summary of the grant application or pitch deck. At some point, all works need to be explained to someone else, before they become Great Works.
Walked away and went down the street. Every other dealer was more than happy to go on test drives, even when they had low inventory.
Only major browser not to support it. If they enable it and put hooks for BLE event callbacks, we would no longer need a custom app per-device.
Also, if BLE support was there, you could provision your WiFi-connected device without having to go do the whole AP-mode dance: push button on device, toggle WiFi on your phone, set it up on WiFi, etc. It's a big usability blocker for consumer devices. That whole sequence could be automated by visiting a URL on your phone or desktop.
They've announced they won't support it, ostensibly because of fingerprinting and privacy concerns. But that could be tackled the same way they've blocked all the other fingerprinting methods (fuzzing, threat of blocking, etc.)
Also: WebXR please.
The ESP32 ecosystem, though, is much larger.
Until recently, the only devkit you could find was the Seeedstudio Wio Terminal. Just came across a devboard on AliExpress for < $6. Looks interesting.
Not sure why, but there it is: https://turbotax.intuit.com/tax-tips/jobs-and-career/can-you...