I started programming by making games in TI-BASIC, for the TI-83+ graphing calculators. There were some weird tricks like omitting all ending parentheses. Good preparation for weird hacks in real languages.
So many crazy hacks for that system, I remember trying to use text sprites and there were certain vertical slices of pixel configurations that you just could not draw because there were no characters in the font where the leftmost column contained that combination of pixels which were off/on.
oh that's a miserable environment. i remember discovering that the label search starts from the beginning of your program text each time you branch (there's no table of label positions) so branching is much slower in later parts of your code.
the ti-81 was somehow worse. the If conditional only had the implicit else form (no Then/Else/End), there were no looping constructs (just Lbl, Goto, DS< and IS>), you had two lists for array-like data, and i can't recall ever figuring out how to manipulate strings—it may not have been possible.
But they don't take more time to move (on the same partition). Also it would be nice to see at a glance if a folder contains a lot of data (number of bytes, not files) before starting an operation.
if you are moving a folder of files within a partition (hey, this was your idea) then you don't care how many or how big they are. only if you move them to a different partition would you care, but in that case as you hover over the other partition, you'd want the folder to become helium or hydrogen light, so you would need to exert more force to get it to touch down in the folder. oh the humanity!
I first started coding in high school on the TI-84 calculators. My 1st language was TI-BASIC, 2nd was Z80 assembly - quite a big step - and I quit when I faced some tricky bugs that my teenage self could not figure out :-) Back then, I don't believe they had a C/C++ toolchain. Some time later, I tried using Small Device C compiler (SDCC), but encountered several compiler bugs which I couldn't fix but duly reported. Great to see there is such excellent tooling nowadays.
Disagree with first example. If that condition is only used once, adding a variable introduces more state to keep track of, that could just be a comment next to the conditional.
Hard to know if you're referring to Chromebook/Android/Web, but looks like the web one. If that's the calculator from the google.com web-page, that is surely a stylesheet/font that failed to load (sometimes?). Try to look at the browser developer console next time it happens for some request errors.
Reminds me of TI-BASIC for the TI-83 graphing calculators... The closing ')' is optional at the end of a line, and omitting it could make your program slightly faster...
Idea: deplane by row. Each row leaves when a light in that row turns on. An algorithm decides when to turn them on based on several factors: keeping large groups together, expected speed of deplaning (eg. elderly may be slower), current occupancy of the aisle. Advantage: should be very fast, easy to follow, groups stay together.
reply