TODO can anything interesting and deep be said about "why phase transition happens?" physics.stackexchange.com/questions/29128/what-causes-a-phase-transition on Physics Stack Exchange
How to play scores and save them to files is discussed at: doc.sccode.org/Guides/Non-Realtime-Synthesis.html
They have a nice looking IDE, but running anything from the command-line interface is super hard, much unlike Csound. How to get a decent hello world: stackoverflow.com/questions/65360414/how-to-play-a-supercollider-file-non-interactively-from-the-terminal-command-lin
Sample composition with custom synths + notes: sccode.org/1-5cl
leanpub.com/ScoringSound looks like a decent tutorial, it is basically the Csound FLOSS manual for SuperCollider.
Not a telephone-based system, needing its own network, and was killed particularly by fax which is. Telex evolved from the Telegraph, which is a binary system at the physical layer.
Somewhat midway between a syllabary and an alphabet: you write out consonants, and vowels are "punctuation-like-modifiers".
In a bicycle you just have too much more control and awareness than in a car, so if the way is completely clear, you should be allowed to stop, look if the way is clear, and then run reds.
This is the cutest product name ever.
Since 1992, Mr. SQUID has been the standard educational demonstration system for undergraduate physics lab courses.
YBCO device, runs on liquid nitrogen.
- always upvote questions you care about, to increase the probability that they will get answered
- never upvote other people's answers unless you might gain from it somehow, otherwise you are just giving other high reputation users more reputation relative to you
- only mark something to close or as a duplicate if it will bring you some advantage, because closing things creates enemies, especially if the OP has a high profileOne example advantage is if you have already answered the question (and the duplicate as well in case of duplicates), because this will prevent competitors from adding new better answers to overtake you.
- protect questions you've answered whenever someone with less than 10 reputation answers it with a bad answer, to prevent other good contributors from coming along and beating you
- when you find a duplicate pool answer every question with similar answers.Alter each answer slightly to avoid the idiotic duplicate answer detector.If one of the question closes, it is not too bad, as it continues netting you to upvotes, and prevents new answers from coming in.
- follow on Twitter/RSS someone who comments on the top features of new software releases. E.g. for Git, follow GitHub on Twitter, C++ on Reddit. Then run back to any question which has a new answer.
- always upvote the question when you answer it:
- the more upvotes, more likely people are to click it.
- the OP is more likely to see your answer and feel good and upvote you
- if a niche question only has few answers and you come with a good one, upvote the existing ones by other high profile users.This may lead to them upvoting or liking you.
- always upvote comments that favor you:
- "I like this answer!" on your answers
- "also look at that question" when you have answered that question
- if you answer a question by newbie without 15 reputation, find their other questions if any and upvote them, so that the OP can upvote your answer in addition to just accepting
- if a question has 50 million answers and you answer it (often due to a new feature), make a comment on the question pointing to your answer
- if you get a downvote, always leave a comment asking why. It is not because you care about their useless opinion, but because other readers might see the comment, feel sorry for you, and upvote.
- ask any questions under a separate anonymous accounts. Because:
- intelligent people are born knowing, and don't ever ask any questions, so that would hurt your reputation
- downvoting questions does not take 1 reputation away from the downvoter, and so it greatly opens the door for your opponents to downvote you without any cost.
Every article now has a (very basic) GitHub-like issue tracker. Comments now go under issues, and issues go under articles. Issues themselves are very similar to articles, with a title and a body.
This was part of 1.0, but not the first priority, but I did it now anyways because I'm trying to do all the database changes ASAP as I'm not in the mood to write database migrations.
Here's an example:
- ourbigbook.com/go/issue/2/donald-trump/atomic-orbital a specific issue about the article "Atomic Orbital" by Donald Trump. Note the comments possibly by other users at the bottom.
- ourbigbook.com/go/issues/1/donald-trump/atomic-orbital list of issues about the article "Atomic Orbital" by Donald Trump
There are unlisted articles, also show them or only show them.