Hồng Thất Công
Đả Cẩu Bổng Pháp
I pronounce Puh Rei like in Parade
Just curious. I don't want to bring that discussion here, but some people might be able to make use of more. I don't know until I try it if it is too much or too little. The question about the location of the RAM was somewhat related to this, and I am content that we only need to replace the CPU board to get nearly a whole different system.Why is it too much? seriously, 2GBs on a lightweight ARM device is plenty.Is 2GB of RAM set in stone?
That was what I meant. I heard him say it similar to how I do, and at least one other way. I just want to know which is more technically correct. I am not ashamed of pronouncing things properly even if it isn't the popular way.I'm pretty sure I heard at least 2 different pronunciations of Pyra from ED during the presentation so maybe he was just covering all his bases. ;-)
- Neelix
Why wasn't that in the poll ? Sounds great"Panzwora"??
I guess space and derived from that money and power consumption are the main factors here. We only have a certain amount of space, including more RAM would mean increasing the cost significantly as one way to do it, would be to buy the same amount of memory modules, but with higher capacity. If space would be left to "just" buy more modules , you have additional modules that consume additonal power, with a memory module beeing a component that usually is always on. It's weighing the "costs" against each other, surely there will always be people that try to bring the hardware to its limits, but for the majority of users 2GB should be enough (and looking at the Pandora, this assumptions looks logical to me)Just curious. I don't want to bring that discussion here, but some people might be able to make use of more. I don't know until I try it if it is too much or too little. The question about the location of the RAM was somewhat related to this, and I am content that we only need to replace the CPU board to get nearly a whole different system.
"I personally don't care how you pronounce, as long as you're using and bettering it."
FirefoxI don't really see for what applications you would need more RAM.
I'm from Britain as well (not saying Brit because i'll be forced to stab myself) and I say Pie-ruh so .As a Brit, I would naturally pronounce "Pyra" much like "Pirate" or "Python"
"Pie-rah"
Minecraft doesn't need that much RAM like many people think, 1GB (system)RAM through Java on my PC (64 Bit), some people even limit the RAM Minecraft (java) reserves lower than 512MB to improve the performance, don't ask me why and how this works but afaik it's one of these Java things like garbage collection. ^^"ptitseb's new memory hungry Minecraft
So depending on how old the Pyrrha myth actually is, it could have been pronounced Poo-rah originally, then from 500BC or so it was Pü-rah for at least 1500 years. Then, in the last 1000 years or so, pronunciation shifted to Pee-rah in most of Europe (including Greece), and in the last 600 years or so, English underwent the Great Vowel Shift, which would gradually move it from Pee-rah to Pie-rah, like the word "time" on this chart:In early Greek it was pronounced like English oo [u]. In Classical Greek, it was pronounced like French u or German ü, i. e., [y] (a sound that is not found in most dialects of English). This was the case at least until the year 1030AD.[2] In Modern Greek it is pronounced like continental i or English ee, [i]
Firefox works fine on the Pandora, with 512MB of RAM. You would need to open a lot of tabs to run out of RAM if you have 1GB of RAM.FirefoxI don't really see for what applications you would need more RAM.
I will look into this a bit more for my personal knowledge. Thanks for giving me a head start.So depending on how old the Pyrrha myth actually is, it could have been pronounced Poo-rah originally, then from 500BC or so it was Pü-rah for at least 1500 years. Then, in the last 1000 years or so, pronunciation shifted to Pee-rah in most of Europe (including Greece), and in the last 600 years or so, English underwent the Great Vowel Shift, which would gradually move it from Pee-rah to Pie-rah, like the word "time" on this chart:
Looks like you havent used the latest version on Pandora. Its slow as hell and nowhere near acceptable.FirefoxI don't really see for what applications you would need more RAM.
Firefox works fine on the Pandora, with 512MB of RAM. You would need to open a lot of tabs to run out of RAM if you have 1GB of RAM.
Anyway, I'm fine with 2GB, but I'm just pointing out that for most users, for most use cases, 1GB would probably be more than enough most of the time.
And the mozilla monkeys said they would heavily reduce Ram usage though. What a bunch of clowns.Something happened with RAM-usage with recent firefox versions. A friend used to be able to have 3000+ tabs open on his desktop without any issues. Now it'll chug along until all swap and RAM is used, and then get killed by the OOM killer.
Very true. I tried it and found that it wouldn't work for me, even for light browsing. The PandoraLive article was pretty helpful.Looks like you havent used the latest version on Pandora. Its slow as hell and nowhere near acceptable.FirefoxI don't really see for what applications you would need more RAM.
Firefox works fine on the Pandora, with 512MB of RAM. You would need to open a lot of tabs to run out of RAM if you have 1GB of RAM.
Anyway, I'm fine with 2GB, but I'm just pointing out that for most users, for most use cases, 1GB would probably be more than enough most of the time.
I don't want you to waste your time, but depending on how this was done it would have helped me illustrate a point to someone a couple weeks ago.OK, with poor coding anything can be slow and/or use plenty of RAM. My point was not about a specific version of Firefox, but about the fact that 1GB should be enough for web browsing even with a fully featured browser and many tabs. Of course that does not mean that it is impossible to mess things up. I can make a basic ASCII text editor that requires 16GB of RAM and a 3GHz octa-core CPU if you want.
Just allocate some huge chunks of memory and write some random stuff in it to force them to be actually allocated and not be compressible with zram or something like that. Do some read and writes in them every now and then to make sure they don't end up in swap. And to make it need a fast octacore cpu, create 7 cpu stress test threads to keep 7 cores busy, and let the 8th thread be the actual ASCII editor where the main loop uses some amount of cpu stress test work instead of going to sleep while waiting for user input. You could make it crash if too much physical time is needed per cycle, so it would work fine on a 3GHz core but crash miserably on a 2.5GHz core.I don't want you to waste your time, but depending on how this was done it would have helped me illustrate a point to someone a couple weeks ago.OK, with poor coding anything can be slow and/or use plenty of RAM. My point was not about a specific version of Firefox, but about the fact that 1GB should be enough for web browsing even with a fully featured browser and many tabs. Of course that does not mean that it is impossible to mess things up. I can make a basic ASCII text editor that requires 16GB of RAM and a 3GHz octa-core CPU if you want.
On the Pyra pronunciation, how would the ü be pronounced? Maybe you can start with something like "pure" to help me get the sound and mouth stuff right, or direct me to other resources. I am still reading through wikipedia articles.