Well, it's still like this. One problem at a time.
1. In co-operative multitasking, the computer oompaloompas work on the calculator one at a time and let their boss know when the calculator is free to use. The working oompaloompa can also decide to take a break, leave their work on the desk and let someone else do their work while they do not need the calculator.
2. In pre-emptive multitasking the boss tells an oompaloompa to start working. The oompaloompa is forced to work until their work is done or the boss decides to hit it with a stick and put some other oompaloompa to work. Poor oompaloompa does not know how much time he has and when he gets hit, he has to drop his work immediately.
3. In symmetric multiprocessing the oompaloompas have multipla calculators but only one table and a filing cabinet. The oompaloompas have to coordinate together how to organize their work, so they don't scribble on each others notes, while they take turns on the calculator. The boss is usually in charge of the desk space and the filing cabinet.
4. In distributed vector... I think I write something about hungry philosopher oompaloompas now! They are not good with forks. Or something... Anyway, what was I speaking of? Oh yeah, I'm thirsty. Mmmm... Sluuuuuurmmm...
By your id, I'd imagine you were chewing on punch cards when the dinosaurs roamed the earth, but you seem to be fucking clueless about ARM. ARM is not "a processor" or a specific set of instructions. There IS a specific set of ARM designs that are "industry standard", such as ARM%, THUMB, Cortex, etc. It is cheap to license one of these, fab your own and be compatible with everyone else who licensed the same stuff. ARM processors are not "unable" to do anything. They are complete processors and by definition can do anything you throw at them. If you want to decode blueray faster -- fine -- just spec a proc with a dedicated unit for it. Or use a separate die for it.
ARM is a god damn godsend compared to other designs at the moment. In fact, I'm not sure if anyone could streamline chip design like that in next 10 years like ARM has done.
Anyway, consider yourself scolded by a kid who is a certified lauterbach ARM debugger and has prodded pretty much every Nokia device in between 2001-2008.
No-one gives a shit-tit-fucking-god-damn-fuck if you had mod points or if you are about to post, so just get on with it you piece of ass-fucking-turkey-gobling-diddleydoo-poo-head cunt.
"Computers are useless. They can only give you answers." - Picasso
I guess that's what you get when people have no foresight
That statement is as insightful as ever. Just think about what it implies. Of course, I do not know if it truely was an ignorant comment, but to me it reads as very terse, subtle and clever commentary about human nature
Well, to be honest, I was considering if it should be there or not. Jquery-ui actually makes writing "teh web, second edition"-pages a lot more tolerable than without. However, I'd rather not have them at all. I guess that was a misjudgement, but going into detail about why I think javascript itself is bad would be too involved, because there's a lot _good_ than can be done with it. In fact, JavaScript is kinda neat because it is so abstract that in itself it is pretty much useless without 3rd party libraries:P
It seems that in the last two years, the brainless masses that started studying IT in hopes of big moaneyz have graduated and unleashed their clueless wits upon the industry. I think that anyone who didn't disassemble and (succesfully?) reassemble their toys when they were 5 should stay the fuck out of IT.
Fellow engineers, please. When you see stupid shit like this going, please allocate couple of hours of your time to research and address WHY this shit is stupid. We intuitively know that it is ridiculous to first use sockets to deliver another stateless protocol, on top of which you implement another stateful protocol, etc... But if you just shrug and say "well, that's retarded" and figure it will never catch up because you know it is a bad idea; just look at Spring, Hibernate and other Java EE bullshit. Then Query, JQuery-ui, etc. Todays "technical" managers will buy any bullshit they do not understand. Just like they did when you were 20 and wanted to wow them. And thus, this shit becomes defacto-standard in the industry.
It is like first semester materials engineer discovering that carbon steel has awesome properties: "We should build all the fucking bridges out of 3mx20m hunks of carbon steel!" without realizing there might be a more elegant way to use the resources in your possession.
Well, at least I feel good that "I was right" when they find out in 120 years that all that bullshit with 102342-layers of indirection to accomplish a simple state parser was useless. No, wait. No I don't because I will be dead.
I bought LG GT540 because that was the only android phone I could afford. Do I complain that there is no flashing support? Do I complain that it is only 1.6 Android? Do I complain that it sometimes defaults to Russian character set? No! Because I made the decision to buy this piece of shit. Yes, if I could afford it, I would have bought a dev phone from Google. Then I would have top-spec phone with all the freedoms. But whining that my 200€ phone does not give the features and freedoms as the €600 phone is just retarded. Oh, hmm.. Just realized my phone is unlocked and is fully paid for. Anyway, parents point stands.
At least on chrome, there's just a checkbox but no explanation next to it. Dunno what it does... Post without karma bonus? Post anonymously? Post humously?
Umm... Never ran out yet in normal use. I think I once ran out after watching youtube videos straight for 7 hours or so.
"3G is draining your battery" is a bogus myth. It used to be true with the old experimental devices and sparse network. Now that the network is so dense, the phone never really has to work to get a good signal.
Or if it actually IS draining your phone, the phone is poorly designed or you have crap network.
Try it some time. Leave it in 3G only, always on and let it idle until you run out of battery. Now try it with GSM only, connect only when needed. The latter should give you SOME extra battery life, but should be of no consequence in normal day to day life.
Magnetic stripe huh? I think I haven't used that part of my card ever. This was issued in...2008. It's secure chips and online verification all the way in scnadinavia now. Helpfully, it is hard to overrun your bank account with a debit card this way. I wonder if this was deployed for my or the banks safety?
Well, hmm... I have no experience of what you are talking about. I run my phone in 3G exclusive mode (aka. "just GSM?, huh? Drop me out of the network please.") and I pretty much always have some sockets open. Be it tethering with my laptop or just android checking my gmail or other mailboxes. I consider my connection "always open" and I cannot think of a single situation where I would have had to wait several seconds unless the network was out of reach....And then I would protest loudly at sonera, querying why I cannot get full speed 3G near the main roads
I would not call is high latency anymore. I get 100-200ms pings. Sure it is high compared to dsl, but no longer unbearably so like with EDGE. Finland, sonera here. 30€/month unlimited data.
I have been poking around with android for a bit now... I've been wondering how the UI will scale to different resolutions. The desktop itself looks fine. I have tried "big screen" and "small screen" phones and have it installed on my netbook. All look nice.
However, scaling an application to different sizes will be odd. You can't just say "I want my window to be 640x480". Well, technically you can (using scrolling layout and absolute positioning) , but it would look even shittier than badly designed normal window.
Anyone got good books to suggest? Namely, how to think about scalable UI's in this context. Is there a shortcut to design an application to look good automagically in different devices, or do I really have to design and test the UI N-times -- N-being the amount of different display geometrics in the market currently?
Well, it's still like this. One problem at a time.
1. In co-operative multitasking, the computer oompaloompas work on the calculator one at a time and let their boss know when the calculator is free to use. The working oompaloompa can also decide to take a break, leave their work on the desk and let someone else do their work while they do not need the calculator.
2. In pre-emptive multitasking the boss tells an oompaloompa to start working. The oompaloompa is forced to work until their work is done or the boss decides to hit it with a stick and put some other oompaloompa to work. Poor oompaloompa does not know how much time he has and when he gets hit, he has to drop his work immediately.
3. In symmetric multiprocessing the oompaloompas have multipla calculators but only one table and a filing cabinet. The oompaloompas have to coordinate together how to organize their work, so they don't scribble on each others notes, while they take turns on the calculator. The boss is usually in charge of the desk space and the filing cabinet.
4. In distributed vector... I think I write something about hungry philosopher oompaloompas now! They are not good with forks. Or something... Anyway, what was I speaking of? Oh yeah, I'm thirsty. Mmmm... Sluuuuuurmmm...
Damn! I want one. I mean with the original brand!
Here in Finland "Reva" is a rather rude word for female genitalia...
By your id, I'd imagine you were chewing on punch cards when the dinosaurs roamed the earth, but you seem to be fucking clueless about ARM.
ARM is not "a processor" or a specific set of instructions.
There IS a specific set of ARM designs that are "industry standard", such as ARM%, THUMB, Cortex, etc. It is cheap to license one of these, fab your own and be compatible with everyone else who licensed the same stuff. ARM processors are not "unable" to do anything. They are complete processors and by definition can do anything you throw at them. If you want to decode blueray faster -- fine -- just spec a proc with a dedicated unit for it. Or use a separate die for it.
ARM is a god damn godsend compared to other designs at the moment. In fact, I'm not sure if anyone could streamline chip design like that in next 10 years like ARM has done.
Anyway, consider yourself scolded by a kid who is a certified lauterbach ARM debugger and has prodded pretty much every Nokia device in between 2001-2008.
Hubris.
Umm, what? There's already cell broadcast messages already defined in the original GSM spec!
No need to reinvent the wheel!
These were planned to be used from emergency systems to location specific advertising. Anyone have any idea why it was never used for anything?
Lord help us! This the gray goo!
Soon it will be fixing cracks we did not anticipate!
I'm all for it!
Movie directed by Peter Jackson -- chock full of bullshit that looks cool -- sounds awesome!
No-one gives a shit-tit-fucking-god-damn-fuck if you had mod points or if you are about to post, so just get on with it you piece of ass-fucking-turkey-gobling-diddleydoo-poo-head cunt.
That statement is as insightful as ever.
Just think about what it implies. Of course, I do not know if it truely was an ignorant comment, but to me it reads as very terse, subtle and clever commentary about human nature
Oh, thanks for making a reasoned reply to my rant, instead of flaming back :)
And no. I do not have any better alternative to offer.
Well, to be honest, I was considering if it should be there or not. Jquery-ui actually makes writing "teh web, second edition"-pages a lot more tolerable than without. However, I'd rather not have them at all. :P
I guess that was a misjudgement, but going into detail about why I think javascript itself is bad would be too involved, because there's a lot _good_ than can be done with it.
In fact, JavaScript is kinda neat because it is so abstract that in itself it is pretty much useless without 3rd party libraries
It seems that in the last two years, the brainless masses that started studying IT in hopes of big moaneyz have graduated and unleashed their clueless wits upon the industry.
I think that anyone who didn't disassemble and (succesfully?) reassemble their toys when they were 5 should stay the fuck out of IT.
Fellow engineers, please.
When you see stupid shit like this going, please allocate couple of hours of your time to research and address WHY this shit is stupid.
We intuitively know that it is ridiculous to first use sockets to deliver another stateless protocol, on top of which you implement another stateful protocol, etc... But if you just shrug and say "well, that's retarded" and figure it will never catch up because you know it is a bad idea; just look at Spring, Hibernate and other Java EE bullshit. Then Query, JQuery-ui, etc. Todays "technical" managers will buy any bullshit they do not understand. Just like they did when you were 20 and wanted to wow them. And thus, this shit becomes defacto-standard in the industry.
It is like first semester materials engineer discovering that carbon steel has awesome properties: "We should build all the fucking bridges out of 3mx20m hunks of carbon steel!" without realizing there might be a more elegant way to use the resources in your possession.
Well, at least I feel good that "I was right" when they find out in 120 years that all that bullshit with 102342-layers of indirection to accomplish a simple state parser was useless.
No, wait. No I don't because I will be dead.
This...
Mod up parent etc...
I bought LG GT540 because that was the only android phone I could afford. Do I complain that there is no flashing support? Do I complain that it is only 1.6 Android? Do I complain that it sometimes defaults to Russian character set?
No! Because I made the decision to buy this piece of shit.
Yes, if I could afford it, I would have bought a dev phone from Google. Then I would have top-spec phone with all the freedoms. But whining that my 200€ phone does not give the features and freedoms as the €600 phone is just retarded.
Oh, hmm.. Just realized my phone is unlocked and is fully paid for. Anyway, parents point stands.
Same history here. I actually got hooked on a MUD once again. BatMUD rocks. Chip off the old rock...
At least on chrome, there's just a checkbox but no explanation next to it.
Dunno what it does... Post without karma bonus? Post anonymously? Post humously?
And you just have to post a link to the useless blog post instead of the actual list at the more respected source, 2600.
Umm... Never ran out yet in normal use. I think I once ran out after watching youtube videos straight for 7 hours or so.
"3G is draining your battery" is a bogus myth. It used to be true with the old experimental devices and sparse network. Now that the network is so dense, the phone never really has to work to get a good signal.
Or if it actually IS draining your phone, the phone is poorly designed or you have crap network.
Try it some time. Leave it in 3G only, always on and let it idle until you run out of battery. Now try it with GSM only, connect only when needed. The latter should give you SOME extra battery life, but should be of no consequence in normal day to day life.
Magnetic stripe huh? ...2008.
I think I haven't used that part of my card ever. This was issued in
It's secure chips and online verification all the way in scnadinavia now. Helpfully, it is hard to overrun your bank account with a debit card this way. I wonder if this was deployed for my or the banks safety?
ohlawl....
Good thing about that, is that you can afford every fucking device that uses it, and you can test all of those in an hour.
Well, hmm... I have no experience of what you are talking about. ...And then I would protest loudly at sonera, querying why I cannot get full speed 3G near the main roads
I run my phone in 3G exclusive mode (aka. "just GSM?, huh? Drop me out of the network please.") and I pretty much always have some sockets open. Be it tethering with my laptop or just android checking my gmail or other mailboxes.
I consider my connection "always open" and I cannot think of a single situation where I would have had to wait several seconds unless the network was out of reach.
I would not call is high latency anymore. I get 100-200ms pings. Sure it is high compared to dsl, but no longer unbearably so like with EDGE.
Finland, sonera here. 30€/month unlimited data.
I have been poking around with android for a bit now...
I've been wondering how the UI will scale to different resolutions. The desktop itself looks fine. I have tried "big screen" and "small screen" phones and have it installed on my netbook. All look nice.
However, scaling an application to different sizes will be odd. You can't just say "I want my window to be 640x480". Well, technically you can (using scrolling layout and absolute positioning) , but it would look even shittier than badly designed normal window.
Anyone got good books to suggest? Namely, how to think about scalable UI's in this context. Is there a shortcut to design an application to look good automagically in different devices, or do I really have to design and test the UI N-times -- N-being the amount of different display geometrics in the market currently?
A young curious elf...
- Greater Faydark
Watch out for the brownie
- Butcherblock mountains.
Sit in the docks for hald an hour because you missed the boat by an inch
- Ocean of bored to tears.
Spend an hour because you zoned back and forth from freeport while getting a soda
- Commons
Wow, damn. These are big zones. Damn this running is boring.
- High Hold Pass
Try to navigate around agro mobs. Die and return to Greater Faydark.
- Run through Karanas
Damn, Commons were actually quite small zones... Get killed by some flying lion-kinda-things couple of times.
- Qeynos hills
Huray! Almost there!
Yip! Yip! What's that?
- Qeynos
Damn, this place is pretty boring... I'll think I'll head back now.
Mod parent up.
And the troll modder can go suck a dick or die in a fire. (...to get college money)