Nope, it's like the guy in the other sub-thread was saying, it was CHRP (basically a common BIOS and architecture for all PPC systems) and one of Apple's many attempts at a new OS (either PowerOpen or Pink). PowerPC was going to be the one thing to rule them all.
Then something happened. IBM decided to only make high-powered server CPUs, and Motorola decided to only make low-powered embedded CPUs. Apple was stuck in the middle with no CPUs that they could use for laptops (weak FSB) and no CPUs that they could use for desktops without using liquid cooling (don't buy a used G5 tower, it might leak!). So Steve Jobs said fuck it, we're going with five blad... er, Intel.
Not to mention that the whole point of emulating apps for the same OS with a different instruction set is that most of the time is taken up inside the OS and its libraries anyhow. If 5% of your time is spent running at 25% of the speed, you don't lose much.
And anyone with half a clue would have gone to System Preferences -> Security & Privacy -> General and turned it off. The difference? Windows 10 S won't let you turn that off, ever.
So how to do they plan to handle the case of a launch where the first stage returns to a pad on the launch site, but the payload goes into space? Which mileage do they use? Is the distance measured from the launch site to the landing site, or some arbitrary point in space for each half of the flight?
I hadn't heard of Kodiak before, but Wallops has launched some ISS supply missions. Even though it's a bit north, Wallops is somewhat unique in that it can launch both polar and ISS missions, thanks to the Russians needing a high inclination for Baikonur. And it seems that both of those locations have had multi-year setbacks due to launch failures.
When I look at a map, I see that the Texas coast around Houston isn't a bad place for polar launches, though Louisiana is probably better because of the angle for sun-synchronous orbit. The only land downrange is a narrow strip of southern Mexico which is sparsely populated. So there's yet another good option that isn't California. The main problem is probably hurricanes, which can also affect launch sites along the GA/SC/NC coast.
One more thing about the scrolling, set the scroll bars to show "always". Seriously, just poke around in the System Preferences a while and see what settings there are.
- it's a laptop, you can plug a real keyboard into it
- I don't understand what the touchpad has to do with Siri, must be a touchbar thing, again, get a proper keyboard
- turn off spaces, that's one of the things they added after 10.6 that I find particularly annoying, also use the green widget at the top corner of the window to expand, not the two arrows thing, learn to use overlapping windows better, use the dock icon of an app or command-tab to switch all windows at once, then strategically leave window corners sticking out on the edge of the screen to click in just the window you need, and with enough resolution you can even put things side-by-side
- use list view? I never use icon mode in the Finder, I mostly only ever see it when I open a.dmg
- learn to snap up to the top of the screen with your mouse/trackpad, Fitts' Law
- you can't run them on Linux either without adding crap, so? it's a completely fucking different OS. You could also try Parallels.
- I don't know what you mean by "links in the browser", if you mean web browser, use a different one? Safari is hardly a great browser, not sure why you would use it for serious stuff, I only use it when I encounter a web site with a browser incompatibility. Anyhow, maybe you are "holding it wrong", trying to do things that no old-time user would even consider, or you simply haven't found the right config settings. Then again, there are reasons I'm still staying on 10.9.
- you can turn off the software update nags, just unlike Windows 10. Again, I'm still on 10.9 because I don't want to deal with various annoying things Apple keeps slipping into newer versions. I turn off a lot of other default Notification Manager nags too. I can see how they can be useful to some people, but I don't need that level of nag.
- I prefer TextEdit and command line make most of the time myself, but I've been mostly making smaller stuff that I don't need a "real debugger" for. Also, that new find/replace thing is annoying with how it fucks up keyboard focus, and it's somehow worse in Xcode than TextEdit. I still miss the classic 10.6-era find/replace as a separate window.
- I don't use iPhone, can't say anything about that
- I'm still using 2010-2012 era hardware, sometimes Apple has an era with hardware I don't want, the late '90s were particularly bad
- depends on how you "hold it" ha ha, but you might be using something that uses some CPU, try "top -u" in a terminal window and see who might be a hog
- first of all, you did click on that little triangle next to the file name in the save as dialog to show the NeXT tree view, right? It's in wuss mode by default, on a per-app basis.
- again, who is stopping you from getting a real keyboard? And I don't mean Apple's current LOOKHOWTHINIAM keyboards, try finding a keyboard from the '00s. If you are doing serious development, you should be at a desk anyhow, where you have space for a real keyboard, not at coffeebucks. But gonna admit I don't like that keybar shit, I at least want keys I can feel. It's might be cute for doing some live performance shit, but not for hacking code
I put my Dock on the right (with wide screens, conserving vertical space is more important), one or two Terminal windows peeking out at the bottom edge (I have to leave a bit more space than I used to now that the grow areas are on all sides of a window now), and a couple of text files I deal with regularly peeking out along the left edge. I make the most of that Fitts' Law.
However, this go around we ain't going to put a man on Mars (yeah, it's scheduled 20 years from now, it's always been 20 years for the past 50 years).
The thing is, it's been so long that civilian technology is surpassing governmental interest in going beyond LEO. The re-landings that SpaceX is doing are one of the things that is driving down the cost of spaceflight. Really, the main difficulty in a Mars mission is the duration, because without a large power source (like a nuclear generator powering ion engines), the mission duration is about 2 1/2 years whether or not you spend most of that on planet. The long duration means that you have to worry about supplies and medical situations.
It's sort of like 19th century naval polar expeditions, only without water to float in and air to breathe and wildlife to eat and even natives to show you how to make a proper sled when you get into trouble. Even then they had life support troubles like food cans soldered with lead that contaminated the food.
The real real question is if the "full thrust" version of the SLS will ever exist. For now they are only making the lower-thrust version that is not much better than FH.
The worst thing about LH2 is that once you get it cold enough to be liquid, it changes phase with the relative spins of the two atoms, and the heat generated by that warms it up just enough to become a gas again. It takes days to properly chill LH2.
I think you missed the most important part. They wired a NEW neighborhood, that hadn't been previously wired. The major blockade to getting the last mile of fiber installed is usually right of way, both on utility poles (they are often owned by a competitor) and it's even worse when all the wiring is underground. Sometimes the old wiring in a neighborhood falls apart to the point where it needs to be completely replaced, and at that point you will probably see the "only one block gets gigabit" effect.
I've had strictly DSL in some for or other since early 2000, and I've rarely had "connectivity issues". The most notable times were first, when the local copper down the alley degraded to the point where POTS service gave up before DSL did (though this gave me my first lesson in how TCP/IP doesn't tolerate even 10% packet loss very well), and second when (at least three times on two lines!) someone re-punched the wires inside a breakout box incorrectly. There have also been times (usually after midnight) where I lose internet for a few minutes, probably when they force an update and reboot the modem. Oh yeah, and there was one incident where they sent a bad update to the remote terminal and bricked it (!), and couldn't get a replacement until the second day.
Those breakout box incidents were all after Uverse began, so either they had idiots upgrading their network (no old-school Bell System repairman would have done something so stupid), or they were intentionally trying to fuck with people who still had classic DSL. (which they were deprecating)
But five incidents over 17 years with at least seven different installs in two cities? Not bad. Certainly not the "daily issues" with Comcast that someone else in these replies mentioned.
For example, two months ago I drove about two miles on a horribly bumpy dirt road. Two weeks later and I had a coolant leak. Turned out that a hose clamp had come loose. Hmm, I wonder how that could have happened?
Seriously, flying cars are probably the dumbest idea that just won't die.
I'm not quite old enough to have used FORTRAN. I grew up on BASIC and Z-80 assembly language on a TRS-80 (and a bit of HP BASIC on equipment at school), but when I went to college in 1982, they were using PL/I. The first semester was even on IBM equipment, but fortunately they got a VAX late in the semester, because I managed to screw up my JCL by trying to reformat it to be readable. I still don't know why it took DEC so long to add the UNTIL statement to their PL/I compiler.
Then I got into programming on the Macintosh, so I started using Pascal. Also, Turbo Pascal was a thing, and they were both UCSD variants. But one of the worst things to do is use Pascal and PL/I at the same time. (as in same era, not simultaneously) The function headers are syntactically backwards to each other.
I didn't even officially switch over to C until after 2000. I even have one program I use sometimes that started with code I originally wrote in college in PL/I, then ported to Pascal, then again ported to C.
robots.txt is intended to indicate what parts of a site should not be scanned recursively, often due for technical reasons such as generated content> It especially for sub-paths like/cgi-bin/, but there is no technical reason why the content of any arbitrary URL can't be programmatically generated. It might be and you wouldn't even know it, because the generated content may be the same most of the time, such as a navigation menu.
However, it was also not intended to be used to remove previously-archived content, as archive.org is currently using it. When an archived page changes status in robots.txt, they should note the first date that the status changed, then simply stop updating it until and if robots.txt re-allows it.
scanning and archiving are two different operations, and robots.txt is only intended to apply to the former.
To be completely fair, upper VHF (7-13) is rather nice for ATSC, but a lot of antennas without VHF elements are sold these days. Lower VHF is rather crap for ATSC, though. Maybe they are the ones who deserve a "discount" (whatever that is) these days.
The scene with the spaceship and playing the music is awesome (I read that one of the Arp synthesizer guys was actually cast as one of the music crew), the mashed potatoes scene is funny, everything else I guess is meh. But a few scenes does not make a great movie. Overrated? Perhaps, but at the time it was really hyped.
Slashdot Mirror
Nope, it's like the guy in the other sub-thread was saying, it was CHRP (basically a common BIOS and architecture for all PPC systems) and one of Apple's many attempts at a new OS (either PowerOpen or Pink). PowerPC was going to be the one thing to rule them all.
Then something happened. IBM decided to only make high-powered server CPUs, and Motorola decided to only make low-powered embedded CPUs. Apple was stuck in the middle with no CPUs that they could use for laptops (weak FSB) and no CPUs that they could use for desktops without using liquid cooling (don't buy a used G5 tower, it might leak!). So Steve Jobs said fuck it, we're going with five blad... er, Intel.
Not to mention that the whole point of emulating apps for the same OS with a different instruction set is that most of the time is taken up inside the OS and its libraries anyhow. If 5% of your time is spent running at 25% of the speed, you don't lose much.
as much as Apple touts standards and practices in their own operating systems, they play fast and loose with Windows.
Yes, but everybody plays fast and loose with Windows, especially Microsoft.
Hey, be fair, the OS X version only sucks a little bit. It is the Windows version that sucks so hard that a black hole appears on your hard drive.
And anyone with half a clue would have gone to System Preferences -> Security & Privacy -> General and turned it off. The difference? Windows 10 S won't let you turn that off, ever.
But will it work on my Penmiut?
So how to do they plan to handle the case of a launch where the first stage returns to a pad on the launch site, but the payload goes into space? Which mileage do they use? Is the distance measured from the launch site to the landing site, or some arbitrary point in space for each half of the flight?
I hadn't heard of Kodiak before, but Wallops has launched some ISS supply missions. Even though it's a bit north, Wallops is somewhat unique in that it can launch both polar and ISS missions, thanks to the Russians needing a high inclination for Baikonur. And it seems that both of those locations have had multi-year setbacks due to launch failures.
When I look at a map, I see that the Texas coast around Houston isn't a bad place for polar launches, though Louisiana is probably better because of the angle for sun-synchronous orbit. The only land downrange is a narrow strip of southern Mexico which is sparsely populated. So there's yet another good option that isn't California. The main problem is probably hurricanes, which can also affect launch sites along the GA/SC/NC coast.
One more thing about the scrolling, set the scroll bars to show "always". Seriously, just poke around in the System Preferences a while and see what settings there are.
- it's a laptop, you can plug a real keyboard into it .dmg
- I don't understand what the touchpad has to do with Siri, must be a touchbar thing, again, get a proper keyboard
- turn off spaces, that's one of the things they added after 10.6 that I find particularly annoying, also use the green widget at the top corner of the window to expand, not the two arrows thing, learn to use overlapping windows better, use the dock icon of an app or command-tab to switch all windows at once, then strategically leave window corners sticking out on the edge of the screen to click in just the window you need, and with enough resolution you can even put things side-by-side
- use list view? I never use icon mode in the Finder, I mostly only ever see it when I open a
- learn to snap up to the top of the screen with your mouse/trackpad, Fitts' Law
- you can't run them on Linux either without adding crap, so? it's a completely fucking different OS. You could also try Parallels.
- I don't know what you mean by "links in the browser", if you mean web browser, use a different one? Safari is hardly a great browser, not sure why you would use it for serious stuff, I only use it when I encounter a web site with a browser incompatibility. Anyhow, maybe you are "holding it wrong", trying to do things that no old-time user would even consider, or you simply haven't found the right config settings. Then again, there are reasons I'm still staying on 10.9.
- you can turn off the software update nags, just unlike Windows 10. Again, I'm still on 10.9 because I don't want to deal with various annoying things Apple keeps slipping into newer versions. I turn off a lot of other default Notification Manager nags too. I can see how they can be useful to some people, but I don't need that level of nag.
- I prefer TextEdit and command line make most of the time myself, but I've been mostly making smaller stuff that I don't need a "real debugger" for. Also, that new find/replace thing is annoying with how it fucks up keyboard focus, and it's somehow worse in Xcode than TextEdit. I still miss the classic 10.6-era find/replace as a separate window.
- I don't use iPhone, can't say anything about that
- I'm still using 2010-2012 era hardware, sometimes Apple has an era with hardware I don't want, the late '90s were particularly bad
- depends on how you "hold it" ha ha, but you might be using something that uses some CPU, try "top -u" in a terminal window and see who might be a hog
- first of all, you did click on that little triangle next to the file name in the save as dialog to show the NeXT tree view, right? It's in wuss mode by default, on a per-app basis.
- again, who is stopping you from getting a real keyboard? And I don't mean Apple's current LOOKHOWTHINIAM keyboards, try finding a keyboard from the '00s. If you are doing serious development, you should be at a desk anyhow, where you have space for a real keyboard, not at coffeebucks. But gonna admit I don't like that keybar shit, I at least want keys I can feel. It's might be cute for doing some live performance shit, but not for hacking code
I put my Dock on the right (with wide screens, conserving vertical space is more important), one or two Terminal windows peeking out at the bottom edge (I have to leave a bit more space than I used to now that the grow areas are on all sides of a window now), and a couple of text files I deal with regularly peeking out along the left edge. I make the most of that Fitts' Law.
Clearly, Microsoft just doesn't have enough courage.
However, this go around we ain't going to put a man on Mars (yeah, it's scheduled 20 years from now, it's always been 20 years for the past 50 years).
The thing is, it's been so long that civilian technology is surpassing governmental interest in going beyond LEO. The re-landings that SpaceX is doing are one of the things that is driving down the cost of spaceflight. Really, the main difficulty in a Mars mission is the duration, because without a large power source (like a nuclear generator powering ion engines), the mission duration is about 2 1/2 years whether or not you spend most of that on planet. The long duration means that you have to worry about supplies and medical situations.
It's sort of like 19th century naval polar expeditions, only without water to float in and air to breathe and wildlife to eat and even natives to show you how to make a proper sled when you get into trouble. Even then they had life support troubles like food cans soldered with lead that contaminated the food.
The real real question is if the "full thrust" version of the SLS will ever exist. For now they are only making the lower-thrust version that is not much better than FH.
...because they insisted on using CFC-free foam.
The worst thing about LH2 is that once you get it cold enough to be liquid, it changes phase with the relative spins of the two atoms, and the heat generated by that warms it up just enough to become a gas again. It takes days to properly chill LH2.
I think you missed the most important part. They wired a NEW neighborhood, that hadn't been previously wired. The major blockade to getting the last mile of fiber installed is usually right of way, both on utility poles (they are often owned by a competitor) and it's even worse when all the wiring is underground. Sometimes the old wiring in a neighborhood falls apart to the point where it needs to be completely replaced, and at that point you will probably see the "only one block gets gigabit" effect.
I've had strictly DSL in some for or other since early 2000, and I've rarely had "connectivity issues". The most notable times were first, when the local copper down the alley degraded to the point where POTS service gave up before DSL did (though this gave me my first lesson in how TCP/IP doesn't tolerate even 10% packet loss very well), and second when (at least three times on two lines!) someone re-punched the wires inside a breakout box incorrectly. There have also been times (usually after midnight) where I lose internet for a few minutes, probably when they force an update and reboot the modem. Oh yeah, and there was one incident where they sent a bad update to the remote terminal and bricked it (!), and couldn't get a replacement until the second day.
Those breakout box incidents were all after Uverse began, so either they had idiots upgrading their network (no old-school Bell System repairman would have done something so stupid), or they were intentionally trying to fuck with people who still had classic DSL. (which they were deprecating)
But five incidents over 17 years with at least seven different installs in two cities? Not bad. Certainly not the "daily issues" with Comcast that someone else in these replies mentioned.
"It was heartbreaking to see that some of our users were upset to learn about how we monetize our free service,"
Heartbroken because the users found out about it.
For example, two months ago I drove about two miles on a horribly bumpy dirt road. Two weeks later and I had a coolant leak. Turned out that a hose clamp had come loose. Hmm, I wonder how that could have happened?
Seriously, flying cars are probably the dumbest idea that just won't die.
I'm not quite old enough to have used FORTRAN. I grew up on BASIC and Z-80 assembly language on a TRS-80 (and a bit of HP BASIC on equipment at school), but when I went to college in 1982, they were using PL/I. The first semester was even on IBM equipment, but fortunately they got a VAX late in the semester, because I managed to screw up my JCL by trying to reformat it to be readable. I still don't know why it took DEC so long to add the UNTIL statement to their PL/I compiler.
Then I got into programming on the Macintosh, so I started using Pascal. Also, Turbo Pascal was a thing, and they were both UCSD variants. But one of the worst things to do is use Pascal and PL/I at the same time. (as in same era, not simultaneously) The function headers are syntactically backwards to each other.
I didn't even officially switch over to C until after 2000. I even have one program I use sometimes that started with code I originally wrote in college in PL/I, then ported to Pascal, then again ported to C.
robots.txt is intended to indicate what parts of a site should not be scanned recursively, often due for technical reasons such as generated content> It especially for sub-paths like /cgi-bin/, but there is no technical reason why the content of any arbitrary URL can't be programmatically generated. It might be and you wouldn't even know it, because the generated content may be the same most of the time, such as a navigation menu.
However, it was also not intended to be used to remove previously-archived content, as archive.org is currently using it. When an archived page changes status in robots.txt, they should note the first date that the status changed, then simply stop updating it until and if robots.txt re-allows it.
scanning and archiving are two different operations, and robots.txt is only intended to apply to the former.
To be completely fair, upper VHF (7-13) is rather nice for ATSC, but a lot of antennas without VHF elements are sold these days. Lower VHF is rather crap for ATSC, though. Maybe they are the ones who deserve a "discount" (whatever that is) these days.
I've heard that the UK MoD 25/8 addresses aren't even connected to the routeable internet.
The scene with the spaceship and playing the music is awesome (I read that one of the Arp synthesizer guys was actually cast as one of the music crew), the mashed potatoes scene is funny, everything else I guess is meh. But a few scenes does not make a great movie. Overrated? Perhaps, but at the time it was really hyped.