The user wants the website to work in IE6, developing and testing only against IE6 to the detriment of other browsers is not generally regarded as a healthy state of affairs.
The standard exists, it is the responsibility of both the producer and consumer of ePUB files to adhere to the standard.
If a large fraction of your users are on IE6 and you can't realistically get them off it, you need to make sure your site works in IE6, and good tooling should help you do this. Of course you also want to make sure it works in other browsers your users use, and a standard may be helpful in doing that.
Yes, for the ones I've owned rooting is very easy. KOReader and Plato are both popular (amongst the community of eReader rooting people) alternatives to the OEM software.
They're presenting it as a "intro to electronics" device. I think they've missed though, as far as I'm concerned, learning to build a "nLab" equivalent device from a bare AVR MCU would be a far more informative and useful introduction then yet another "Babies First blink.c" kit.
Even worse, a fully formed lesson plan, parts, and prerecorded lessons could actually be worth $200. Unlike this widget, which is not worth half that.
The spec page says 100 kHz BW on the oscilloscope, the FAQ says 400 kHz. In either case calling it an "oscilloscope" is a stretch, its the ADC channels on an MCU.
I find it curious that all their promo shots seem to only show the back of the board. I couldnt find any of the component side, or any information about what components are used. My guess would be:
- a very small dual rail supply
- AVR or STM MCU
- Signal generator is PWM through an RC low pass filter
- Oscilloscope is potentially just the input through a resistor network to shift +/- 5V to 0-5V, maybe a buffer to keep input impedance high.
I just don't see $170-200 of value here, or anything close to that.
Even weirder: the Kickstarter campaign says it’s 4 MSPS per channel. 100kHz bandwidth with 4 MSPS per channel just doesn’t make sense. However, they have “verified” 400kHz on their Kickstarter. Not sure who verified it, but it’s verified.
The Kickstarter does have product photos of the back in a gif but be forewarned: they don’t include any chip designations.
The specs are underwhelming, but I could see the value to a beginner being in the software that accompanies it tightly integrated with parts kits and instructions. I'd honestly prefer to see a logic analyzer instead of a mediocre oscilloscope; I feel like the projects that most people learning want to do these days are digital, and simple logic analyzers are more amenable to being cheap while still being useful.
I feel like building an nLab would be a far more valuable learning experience then using one.
The caveat being not just as a DIY soldering kit but as a full "course" in the design and construction of it.
Its got a power supply, an MCU, analog I/O, digital I/O. Learning the theory of how to read a 100kHz analog signal is far more valuable then a device that can read a 100 kHz signal.
A company operating above board would be sure to carefully document the state of the rental before and after whatever work they were doing. Any tradesperson/installer/technician/repair person will have tales of how they were accused of stealing grandmas wedding ring from the bottom of the sock drawer while repairing a leak in the kitchen.
So either Bot Company damaged property and is trying to pretend they didn't. Or they are incompetent and failed to document the state of the property or handle the owners complaints appropriately.
Given that their training robots and would therefore be collecting as much data as possible, including camera data, I'm leaning towards malice instead of ignorance.
You are technically correct, the best kind of correct. However! That would be a terrible UX/UI experience. While showing distances on a linear scale is accurate, it fails to capture all the information a person in an interstellar ship may wish to see.
Something like logarithmic distances would better capture information like "Am I about to crash into the star or enter a nice orbit" while still showing the full picture of where you are in relation to where you're going and where you came from.
No idea of that's what happened here, just a thought, I'm not an expert in starship computer interface design.
For something like a transfer between Starships you can resolve a lot of those problems by (very) gently spinning the 2 craft. It won't take much force for the liquids to settle at the bottom of their respective tanks where you would presumably put the intakes.
reply