Slashdot Mirror


User: OldOOCoboler

OldOOCoboler's activity in the archive.

Stories
0
Comments
9
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 9

  1. Re:explanation about the condition of the grid on In Oregon, Wind Power Surges Disrupting Grid · · Score: 1

    "...needing to sell..." - What obligates Washington to sell excess capacity? Is there a federal law in play? Or has the Washington legistlature voted to sell it? Or is it privately owned dams?

  2. Re:Carbon Footprint? on How Sperm Whales Offset Their Carbon Footprint · · Score: 3, Insightful

    Lobiusmoop said "directly or indirectly". Cattle in feedlots eat corn grown with fertilizers made from previously sequestered oil. If you use oil or coal that took millions of years to sequester then you're not neutral. Whale's don't add any previously sequestered carbon to the biosphere (unless they drink straight from the BP wellhead).

  3. Re:China to Europe on China To Connect Its High-Speed Rail To Europe · · Score: 1

    How many people use a rail line from one terminus to the other? I've taken Amtrak hundreds of times, but the absolute longest journey was D.C. to New Haven in a snowstorm when the airports were closed. The rest were Boston to New Haven, New Haven to Philly, etc. This project puts China at the center of a network and makes other points on the network both more important and more dependent on China.

  4. Re: Global Warming Potential (GWP) on The Arctic Is Leaking Methane · · Score: 1

    IANAAS (atmospheric scientist) - I waste way too much time puzzling over this stuff. It's probably covered in atmostpheric science 101. I answered because I remembered different numbers than yours; I had to go search for that site. I agree about the bad name thing - too much simplification without enough surrounding explanations. Know any good (non-political) books?

  5. Re: Global Warming Potential (GWP) on The Arctic Is Leaking Methane · · Score: 1

    Careful - there is disagreement on the numbers. Methane contributes to the production of ozone in the tropsphere. Methane (with a half-life of 8.4 years) is 1/4096th of its original concentration after 100 years. The relatively high GWP after 100 years includes the secondary effects and we don't yet know how those will grow (or shrink). Check out http://unfccc.int/ghg_data/items/3825.php

  6. The kill switch breakpoint on DARPA Aims for Synthetic Life With a Kill Switch · · Score: 1

    From what I've read no computer can model DNA behavior faster than DNA itself can manipulate a supply of proteins. The kill switch might be there so that they can "run" massively parallel variations and use the kill switch as a sort of debug breakpoint. But IANAMB (molecular biologist).

  7. So the BIOS will do multitasking, security, etc? on The Future Might Be BIOS and Browsers · · Score: 1

    OK, maybe OS's are bloated, but lets not get bulemic trying to go thin client.

  8. Re:I hope they're removed, on Barr Sues Over McCain's, Obama's Presence on Texas Ballot · · Score: 1

    Look, it might not be in the constitution, but there was this little dust-up called the Civil War that decided the line between states and Federal jurisdiction. If the states can override federal marijuana laws they can also override slaverly laws. So lets not throw away federalization, lets fix it.

    BTW - Who says a write-in needs to be 70 days before? Isn't the whole point of a write-in something done ON election day?

  9. COBOL is hard-pressed to compete on Why COBOL Could Come Back · · Score: 1

    Yes the technologies have become more complicated, but using COBOL for new development won't change that. Just because standard procedural COBOL can't (easily) particpate in an SOA enterprise doesn't mean we don't WANT the application to be part of the SOA. So we usually wrap the COBOL in Java, or convert it to a COBOL object (yes, there are such things). You could leave the app out of the SOA and do a lot of ugly EDI (or more likely swivel-chair interfacing), but that only means you've made thing simpler by making them less useful.

    So leave procedural COBOL exactly where it is today - the legacy that we have to keep running but that we also should be working to replace.

    Now OO COBOL is another matter. If building new functionality (including writing new programs) in a large legacy COBOL system then IMHO using OO Cobol can make sense. If you want to use OO technology and you are bound to a legacy system then OO COBOL is easy, whereas calling a Java object can be a PITA (the native data types just don't match up, Exceptions work differently, even simple objects like String can't be passed, COBOL is not strongly-typed, garbage collection works differently, etc etc. The list goes on and on).