739 karma · joined February 20, 2007
reach me at jedavis83@gmail.com
It looks like you're doing this calculation:
Isp * Gravity / Gravity
If you're trying to predict the hover duration, that will depend on the delta V of the vehicle. Then, a hover duration would be:
Delta v / Gravity
Not sure what the expected delta V is for the Dragon though.
Some resources:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
http://en.wikipedia.org/wiki/Chunked_transfer_encoding
http://en.wikipedia.org/wiki/HTTP_ETag
I'm glad you're addressing this problem! I always end up with file(1).zip in my downloads folder.
http://www.northernsun.com/images/imagelarge/Bake-Sale-Bumpe...
1/2 * c * v^2
Where c is the capacitance in farads, and v is the voltage. That will produce a value of joules. Note that the capacitor is rated for a given voltage, so that goes in as v.
Converting watt hours to joules goes like this: A watt is one joule per second, so a watt hour is 3600 joules.
Keep your pulse on new technologies, and write your own to expand your expertise. But don't use the wrong tool for the job out of boredom.
Just replied to you via email as well. For everyone else: we haven't yet tested this, but look forward to adding this as an officially supported datasource in the future.
1. We've been keeping the demo link a bit hidden, but we're among friends here, so feel free to check out: https://chartio.com/demo/ for some sample data.
2. Absolutely -- we're going to be developing an SSH version for Windows in the future.
3. MS-SQL support is in the works, so stay tuned.
4. Very good point -- the CSV export is relatively basic, and will be more fully featured in the future.
Glad you enjoyed what you've seen so far, and let us know if you have any other ideas for us to focus on!
If this hits your skin, you probably won't feel it due to the high frequencies involved, similarly to how you won't hear sounds over ~20khz. Your body wont' be able to process it neurologically. You will, however, get a really nasty burn from it, which can get bad if you don't sense the initial shock. If it hits your torso, you could potentially experience heart rhythm issues, but unlikely.
Voltage and frequency dangers are funny things. The most dangerous voltages are from about 50V to 1000V because it interferes with your nervous system -- lower and the current is too low to affect you, and higher causes you to reflexively release. The most dangerous frequencies are ~1Hz to ~10kHz. They're most likely to mess with your cardio rhythms in a bad way. Funny thing about this is that the most dangerous voltages and currents are found in household voltages -- 120V@60Hz (220V@50Hz in Europe).
If there are differences between IE and (Chrome|Firefox|Opera), then it will require additional developer time. Just testing for those differences will require additional developer time.
I don't want to demonize IE. Supporting any browser requires testing. IE has been especially reluctant to adopt web developer trends and needs to work hard to regain developers' trust. Supporting it isn't just the cost of a testing environment.
However, presenting the data with pie charts isn't really acceptable. 3d pie charts, even less acceptable. And 3d pie charts with gradient shading is worse still. If you want readers to take data-driven articles seriously, please learn even the basics of data visualization and how to best demonstrate the differences in data, and how to further compare the data contained. A side-by-side stacked bar chart would allow viewers to easily compare values relative to each other within the bar chart, and also to visually compare across the 3 companies.
Indeed it would be. That said, CoffeeScript is a compiler of sorts.
> And we'd like to do it in a more elegant way than constantly writing "if(argument === ...) then ... else ..."
This doesn't really seem to solve that problem. It just throws consistent errors if the types don't match. Your code would likely throw its own error if you didn't check the type manually. In my experience, native js errors are as easy or easier to track down that throwing errors yourself.
> Contracts also allow us to check invariants that might not result in a run-time exception but could lead to the code just being subtly wrong.
Ah, ok. That makes more sense. They're like python decorators, only single purpose.