That car had the digital "Heads Up Display" on the windscreen that a lot of modern cars are getting back now. I wonder why it fell out of fashion for three decades?
I swore to the cop that the tree just jumped out in front of my 280Z.
The 0-60mph time for a 2025 Ford F-150 pickup truck is 5.8 seconds. Today's "performance" cars are in the 2 to 3 second range.
It was a more leisurely time.
I remember this every time something like a Cadillac Escalade leaves my 21-year-old 350Z in its dust...
Got a l28 turbo waiting to be refreshed as well.
I should stop working on this refactor and go work on it.
Nismo is coming out with a new DOHC head for the car... https://japanesenostalgiccar.com/nismo-dohc-nissan-datsun-l-...
There was also this gent who made his own DOHC off of a Honda head.
https://forums.hybridz.org/topic/119641-twin-cam-head-for-th...
What are examples of these "new applications" that are needed every day? Do consumers really want them? Or are software and other companies just creating them because it benefits those companies?
I've worked (still do!) for engineering services companies. Other businesses pay us to build systems for them to either use in-house or resell downstream. I have to assume that if they're paying for it, they see profit potential.
Everyone and everything has a website and an app already. Is the market becoming saturated?
The market is nowhere close to being saturated.
Also the connection process isn't power-prohibitive for BLE, and it doesn't have to take a long time. It's just that most Bluetooth software stacks suck balls. Basically only Apple's is good.
As I recall BLE only supports hosts connecting to 7 peripherals simultaneously which is a bit rubbish, but if you're a gym with some custom ANT+ receiver you can definitely get a custom BLE receiver that can connect to more devices (assuming someone makes such a thing).
I don't know how difficult it would be to connect, grab a bunch of data and disconnect from 24 BLE devices in a one-second period, which is pretty much what you'd need to be an effective workaround for ANT+. In a competitive environment, data from each device changes very rapidly.
But rural Europe was no picnic either - you would still be likely to die in all sorts of painful ways, from sepsis, diseases, accidents, childbirth, etc. And my god, it would have been dull.
Honestly, if you forced me to go back to the 17th century, I would probably take the risk and live in London. At least there is the possibility of crossing paths with Samuel Pepys, Christopher Wren, the early Royal Society etc. while you sit in your coffeehouse reading a freshly-printed news sheet.
A PhD student once mentioned to me that when people envisage themselves in history, they always assume they'd be upper class. No one ever thinks that they'll be poor :-)
https://en.wikipedia.org/wiki/ANT_(network)
I believe that's what the author was referring to when describing it as failed, but yes, this could've been worded better.
Contrast with BLE where you would have to make a connection to each device. The overhead of connecting and disconnecting, in addition to being power-prohibitive, takes too long. Some manufacturers have workarounds to enable use of their BLE products in a group fitness environment, but they are pretty much lacking.
It'll be interesting to see how the problem is solved if indeed ANT+ does go away.
The answer to this (throughout the ages) should be the same: read the authoritative source of information. The official API docs, the official language specification, the man page, the textbook, the published paper, and so on.
Maybe I am showing my age, but one of the more frustrating parts of being a senior mentoring a junior is when they come with a question or problem, and when I ask: “what does the official documentation say?” I get a blank stare. We have moved from consulting the primary source of information to using secondary sources (like O’Reilly, blogs and tutorials), now to tertiary sources like LLMs.
If I have a problem with a USB datastream, the last place I'm going to look is the official USB spec. I'll be buried for weeks. The information may be there, but it will take me so long to find it that it might as well not.
The first place to look is a high quality source that has digested the official spec and regurgitated it into something more comprehensible.
[shudder] the amount of life that I've wasted discussing the meaning of some random phrase in IEC-62304 is time I will never get back!