hobos_delight
Joined 15 years ago
Joined 15 years ago
The software on the other hand... I would love per-key profiles (like the polestar) and buttons doing the thing they're labeled for when using CarPlay - but I _hope_ these things can be updated OTA. The UI and responsiveness is really quick however, especially compared to the P2 which feels woefully underpowered with constant UI lags.
Terrible software seems to be par for the course in cars.
I love these watches after moving from an Apple watch, primarily for two reasons:
1) the battery life - I cant stand having to charge my watch every day or so - my (current) Tactix 7 will go ~3-4 weeks depending on how much GPS I use.
2) (this may be out of date) when I would use the Strava or Run app on the Apple watch, it would not signal when it had a GPS fix, which resulted in a number of runs that had a "teleport" at the start, resulting in messed up metrics. Only a small thing, but it really frustrated me.
It took about a week to finally get used to paredit-mode (and rainbow-parens, because…) but once I did it is the most productive I have ever felt, I keep trying to find that experience again.
Unfortunately the dynamic types and slow build system (lein) made the build step quite tedious (this was 11-12 years ago) - but in terms of expressing ideas, man - paredit + lisp style was amazing!
I think my original point was more in the “engineers want to do cool, scalable stuff” realm - and so any solution has to support scaling out to the n’th degree.
Organisational factors pull a whole new dimension into this.
I’ve spent time in some of the largest distributed computing deployments and cost was always a constant factor we had to account for. The easiest promos were always “I saved X hundred million” because it was hard to argue against saving money. And these happened way more than you would guess.
The reason we use these is for when we have a data set _larger_ than what can be done on a single machine.
Oracle acquired Java with Sun Microsystems, it was originally designed for embedded systems and the dream of “write once, run everywhere”.
The idea of a “hardware JVM” always fascinated me, I seem to recall some parallax microcontrollers that could run a subset of jvm bytecode back in the 90s, but never actually got to play with them.
I tried thinking a bit outside the box for other questions that would break down the search space - but none of them were any improvement on the binary search.
It's the same model they use for operating in China.
From an operational perspective this makes things very hard - as you don't actually get access to the services - you need to run an operator from the independent company through the troubleshooting / mitigation for any incident.