WiseWeasel is VERY expert about Maemo, and it's competitors. (I bow to the Wise one.) But IMO, Nokia's current product (N900) and it's short-term pipeline have a big hardware issue effecting the UI, and putting Qt into the Maemo software "stack" entices software developers into making the world of Nokia Apps a lot less consistent, rather than more consistent.
The Nokia hardware platform problem is multitouch. Resistive touchscreens are much less expensive to build, and multitouch is possible on such technology- but like the early days of LCD TV trying to compete with Plasma, the behavior is manifestly worse. Just like the old LCDs did a terrible job with motion, the current resistive screens do a really terrible job of recognizing a user's touch. Even a single-touch action gets mishandled or unrecognized from time to time. It's a hardware problem, and IMO Nokia's premier product is behind the competition in touchscreen. Resistive screens may catch up Capacitative screens in the future, or Nokia might switch in a future product... but right now, even the N900 is frustrating to use, and this is the main reason why.
The software problem is upcoming, not yet even present in Maemo v5. As you all know, Nokia bought Trolltech, the makers of the 'Qt' graphics toolkit. Nearly all of 'Qt' is now open source code, LGPL. (The switch to this particular license, granting un-revocable and very liberal terms others to use as they please, was a Nokia choice, subsequent to the purchase.) Software developers were, and are, thrilled by the possibility of "write once, run anywhere" graphical applications. And I think that this was an important reason for Nokia's acquisition, even if the main reason had been a defensive purchase of TrollTech's toolkit 'intellectual property' before it got bought by someone else and patented/re-licensed under nasty terms by someone else.I'll guess that both considerations were considered to be extremely important.
But Maemo 6 inherits two GUI tookits: It's own, which is fairly complete but totally non-portable; and QT v4, which is beautifully designed, but not yet sufficiently complete, not even for computer applications. (You need to provide tons of widgets yourself, either by writing them raw or using another toolkit to "help out" with additional elements. KDE and the Maemo 6 Graphics Library can theoretically utilize qt elements as "lower layer" items, but it's hard to do it all from inside Qt-- it just isn't there yet.) KDE uses Qt very heavily, as an underlying "layer". Maemo use of Qt brand new, and IMO you're better off using the legacy elements. Instead of instantiating a Qt window, with it's controls, you're going to want to create a Maemo window, in the "old" way. After you've committed yourself to which kind of App Window it is, all the child controls and methods are totally different source code. So, if you want to create an App for both desktop KDE and Symbian phones, your code grows into a huge jungle of #ifdef MAEMO.... #elif KDE.... #endif macros, nearly as thick and nasty as using common source code for Linux/X11 and win32 implementations of your program. Development and maintenance of such stuff isn't easy or fun, so SOME people will try to code using just QT-- and I'm afraid that their Apps might end up looking a lot different. Two UI's for the end user, in different programs on the same device, would IMO be a disaster for Nokia.
I don't think the problem comes from departmental infighting, I think that it's more a question of not-enough-time. It takes time, LOTS of time, to unify those toolkits, and everyone who already wrote something (the writers of KDE4; the writers of KDE Apps; all the writers of Maemo Apps) depends on the groups of developers (i.e., the writers of Qt and the writers of the Maemo graphics tookit) not to break their existing GUI code. The time and money simply wasn't there for such an enormous project. I won't be surprised if it isn't there for Mameo-7, or Maemo-8, either. Be
.... has a long history of cooperation with MS in attempting to hurt Google, and that's why they have always partnered up with Yahoo! I can't say whether the few remaining Telco monopolies cooperated with India independently of MS/Bing and asked Yahoo to do this, or whether Yahoo caved on its own. But I feel that India probably contacted Yahoo directly, and it was Yahoo's choice (reaching the same conclusion as Bing, under the same circumstances, but without any "collusion").
As for Yahoo being absorbed into Bing, or visa-versa-- Yahoo certainly IS sorry that they held out for too much money in rejecting the previous buy-out offers. IMO, though, it's now unlikely that Steve Ballmer will be an efficient "businessman" about buying them now: Yahoo's rebuff of the previous offers has made them an enemy of the "I WANT TO KILL XYZ!" variety, he's into another chair-throwing temper tantrum and wants to grind them up into a pile of raw sausage filing as revenge. It might be smarter business to buy Yahoo and it's customer base before destroying it, but Ballmer will spend energy and money to choke off their air supply first. He's got vast amounts of cash to pour into Bing and subsidize it's paid advertisers, or subsidize a cheaper "store" system for online small business. Yahoo tries to do whatever MS wants, and they were partners before the takeover battle.... but he can kill them, and I think that he really wants to.
The problem for MS killing Yahoo! by competition isn't the web search, and it isn't the support of online stores. It's the email client base. Even among clueless casual computer users, the nightmares of "HotMail" (together with it's "Microsoft Passport" security fiascoes) have taught them to never, ever become a client of a Microsoft-hosted email service again. If ATT/Yahoo mail gets killed, GMail wins.
Dennis seems to have spoken of the "value" of the software so often that he has succumbed to his own (and Warren's) hype. His talk and actions seem to show something of crazed fantasy about "his" design and implementation.
So from a taxpayer's perspective, and the perspective of anyone who has been abused by the "truthiness" of that software in production, they ALL suck, and Dennis, the "creator", sucks worse. But I feel that Warren and Jim are "worse"- because (IMO) they're not showing signs of overwhelming mental illness. They're just greedy, lying. cheating, criminal bstrds.
At that time, Jim Gibbons was a Congressman (not yet the "worst governor in America"). He and Warren Tripp have a long and IMO unsavory relationship, going WAY back. Before Tripp and Montgomery started fighting about who "owned the code", there were large campaign contributions. And possibly worse: somehow, Warren Tripp and his wife ended up on the same Caribbean Cruise as Jim and Dawn Gibbons (who seemed to have brought a large sum of gambling money with them, wink-wink).) An Email from Tripp's wife to her husband on March 22, a few days before, definitely said, "Please don't forget to bring the money you promised Jim and Dawn". And Warren Tripp responded just a few minutes later, with ""Don't you ever send this kind of message to me! Erase this message from your computer right now!"
The emails are not in dispute. But in Nevada, and even at the Federal level, funny things happen with investigations of powerful people. Jim Gibbons later claimed that this was were probably references to campaign contributions, which he said were lawful and reported in accordance with campaign finance laws. Everyone accepts the later claim that these emails "...were probably references to campaign contributions, which he said were lawful and reported in accordance with campaign finance laws." [quotation from the Wall Street Journal]. Right, Warren Tripp went FRANTIC about lawful and proper campaign contributions, which were to be handed over within International Waters on a cruise ship?
Anyway, Warren was obviously a computer expert, knowing that "Erase this message from your computer right now!" would destroy all references and copies of the email. (guffaw.)
"Trojan.PWS.ChromeInject.B" is definitely only effective in Windows, because it installs and executes these files:
"%ProgramFiles%\Mozilla Firefox\plugins\npbasic.dll"
"%ProgramFiles%\Mozilla Firefox\chrome\chrome\content\browser.js"
browser.js calls the The dll file, which can't run in Linux, etc. unless you're running a WINDOZE Firefox via crossover (which would be insanely stupid). Also, since it's installed into the program directory (rather than the user's profile), VISTA will almost certainly make you click for "administrator confirmation" before writing the files. (I don't know for sure, because I don't have VISTA.)
- - - - -
When I enter the URL for http://www.bitdefender.com/VIRUS-1000451-en--Trojan.PWS.ChromeInject.A.html#, the page content is identical the version for "Trojan.PWS.CHromeInject.B" (even the given name is "Trojan.PWS.ChromeInject.B", they even over-wrote the ChromeInject.A page by accident or, ChromeInject.A isn't spreading in the wild AND has nearly identical characteristcs, perhaps differing only in file sizes.)
BitDefender provides the following list of banks their page for this version, http://www.bitdefender.com/VIRUS-1000451-en--Trojan.PWS.ChromeInject.B.html:
It filters the URLs within the Mozilla Firefox browser and whenever encounter the following addresses opened in the Firefox browser it captures the login credentials.
akbank.com
caixasabadell.net
credem.it
areasegura.banif.es
banca.cajaen.es
openbank.es
poste.it
banesto.es
carnet.cajarioja.es
gruposantander.es
intelvia.cajamurcia.es
net.kutxa.net
bancopastor.es
bancamarch.es
caixamanlleu.es
elmonte.es
ibercajadirecto.com
bancopopular.es
bancogallego.es
bancajaproximaempresas.com
caixa*.es
caja*.es
ccm.es
bancoherrero.com
bankoa.es
bbvanetoffice.com
bgnetplus.com
bv-i.bancodevalencia.es
clavenet.net
fibancmediolanum.es
sabadellatlantico.com
arquia.es
banking.*.de
westpac.com.au
adelaidebank.com.au
pncs.com.au
nationet.com
online.hbs.net.au
www.qccu.com.au
boq.com.au
banksa.com
anz.com
suncorpmetway.com.au
quiubi.it
cariparma.it
bancaintesa.it
popso.it
fmbcc.bcc.it
secservizi.it
bancamediolanum.it
csebanking.it
fineco.it
gbw2.it
gruppocarige.it
in-biz.it
isideonline.it
iwbank.it
bancaeuro.it
bancagenerali.it
bcp.it
unibanking.it
uno-e.com
unipolbanca.it
carifvg.com
cariparo.it
carisbo.it
islamic-bank.com
banking.first-direct.com
natwestibanking.com
itibank.co.uk
co-operativebank.co.uk
lloydstsb.co.uk
mybankoffshore.alil.co.im
abbeynational.co.uk
mybusinessbank.co.uk
barclays.com
online.co.uk
my.if.com
anbusiness.com
hsbc.co
anbusiness.com
co-operativebankonline.co.uk
halifax-online.co.uk
ibank.cahoot.com
smile.co.uk
caterallenonline.co.uk
tdcanadatrust.com
schwab.com
wachovia.com
bankofamerica
kfhonline.com
wamu.com
wellsfargo.com
procreditbank.bg
chase.com
53.com
citizensbankonline.com
e-gold.com
paypal.com
usbank.com
suntrust.com
banquepopulaire.fr
onlinebanking.nationalcity.com
I'm running a test build with 4 additional fixes not yet applied to the trunk. (Updated almost every night.) My score, 97, hasn't changed since I clipped the page as a picture here: http://forum.mandriva.com/viewtopic.php?t=95531
However, there IS still timing trouble (laggyness) exactly as you describe. Here's the details of my current report, Athlon 3500+ with integrated NVida 6150 (buried alive by Compiz Fusion with tons of glitz: rotating cube, two kinds of mouse-based window selectors, wobbly windows, etc.). Your box seems to be nearly twice as fast as my old one, running Linux.
Failed 3 tests.
Test 26 passed, but took 306ms (less than 30fps)
Test 39 passed, but took 36ms (less than 30fps)
Test 40 passed, but took 69ms (less than 30fps)
Test 46 passed, but took 57ms (less than 30fps)
Test 65 passed, but took 124ms (less than 30fps)
Test 69 passed, but took 3 attempts (less than perfect).
Test 71 passed, but took 183ms (less than 30fps)
Test 77 failed: expected '4776' but got '6980' - getComputedTextLength failed.
Test 78 failed: expected '90' but got '0' - getRotationOfChar(0) failed.
Test 79 failed: expected '34' but got '33' - SVGSVGTextElement.getNumberOfChars() incorrect
Total elapsed time: 4.85s
I'll SWAG that test 77 is due to either unimplemented downloadable text (leading to selection of an alternate font already present on my box), or differences in Linux versus Windows font sizings of a font which is already available. Test 78 is clearly just not implemented at all, and Test 79 seems to be just a "minor" rounding error in something which is already implemented.
My build now includes a bunch of further Tracemonkey JIT fixes and enhancements which landed on the tree AFTER the beta branch was cut. I ran acid3 twice, and the second run was a bit faster than the first-- second results show above. But I've got oodles of other tabs open at the same time, and didn't bother to check out how much they hurt my results.
While printing on Linux is absolute garbage; they haven't done a new Thunderbird version in YEARS; they still haven't released the Sunbird Calendar; and they've still got IMPORTANT defects which are years and years old. Opera and Konqueror do a better job with "IE-encoded" web pages than Firefox does.
I remember when Mozilla seemed to concentrate on their customers needs. Now, they seem to be behaving more and more as a subsidiary of Google. (They seem to think that you don't need a reliable, usable desktop email client anymore-- because THEY'VE decided that you're gonna be happy using GMail!) And now, maybe because Google needs IE to work better, Mozilla pours time and effort and money into fixing IE.
The corporation seems focused on making big deals, the old software which I loved since Mozilla 0.6 seems to be getting treated as "legacy crap". Hey, business people, you don't gains market share by improving your competitor! What ARE they thinking?
Yeah, they fixed some little bugs for Windows and Mac. But on Linux, the "print..." dialog doesn't even pretend to give you the opportunity to print "selection".
Your only choices are "all", or "range of pages". A checkbox exists for "current page only", but it can't be selected. Linux remains a 3rd class platform, as far as Mozilla.org is concerned.:(
Opera does a great job with this (so it's not within CUPS or Laserjet support, it's entirely Mozilla's fault.)
BTW, I'm not yet running 3.1 nightlies: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1 - Build ID: 2008070206
if it's just the appearance changes (i.e., SSL sites not shown in yellow, big layout) you can use "old location bar", but you might also look at changing your theme: "classic compact" looks pretty much as Firefox 2 did, and it saves a lot of vertical space too. (Nice on laptops.) I use it, and install it on all my customer's machines.
Instructions below, to prevent pop-up of matches, are excellent.
The update for FF2 was pushed out a day before the FF3 update (on Tuesday morning, versus Wednesday afternoon). If you aren't using 2.0.0.16, you're prone to the same attack.
To be absolutely safe, back up your profile directory from OUTSIDE Firefox and 'turn on' only a few at a time. If it breaks so badly that Firefox won't even start, just restore the proofile directory from one of your "backup" copies.
BTW, there's some out-of-date comments here, NTT does not force you to "make ALL compatible" at the same time anymore.
She's still living at the Governor's Mansion in Carson City, he only visits to conduct "official functions".
Maybe he's in a funk about that, and lashing out at widows and dead people helps him to feel better. (And yes, his emotional maturity level OFTEN appears to be on par a typical two-year-old.)
Cripes, the man held a permit (now surrendered, it was fraudulent) for NINE concealed handguns. One, Two, maybe Three, I can understand that. Maybe even Five. But Nine concealed weapons ???
OTOH, this "Public Servant's" private residence is far larger and more luxurious than the Governor's Mansion. I live in Nevada (Reno), and DW commutes to Carson City.
So now the Gov. wants to F. with dead people, and their widows. Lots of people call Nevada the "F.U." State, this sort of thing ain't new around here.
I agree. In the past, (as well as right now), ATI-written GPU "Catalyst" drivers for Linux have usually been bug-riddled, feature-poor, and a problem waiting to happen. And so, the vast majority of Linux "heavyweights" have been building and buying computers with NVidia. (Both discrete and integrated.)
BUT, AMD/ATI has recently offered the actual specifications, under FREE license terms, for Linux folks to write driver code under the GPL. (ATI personnel can also take part, as long as they offer their code under GPL terms.) This could be huge. And unlike Apple systems, many Linux boxes are built as low-end machines, naturally targeting integrated graphics anyway.
My own PC cost less than $250, and adding a graphics card + passive cooling was a significant cost. It was, of course, an NVidia card... and I expect that ATI graphics will really become viable soon, due to their having released the full specifications required to write FLOSS drivers.
ISO is broken. The ISO needed to look to their own reputation during this horrific, scandalous MESS. Shame on the ISO for not protecting their own "voting process" from P-Member ballot stuffing, NSB chairperson abuses, and even allowing the "fast-track" process for such an enormous and controversial "standard" in the first place. It should be necessary for EU administrators and legal action in the various voting countries to fix this, ISO should have fixed it themselves!
The winds were NOT very high this morning....
on
Steve Fossett Missing
·
· Score: 4, Informative
Although the upcoming cold front is expected to create high winds this afternoon, conditions this morning were quite good. I hope that he was able to ditch in a survivable place, and pray for his safety.
You CAN still use Tab Mix Plus (3.5 "release candidate" builds from tmp.garyr.net) to make all of the tab UI and operational adjustments which you want.
OT: A previous post asked about adblock+. Version 0.7.1.2 is FF2 compatible, doesn't even need "Nightly Tester Tools" to "override" version checking.
And of course, all the "flash" whiners should be using flashblock. 1.5.1 works fine, although IIRC it does need the version override via "Mr. Tech Local Install" extension.
GreaseMonkey, Platypus, and RIP work great, I'd never use a FF without 'em.
I'm actually disappointed by the relative lack of new features in FF2. They mostly just incorporated (and internationalized) stuff previously available in Extensions (spell check, tab mix plus). But there is a good stack of bug fixes, it is a worthwhile upgrade.
Before anyone whines about extensions which aren't available yet: This is still only a RELEASE CANDIDATE, jeez, give the extension developers a few weeks to get their stuff updated. If you don't like using it in pre-release state, DON'T INSTALL IT !!!
The contract doesn't merely say that "a large part" of the royalties go to Novell (95%)... it says that SCO must deliver ONE HUNDRED PERCENT of Royalties to Novell, and then Novell gives 5% commission BACK.
Nice post, nice reference! But each of these is a really bad example of a "decommissioned nuclear power plant":
Fort St. Vrain: An HTGR reactor, technically way different from typical power stations now in operation. It only ran for 13 years, almost NEVER at anywhere near it's rated output, because it kept having breakdowns and operational failures. (The short lifespan, and running at extremely low power, prevented the building materials from being irradiated in the way that the building of a "successful" power station would be.) The record of this reactor was a safety nightmare, and it was a financial nightmare for it's Colorado customers. Also, the "cost" of dealing with the high-level waste was hidden via sending it to the National Lab facility in ID (i.e., TAXPAYER subsidy). Here's a reference for some history: http://fsv.homestead.com/FSVHistory.html Note that although they claim to be fully decommissioned, the building is still sitting there, apparently not in use for anything which would expose people for exgtended periods.
Shoreham: Gadzooks, want to you label this as a success story ??? It cost $6 Billion to build, it completed it's 5% power test successfully, and then it was promptly shut down forever (after less than 1 month). I agree that a nuclear power plant is easy to decommission, if you never actually use it to generate any electric power! But we're hopefully talking about power plants which actually generate electricity, right?
CTVR Yes, the NRC fact sheet lists it as a decommissioned reactor... but a quick Google shows nothing about this reactor, except a copies of the NRC list. I don't think that this was a Civilian Electrical power station. Possibly, NRC and Military came up with some backroom "let's mark it cleaned up" deal to hide a mess. If you can find a URL for a public utility which operated it, please advise!
Pathfinder only ran for 13 months http://www.nrc.gov/info-finder/decommissioning/com plex/pathfinder.html, and was characterized by the GAO as "a small demonstration plant" (although it's actually listed as way larger than the CVTR toy, see GAO/RCED-99-75 'Nuclear Regulation'). Small output and barely a year of operating time == extremely simple and cheap to clean up. This is another "example" which hardly generated any electrical power at all.
Douglas Point Per this PDF dated October 2004, http://www.nea.fr/html/rwm/wpdd/canada.pdf "No commercial nuclear power reactors are undergoing active decommissioning in Canada. Three prototype power reactors (NPD, Douglas Point, and Gentilly-1) have been partially decommissioned and put into storage with surveillance mode pending final decommissioning at an undetermined future date." Looks to me like it wasn't a commercial nuclear power station, (just an AECL prototype), and it hasn't yet been decommissioned..
Still... If you've got other candidates which (a) weren't "toy-sized"; and (b) ran for at least 20 years, let's discuss them!
Elk River was a tiny 22 Megawatt reactor, which was only running for 4 years. It is best characterized as a "research" reactor. (Hint: Google the exact phrase "Elk River Research"... it was research, not production.
Real-world powerstations are typically up to 50x as powerful, and (more important) they are typically run for about 8 times as long (i.e., a lifespan of 30-40 years). The scale and scope of the decommission problem is DIRECTLY related to how long the installation was running... that's what determines the radioactivity of the structural materials in the reactor building. And a production reactor also has an enormous volume of radioactive material to deal with-- according to CCNR http://www.ccnr.org/me_worry_2.html, typically about 7000 cubic meters.
They state that Elk River cost only $6 million to build (a pipsqueek; a typical production nuclear site costs $50M+). But they they list a cost of $57 million to dismantle it! This is a success story ???
Another "success story", Shippingport, cost "only $91 million". But that number is fraudulent, because (a) the reactor vessel was shipped intact to Hanford WA, where nearly all of the dismantling work was done for free (i.e., on the TAXPAYERS' dime); (b) the vessel and other disposed materials were disposed in Federal WA and ID facilities at fees far below those of commercial sites like Barnwell; (c) only the "nuclear parts" were dismantled, not the "conventional parts" (they didn't do the whole job!); and (d) like Elk River, Shippingport was a pipsqueek, only 72 MegaWatts.
The only other decommissioned and dismantled reactor in USA history is Shoreham. (I exclude the tiny and irrelevant Sodium-Experimental at Santa Susana.) Shoreham was 100% easy, because it was in 'production' for less than a month: hardly any of the non-nuclear parts had time to develop any radiation at all.
All other USA reactors, AFAIK, are entombed, SAFSTOR, or DECON in progress. Basically, we're waiting several decades for the radiation to "work its way downwards", and inflict the costs on our Grandchildren and Great-Grandchildren.
However, it ISmy opinion that this is a great streategy for all of the Nukes which are already built and running (or built, done running, and shut down). Letting all of this hot stuff sit in place for a while, to cool down, is far better than schemes such as packing it while still really hot into "permanent disposal" containers at Yucca Mountain... containers which we might find horribly difficult to dismantle and re-entomb if/when they fail. (Kinda like the Chernyobl concrete entombment failing.)
- - - -
I'd mod gonefishing up... he had a real point of discussion. Dave's post is not "insightful", it's just nasty and thoughtless.
Dave, you can't PROVE a "there exist none" generalization such as I made, you DISPROVE it by counterexample (as gonefishing does). That's how way logic works. Heard of Aristotle?
5000 years of 'civilization': First, it's not one civilization, but many separate civilizations. Historically, none have lasted more than a few hundred years. And yet, you ask me to provide "a reason why such a feat would not be possible". Again, you use childish sophistry... because I won't make a guarantee that it's 100% impossible, you snear that my scenario (failure only 80% likely? 95% likely?) doesn't matter. How many 'lost' languages don't we understand? But for a few dedicated monks in Ireland, we'd be without lots of significant writings from Roman times. And yet, you aren't worried that our maps and lists of where not to go won't be lost? Even in 10,000 years?
My '60 years experience' point is this: In the history of mankind, no weapon of war has preiously been invented and noteventually used. We have a 60-year old uneasy truce in place on nukes.... but the nuclear power station fuel rod business uses the same technology as the nuclear warhead materials busines
Here's a delicious quote... not too long, I think, to show in full. From the 2006 edge.org question, "what is your dangerous idea", answer from Jeremy Bernstein:
"The most dangerous idea I have come across recently is the idea that we understand plutonium. Plutonium is the most complex element in the periodic table. It has six different crystal phases between room temperature and its melting point. It can catch fire spontaneously in the presence of water vapor and if you inhale minuscule amounts you will die of lung cancer. It is the principle element in the "pits" that are the explosive cores of nuclear weapons. In these pits it is alloyed with gallium. No one knows why this works and no one can be sure how stable this alloy is. These pits, in the thousands, are now decades old. What is dangerous is the idea that they have retained their integrity and can be safely stored into the indefinite future."
No nuclear power station has ever been fully decommissioned successfully. All of human civilization has a history of about 5000 years, and yet we imagine that we can successfully manage this incredibly deadly poison for thousands of years into the future. And, on the basis of barely 60 years, some so-called experts express "confidence" that there won't be enormous disasters, both accidental and intentional, in the future.
Instead of huge taxpayer subsidies to make more Nukes, and continuing to never really clean them up afterwards, why not spend some research and pricing support $$$ to get solar panels as a standard roofing material on people's houses? (Or, at least stop building and re-roofing houses with black asphalt shingles in hot geographical regions.... an incredibly wasteful practice.)
(Pure FUD... are you proudly clueless, or are you 0wn3d by criminal monopolists? If you're only a TROLL, please get off the computer and go eat some donuts.)
First of all, Mozilla.org has CUT THE BRANCH Alpha-1, but the test builds are not yet good enough to designate the result as the 'Alpha1' RELEASE.
The extension "Nightly Tester Tools" allows you to ignore the build IDs in the.xpi file, 'forcing' compatibility. They'll at least load once... they might, in some circumstances, immediately disable themselves. Or, they might break completely.
When it happens, the 'Alpha' designation means that no more major new features will be allowed from that point onwards. Also, it should be at least somewhat useable. It DEFINITELY doesn't mean that it's ready 'informal' use... you need to make a COMPLETE backup of your profile before installing one of these nightly builds.
The biggest new feature is 'places', a gigantic re-write of 'bookmarks' to include RSS and some new features. IMHO, it's badly broken. I've used several nightlys in recent weeks, and disasterous problems, (already known, but still to be fixed) have forced me back to a mid-February build.
Be sure to check the mozillazine forum firefox-builds (at http://forums.mozillazine.org/viewforum.php?f=23 , NOT the firefox-support forum) for the most recent "The Official Win32 2006mmdd Build is out" thread. Then, look at the unfixed bugs in the list. And ***IMPORTANT*** use the last link in the bugs list to look at the separate list for 'places'.
As I write this, the Places list includes 216 bugs. One is a 'BLOCKER', another is 'CRITICAL' , and 15 are 'MAJOR'. I wouldn't use the current nightly on my box. (With my usage, the 'Critical' is more important than the 'blocker'). But, in any case, I'd recommend that you wait until there aren't any 'CRITICAL' bugs which could affect you before downloading any nightly.
*IF* you download and use a nightly, I say that you are MORALLY OBLIGATED to check for duplicates on any bugs you find. Right now, that means you've got 194 'normal', 'blocker', and 'critical' bugs to cehck against... just for places.
for everyone's sake, WAIT FOR A HALF-DECENT BUILD!
Slashdot Mirror
The Nokia hardware platform problem is multitouch. Resistive touchscreens are much less expensive to build, and multitouch is possible on such technology- but like the early days of LCD TV trying to compete with Plasma, the behavior is manifestly worse. Just like the old LCDs did a terrible job with motion, the current resistive screens do a really terrible job of recognizing a user's touch. Even a single-touch action gets mishandled or unrecognized from time to time. It's a hardware problem, and IMO Nokia's premier product is behind the competition in touchscreen. Resistive screens may catch up Capacitative screens in the future, or Nokia might switch in a future product... but right now, even the N900 is frustrating to use, and this is the main reason why.
The software problem is upcoming, not yet even present in Maemo v5. As you all know, Nokia bought Trolltech, the makers of the 'Qt' graphics toolkit. Nearly all of 'Qt' is now open source code, LGPL. (The switch to this particular license, granting un-revocable and very liberal terms others to use as they please, was a Nokia choice, subsequent to the purchase.) Software developers were, and are, thrilled by the possibility of "write once, run anywhere" graphical applications. And I think that this was an important reason for Nokia's acquisition, even if the main reason had been a defensive purchase of TrollTech's toolkit 'intellectual property' before it got bought by someone else and patented/re-licensed under nasty terms by someone else.I'll guess that both considerations were considered to be extremely important.
But Maemo 6 inherits two GUI tookits: It's own, which is fairly complete but totally non-portable; and QT v4, which is beautifully designed, but not yet sufficiently complete, not even for computer applications. (You need to provide tons of widgets yourself, either by writing them raw or using another toolkit to "help out" with additional elements. KDE and the Maemo 6 Graphics Library can theoretically utilize qt elements as "lower layer" items, but it's hard to do it all from inside Qt-- it just isn't there yet.) KDE uses Qt very heavily, as an underlying "layer". Maemo use of Qt brand new, and IMO you're better off using the legacy elements. Instead of instantiating a Qt window, with it's controls, you're going to want to create a Maemo window, in the "old" way. After you've committed yourself to which kind of App Window it is, all the child controls and methods are totally different source code. So, if you want to create an App for both desktop KDE and Symbian phones, your code grows into a huge jungle of #ifdef MAEMO .... #elif KDE .... #endif macros, nearly as thick and nasty as using common source code for Linux/X11 and win32 implementations of your program. Development and maintenance of such stuff isn't easy or fun, so SOME people will try to code using just QT-- and I'm afraid that their Apps might end up looking a lot different. Two UI's for the end user, in different programs on the same device, would IMO be a disaster for Nokia.
I don't think the problem comes from departmental infighting, I think that it's more a question of not-enough-time. It takes time, LOTS of time, to unify those toolkits, and everyone who already wrote something (the writers of KDE4; the writers of KDE Apps; all the writers of Maemo Apps) depends on the groups of developers (i.e., the writers of Qt and the writers of the Maemo graphics tookit) not to break their existing GUI code. The time and money simply wasn't there for such an enormous project. I won't be surprised if it isn't there for Mameo-7, or Maemo-8, either. Be
As for Yahoo being absorbed into Bing, or visa-versa-- Yahoo certainly IS sorry that they held out for too much money in rejecting the previous buy-out offers. IMO, though, it's now unlikely that Steve Ballmer will be an efficient "businessman" about buying them now: Yahoo's rebuff of the previous offers has made them an enemy of the "I WANT TO KILL XYZ!" variety, he's into another chair-throwing temper tantrum and wants to grind them up into a pile of raw sausage filing as revenge. It might be smarter business to buy Yahoo and it's customer base before destroying it, but Ballmer will spend energy and money to choke off their air supply first. He's got vast amounts of cash to pour into Bing and subsidize it's paid advertisers, or subsidize a cheaper "store" system for online small business. Yahoo tries to do whatever MS wants, and they were partners before the takeover battle.... but he can kill them, and I think that he really wants to.
The problem for MS killing Yahoo! by competition isn't the web search, and it isn't the support of online stores. It's the email client base. Even among clueless casual computer users, the nightmares of "HotMail" (together with it's "Microsoft Passport" security fiascoes) have taught them to never, ever become a client of a Microsoft-hosted email service again. If ATT/Yahoo mail gets killed, GMail wins.
So from a taxpayer's perspective, and the perspective of anyone who has been abused by the "truthiness" of that software in production, they ALL suck, and Dennis, the "creator", sucks worse. But I feel that Warren and Jim are "worse"- because (IMO) they're not showing signs of overwhelming mental illness. They're just greedy, lying. cheating, criminal bstrds.
The emails are not in dispute. But in Nevada, and even at the Federal level, funny things happen with investigations of powerful people. Jim Gibbons later claimed that this was were probably references to campaign contributions, which he said were lawful and reported in accordance with campaign finance laws. Everyone accepts the later claim that these emails "...were probably references to campaign contributions, which he said were lawful and reported in accordance with campaign finance laws." [quotation from the Wall Street Journal]. Right, Warren Tripp went FRANTIC about lawful and proper campaign contributions, which were to be handed over within International Waters on a cruise ship? Anyway, Warren was obviously a computer expert, knowing that "Erase this message from your computer right now!" would destroy all references and copies of the email. (guffaw.)
sorry about the formatting, I should have used preview! Per above, it definitely is Windows-only.
Just go to the URL, http://www.bitdefender.com/VIRUS-1000451-en--Trojan.PWS.ChromeInject.B.html
"Trojan.PWS.ChromeInject.B" is definitely only effective in Windows, because it installs and executes these files: "%ProgramFiles%\Mozilla Firefox\plugins\npbasic.dll" "%ProgramFiles%\Mozilla Firefox\chrome\chrome\content\browser.js" browser.js calls the The dll file, which can't run in Linux, etc. unless you're running a WINDOZE Firefox via crossover (which would be insanely stupid). Also, since it's installed into the program directory (rather than the user's profile), VISTA will almost certainly make you click for "administrator confirmation" before writing the files. (I don't know for sure, because I don't have VISTA.) - - - - - When I enter the URL for http://www.bitdefender.com/VIRUS-1000451-en--Trojan.PWS.ChromeInject.A.html#, the page content is identical the version for "Trojan.PWS.CHromeInject.B" (even the given name is "Trojan.PWS.ChromeInject.B", they even over-wrote the ChromeInject.A page by accident or, ChromeInject.A isn't spreading in the wild AND has nearly identical characteristcs, perhaps differing only in file sizes.) BitDefender provides the following list of banks their page for this version, http://www.bitdefender.com/VIRUS-1000451-en--Trojan.PWS.ChromeInject.B.html: It filters the URLs within the Mozilla Firefox browser and whenever encounter the following addresses opened in the Firefox browser it captures the login credentials. akbank.com caixasabadell.net credem.it areasegura.banif.es banca.cajaen.es openbank.es poste.it banesto.es carnet.cajarioja.es gruposantander.es intelvia.cajamurcia.es net.kutxa.net bancopastor.es bancamarch.es caixamanlleu.es elmonte.es ibercajadirecto.com bancopopular.es bancogallego.es bancajaproximaempresas.com caixa*.es caja*.es ccm.es bancoherrero.com bankoa.es bbvanetoffice.com bgnetplus.com bv-i.bancodevalencia.es clavenet.net fibancmediolanum.es sabadellatlantico.com arquia.es banking.*.de westpac.com.au adelaidebank.com.au pncs.com.au nationet.com online.hbs.net.au www.qccu.com.au boq.com.au banksa.com anz.com suncorpmetway.com.au quiubi.it cariparma.it bancaintesa.it popso.it fmbcc.bcc.it secservizi.it bancamediolanum.it csebanking.it fineco.it gbw2.it gruppocarige.it in-biz.it isideonline.it iwbank.it bancaeuro.it bancagenerali.it bcp.it unibanking.it uno-e.com unipolbanca.it carifvg.com cariparo.it carisbo.it islamic-bank.com banking.first-direct.com natwestibanking.com itibank.co.uk co-operativebank.co.uk lloydstsb.co.uk mybankoffshore.alil.co.im abbeynational.co.uk mybusinessbank.co.uk barclays.com online.co.uk my.if.com anbusiness.com hsbc.co anbusiness.com co-operativebankonline.co.uk halifax-online.co.uk ibank.cahoot.com smile.co.uk caterallenonline.co.uk tdcanadatrust.com schwab.com wachovia.com bankofamerica kfhonline.com wamu.com wellsfargo.com procreditbank.bg chase.com 53.com citizensbankonline.com e-gold.com paypal.com usbank.com suntrust.com banquepopulaire.fr onlinebanking.nationalcity.com
However, there IS still timing trouble (laggyness) exactly as you describe. Here's the details of my current report, Athlon 3500+ with integrated NVida 6150 (buried alive by Compiz Fusion with tons of glitz: rotating cube, two kinds of mouse-based window selectors, wobbly windows, etc.). Your box seems to be nearly twice as fast as my old one, running Linux.
I'll SWAG that test 77 is due to either unimplemented downloadable text (leading to selection of an alternate font already present on my box), or differences in Linux versus Windows font sizings of a font which is already available. Test 78 is clearly just not implemented at all, and Test 79 seems to be just a "minor" rounding error in something which is already implemented.
My build now includes a bunch of further Tracemonkey JIT fixes and enhancements which landed on the tree AFTER the beta branch was cut. I ran acid3 twice, and the second run was a bit faster than the first-- second results show above. But I've got oodles of other tabs open at the same time, and didn't bother to check out how much they hurt my results.
I remember when Mozilla seemed to concentrate on their customers needs. Now, they seem to be behaving more and more as a subsidiary of Google. (They seem to think that you don't need a reliable, usable desktop email client anymore-- because THEY'VE decided that you're gonna be happy using GMail!) And now, maybe because Google needs IE to work better, Mozilla pours time and effort and money into fixing IE.
The corporation seems focused on making big deals, the old software which I loved since Mozilla 0.6 seems to be getting treated as "legacy crap". Hey, business people, you don't gains market share by improving your competitor! What ARE they thinking?
Your only choices are "all", or "range of pages". A checkbox exists for "current page only", but it can't be selected. Linux remains a 3rd class platform, as far as Mozilla.org is concerned. :(
Opera does a great job with this (so it's not within CUPS or Laserjet support, it's entirely Mozilla's fault.)
BTW, I'm not yet running 3.1 nightlies: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1 - Build ID: 2008070206
if it's just the appearance changes (i.e., SSL sites not shown in yellow, big layout) you can use "old location bar", but you might also look at changing your theme: "classic compact" looks pretty much as Firefox 2 did, and it saves a lot of vertical space too. (Nice on laptops.) I use it, and install it on all my customer's machines. Instructions below, to prevent pop-up of matches, are excellent.
The update for FF2 was pushed out a day before the FF3 update (on Tuesday morning, versus Wednesday afternoon). If you aren't using 2.0.0.16, you're prone to the same attack.
To be absolutely safe, back up your profile directory from OUTSIDE Firefox and 'turn on' only a few at a time. If it breaks so badly that Firefox won't even start, just restore the proofile directory from one of your "backup" copies. BTW, there's some out-of-date comments here, NTT does not force you to "make ALL compatible" at the same time anymore.
Here's a few WHICH WORK in Mandriva Linux: Generated: Wed May 21 2008 13:42:38 GMT-0700 (PDT) User Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008051202 Firefox/3.0 Build ID: 2008051202 Enabled Extensions: [38] * Adblock Plus 0.7.5.4 * Adblock Plus: Element Hiding Helper 1.0.4 * AutoFormer 0.4 * ColorfulTabs 3.0 * Connect to address 1.1.7 * Console 0.3.9.2 * Download Statusbar 0.9.6.1 * Extension Developer 0.3.0.20060726 * Extension Manager Extended 2.6.3.2 * Flashblock 1.5.6 * Forecastfox 0.9.6 * Form Saver 0.7 * Greasemonkey 0.7.20080121.0 * Html Validator 0.8.4.0 * JavaScript Debugger 0.9.87.3 * Mozilla Quality Extension 0.1.5 * MR Tech Local Install 5.3.2.6 * Nightly Tester Tools 2.0.2 * Nuke Anything Enhanced 0.68.1 * Platypus 0.66 * QuickJava 0.4.2.1 * Remove It Permanently 1.0.6.3 * RSS Validator 0.3.2 * Screen grab! 0.93 * Searchbar Autosizer 1.3.8 * Stop-or-Reload Button 0.2.2 * Tab Mix Plus 0.3.6.1.080416 * Text Complete 0.9.9.3 * Tinderstatus 0.2.8 * Toolbar Buttons 0.5.0.4 * User Agent Switcher 0.6.11 * View Dependencies 0.3.3.0 * Web Developer 1.1.5 * YesScript 1.3 I used NTT to "force compatibility" for most of them. I also use: Installed Themes: [5] * Classic Compact 3.0.7 (THIS ONE IS ACTIVE) * Default 3.0 * LittleFox 1.8.28 * Walnut for Firefox 1.8.28 Installed Plugins: (3) * Default Plugin * Java(TM) Plug-in 1.6.0_05-b13 * Shockwave Flash
She's still living at the Governor's Mansion in Carson City, he only visits to conduct "official functions". Maybe he's in a funk about that, and lashing out at widows and dead people helps him to feel better. (And yes, his emotional maturity level OFTEN appears to be on par a typical two-year-old.) Cripes, the man held a permit (now surrendered, it was fraudulent) for NINE concealed handguns. One, Two, maybe Three, I can understand that. Maybe even Five. But Nine concealed weapons ??? OTOH, this "Public Servant's" private residence is far larger and more luxurious than the Governor's Mansion. I live in Nevada (Reno), and DW commutes to Carson City. So now the Gov. wants to F. with dead people, and their widows. Lots of people call Nevada the "F.U." State, this sort of thing ain't new around here.
I agree. In the past, (as well as right now), ATI-written GPU "Catalyst" drivers for Linux have usually been bug-riddled, feature-poor, and a problem waiting to happen. And so, the vast majority of Linux "heavyweights" have been building and buying computers with NVidia. (Both discrete and integrated.) BUT, AMD/ATI has recently offered the actual specifications, under FREE license terms, for Linux folks to write driver code under the GPL. (ATI personnel can also take part, as long as they offer their code under GPL terms.) This could be huge. And unlike Apple systems, many Linux boxes are built as low-end machines, naturally targeting integrated graphics anyway. My own PC cost less than $250, and adding a graphics card + passive cooling was a significant cost. It was, of course, an NVidia card... and I expect that ATI graphics will really become viable soon, due to their having released the full specifications required to write FLOSS drivers.
ISO is broken. The ISO needed to look to their own reputation during this horrific, scandalous MESS. Shame on the ISO for not protecting their own "voting process" from P-Member ballot stuffing, NSB chairperson abuses, and even allowing the "fast-track" process for such an enormous and controversial "standard" in the first place. It should be necessary for EU administrators and legal action in the various voting countries to fix this, ISO should have fixed it themselves!
Although the upcoming cold front is expected to create high winds this afternoon, conditions this morning were quite good. I hope that he was able to ditch in a survivable place, and pray for his safety.
dev builds will be going forwards into FF3.
You CAN still use Tab Mix Plus (3.5 "release candidate" builds from tmp.garyr.net) to make all of the tab UI and operational adjustments which you want. OT: A previous post asked about adblock+. Version 0.7.1.2 is FF2 compatible, doesn't even need "Nightly Tester Tools" to "override" version checking. And of course, all the "flash" whiners should be using flashblock. 1.5.1 works fine, although IIRC it does need the version override via "Mr. Tech Local Install" extension. GreaseMonkey, Platypus, and RIP work great, I'd never use a FF without 'em. I'm actually disappointed by the relative lack of new features in FF2. They mostly just incorporated (and internationalized) stuff previously available in Extensions (spell check, tab mix plus). But there is a good stack of bug fixes, it is a worthwhile upgrade. Before anyone whines about extensions which aren't available yet: This is still only a RELEASE CANDIDATE, jeez, give the extension developers a few weeks to get their stuff updated. If you don't like using it in pre-release state, DON'T INSTALL IT !!!
The contract doesn't merely say that "a large part" of the royalties go to Novell (95%)... it says that SCO must deliver ONE HUNDRED PERCENT of Royalties to Novell, and then Novell gives 5% commission BACK.
Still... If you've got other candidates which (a) weren't "toy-sized"; and (b) ran for at least 20 years, let's discuss them!
Real-world powerstations are typically up to 50x as powerful, and (more important) they are typically run for about 8 times as long (i.e., a lifespan of 30-40 years). The scale and scope of the decommission problem is DIRECTLY related to how long the installation was running... that's what determines the radioactivity of the structural materials in the reactor building. And a production reactor also has an enormous volume of radioactive material to deal with-- according to CCNR http://www.ccnr.org/me_worry_2.html, typically about 7000 cubic meters.
They state that Elk River cost only $6 million to build (a pipsqueek; a typical production nuclear site costs $50M+). But they they list a cost of $57 million to dismantle it! This is a success story ???
Another "success story", Shippingport, cost "only $91 million". But that number is fraudulent, because (a) the reactor vessel was shipped intact to Hanford WA, where nearly all of the dismantling work was done for free (i.e., on the TAXPAYERS' dime); (b) the vessel and other disposed materials were disposed in Federal WA and ID facilities at fees far below those of commercial sites like Barnwell; (c) only the "nuclear parts" were dismantled, not the "conventional parts" (they didn't do the whole job!); and (d) like Elk River, Shippingport was a pipsqueek, only 72 MegaWatts.
The only other decommissioned and dismantled reactor in USA history is Shoreham. (I exclude the tiny and irrelevant Sodium-Experimental at Santa Susana.) Shoreham was 100% easy, because it was in 'production' for less than a month: hardly any of the non-nuclear parts had time to develop any radiation at all.
All other USA reactors, AFAIK, are entombed, SAFSTOR, or DECON in progress. Basically, we're waiting several decades for the radiation to "work its way downwards", and inflict the costs on our Grandchildren and Great-Grandchildren.
However, it ISmy opinion that this is a great streategy for all of the Nukes which are already built and running (or built, done running, and shut down). Letting all of this hot stuff sit in place for a while, to cool down, is far better than schemes such as packing it while still really hot into "permanent disposal" containers at Yucca Mountain... containers which we might find horribly difficult to dismantle and re-entomb if/when they fail. (Kinda like the Chernyobl concrete entombment failing.)
- - - -
I'd mod gonefishing up... he had a real point of discussion. Dave's post is not "insightful", it's just nasty and thoughtless.
No nuclear power station has ever been fully decommissioned successfully. All of human civilization has a history of about 5000 years, and yet we imagine that we can successfully manage this incredibly deadly poison for thousands of years into the future. And, on the basis of barely 60 years, some so-called experts express "confidence" that there won't be enormous disasters, both accidental and intentional, in the future.
Instead of huge taxpayer subsidies to make more Nukes, and continuing to never really clean them up afterwards, why not spend some research and pricing support $$$ to get solar panels as a standard roofing material on people's houses? (Or, at least stop building and re-roofing houses with black asphalt shingles in hot geographical regions.... an incredibly wasteful practice.)
(Pure FUD... are you proudly clueless, or are you 0wn3d by criminal monopolists? If you're only a TROLL, please get off the computer and go eat some donuts.)
The extension "Nightly Tester Tools" allows you to ignore the build IDs in the .xpi file, 'forcing' compatibility. They'll at least load once... they might, in some circumstances, immediately disable themselves. Or, they might break completely.
When it happens, the 'Alpha' designation means that no more major new features will be allowed from that point onwards. Also, it should be at least somewhat useable. It DEFINITELY doesn't mean that it's ready 'informal' use... you need to make a COMPLETE backup of your profile before installing one of these nightly builds.
The biggest new feature is 'places', a gigantic re-write of 'bookmarks' to include RSS and some new features. IMHO, it's badly broken. I've used several nightlys in recent weeks, and disasterous problems, (already known, but still to be fixed) have forced me back to a mid-February build.
Be sure to check the mozillazine forum firefox-builds (at http://forums.mozillazine.org/viewforum.php?f=23 , NOT the firefox-support forum) for the most recent "The Official Win32 2006mmdd Build is out" thread. Then, look at the unfixed bugs in the list. And ***IMPORTANT*** use the last link in the bugs list to look at the separate list for 'places'.
As I write this, the Places list includes 216 bugs. One is a 'BLOCKER', another is 'CRITICAL' , and 15 are 'MAJOR'. I wouldn't use the current nightly on my box. (With my usage, the 'Critical' is more important than the 'blocker'). But, in any case, I'd recommend that you wait until there aren't any 'CRITICAL' bugs which could affect you before downloading any nightly.
*IF* you download and use a nightly, I say that you are MORALLY OBLIGATED to check for duplicates on any bugs you find. Right now, that means you've got 194 'normal', 'blocker', and 'critical' bugs to cehck against... just for places.
for everyone's sake, WAIT FOR A HALF-DECENT BUILD!