×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Google Blogger Leaves Beta

CmdrTaco posted more than 7 years ago | from the more-emo-please dept.

Google 67

VE3OGG writes "It would seem that Google's famed, award-winning blogging software, Blogger, has just left beta, ABC reports, and entered a growing (but still short) list of Google products to move out of beta. Of course, with this change is status also came a few crucial new features for Google's blogging agent, specifically Google account integration, "Web 2.0" code free updates, and tagging."

cancel ×
This is a preview of your comment

No Comment Title Entered

Anonymous Coward 1 minute ago

No Comment Entered

67 comments

Excellent news... (4, Funny)

D-Cypell (446534) | more than 7 years ago | (#17337320)

...Just a few years in Gamma, couple in Delta, a nice amount of Epsilon testing and we might have it nailed!

First? (1)

kjart (941720) | more than 7 years ago | (#17337400)

Is this the first Google product to actually make it out of Beta (aside from search, of course)? In a way it's kind of sad if it is.

Re:First? (-1, Troll)

Anonymous Coward | more than 7 years ago | (#17337508)

Yeah it's terribly sad. Google should build their products like Microsoft and say they are production ready regardless of how well they have been tested. And it's also terribly sad that Google has so many products in beta yet still manages to make >$7 billion in revenue. You must be thinking that Google has a foolish business model. Keep on thinking that about the 1 decade old company.

Re:First? (1)

kjart (941720) | more than 7 years ago | (#17338236)

No, I would've thought it sad because it would've been the second product that huge, 10 year old company had finished. However, as another, more enterprising AC pointed out, it is not there first non-beta after search, they have at least Google News as well.

Google should build their products like Microsoft and say they are production ready regardless of how well they have been tested.

This is, however, still sad to me. So the word "beta" is somehow a magical umbrella to shield against flaws? The problem with this is that all the Google "betas" are essentially wide open to the public and extremely long lasting. Look at Gmail - it's essentially an open beta (I know, invites - but who doesn't have one who wants one?) and has been around for quite awhile now. It just seems like a complete lack of follow through and yes, that is sad for a company of Google's caliber: just finish what you start, damnit.

Re:First? (0)

Anonymous Coward | more than 7 years ago | (#17342246)

Although it might seem from the outside that we just "forget" that products are still in beta, that's really not true. Typically, if a long-lasting product is still in beta like GMail it's because it has not yet achieved internal standards for reliablity and scalability. Products do, in fact, come out of beta all the time, but they tend not to get noticed ... sometimes because international versions come out of beta at different times to the US version.

Re:First? (1)

wiredlogic (135348) | more than 7 years ago | (#17338594)

The current Google groups interface was in beta in the past. There is now a new beta [google.com] for the third implementation of Google groups. This is the only feature to go into beta twice.

Re:First? (1)

owlnation (858981) | more than 7 years ago | (#17342004)

No. Google Earth, as one example, is also out of Beta.

I have a blogger account set up as a mirror of my Wordpress one. So I saw this news earlier today when I updated the blog. It surprised me. The reason why I use the Wordpress blog as my main one, is quite simply it is light years ahead of Blogger. The Wordpress one even has a built in Analytics - from Google nonetheless - you have to open an account separately for Blogger.

Blogger isn't bad, it's simply ho-hum. My personal feeling is that it should have stayed in beta another six months or so and grown a little more feature rich, and actually, stable as well - adding sidebar widgets etc is a little precarious with Blogger.

The "beta" crap (4, Insightful)

danpsmith (922127) | more than 7 years ago | (#17337426)

Everyone complains about Google's products being permanently in beta, but at least in some cases, the term is largely justified. For instance: docs and spreadsheets is in beta. This is well deserved, the online word processor still can't handle enter presses adequately and screws up the formatting when trying to edit online. In my opinion, Google moves products out of beta when they are ready for general consumption. The only difference is that they aren't worried about having the whole of the audience for their products be beta testers, because, frankly, they only get money through ad traffic. In effect, it works well on both ends, because we can start to see which services Google will have finalized, used the products before they are really ready to be used and then have a final product eventually.

Re:The "beta" crap (1)

nine-times (778537) | more than 7 years ago | (#17337616)

Also, it's just not a bad from their standpoint to get a whole lot of free beta testers. The only down side to Google's beta testing is that they're tipping their hand to any competition, but that downside is incurred by Google, and they seem fine with it. All in all, I'm not sure it's worth complaining.

Re:The "beta" crap (2, Interesting)

zataang (596856) | more than 7 years ago | (#17338216)

The other thing is that despite the shortcomings, they do get my work done. Docs and spreadsheets has a large number of bugs, but I can live with them just because shared-editing saves us a whole lot of hassle.

Re:The "beta" crap (1)

massysett (910130) | more than 7 years ago | (#17338674)

GMail fully deserves its Beta label. I often get "Oops, the system was unable to perform that function" errors. Sometimes I go to the website only to see "Gmail is temporarily unavailable." It's so much better than any other webmail that I put up with the Beta glitches (and hope they don't lose my mail!)

W3C compliance? (1)

jdbartlett (941012) | more than 7 years ago | (#17345586)

Here's a surprise for anyone who's gotten used to my usual Google-praising: IMO, Blogger could stand to be in beta for a while longer--the new Blogger template tags still fail to produce W3C compliant links etc. If Google developers aren't going to follow the rules, why do they leave the strict DOCTYPE in their templates?

Why does Google sit on acquisitions? (4, Insightful)

Salvance (1014001) | more than 7 years ago | (#17337458)

The new Blogger beta is, quite frankly, a disappointment. Blogger was pretty amazing when it came out years ago, but since Google bought them the brand has languished far behind competitors (Wordpress, Typepad, etc). Now Google adds a couple extra features, removes the Beta tag, and expects great fanfare. They just get ho-hum from me.

Re:Why does Google sit on acquisitions? (1)

garcia (6573) | more than 7 years ago | (#17337680)

Now Google adds a couple extra features, removes the Beta tag, and expects great fanfare. They just get ho-hum from me.

Why break something that works pretty well as it is? I have heard some complaints from longtime Blogger users that they may have to use Picasa to now do their images. That worries them because of the free image unlimited image hosting that Blogger used to provide.

Personally, I don't like Blogger or the integrations that Google has done and that's why it gets a "ho-hum" from me. It has nothing to do w/Google "sitting on it".

Re:Why does Google sit on acquisitions? (1)

BAM0027 (82813) | more than 7 years ago | (#17338534)

A significant aspect of this release is the move away from blogger's original infrastructure. The blogging service (still free!) is now on a much more robust and better performing back end.

I find it odd that this aspect of the upgrade isn't front page news, but I guess that would point to a significant shortcoming of the previous version. Bottom line is that now the service is primed from the base up for progress. We'll see what that actually looks like.

p.s. Lastly, AFAIK, the transition of blogs from the old infrastructure to the new one has been seamless and failure-free. That means a lot to me as well as Google shows immense respect for the content of blogs and they are willing to move slowly and take the hit from public perception all in the spirit of being responsible. I like that about Google.

Blogger doesn't recognize (1)

Geof (153857) | more than 7 years ago | (#17341192)

They may have left beta, but I'm not sure they've entered the 21st century. Blogger forbids the <cite> tag in reader comments. Is there some nefarious use of citations of which I'm unaware? I know this is just a small thing, but to me it speaks volumes. (I suspect <cite> isn't alone, but I don't use Blogger much so it's the only one I've run into.)

Re:Why does Google sit on acquisitions? (1)

diegocgteleline.es (653730) | more than 7 years ago | (#17341338)

Yeah, Blogger has been stuck for a while...this release is kind of a "catch-up". IMO, google bougth blogger because of the programmers, not the product. The guys who implemented the origina blogger maybe working in other areas, not in blogger anymore.

Gmail (1)

stocke2 (600251) | more than 7 years ago | (#17337496)

now if Gmail could just make it out of beta

Re:Gmail (0)

Anonymous Coward | more than 7 years ago | (#17344298)

now if Gmail could just make it out of beta


Never going to happen. The data provided by the invitations system is just too valuable to give up.

Gmail was out of "beta" the moment the first invitation was sent. I'd say the ruse has been a wild success.

They may remove the "beta" label at some point, but the invitation system is here to stay.

I have received dozens of Gmail invites over the years, but have not accepted one of them, and never will.

If Google wants to know what my online social circle is, they can be upfront and honest about it, and if they ask nicely, and offer to pay me for that information, then I may tell them. Otherwise It will be a cold day in hell before I ever accept a gmail invite.

"Do no evil"... uh huh... I guess creepy, underhanded and dishonest is OK though.

Google's Beta Strategy (1, Troll)

tqbf (59350) | more than 7 years ago | (#17337586)

The genius of Google's strategy of keeping applications "in beta" forever is that they get two press events for each product launch.

What I don't get is, why do you people keep falling for it?

Re:Google's Beta Strategy (0, Troll)

neoform (551705) | more than 7 years ago | (#17337716)

It's all part of "web 2.0", hell, i bet they'd get a press release if they added a couple gradients to a few block elements on their page..

Re:Google's Beta Strategy (1)

photomonkey (987563) | more than 7 years ago | (#17350162)

Although Google does leave stuff in beta forever (and has diluted the notion of what beta software, or for that matter 'final' software is), I don't really think it's only so they get the PR effect twice. Companies like Google can buy more PR than mere mortals could typically imagine.

Looking at Google News specifically, I think they leave it in beta because they haven't figured out how to make money on it yet, and once they do it as a for-profit venture, they'll have to start paying for the news on their site.

Another reason they might leave stuff in beta forever, is that there is no practical commercial use for the software, but it's constant development leads to advances in other software that has commercial uses AND makes them money. While these things are under development, they leave stuff in beta to AVOID a pr black eye if they pull a product or discontinue a project.

At any rate, I suspect there is far more to it than getting a release-party double whammy every time.

Google product? (3, Insightful)

Otter (3800) | more than 7 years ago | (#17337608)

...entered a growing (but still short) list of Google products to move out of beta...

Anyway, didn't they buy Blogger? And was it "beta" when they bought it, or do they actually move acquired products backwards in their lifecycle?

Re:Google product? (2, Interesting)

momerath2003 (606823) | more than 7 years ago | (#17338472)

The new "Blogger beta" represents a complete overhaul of the Blogger system by the Google team.

I just tried this out yesterday. (4, Interesting)

jZnat (793348) | more than 7 years ago | (#17337664)

And of course, the Safari/Konqueror love was nonexistent. Works perfectly in Firefox, obviously, but you can't create new or edit existing blog posts in Safari/Konqueror with or without the WYSIWYG editor.

Re:I just tried this out yesterday. (0)

Anonymous Coward | more than 7 years ago | (#17338428)

Konquer scuks

Re:I just tried this out yesterday. (0)

Anonymous Coward | more than 7 years ago | (#17338614)

Then stop using shite like Safari and Konqueror! Chirst, I'm forced to use a Mac/POSX at work, but Safari has not been launched since I got the damned thing. Firefox I can use on any platform and have a uniform browsing experience -- why go with more proprietary crap in the case of Safari?

Re:I just tried this out yesterday. (1)

Ngarrang (1023425) | more than 7 years ago | (#17341362)

And of course, the Safari/Konqueror love was nonexistent. Works perfectly in Firefox, obviously, but you can't create new or edit existing blog posts in Safari/Konqueror with or without the WYSIWYG editor.
You can set the blogger features to allow you to e-mail your posts to it. You can also publish posts from Writely (Docs & Spreadsheets).

Re:I just tried this out yesterday. (1)

jZnat (793348) | more than 6 years ago | (#17353808)

I didn't know you could email posts. Friggin' sweet.

And I don't think Writely works in Konqueror/Safari due to the lack of rich text editting features found in Firefox, Seamonkey, IE, and probably Opera (don't know offhand), so that doesn't really help.

The main difference is, it works... (1)

RealGrouchy (943109) | more than 7 years ago | (#17337714)

Finally, posting to blogger works in the browser of *my* choice.

A few months back, I noticed that it would take me up to the "preview post" stage, but when I tried to go any further (like, actually post it) I would get a blank page in my SeaMonkey browser.

Google's FAQ simply said "get firefox". I did, and it still didn't work (probably some residual settings), so I removed FF. I would have to go to a public computer terminal with FF to post. PITA!

Now, at least, I can post with SeaMonkey.

- RG>

Personal revenue from blogger? (2, Informative)

192939495969798999 (58312) | more than 7 years ago | (#17337722)

I thought I heard that the new blogger was going to allow you to earn back some of the ad revenue from your blog, so that you weren't just generating income for the parent company off of your traffic. Can anyone confirm?

Re:Personal revenue from blogger? (1)

ben there... (946946) | more than 7 years ago | (#17338586)

You could just host your Blogger content on your own host instead of blogspot.com.

Only blogspot.com's TOS [blogger.com] forces you to display their ads, not Blogger's.

Blogspot is the only blogger now (0)

Anonymous Coward | more than 7 years ago | (#17339242)

You can't publish on your own site anymore.

As I understand it, the new Blogger upgrade changed the publishing paradigm it uses. Now, all the pages are dynamically generated on the Blogger servers so there aren't any files to statically publish on your own server.

Having said that, there's an easy sign-up to Google AdSense right on the Blogger dashboard under the heading "Make money!".

/.typos (0)

Anonymous Coward | more than 7 years ago | (#17337918)

with this change is status should have been with this change in status

Still a Few Bugs in the System (5, Interesting)

Doc Ruby (173196) | more than 7 years ago | (#17337964)

It's still going to have bugs, like all SW (and everything else). Most of its users won't notice the difference with the qualitative version change, except maybe the usual new features magically appearing. So what's the difference between "Beta" and "release", when the Beta was a "public Beta release"?

I bet it's just some way to start charging money for access. Might as well drop the "Beta" designation, and just call "releases" the "money release".

FWIW (little, post-Netscape), "Alpha/Beta/Release" aren't subjective names. "Alpha" is a version tested (used) by people who also designed/implemented it. "Beta" is a version tested by people who didn't design/test it, unless perhaps the design/test team did get them to produce and/or review acceptance tests/criteria. And "Release" is the version that has been tested OK against release criteria.

To be complete, correct version numbering isn't very subjective, either. The format is >major<.>minor<.>patch< . Bugfixes (not new features) increment the "patch" number. Format changes, in API, transmission (eg. network) or storage (eg. files) still backwards compatible increment the minor number. Feature changes still using the same UI increment the minor number. Format changes not backwards compatible, feature changes which change the UI, or transformational bugfixes which change either formats or UI to break backwards compatibility all increment the major number. Incremental builds can extend the numbers with a dash (eg. "2.13b4.77-154", for the 154th build of the 77th bugfix of the 4th beta of version 2.13), but only in Alpha and Beta versions, not actual releases. A good project's bug reporting will list bugs by their reported ID in lists of which bugfix release fixes them. "Release Candidate" numbers are just nicknames for the last in the series of Betas. Much as the the b1 version is identical to the last Alpha version.

That's it. Each number change should have an Alpha/Beta/Release version, though Alphas can sometimes be skipped with tiny bugfixes. So there's no need for "odd/even" version numbering to reflect "development" versions. And numbers are sequential, except of course when a higher order number increments, resetting the smaller order number (eg. 2.13.77 -> 2.14.0 ->2.14.1). Version numbers have been hijacked by marketdroids, which just confuses the market they bamboozle, which is ultimately bad for sales, and even worse for costs of support. The version number should tell people whether to upgrade, and whether their old data, training and related activities will be noticeably impacted (with associated extra costs).

Netscape broke everything with it's "public Beta" release that defined Web SW distribution. Microsoft has made the curse ubiquitous with SW versions 1, 2, 3 standing in for Alpha, Beta, Release, but mixing it up with new features to substitute for bugfixes. And Service Pack versions that form an entire new chain, and ongoing patches, and every other unmanageable version numbering "scheme" possible. And Linux distros continue the damage with the odd/even numbering and arbitrary versioning, with major releases measured in minor numbers, requiring various extra versions, and version numbering of each release for each distro.

But the numbering schemes change monthly, quarterly. If developers just return to the simple discipline, we'll get back to numbers that actually mean something helpful to users and developers, not just marketdroids counting up to their next bonus.

Re:Still a Few Bugs in the System (1)

scgops (598104) | more than 7 years ago | (#17339128)

>"Alpha/Beta/Release" aren't subjective names.

It's nice to know someone still believes in fairy tales.

>Version numbers have been hijacked by marketdroids...

That, at least, is true.

Re:Still a Few Bugs in the System (1)

ReallyEvilCanine (991886) | more than 7 years ago | (#17340800)

The format is >major<.>minor<.>patch< .

The format is <major build>.<minor build>.[ <version> [ .<patch> [.<level> [b [.<tree>]]]]]

  • pre-alpha: A good deal of the base code runs. It's full of bugs.
  • alpha: The base code is fairly stable. Let's get the rest of the modules working.
  • beta: Code freeze. The software is stable. The modules work. Let's find the bugs.
  • release candidate: Customers can peek, familiarise themselves and file bug reports.
  • dogfood: We're rolling it out internally to find the rest of the bugs.
  • release to manufacturing: We're done. Future bugs and enhancements to be done in patches.

So what's the difference between "Beta" and "release", when the Beta was a "public Beta release" Who gives a shit? A "public beta" is called a "Release Candidate".

I wrote about the problem of "beta" software [blogspot.com] a couple months ago.

Re:Still a Few Bugs in the System (1)

Doc Ruby (173196) | more than 7 years ago | (#17341126)

Your nomenclature is meaningful only (to some people) within your organization. What does "a good deal" or "fairly" mean? Or even "the rest of the bugs"? Numbers assigned to those conditions don't mean anything except whenever it was convenient to declare those completely unaccountable statuses "the next version". There's no info value in the numbers, and no way to know when to assign the numbers.

There is a relationship between versioning (and its numbers) and development/release workflow. But your scheme is just more arbitrary names. Who gives a shit, except marketing? The scheme I detailed is not only objectively informative to everyone, private and public, but had been used for years with those meanings until Netscape simultaneously exploded both SW distribution and marketsprach naming.

Re:Still a Few Bugs in the System (1)

ReallyEvilCanine (991886) | more than 7 years ago | (#17341986)

This has been the basic nomenclature format in every place I've ever been over the past 15 years. What does "a good deal" or "fairly" mean? Depends on the Project Manager, the goals and objectives. Each project is different. Some don't even have "pre-alpha". In general alpha has meant "the code runs but it's unstable as hell. It can perform the basic tasks that we've described in $ListOfObjectives although you might have to try five times and prod it along."

Of course, you could be ready for beta testing when the shitheel customer or some Marketing droid comes back and wants to add and massively change functionality. In the case of really large applications you have major and minor code freezes, the major being general functionaliteis (normally externally driven) and the minor being internal enhancements, ideas, tweaks and patches.

With numbering, tree, beta and level are internal numbers which rarely see the light of day as anything other than internal build numbers, once released to the public, even if withdrawn, maj.min.ver[.pat] is pretty standard, from Microsoft to Oracle to Sun. That Joe's Software House and Grill doesn't use such nomenclature doesn't change this.

Shall we argue next over the readability of K&R vs. Whitesmiths?

Re:Still a Few Bugs in the System (1)

Doc Ruby (173196) | more than 7 years ago | (#17342304)

Maj.min.patch-build is pretty standard, but what the numbers mean has been all over the place. In Silicon Valley where I learned the meanings (starting in 1990), in NYC (mostly Wall Street) where I saw it confirmed, and in Toronto where I taught all my own developers out of school, those numbers mean the same thing I mentioned. Clear meanings usable by SW producers and consumers alike. Telling you when to upgrade, and what the costs/risks would be. A separate meaning from the development process' goals: the meaning is the results.

As for K&R etc, I usually ride that hobby horse when it's ontopic. Just to keep the ball rolling, I go with: // Comment describes function's function.
type3 functionName(type arg1, type2 arg2)
{ // Comment describes function's approach.
        type3 localVarNameT3, anotherT3;
        *type3 localVarNameT3Ptr;
        type4 localVarNameT4; // Comment describes first phase. // Comment describes first step;
        statement;
        localVarNameT3Ptr =
                (f() > 2)? arg1 : arg2; // Comment describes second step on all iterations.
        while(localVarNameT3 = 0; localVarNameT3 2)? arg1 : arg2; // Comment describes second step on all iterations.
        while(localVarNameT3 = 0; localVarNameT3 = GLOBAL_DEF; ++localVarNameT3)
        { // Comment describes each iteration. // Comment describes first step.
                if(step())
                { // Comment describes what step's true result means.
                        localVarNameT4 = localVarNameT3 * 2;
                }
                else
                { // Comment describes what step's false result means. //
                }
        } // optional "while" repeat condition, if lots of braced blocks
        cleanupStatement(); // Comment describes next phase. // Comment describes first step of next phase;
        anotherStatement; ... // Comment describes return value's meaning.
        return(localVarNameT3Ptr);
} // function1Name // Comment describes function2Name's function.
void function2Name(type arg1, type2 arg2)
{ // Comment describes function2Name's approach. ...

BTW, I write the comments first.

Re:Still a Few Bugs in the System (1)

Doc Ruby (173196) | more than 7 years ago | (#17342368)

Forget it - even ECODE and CODE tags don't preserve the (multiple) newlines that make it really readable. And Slashdot's lame filter complains that 33.0 characters per line is too few.

Re:Still a Few Bugs in the System (1)

DerekLyons (302214) | more than 7 years ago | (#17341002)

Netscape broke everything with it's "public Beta" release that defined Web SW distribution. Microsoft has made the curse ubiquitous with SW versions 1, 2, 3 standing in for Alpha, Beta, Release, but mixing it up with new features to substitute for bugfixes.

Microsoft was doing that long before Netscape even existed - across the Eighties wise computer users didn't buy anything from Microsoft until version 3.0 hit the streets.

Re:Still a Few Bugs in the System (1)

Doc Ruby (173196) | more than 7 years ago | (#17341180)

I agree that MS was abusing the naming system before Netscape was created in 1994. But what SW did MS release in the 80s that was even v3? Not that such history contradicts your statement...

Re:Still a Few Bugs in the System (1)

DerekLyons (302214) | more than 7 years ago | (#17341522)

I agree that MS was abusing the naming system before Netscape was created in 1994. But what SW did MS release in the 80s that was even v3? Not that such history contradicts your statement...

MS-DOS, Windows (which crept across into the 90's), Quick Basic (which also crept into the 90's and is *not* to be confused with the QBASIC that shipped with DOS 5), and various other professional tools/languages. (It's all but forgotten today - but across the Eighties Microsoft was a major player in the developer market.)

Re:Still a Few Bugs in the System (1)

Doc Ruby (173196) | more than 7 years ago | (#17341836)

I remember 80s MS. I learned C with MS C v5, so I guess they "got it out of beta" by then. As I recall, they did - it was IBM which hadn't gotten the PC out of beta, because it still required extra packages to cope with "Extended Memory", "Expanded Memory" and even "memory models" (ranging to "huge" for >1MB, I think I recall) hardcoded as compiler flags.

What's the deal with blogspot? (1)

wiredlogic (135348) | more than 7 years ago | (#17338532)

What's going on with Blogspot. All of the blogs I occasionally checkup on have either disappeared or been hijacked by spammers. This all happend in the last couple months when Google was reorganizing things.

Feature complete? (1)

lillevi (624279) | more than 7 years ago | (#17338678)

Of course, with this change is status also came a few crucial new features
Seems kinda strange to add features when you are releasing software. Shouldn't new features be added to a new cycle? Isn't a beta meant to be feautre complete?

Re:Feature complete? (1)

scgops (598104) | more than 7 years ago | (#17339188)

Good point. Most companies add features in beta releases, and go live once things are stable. I guess Google didn't care to solicit feedback on the new features before the official launch.

from a different perspective (2, Interesting)

alphafoo (319930) | more than 7 years ago | (#17338756)

Ironically, I just switched away from Blogger last week because the new templates, although great-looking, are not easily configured for right-to-left (RTL) languages. I'm not a CSS expert but I did give it a try over the weekend and eventually I gave up fighting it and reverted back to the old template which relied on my surrounding each entry and post title with a DIV DIR=RTL.

I searched around to see what other people had done with the new Blogger and to see if I could just use someone else's template, but all of the ones I saw were a mess. Some parts RTL, some not, some of the layout broken. So, I moved to a site with excellent RTL support, but difficult to use because it seems to have been built and tested solely for Internet Explorer, so Firefox1.5 and Safari and Opera on the Mac all choke on various (but different) aspects of the posting process.

If someone has had some success making a clean Blogger template using Arabic/Farsi/Hebrew/etc, please share.

Not totally out of beta (0)

Anonymous Coward | more than 7 years ago | (#17340750)

Out of beta for new accounts, but they are still having problems migrating old accounts to the new service. Many old accounts get a "you can't upgrade now, but we're working on the problem" message...

Finally (1)

deusdiabolus (664790) | more than 7 years ago | (#17342338)

Maybe this means that now the third-party blogging client developers will be able to get their software working with Blogger accounts again.

Try Just Looking at the Front Page in Firefox 2.0 (0, Offtopic)

Master of Transhuman (597628) | more than 7 years ago | (#17344258)

The JavaScript just KILLS Firefox 2.0. Just scrolling up and down the page is a nightmare - and it's a short page!

Opera scrolls the page much faster and more smoothly.

Firefox 2.0 has a LOT of work to do on it. Every day it irritates me more with its erratic performance, broken download function (on Kubuntu Linux, anyway), and occasional crashes and lockups due to JavaScript issues.

Note: I'm not complaining about Google Blogger - I haven't used it yet - - I'm just complaining about crap software in general.

Re:Try Just Looking at the Front Page in Firefox 2 (1)

Mr Z (6791) | more than 7 years ago | (#17349682)

It's the translucent elements that seem to do it. Those drag Firefox to its knees, and according to 'top,' all the MIPS are being spent in the X server, not the browser. They need to figure out a faster way to do things that doesn't soak the X server like that.

--Joe

Re:Try Just Looking at the Front Page in Firefox 2 (1)

Master of Transhuman (597628) | more than 7 years ago | (#17350130)


Thanks for pointing that out. Good call.

Makes me even more nervous about all the 3D eye candy the distros want to put in these days.

Slightly inaccurate (1)

aricept (810752) | more than 7 years ago | (#17346690)

There have been two versions of Blogger for a while now - "Blogger" and "Blogger in Beta". "Blogger in Beta" was the upgrade with new features, like the drag-and-drop element placement, the new template code, etc. "Blogger" is the original code. You had a choice between either of them, and each had a separate login area.

Saying that Blogger is just leaving Beta is inaccurate. The new version is just leaving Beta.
Check for New Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Sign up for Slashdot Newsletters
Create a Slashdot Account

Loading...