So the thing about wanting an ebike rather than a normal bike is that my bad leg means I want the assistance regardless.
I'm currently fancying e-bikesdirect.co.uk/brands/wβ¦
I can turn off/down the assist to get more exercise as I get more confident and less enormously fat.
It gets more complex when you realise Need a folding bike or I can't have it anyway because I have nowhere to keep a full-size bike
I shall endeavour to take advice from a shop before ordering anything.
I am, as you are all no doubt aware, quite overweight. My brother suggested I get an electric bike as a way to encourage me to exercise, while giving me some assistance to stop me from giving up.
What do you lot think?
GUYS I HAVE SHAMELESSLY TESTED THE NFC LED NAILS ON THE BUS TO CAPTURE THIS BEAUTIFUL VIDEO. I didnβt even have to touch it!ππ #nfcnails#lednails
Well, it looks like flexibility wins over size/performance. I'll be designing an expression DSL for my stuff this week I guess :-D
Thanks all who voted/commented.
Knowing C is useful because it gives a good grounding in *why* a lot of computing is like it is.
*using* C on the other hand... Only for special situations IMO :-)
Codegen would be smaller, faster, lower latency, lower power.
Data-driven is likely more easily debuggable. Either would be easy to change later.
There are no colleagues to explain it to (personal project)
Which is preferable, when building an app for an embedded Linux platform? Trying to decide between converting my data driven approach to code-generation, or expanding the data approach to support expressions and data dependencies.