RPi with 512mb Memory?

Interesting.  Site looks legitimate.  512MB Model B is listed as "coming soon", and price difference is reasonable.  When people were whingeing about 256MB being too small a year ago, the RasPowersThatBe explained that 512MB was a lot more expensive.  But that was a year ago, so the differential may be a lot smaller now.

I wonder if this is something that slipped through and au.element14 was supposed to keep mum so that people wouldn't cancel current orders, leaving distributors stuck with 256MB inventory?  Personally I'm quite content with 256MB -- hey, it's twice the size of my BeagleBoard rev B4.

I recon that the price should drop another $10 dollars if it is just a RAM upgrade.  But what If there is other fixes such as RG1 and maybe a processor boost?

Who knows.

I recon that the price should drop another $10 dollars if it is just a RAM upgrade.  But what If there is other fixes such as RG1 and maybe a processor boost?

Who knows.

Fergus, I think you're onto something with the 512MB discovery and your question about the Model A.  My guess is there's something afoot, to coincide with the Raspberry Pi Foundation US Hackspace Tour which begins 18 September.  I'm planning to go to the San Francisco event on 29 September, mostly for the talk by RasPivangelist Rob Bishop, described thusly:

RaspberryPi: Past, Present & Future - An introduction to the RaspberryPi, including an overview of its history and development, details on the technical specification and an outline of future developments.  Followed by a Q&A session.

The timing of the tour combined with your 512MB discovery jumps me to the conclusion that RasPi will be announcing a Model B upgrade to 512MB combined with availability of the Model A, ending the "please Liz, may I have some more RAM" whingeing at the high end and the "GNU/Linux box for $25 -- some day" whingeing at the low end.  This is similar to what BeagleBoard did by introducing the more expensive XM while reducing the price of the BeagleBoard rev C.

This is all light-hearted SWAG based on the facts outlined above and I have no other information to confirm or deny whether this is going to happen.  In any case, I'll be nice to Rob :-)

> In any case, I'll be nice to Rob :-)

Can you make any sense out of Liz's request that you "be nice"?

The "journalist" used the exact same words.

coder27 wrote:

 

> In any case, I'll be nice to Rob :-)

 

Can you make any sense out of Liz's request that you "be nice"?

The "journalist" used the exact same words.

I'm not a mind-reader, but I suspect someone might not have been amused by the Kate Beaton cartoon, the Apocalypse Now reference, or commenting on choice of adverbs.  I doubt the Green for Danger reference ruffled feathers as it's a pretty obscure movie -- at least in the USA.  Maybe it's frequently shown on British TV.

I try to be careful not to make personal attacks, and our soi-disant journalist didn't call me out by name.  However, IMO the words and actions of leaders of any community should be subject to review by the community, and if community members feel that leaders are saying or doing things that are not in the community's best interest they should be able to comment accordingly.  I think Liz's suggestion that one shouldn't write anything one wouldn't say face-to-face is a good standard.

IMO satire can add perspective, but not everyone has cultivated a sense of humor, and humor varies between people and cultures.  Also, a sense of humor may be suppressed by overwork and/or having to deal with trolls and nutjobs on a regular basis.  So I try to be nice.

> our soi-disant journalist didn't call me out by name

It seems a bit incongruous that the "journalist", who claimed not to have

missed any subtleties, didn't call you out by name on this forum,

but on the rpi.org forum you are called out by name by someone who

claims "our skins are so thick we are pachydermous."

https://twitter.com/Raspberry_Pi/status/241583069038010368

What casued this mistake in the first place?

The link does not work any more - as it shouldn't.  So all seems to be resolved.

> What caused this mistake in the first place?

Depends what you consider the mistake to be, announcing a product you

don't have, or not having a product you're announcing.

In any case, I don't think the wait will be too much longer.

coder27 wrote:

 

> What caused this mistake in the first place?

 

Depends what you consider the mistake to be, announcing a product you

don't have, or not having a product you're announcing.

 

In any case, I don't think the wait will be too much longer.

Defenantly agree