it goes beyond just development environment. It's like saying iOS is doing well because they chose Objective C.
The problem Nokia had, continues to have, and will have in the future is that they have no goddamned vision when developing products. The N8 hardware was well received, however, the Symbian^3 software was a goddamned joke compared to iOS and Android(and possibly BB).
They're an engineering company that's in desperate need of designers and artsy fartsy types.
On the flipside, look at what happened with pre-Honeycomb Android appearing on tablets and giving people a bad impression of the OS in that formfactor... you can hardly blame Google for holding back for the moment.
I thought Android was supposed to be flexible? is this not the case? I thought Android was resolution independent, is this also not the case? if it's not and the UI API aren't up to snuff, then what's the change between 2.3 and 3.0 that's so different at the kernel and API level?
Apple doesn't issue OTA updates. Even if they could, it wouldn't fit their vision of mobile computing. Computer on the desk, iPhone outside, iPad on the couch.
Unless the entire police force shows up, you usually don't get arrested or beaten by everyone who's in the entire police force. But it's OK to say, "I was beaten/arrested/etc. by the cops."
Besides, this is all speculation, until Lion ships, we have no idea if Samba's even going to be left out of Lion.
The GPLv3 issues in this particular case shoot way over my head. But, the GPL isn't the problem.
WP7 isn't being supported by ZTE and other bulk low-to-mid-end OEMs because of it's licensing requirements(namely, money; and the fact that WP7 hasn't moved a lot of phones).
h.264 is being cross licensed mostly due to patent AND compatibility issues. GPL isn't the core of this issue. Getting sued by the MPEG LA is.
GPL is the solution. If you want your source to be available and don't care what happens to the binary, go GPLv2. If you care about the binary and have RMS like thoughts about "Freedom" and computing go for the GPLv3. The GPL is a legal boilerplate that allows developers the freedom-as-in-freedom to have a legal backing so they can have their wishes respected when it comes to what happens to their code.
What Apple's doing is simply respecting the spirit of the GPL v3. If you really want Samba in Lion server, you can build it yourself from source in Lion after installing Xcode. If you really want Samba, you'll probably know how to do this, and if you don't, you'll probably want to know how to do this anyway.
I was trying to find an obscure album. I tried harvesting used record stores, p2p, etc. Turns out the damn thing was on iTunes for 10 bucks. Can't beat that.
What they mean is that you can't rip the code out of the ROM in part or in whole, repackage it and resell it.
I don't think they had Jailbreaking in mind when they wrote that section of the EULA.
EULAs are giant CYAs when it comes to certain things. The section below states that the iPhone won't ask if what you're loading onto your iPhone is legally licensed to you, but please don't do it.
...which usually means I'm wrong, anyway, but didn't i4i have a specific and very valid claim to a patent here?
Software patents are bad, no doubt, and we're seeing a horrible precedent set, but wasn't the specifics behind their use of XML in documents legitimately infringed by Microsoft?
I'm torn here. First, I really don't like the idea of being sued over code I may write.
HOWEVER, I do like the idea of suing any bastard who's masochistic enough to implement XML the way Microsoft did in their office suite.
Natural home birthing is twice as likely to kill the mother or the child as birthing at a hospital.
Here's the rub with that statistic, the number is insanely low to begin with, meaning that the reality is that home birthing with a midwife really isn't all that dangerous(it's still all natural woo woo, but that's not the point).
Sure, UIWebView is 50% slower than Android in this test, but, the real measurable difference isn't say the difference between IE6 and Chromium's daily build in Sunspider. The difference is largely negligible.
I could name a few iOS apps that use the HTML/JS rendering API available to native Apps, for example, ANY twitter client will open links in a browser. My bank's banking app is just a thin wrapper around their mobile page.
I'm just not sure the previous generation of JS engines were all that slow, and while JS performance boosts are always welcome, I'm not sure if any app right now *needs* it.
I'm just not convinced that there's a conspiracy here. I'm pretty sure Apple has the same view I'd have. I don't think that many people are using web apps in the first place and I'm not sure if there are any native apps that could use the performance boost that Nitro in this iteration of iOS, so once Safari was set up to use the new JS engine, they shipped it.
UIWebView is still pretty fast. 2 seconds versus 3 seconds is nothing to sneeze at. I'd still take it over say Trident, or whatever they based WP7's JS engine on.
I doubt that it's about not biting into app store revenue, app revenue just simply doesn't make up a huge portion of Apple's revenue. Getting hardware into people's hands is.
âoeWe know thereâ(TM)s no such thing as a perfect Web page load measurement.â
My first thought was, why not have a simple page that grabs the current time, loads a page in the iframe, when the iframe triggers it's ready() event, grab the current time and compare against the start for a load time analysis? the overhead of having it in an iframe can't be *that* bad can it?
for some reason that story reminded me of this quote from Good Will Hunting.
Sean: Hey, Gerry, In the 1960s there was a young man that graduated from the University of Michigan. Did some brilliant work in mathematics. Specifically bounded harmonic functions. Then he went on to Berkeley. He was assistant professor. Showed amazing potential. Then he moved to Montana, and blew the competition away. Lambeau: Yeah, so who was he? Sean: Ted Kaczynski.
If I remember my history correctly, IDE debuggers integrated a browser into the IDE, Firebug and these various developer consoles have been debuggers integrated into the browser, sort of the other way around.
Plus Firebug is a snap to use, and probably the best debugger I've used(Chrome's is really good for troubleshooting CSS issues, but, I'd still rather use firebug). IE9's feels very Firebug like and I feel they got it completely right.
I did some snooping around to see if Joe Hewitt contributed to IE9, doesn't look like it.
Their "Developer's Mode" looks like they straight out jacked firebug.
To be fair, Safari and Chrome have similar developer modes. Still surprised me though. Now debugging IE's shitty JS and DOM WILL be easier, it allows operating in IE6, 7 and 8 modes.
Slashdot Mirror
it goes beyond just development environment. It's like saying iOS is doing well because they chose Objective C.
The problem Nokia had, continues to have, and will have in the future is that they have no goddamned vision when developing products. The N8 hardware was well received, however, the Symbian^3 software was a goddamned joke compared to iOS and Android(and possibly BB).
They're an engineering company that's in desperate need of designers and artsy fartsy types.
On the flipside, look at what happened with pre-Honeycomb Android appearing on tablets and giving people a bad impression of the OS in that formfactor... you can hardly blame Google for holding back for the moment.
I thought Android was supposed to be flexible? is this not the case? I thought Android was resolution independent, is this also not the case? if it's not and the UI API aren't up to snuff, then what's the change between 2.3 and 3.0 that's so different at the kernel and API level?
Apple doesn't issue OTA updates. Even if they could, it wouldn't fit their vision of mobile computing. Computer on the desk, iPhone outside, iPad on the couch.
Unless the entire police force shows up, you usually don't get arrested or beaten by everyone who's in the entire police force. But it's OK to say, "I was beaten/arrested/etc. by the cops."
Besides, this is all speculation, until Lion ships, we have no idea if Samba's even going to be left out of Lion.
Errr. what?
I don't completely understand the problem here.
The GPLv3 issues in this particular case shoot way over my head. But, the GPL isn't the problem.
WP7 isn't being supported by ZTE and other bulk low-to-mid-end OEMs because of it's licensing requirements(namely, money; and the fact that WP7 hasn't moved a lot of phones).
h.264 is being cross licensed mostly due to patent AND compatibility issues. GPL isn't the core of this issue. Getting sued by the MPEG LA is.
GPL is the solution. If you want your source to be available and don't care what happens to the binary, go GPLv2. If you care about the binary and have RMS like thoughts about "Freedom" and computing go for the GPLv3. The GPL is a legal boilerplate that allows developers the freedom-as-in-freedom to have a legal backing so they can have their wishes respected when it comes to what happens to their code.
What Apple's doing is simply respecting the spirit of the GPL v3. If you really want Samba in Lion server, you can build it yourself from source in Lion after installing Xcode. If you really want Samba, you'll probably know how to do this, and if you don't, you'll probably want to know how to do this anyway.
I was trying to find an obscure album. I tried harvesting used record stores, p2p, etc. Turns out the damn thing was on iTunes for 10 bucks. Can't beat that.
What they mean is that you can't rip the code out of the ROM in part or in whole, repackage it and resell it.
I don't think they had Jailbreaking in mind when they wrote that section of the EULA.
EULAs are giant CYAs when it comes to certain things. The section below states that the iPhone won't ask if what you're loading onto your iPhone is legally licensed to you, but please don't do it.
EULAs are ridiculous by design.
It's ALL Javascript and HTML5.
no flash.
Only if I didn't have to target IE7 at work...
I'd hate to break this to you but Woolworth's isn't a "local" grocer. They're a national australian chain.
Not only that but they're named after the international chain of department stores.
hey Amazon, want to reconsider that one-click patent?
I meant, sadistic, however, having to write, test and verify that code works is self flagellation at some level.
...which usually means I'm wrong, anyway, but didn't i4i have a specific and very valid claim to a patent here?
Software patents are bad, no doubt, and we're seeing a horrible precedent set, but wasn't the specifics behind their use of XML in documents legitimately infringed by Microsoft?
I'm torn here. First, I really don't like the idea of being sued over code I may write.
HOWEVER, I do like the idea of suing any bastard who's masochistic enough to implement XML the way Microsoft did in their office suite.
Natural home birthing is twice as likely to kill the mother or the child as birthing at a hospital.
Here's the rub with that statistic, the number is insanely low to begin with, meaning that the reality is that home birthing with a midwife really isn't all that dangerous(it's still all natural woo woo, but that's not the point).
Sure, UIWebView is 50% slower than Android in this test, but, the real measurable difference isn't say the difference between IE6 and Chromium's daily build in Sunspider. The difference is largely negligible.
I could name a few iOS apps that use the HTML/JS rendering API available to native Apps, for example, ANY twitter client will open links in a browser. My bank's banking app is just a thin wrapper around their mobile page.
I'm just not sure the previous generation of JS engines were all that slow, and while JS performance boosts are always welcome, I'm not sure if any app right now *needs* it.
I'm just not convinced that there's a conspiracy here. I'm pretty sure Apple has the same view I'd have. I don't think that many people are using web apps in the first place and I'm not sure if there are any native apps that could use the performance boost that Nitro in this iteration of iOS, so once Safari was set up to use the new JS engine, they shipped it.
UIWebView is still pretty fast. 2 seconds versus 3 seconds is nothing to sneeze at. I'd still take it over say Trident, or whatever they based WP7's JS engine on.
I doubt that it's about not biting into app store revenue, app revenue just simply doesn't make up a huge portion of Apple's revenue. Getting hardware into people's hands is.
The target for on die GPUs aren't crysis and call of duty, it's aero and quartz. Which sandy bridge handles very well.
They got a skeptical view counter point...
From the article:
âoeWe know thereâ(TM)s no such thing as a perfect Web page load measurement.â
My first thought was, why not have a simple page that grabs the current time, loads a page in the iframe, when the iframe triggers it's ready() event, grab the current time and compare against the start for a load time analysis? the overhead of having it in an iframe can't be *that* bad can it?
Has it been written off before people even try it?
Given that this is from the same company that gave us the Kin, I'm willing to say yes, and they work in Redmond, Washington.
Because life goes on?
Updates to this really critical situation happen, but so do other things.
Hopefully, some people are taking comfort in handheld gaming when they're in situations they can do very little else too.
for some reason that story reminded me of this quote from Good Will Hunting.
Sean: Hey, Gerry, In the 1960s there was a young man that graduated from the University of Michigan. Did some brilliant work in mathematics. Specifically bounded harmonic functions. Then he went on to Berkeley. He was assistant professor. Showed amazing potential. Then he moved to Montana, and blew the competition away.
Lambeau: Yeah, so who was he?
Sean: Ted Kaczynski.
I hope he does well.
The problem with Packt publishing is that often, they're the ONLY ONES who produce a book on your particular subject.
Hell, Packt's published more information about Moodle's PHP API than THE MOODLE TEAM has. *grumble*
...but I've got plent to be ashamed of. I can explain a bomb. I can't explain some of the shit on my hard drive." -- Marc Maron
If I remember my history correctly, IDE debuggers integrated a browser into the IDE, Firebug and these various developer consoles have been debuggers integrated into the browser, sort of the other way around.
Plus Firebug is a snap to use, and probably the best debugger I've used(Chrome's is really good for troubleshooting CSS issues, but, I'd still rather use firebug). IE9's feels very Firebug like and I feel they got it completely right.
I did some snooping around to see if Joe Hewitt contributed to IE9, doesn't look like it.
Their "Developer's Mode" looks like they straight out jacked firebug.
To be fair, Safari and Chrome have similar developer modes. Still surprised me though. Now debugging IE's shitty JS and DOM WILL be easier, it allows operating in IE6, 7 and 8 modes.