Topics (316k) Articles (328k) Users (379) Discussions (238) Comments (383) Files (10k) New article
Originally by Keyhole Inc., which the nbecame Google Maps, but the format seems standardized and has non-Google support, so should be OK.
Trying to use gallium arsenide was Seymour Cray's fatal last flaw as mentioned at The Supermen: The Story of Seymour Cray by Charles J. Murray (1997).
The Supermen: The Story of Seymour Cray by Charles J. Murray (1997) page 4 mentions:
Cray wanted his new machine to employ circuits made from a material called gallium arsenide. Gallium arsenide had achieved limited success, particularly in satellite communications and military electronics. But no one had succeeded with it in anything so complicated as a computer. In the computer industry, engineers had developed a saying: "Gallium arsenide is the technology of the future," they would say. "And it always will be."
A law of physics is Galilean invariant if the same formula works both when you are standing still on land, or when you are on a boat moving at constant velocity.
For example, if we were describing the movement of a point particle, the exact same formulas that predict the evolution of must also predict , even though of course both of those will have different values.
It would be extremely unsatisfactory if the formulas of the laws of physics did not obey Galilean invariance. Especially if you remember that Earth is travelling extremelly fast relative to the Sun. If there was no such invariance, that would mean for example that the laws of physics would be different in other planets that are moving at different speeds. That would be a strong sign that our laws of physics are not complete.
Lorentz invariance generalizes Galilean invariance to also account for special relativity, in which a more complicated invariant that also takes into account different times observed in different inertial frames of reference is also taken into account. But the fundamental desire for the Lorentz invariance of the laws of physics remains the same.
The busy beaver game consists in finding, for a given , the turing machine with states that writes the largest possible number of 1's on a tape initially filled with 0's. In other words, computing the busy beaver function for a given .
There are only finitely many Turing machines with states, so we are certain that there exists such a maximum. Computing the Busy beaver function for a given then comes down to solving the halting problem for every single machine with states.
Some variant definitions define it as the number of time steps taken by the machine instead. Wikipedia talks about their relationship, but no patience right now.
The Busy Beaver problem is cool because it puts the halting problem in a more precise numerical light, e.g.:
- the Busy beaver function is the most obvious uncomputable function one can come up with starting from the halting problem
- the Busy beaver scale allows us to gauge the difficulty of proving certain (yet unproven!) mathematical conjectures
Complexity: NP-intermediate as of 2020:
- expected not to be NP-complete because it would imply NP != Co-NP: cstheory.stackexchange.com/questions/167/what-are-the-consequences-of-factoring-being-np-complete#comment104849_169
- expected not to be in P because "could we be that dumb that we haven't found a solution after having tried for that long?
An important case is the discrete logarithm of the cyclic group in which the group is a cyclic group.
Pinned article: Introduction to the OurBigBook Project
Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
Intro to OurBigBook
. Source. We have two killer features:
- topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculusArticles of different users are sorted by upvote within each article page. This feature is a bit like:
- a Wikipedia where each user can have their own version of each article
- a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.Figure 1. Screenshot of the "Derivative" topic page. View it live at: ourbigbook.com/go/topic/derivativeVideo 2. OurBigBook Web topics demo. Source. - local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
Figure 2. You can publish local OurBigBook lightweight markup files to either OurBigBook.com or as a static website.Figure 3. Visual Studio Code extension installation.Figure 5. . You can also edit articles on the Web editor without installing anything locally. Video 3. Edit locally and publish demo. Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension. - Infinitely deep tables of contents:
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact





