If the variation of color are indicative of a similar variation in density, why is there so much turbulence in Jupiter, why are the upper layers not more consistent? Tidal motion? Anyone know?
In this post[1] there's a JunoCam picture from a previous flyby, which has been adjusted to be roughly as a human would see it. Still a lot of color though!
This[2] paper studies the ovals but has some details on the atmosphere, including the colors:
The reddish color is usually attributed to red “chromophores”, which are products of a series of complex chemical reactions, such as the UV photolization of ammonia with acetylene. These chromophores can act as coating material for the ammonia particles.
The cloud structure of the Jupiter's atmosphere, and in particular the nature of vortex features, as the [Great Red Spot] and the white ovals, is still puzzling.
This[3] paper tries to reproduce the reactions in the lab and compare them with the observed colors. It goes into some more details around the potential color formation.
I also want to just include this picture[4] because I just love the tiny fluffy clouds, which shadows provides amazing depth feeling.
[3]: https://doi.org/10.1016/j.icarus.2016.03.008Chromophores from photolyzed ammonia reacting with acetylene: Application to Jupiter’s Great Red Spot (use the hub of science for full paper)
It says exaggerated color/contrast. It seems to be a trend lately like the recent images of the Moon and Pluto. They might even be translating non-visible spectra to color so the material composition can be distinguished better, like they do with nebula and such.
It is well intentioned, it makes the images much more informative, and they are just really cool, which helps with public support. But it is also a bit misleading and confuses people.
I don't think you can follow the path originally trodden (competing on asmone 68K/hw with your fellow local coders, exchanging snippets of hw reg info and source) however there's a terrific short series of videos on youtube you might consider:
Wei-ju Wu lays out how to code directly on the hardware in an accessible manner and, importantly, from C, instead of 68K, with lots of examples. Then, if (or rather: when) you have to, you can always step down a level into 68K assembly to get better performance.
I have this one with power tools: "Power tool, power cool", which is intentionally silly, and that just means that if I'm using a power tool I'll put on safety glasses.
I’ve read drinking a small amount of salt water a single time during a survival situation can be beneficial versus no water. I leave it to readers to research this themselves further
"No, that's SMP" - is perhaps too resolute a definition. I'd say SMP is across processes, SMT is within a process, which would put the distinction in software, not hardware architecture.
Definitions are more grey, muddy and dependent on context; in that line of thought, I feel the parent you're responding to is accurate enough to not warrant criticism or even downvotes.
No, these things are really quite clearly defined, and certainly not so muddy to include something like "which would put the distinction in software, not hardware architecture.". These are hardware architecture terms.
For some (myself) the right shift key is the main shift key; so doing away with it would be terrible. Typically holding it down with the right pinky while typing full speed ahead, as well as single movement stroke patterns for <>{}?"+_ and so on, so heavy on all caps C snake case type use (if that makes sense.)
I also use the right shift a lot (though it's not my "main" one) and would hate to see it go away.
But there's no reason for it to be so freaking huge! On the two keyboards I have on my desk (HP EliteBook laptop and a "normal layout" desktop keyboard) the right shift is the second-biggest key after the space bar!
HN influences. It makes a wide and deeply technical circle aware. Maybe a week, month, year they suggest [or recommend to peers], etc. organic growth business like Plausible is about surviving long enough to keep growing your network effect. All these mentions and discussions add up. People remember.
exactly! our first "viral" moment was on HN too and we only got a few direct signups that day but we would never have made it to this point without being on the top of HN that time
The colorful stripes are more likely the decompression routine hammering dff180 (the background color) as a "busy signal" for the user. The Amiga has "chip RAM", which on many unexpanded machines is also the only type of RAM; there are no pre-reserved regions in chip ram; everything (code,data,framebuffers) can be anywhere the programmer wants.
I think OP is (probably?) referring to 8-bit C64 era technology, where framebuffers/video ram are at a fixed location in memory?
Since it's got such a low market share, it's much easier to declare your website "not compatible with Firefox" than it is to test on Firefox, even though 99% of sites that claim they're not compatible with Firefox work perfectly as soon as you spoof your user-agent to WebKit.
ok, interesting. I just checked, as of right now I still very much get the message "Unsupported Browser - In order to provide the best experience we require you use a different browser." So I'm not sure where our configurations differ.
Perhaps Mozilla should create more paid coding positions rather than padding Mitchell Baker's purse. She's sucked a lot of the air out of that organisation.
| keep in mind that picking Java over Cobol for banking software in 90s retrospectively turned out to be the right choice
Is the Java written in the 90's still the same Java written today? I feel the mentioned Lindy effect equally applies to dialect. C++ today is radically different to C++ from the 90's. I'd venture COBOL from the 90's is likely quite similar to COBOL today.
Looking at the Wikipedia page for Cobol 2002 and 2014, the last two major releases, it looks like they've gained features such as Object Oriented Programming, Recursion, data types like Booleans, pointers, and user-defined functions. So I'm going to bet modern COBOL looks totally different to that of the 90's!
I spent ~5 years working on a COBOL compiler. In practice, production COBOL compilers pick and choose which parts of the standard they choose to implement based on customer demand, and there's not a lot of demand for most of the new stuff. To a first approximation, almost all COBOL code is legacy code in maintenance mode, and I would guess that a significant fraction of COBOL running today has barely been touched since the 90s, if not earlier.
Been a while since I read it, but iirc one of his examples is of fellow captives telling themselves they'll be free before the new year, then the new year comes, still not free, and those would be the first ones to go (your "giving up").
But the alternative I never took as "resisting" - but "purpose." Frankl's own purpose being the study of people under such extreme conditions, but his point (again, iirc) being that having that indefinite, daily, purpose is what keeps people alive and brings meaning.
Now, granted, it's been a while since I read it, but can you provide some color to this notion of "resisting" ? It'd be interesting if you took something completely different away from it (or if I remember it incorrectly and should be corrected.)
If the variation of color are indicative of a similar variation in density, why is there so much turbulence in Jupiter, why are the upper layers not more consistent? Tidal motion? Anyone know?