My main gripe about Reddit is the sheer amount of low-value comments, with repeated remarks, jokes and puns trumping constructed and sourced arguments. It is obviously hard to find a good compromise.
1,152 karma · joined January 13, 2014
[ my public key: https://keybase.io/qsantos; my proof: https://keybase.io/qsantos/sigs/AtLN-dncEjUwRsnMmgBht5GAHbFKBcn_c1xsnKpVFL0 ]
My main gripe about Reddit is the sheer amount of low-value comments, with repeated remarks, jokes and puns trumping constructed and sourced arguments. It is obviously hard to find a good compromise.
------------------------------
If I read you correctly, you are raising two arguments:
1. what does an individual gains from participating in the project
2. objectively, why homo sapiens?
Regarding 2, I would say that there is not much to say aside from that we are not objective, and would prefer it if it was “us” who got to get to Mars.
I find point 1 much more interesting, especially what it says about society. Some individuals are very interested in the colonization of space, but not all are ready to directly work on it, and others are just uninterested.
However, having a structured government and a tax system allow us to make better use of individual skills, even that of those who are not directly interested in the project. Additionally, this is the kind of project where the ROI would be very long term and hard to estimate. Large scale coordination (governments and international institution) allow to make use of the "surplus workforce" that automatization is slowly making grow.
* jokes
* complaints about downvotes
* downvote predictions (thus self-fulfilling prophecies)
* single word / single expression
* simply (dis)agreeing (there are up/downvote buttons for that)
* condescendence, insults, etc.
This is very different from Reddit where numerous threads end up littered with jokes and puns. On the other hand the following types of comments tend to get upvoted:
* insightful and well structured (as in: cut in several paragraphes)
* food for thought
* counter-point (politely worded, obviously)
* sourced
----------------------------------------
Your first comment was probably mostly perceived as a joke:
* “ROFL” just expresses your personal reaction to previous information, and the common use of this acronym usually signals a low quality comment
* “Bootstrap has become a sign of a lazy developer”: this reads as both condescending (“lazy developer”) and unsupported; a more constructed argument with the same idea would have been fine
Your second comment contains the word "downvote", which is often enough to get downvotes.
----------------------------------------
You might want to have a look at:
Anyone can make a tiny isolated network and create a fork that will look real to the target (here, the iPhone).
This is remotely related to the CAP Theorem [1]. Namely, you expect a blockchain not to fulfill the consistency requirement.
1. people might get harmed by the radiation (true)
2. evacuate them (still arguably sensible)
3. radiations caused harm because people were evacuated
You can contact me on the address listed on my Github profile, or the one on my Hacker News profile (yoha@sinon.org)!
I know how much of a hassle it can be to handle even simple dependencies when you use a different system and workflow, so I tried to make it as seamless as possible.
There still is a lot of work to do. For now, I only implement patched conics (i.e. I only consider one planet/moon at once and ignore the influence of other celestial bodies on the trajectory), and it is not really easy yet.
Handling n-body physics would not be that hard, but I prefer to focus on having a simple model (patched conics) work well first.
Don't hesitate to contact me at either yoha@sinon.org or at the mail address on my Github profile, if someone have an issue installing. It should work on both Linux and Windows but I have not yet any nice packaging, so it might require some tweaking around (i.e. installing PyOpenGL on Windows manually).
Basically, a very much work-in-progress pile of code to plan orbital trajectories and interplanetary travel. Its also quite handy when doing simple computations:
>>> # distance to the Sun, in light-seconds
>>> Earth.orbit.semi_major_axis / c
499.00650691887006
>>> # Martian year, in (usual Earth) days
>>> Mars.orbit.period / Earth.solar_day
686.9944644093075
>>> # ping to New Horizons (light roundtrip), in hours
>>> (Pluto.orbit.periapsis - Earth.orbit.apoapsis) / c / 3600 * 2
7.9167895224639375
The graphical interface does work though! (kinda) It's initially inspired from Kerbal Space Program, so it defaults to showing Kerbin and its universe. However, you can choose Earth instead. I like to just zoom in and out, and explore the Solar system; the vastness of that is so mindblowing!How yeah, and a link: https://github.com/qsantos/spyce/
It shows… 5 data points.
[1] https://imgur.com/gallery/bxzeN [2] https://www.reddit.com/r/educationalgifs/comments/468290/a_c...
Another take on this, from Scott Alexander: http://slatestarcodex.com/2014/12/17/the-toxoplasma-of-rage/ .
g already means "9.8 m/s²"
Thus, normal gravity is 1g and free fall is 0g. 9.8g would mean 9.8 times the gravity at Earth surface, that is "96 m/s²". You would feel almost ten times as heavy. For reference:
Jupiter "surface" gravity is 25.9 m/s²
Sun "surface" gravity is 274 m/s²
The usual approach is to take a random odd number of desired length and then have a probabilistic primality test (much faster than what would be needed for a formal proof). Several attacks rely on bad entropy or bad pseudo random number generators (PRNG) to guess what prime was selected.
telnet towel.blinkenlights.nlOn the other hand, that might help make people understand how to pick a good password.
Thanks for spreading arcane knowledge!
Regarding the naming convention, I am trying to stick to PEP8 as strictly as possible (sometimes, even in C) and to use overly explicit variable names. I had not noticed that you did that too for the structure member, with `longitude_of_ascending_node` and such. My objective is to have the code be as readable as possible to a newcomer (hence Python, too).
It might be interesting to link to all codebases that might be relevant. Maybe I will add a list to https://airsick.guide/tools.html.
---
I only searched briefly for more stable methods. Thanks for the reference, I'll have a look!