Nuke

i think mp3 is streamable. what are you trying to do?

perfect immortality violates the second law of thermodynamics. virtual immortality might work, possibly through nanotechnology, where you dont naturally die but you can die from other causes. for example in events where terminal damage is done before the internal damage control nanobots can do anything about it. i can imagine having these nanobots installed and maintained costing a fortune, considerable opportunities for conflict to make a good scifi. life extension is another possibility where you have lifespans of a few hundred years, simply through advances in medicine. such as the doubling of natural life expectancy we have already accomplished since the stone age. growing of replacement bodies may also be a thing, but you cant do this to a brain. neurological degeneration may ultimately limit the effectiveness of such a process. cyborgification has the same problem, bodies are easy, but if you dont have a method to upload a consciousness, then its no different than a meat mech. if a way is devised of backing up the human mind to a computer then that would give you virtual immortality. but i have a feeling this would be like plugging a hard drive for a running system into another machine with different hardware. nothing would work right and it would fundamentally alter ones consciousness. you could still die and you would have to face the heat death of the universe, and that would probibly kill you. this is also going to be a high cost affair and source of conflict. in scenarios where immortality of any kind is viable, you are going to end up with a gerontocracy government run by the oldest individuals, younger immortals would make up the middle class and normal humans would be relegated to a disposable lower class. obviously since it would be possible for immortals to die through various accidental and intentional means, the dangerous jobs would mostly be relegated to the lower class. but thats ok, conflict makes good scifi.

i always figured westeros was on a dyson sphere around a very unstable star (perhaps on the verge of going nova). hence the curve of the intro map and the we all live in the eye of a giant myth.

if there are any whining or hissing sounds comming from the psu, then you might have some dieing caps in there. if it were me id replace them. but this is one of those high voltage jobs that requires someone who knows what they are doing. normally people just get a new one. you also just cant use a multimeter here. you need to test things under load since voltage will change as you draw more current from the rails. voltages may be fine when there is nothing drawing current, as soon as you try to pull an amp or two, voltage drops out of spec. there are dummy load boards out there for this kind of thing. but again not for electronics noobs.

its never really hurt performance all that much for me. ive done this on single drives, ssd drives, and multiple drive/ssd/both configurations. it gives me piece of mind that the os wont toast my files, or that i wont when messing with the system. it also makes things easy to backup, you just copy the whole data partition with the self booting partition imaging tool of your choice (which is often faster than copying the files under windows). i dont like how the user folder is a dumping ground for files that i neither created nor want to keep. so im very selective of what gets junctioned over. i avoid the user folder like the plague when saving important files. current config is two ssds, a larger 500gig for data (one big partition), 256gig for os (default partitioning for os). when i just ran the 500gb i had a 150 gig partition for the os, and the rest was set up for data. i probibly shouldn't have brought it up. its just something thats worked for me a couple times, it is kind of a stupid way to recover data. especially now when you can get a 64gig thumbdrive for $12. i used to be a system builder so i knew the windows 9x/2k/xp installers inside and out. i have less experience with newer versions of windows, but its really all the same, where you want it, what settings you want, etc. when your only tool is a hammer every problem looks like a nail. (actually its a really good way to get people to leave me alone about fixing their mundane computer problems).

my only requirement from a filesystem is that it doesn't eat my files. ntfs has never eaten a file of mine and thats why i still use it. i have linux installs in my room that use a myriad of file systems, but ive not use them enough to judge how good they are at not eating files. if it aint broke dont fix it.

i dont even own a microwave, it ruins the food.

its certainly something to be really careful about. but its a method that saved the day for me a couple of times in lieu of appropriate backup media. where you have one computer with one drive and everything is on one partition, your os is dead, and you dont own a flash drive big enough to back everything up. some versions of windows will install to existing partitions without formatting them, but it is neccisary to clear any directories that it expects to use, such as windows, program files, etc. its very easy to inadvertently delete the users folder, so only use this as a last resort. if you can backup, do so, and just do a clean os install.

actually if you got a boot disk of any kind you should be able to go in and delete everything but the users folder, then instal windows to that drive without formatting.

i usually do two partitions on single drive systems just for this very situation. i keep about 150gb for the os partition(s), and everything else is for data. should the os ever go kaput, you can format the os partition(s) and install a new os there without loosing data. the os doesnt like it when you do this so you need to set up junction points so that your data appears to be were the os wants it, while its on another partition entirely. on a working system just use mklink from the command prompt to create junction points. i think the syntax is: mklink /j "linkpath" "targetpath" linkpath is the directory where the link is created, for example "c:\Users\username\Documents\" (use quotes if the path has spaces) targetpath is where the data actually is stored, for example "d:\documents\" (use quotes if the path has spaces) so mklink /j "c:\Users\username\Documents\" "d:\documents\" windows will think "c:\Users\username\Documents\" and all its files and sub directories are on the drive where the link is created, however it is actually in "d:\documents\". any changes you (or the system) make to the files in "c:\Users\username\Documents\" will appear in "d:\documents\" and vise versa. if you format the c drive however, it will only destroy the junction point and not the files on the other drive. you need to plan for this when setting up a system, have 2 partitions minimum, and if you have a bunch of junction points it helps to stick all the commands to make them in a batch file to recreate them whenever your os decides to start being broke. in your case i think your best bet is to set up a flash drive as a live linux distro so you can recover your data, then restore it after you get your system up and running with what ever os you install (this would be a good time to partition your dive). there are a number of lightweight linux distros you can stick on a flash drive. i usually just use the ubuntu instal iso copied to a flash drive. but there are other distros specifically for running off of flash drives, which frees up space for backups.

i wouldn't mind having a multiple resource, no conversion system. resource locations would be biome based, each biome would have a list of resources which are available there, what their concentration is (this only affects extraction rate, resources are effectively unlimited because you could never extract enough to deplete an object the size of a planet), and what part is needed for extraction at that location. scanning would simply indicate what biome you are landed on or flying over. this might be mapped out, for convenience, but could be determined simply by doing science there. i believe biomes cover land and ocean environments, but atmospheric composition would be defined on a planet by planet basis. not sure how asteroids would be handled, perhaps they would get their own biome maps, or would just have a randomly generated composition as they are spawned. key feature is that mining equipment is resource agnostic. it extracts whatever resource is in the area, provided that the mining equipment functions in that area. where a piece of mining equipment operates is also biome dependent. you might have ice drills for extracting liquids/gasses from icy locations, you might have soil processors for loose regolith, you might have a rock drill for hard surfaces, or simply a pump and hose for wet locations. intakes would also become resource agnostic, producing the local resources based on what atmosphere you are in. extractors might not run for free. it would require a resource to operate (usually electric charge) which would be consumed as the part is extracting. some resources might need another resource during extraction, for example you might need a reducing agent to produce metals, or you might need lf/oxy to produce heat needed to melt ices. but ultimately the thing that comes out is what you were after in the first place with no intermediate resources or waste products to worry about. in the end you have a system where you dont have a bunch of interdependent parts that you need on every isru mission. the minimum parts you need is one, an extractor. of course this means you cant scan and have to get in your rover and drive around to find the needed biome, and you can only mine at biomes your extractor works with. you can send a probe ahead and scan if you want, but its not required. if you want to set up fuel dumps all over the place you might need a fully decked out vessel with 5 kinds of extractor and a mapping scanner. you can bring everything but the kitchen sink so you can go anywhere and keep going, or use the bare minimum for a light flight and accept the limitations of your equipment, so how you play with it is up to you. how to avoid making all this too easy? easy, dont put everything all in one biome. you might need to gather a reagent from one location to extract resources at another. you might find a sea of readily available hydrocarbons, but still need to find an oxidizer source, which may very well not be in any of the current object's biomes. you might need to land in 3 different places to do a complete refueling. if by some chance you find water and can make both lh and oxy, you might not be able to find monopropellant there, or perhaps its locked up in hard rock and you need a more robust piece of hardware or more power to get it out. you might need to fly around lathe for an extended period of time to top off a xenon tank, all while burning precious fuel. there is room here to strike a balance between too hard and too easy.

http://www.bbc.com/news/science-environment-29932609 heres what a noob solar system looks like.

neither political party is the same as it was in the 60s. the main difference is in the days of ye olde space programme, congress was capable of getting things done.

with regards to 4, i tell people if i didnt build it i cant help you. its a blatant lie but it keeps them from exploiting my skills. the best thing you can do with your computer skills is to keep them to yourself. you can trade them for money but that kinda thing makes me feel cheap. "something something wizzards something".

5 and 6. a lot of programmers are uncomfortable working with hardware, and a lot of hardware people cant code. i span this gap. im also capable of building custom hardware and connecting it to my rig without fear of blowing something up. i also wrote my own bytecode language interpreter (though i still haven't finished the assembler so its kind of all hex right now).

broccoli is one of those veggies that is just begging to be sauced. you drench it in sauce and it can hold on to it. this can be a cheese sauce, an herb sauce, whatever. im partial to stir frys myself. i have an asian sauce that works well with broccoli. muricans seem to think cooking veggies means opening a bag of frozen veggies and mindlessly boiling it. its no wonder kids dont eat them.

i was already pretty good at space flight before ksp thanks to orbiter. ksp just made it more fun.

it does depend on language, implementation, your fpu architecture, and your compiler, etc. i was specifically refering to fpu compare though there are other ways of doing the same operation, and they might improve performance in some situations. but then again you can do all kinds of geeky, cool, and sometimes useful things by casting a float to int and operating on it as if it were an integer.

-0 is a quirk of floating point units. its simpler logic wise to use a sign bit rather than a twos complement mantissa. a multiplication for example just needs to xor the bit independently of the other parts of the number. this means negative zero is a thing, but i think if you do something like 'if(anegativezero==apositivezero)' it will be true.

i think you can take a system of point masses and come up with a moi matrix to represent them. i dont remember the math though.

get a gtx750ti with that pc. the card needs very little power and doesnt need a 6 pin connector (it draws all it needs from the bus). i recently got one and was fairly happy with its performance, considering its a middle range card.

if the probability of engine survivability could be high enough, it might be worth it.

i wonder if you could lithobreak liquid engines and boosters by using the tankage as a massive crumple zone to minimize the damage to the engines. it would require a drogue or something to ensure the thing lands nose first and at a survivable velocity.

i generally dont like these kinds of threads because its wide open for debate. the soviets had us beat early on but messed up the end game with their n1 and left it wide open for apollo. we have been able to gather much data about the solar system and the universe with our robotic missions. but we have utterly failed at manned flight by using roscosmos as a taxi service. all space agencies have had their successes and failures and who is best, second best, etc is very subjective. when it comes right down to it the space race was about proving our abilitys to nuke our enemies, which both the usa and russia pulled off. the real winner is everyone because mad pretty much ensured we didnt have a nuclear war and let us use our space tech for more productive purposes. you win one internet.

if you go with generation old intel (ivy bridge) you might save some cash and get decent performance out of it. you might also wait till after intel releases broadwell (which should happen this quarter or the next) and get a haswell machine on sale (broadwell is just a die shrink anyway). just sit on your money and wait for a sale.