I'm sorry if I insulted your joke but you really should know that equating jobs at BlackBerry with "RIMjobs" isn't funny. Repeating a joke that is made at least 5 times in every thread about BlackBerry (and even more often when they were still called RIM) is not clever or funny. It is trite and lame. You do not have to resort to trying to insult me. Or propositioning me? I don't know- it wasn't very clear.
I am actually. You might not go to many parties but believe it or not most party-goers would rather hear new and funny jokes. Not tired and unfunny ones they've already heard a million times.
Your ruby code is exactly unreadable. Why? As soon as you do many things on one line, it becomes unreadable. Ruby seems to encourage that behaviour.
You are probably just not good at interpreting it well; most humans have no problem with that. For instance- the single line I quoted from you contained several sentences but I had no problem understanding it.
1.upto(10).each{ |i|
print i
}
Case in point. You are actually doing 2-4 things on the first line of that code (depending on how you define a "thing"). But that is how you've structured the way you read code. Thinking that that is the best way because it's all you can muster is the height of hubris. Something simple like that I would prefer on one line; easier to read.
(at least I do when I get in a high vehicle from my sedan)
But yeah- you keep being an obnoxious asshole.
It's a nice strawman you've constructed there but SUVs can go around on ramps at well above the posted limits. They also usually have big beefy engines (which is why they are usually as being inefficient) and can accelerate to merging speed in safe and reasonable time frames.
Are you the moronic 16 year old that thinks it is a good idea to accelerate from 60k to 140k as fast as possible in traffic in the right lane (or while veering across several lanes of traffic)?
^ That is why strawmen are useless and add nothing to the conversation. Utterly pointless.
Hey, it's very important that my vehicle look more impressive by being taller, even though it raises the center of gravity and greatly increases the risk of rolling over.
You may never have driven a high vehicle but if you have you would immediately notice that being high gains you a better view (at least I do when I get in a high vehicle from my sedan). This is actually pretty nice when turning left at intersections, merging lanes etc. Being as most people drive these vehicles in urban environments and not in environments that would stress their centre of gravity I would posit that they've more concerned about the better view than "looking impressive" or worrying about their centre of gravity.
Exactly what I use in day-to-day outings actually. I live in a comparatively warm area though. Also I tend to use my thumb for most of my phone fiddling which those gloves do not help with. None of it really matters though because no matter how you are interacting with your phone bulky things over your hands is going to impede that.
That have to be redeveloped every new app- hopefully properly. If every app will benefit from having its data transport being more robust like this why not put it in the transport layer where it will be more efficient? With your attitude we should all be happy with HTTP1.0 too.
You certainly would use streaming audio in that situation... And you might check your phone when getting out of the car and send a message of some kind. Now that message fails to send because you interrupt the connection mid way through. Or it just does something else unexpected. An uninterrupted internet connection is pretty much always better than an interrupted one.
When you walk into your house from outside you don't get weird interruptions in service, missed / lost messages or any of the other things that happen when communication is interrupted.
What you or I or any smaller company that's focused on delivering quality systems would do is first limit the scope, get a product owner on the government side, and make that one person fully and totally responsible for scope. And if he tries to shoehorn in a pony, you'd say "Well, that means this core functionality you wanted has to go, or we'll go over budget".
Great in theory and I agree with everything you've said. Limiting scope can be extremely difficult however. Especially when you are dealing with an organization as large and as used to always getting their way as the government. If you can manage to get a professional politician to be "fully and totally responsible" for anything, let alone something that could go very badly for them, then please get involved in lawmaking.
IMO: Taking that much money from government should be considered a very literal hanging offense.
You are assuming that the government had nothing to do with this failure. Software development by committee never ends well.
It's not too uncommon for government projects to have every bureaucrat in the mix trying to get their grubby little paws on it and make it how "they want". I can't even imagine trying to write software and having, literally, thousands of "bosses" giving you contradictory or impossible requirements. Add in lowest-bidder and you start to understand why every government software service you've ever used sucks at least a little bit.
Everything compiled to target these registers. But what about all the stuff that is compiled to target the majority of iOS devices? It's not like ARM has a lack of registers in the first place.
there's no reason to believe there won't be such files, neither as media, nor as, say, game assets in future. None at all.
There's a few reasons to believe it in reality. In the future almost certainly but I doubt we'll see much, if any, use of it for the 5S generation.
More registers have to do with ARM64. While you're getting fixed on "but it simply says 64 bit in marketing material!", developers read that as "It has ARMv8 with all the niceties it brings".
Developers have other things to read to find that information. Developers do not look at marketing material for development tips.
While pushing it to the front lines of marketing is indeed strange, it's not nearly as useless as you think.
It is "useless" presently. That is why I know it's in the marketing material solely for the numbers. In a couple of years I am sure many devices will be 64 bit and using it. Because of that it is still a good idea for Apple to make the 5S 64bit- so they can phase out 32bit earlier. It is smart from their general business strategy of "one device to rule them all". This is how I know that the marketing team was grasping at straws for things to list and hey- bigger numbers worked well for Intel.
mmap an hd video into memory, instant seek to anywhere in the movie with practically 0 overhead.
It is still going to have to load that memory into RAM somewhere. And again I will repeat that there is not likely to be many people storing files that big on their iPhones that they need to seek faster than they already can.
Just because you don't understand the usefulness doesn't mean there aren't plenty of reasons.
The fact that no one has given compelling reasons as to its usefulness gives me all the reason I need to conclude it's "not that big of a deal". There is nothing wrong with going 64 bit. But the fact that it was included in the marketing material is nothing more than "more bits more better". Something that Apple was always supposed to be above I might add.
Register count is probably the biggest immediate boost. This is a tremendous speed advantage to certain applications.
More registers has nothing to do with it being 64 bit. Nothing at all. How are Apple going to deal with most of their devices not having that many registers? Most likely nothing will use them at all until the older devices are phased out. Also, ARM already has abundant registers.
64 bit transition and more registers are a good thing (more registers more so than 64 bit, maybe). But including that in marketing material is nothing but empty promises because, currently, they mean nothing to the end user.
NO ONE, I repeat, NO ONE HAS SAID SNOWDEN COMMiTED TREASON in this thread
You did- or at least tried to. You took something that was not treasonous in the least and made it "appear" treasonous by stating that it "borders on treason". Well tell us- is it treasonous or not? Because if it is not you can stop flapping your mouth about how it is "aiding the enemy". It is not aiding the enemy anymore than anyone else that disagrees with your government.
Especially if they go to a foreign country, stand up and say "I did it" then go to another foreign country and seek asylum.
So he should have what- trusted the government that is clearly not trustworthy and taken 4 or so years of solitary confinement? Would what he said carry more weight with you then? Or would you have just found other reasons to shoot the messenger?
There were legal avenues to expose what was happening without giving secrets to foreign nations and exposing specifics about how we monitor known terrorist organizations.
Oh of course. The legal avenues that would have punished him immediately for thinking for himself and not changed a thing. Stop framing the problem as "how you monitor known terrorist organizations". The problem is how you monitor everyone else and you know it.
Why would anybody be doing that on a phone that probably has 64GB storage total? 0.01% of iPhone users might be able to find a use for that. 0.01% of that might actually do it. Being as there's probably more people that enjoy watching the glass shatter when the phone is dropped than will mmat that amount of storage I'm not sure that is very advantageous.
Slashdot Mirror
I'm sorry if I insulted your joke but you really should know that equating jobs at BlackBerry with "RIMjobs" isn't funny. Repeating a joke that is made at least 5 times in every thread about BlackBerry (and even more often when they were still called RIM) is not clever or funny. It is trite and lame. You do not have to resort to trying to insult me. Or propositioning me? I don't know- it wasn't very clear.
I am actually. You might not go to many parties but believe it or not most party-goers would rather hear new and funny jokes. Not tired and unfunny ones they've already heard a million times.
Sigh. Not only did that joke stop being funny years ago (if it ever was funny) but RIM is no longer in their name anyway.
Your ruby code is exactly unreadable. Why? As soon as you do many things on one line, it becomes unreadable. Ruby seems to encourage that behaviour.
You are probably just not good at interpreting it well; most humans have no problem with that. For instance- the single line I quoted from you contained several sentences but I had no problem understanding it.
1.upto(10).each{ |i|
print i
}
Case in point. You are actually doing 2-4 things on the first line of that code (depending on how you define a "thing"). But that is how you've structured the way you read code. Thinking that that is the best way because it's all you can muster is the height of hubris. Something simple like that I would prefer on one line; easier to read.
(at least I do when I get in a high vehicle from my sedan)
But yeah- you keep being an obnoxious asshole.
It's a nice strawman you've constructed there but SUVs can go around on ramps at well above the posted limits. They also usually have big beefy engines (which is why they are usually as being inefficient) and can accelerate to merging speed in safe and reasonable time frames.
Are you the moronic 16 year old that thinks it is a good idea to accelerate from 60k to 140k as fast as possible in traffic in the right lane (or while veering across several lanes of traffic)?
^ That is why strawmen are useless and add nothing to the conversation. Utterly pointless.
You should probably be aware that ePub is basically a zipped HTML document.
Hey, it's very important that my vehicle look more impressive by being taller, even though it raises the center of gravity and greatly increases the risk of rolling over.
You may never have driven a high vehicle but if you have you would immediately notice that being high gains you a better view (at least I do when I get in a high vehicle from my sedan). This is actually pretty nice when turning left at intersections, merging lanes etc. Being as most people drive these vehicles in urban environments and not in environments that would stress their centre of gravity I would posit that they've more concerned about the better view than "looking impressive" or worrying about their centre of gravity.
Exactly what I use in day-to-day outings actually. I live in a comparatively warm area though. Also I tend to use my thumb for most of my phone fiddling which those gloves do not help with. None of it really matters though because no matter how you are interacting with your phone bulky things over your hands is going to impede that.
Nokia's decline started over a decade ago when they thought the future of mobile phones was disposable fashion accessories.
Is that not what they are? Was their problem was being too early in coming to that conclusion?
Holes are known for their efficiency at losing heat. If frostbite is a concern do not poke holes in your insulation!
That have to be redeveloped every new app- hopefully properly. If every app will benefit from having its data transport being more robust like this why not put it in the transport layer where it will be more efficient? With your attitude we should all be happy with HTTP1.0 too.
You underestimate how cold it is in some places / times. Some times you want full-on mittens because gloves of any kind are too cold.
You certainly would use streaming audio in that situation... And you might check your phone when getting out of the car and send a message of some kind. Now that message fails to send because you interrupt the connection mid way through. Or it just does something else unexpected. An uninterrupted internet connection is pretty much always better than an interrupted one.
I don't think anybody is damning Apple for this. Especially not the original post that was just making a pun on the word hack.
"Open link in new tab" worked for me.
When you walk into your house from outside you don't get weird interruptions in service, missed / lost messages or any of the other things that happen when communication is interrupted.
What you or I or any smaller company that's focused on delivering quality systems would do is first limit the scope, get a product owner on the government side, and make that one person fully and totally responsible for scope. And if he tries to shoehorn in a pony, you'd say "Well, that means this core functionality you wanted has to go, or we'll go over budget".
Great in theory and I agree with everything you've said. Limiting scope can be extremely difficult however. Especially when you are dealing with an organization as large and as used to always getting their way as the government. If you can manage to get a professional politician to be "fully and totally responsible" for anything, let alone something that could go very badly for them, then please get involved in lawmaking.
IMO: Taking that much money from government should be considered a very literal hanging offense.
You are assuming that the government had nothing to do with this failure. Software development by committee never ends well.
It's not too uncommon for government projects to have every bureaucrat in the mix trying to get their grubby little paws on it and make it how "they want". I can't even imagine trying to write software and having, literally, thousands of "bosses" giving you contradictory or impossible requirements. Add in lowest-bidder and you start to understand why every government software service you've ever used sucks at least a little bit.
Otherwise known as: tu quoque.
Everything compiled to target these registers. But what about all the stuff that is compiled to target the majority of iOS devices? It's not like ARM has a lack of registers in the first place.
there's no reason to believe there won't be such files, neither as media, nor as, say, game assets in future. None at all.
There's a few reasons to believe it in reality. In the future almost certainly but I doubt we'll see much, if any, use of it for the 5S generation.
More registers have to do with ARM64. While you're getting fixed on "but it simply says 64 bit in marketing material!", developers read that as "It has ARMv8 with all the niceties it brings".
Developers have other things to read to find that information. Developers do not look at marketing material for development tips.
While pushing it to the front lines of marketing is indeed strange, it's not nearly as useless as you think.
It is "useless" presently. That is why I know it's in the marketing material solely for the numbers. In a couple of years I am sure many devices will be 64 bit and using it. Because of that it is still a good idea for Apple to make the 5S 64bit- so they can phase out 32bit earlier. It is smart from their general business strategy of "one device to rule them all". This is how I know that the marketing team was grasping at straws for things to list and hey- bigger numbers worked well for Intel.
mmap an hd video into memory, instant seek to anywhere in the movie with practically 0 overhead.
It is still going to have to load that memory into RAM somewhere. And again I will repeat that there is not likely to be many people storing files that big on their iPhones that they need to seek faster than they already can.
Just because you don't understand the usefulness doesn't mean there aren't plenty of reasons.
The fact that no one has given compelling reasons as to its usefulness gives me all the reason I need to conclude it's "not that big of a deal". There is nothing wrong with going 64 bit. But the fact that it was included in the marketing material is nothing more than "more bits more better". Something that Apple was always supposed to be above I might add.
Register count is probably the biggest immediate boost. This is a tremendous speed advantage to certain applications.
More registers has nothing to do with it being 64 bit. Nothing at all. How are Apple going to deal with most of their devices not having that many registers? Most likely nothing will use them at all until the older devices are phased out. Also, ARM already has abundant registers.
64 bit transition and more registers are a good thing (more registers more so than 64 bit, maybe). But including that in marketing material is nothing but empty promises because, currently, they mean nothing to the end user.
NO ONE, I repeat, NO ONE HAS SAID SNOWDEN COMMiTED TREASON in this thread
You did- or at least tried to. You took something that was not treasonous in the least and made it "appear" treasonous by stating that it "borders on treason". Well tell us- is it treasonous or not? Because if it is not you can stop flapping your mouth about how it is "aiding the enemy". It is not aiding the enemy anymore than anyone else that disagrees with your government.
Especially if they go to a foreign country, stand up and say "I did it" then go to another foreign country and seek asylum.
So he should have what- trusted the government that is clearly not trustworthy and taken 4 or so years of solitary confinement? Would what he said carry more weight with you then? Or would you have just found other reasons to shoot the messenger?
There were legal avenues to expose what was happening without giving secrets to foreign nations and exposing specifics about how we monitor known terrorist organizations.
Oh of course. The legal avenues that would have punished him immediately for thinking for himself and not changed a thing. Stop framing the problem as "how you monitor known terrorist organizations". The problem is how you monitor everyone else and you know it.
Why would anybody be doing that on a phone that probably has 64GB storage total? 0.01% of iPhone users might be able to find a use for that. 0.01% of that might actually do it. Being as there's probably more people that enjoy watching the glass shatter when the phone is dropped than will mmat that amount of storage I'm not sure that is very advantageous.
So you agree that this "first step" may be better replaced with some other step?