If you have never heard of Boagworld before now I’m afraid that you have missed out, the weekly podcast was one of my main sources of web related news. Recently I have dropped behind a couple of episode so have only just found out that the show has been cancelled. Its a massive shame but I’m sure they had their reasons, so I guess it’s time to move on. So far my replacements are The Sitepoint Podcast and The Big Web Show both are doing a brilliant job of filling the whole that Boagworld left behind R.I.P Boagworld Podcast.
Below is Techi take on how to solve the iPhone 4 signal issue.
As for the death grip, the official fix is still to just buy a bumper (which reportedly doesn’t work as well as Apple would hope) or, as Big Steve says, ‘hold it differently’. I’m gonna start holding phones upside down. Start a trend. It’ll be like playing on Expert Mode, and I just kind of have to guess what the other guy’s saying. ‘Sorry, Dave, I couldn’t make the funeral, I didn’t get your directions clearly. My phone was upside down.’ But my signal will be totally 4G, so whatever. Problem solved.
Article on Drawar:
Imagine the headaches Microsoft would get rid of by using WebKit. No longer could we blame IE for our development headaches. We could test a site in IE, Chrome or Safari and there is a good chance if it works in one that it will work in the other two. That sounds like bliss to me.
There’s one point I’d like to add to this argument: Standardizing on a rendering engine such as WebKit does not mean innovation has to be stifled. Chrome uses WebKit and still has plenty of differentiation with Safari. Its V8 Javascript engine, for one, is entirely custom and known for its remarkable performance. Browsers like IE and Firefox could learn something here — what if IE were to take a build of WebKit, build in Silverlight, and make great use of it in the browser’s default pages?
I realize that WebKit isn’t perfect and there are way too many versions of it out there, but still, as I’ve mentioned before — it’s an open source project working against a standard. It’s used for over 90% of mobile browsing (or will be soon). Browser makers like Microsoft and Mozilla should swallow their pride, take the unique features they’ve each brought to their respective browsers, and start figuring out how to develop them on top of WebKit — it’s the quickest way for web development to move forward as a whole.
Been listening to a lot of these guys lately.
I sometimes like to imagine that there are little men inside my printer that have to work their socks off every time I press the print button. I’d like to think that the guy that made this lego printer shared the same thoughts. I want one of these!!!
