rjd

... umm.. because its white? and every thats white is Apple?

If you actually look at it you'll see its a not printed anything like an Apple keyboard, the letters are offset for one, they are centered on Apple keyboards, and has Windows keys.

From a personal perspective I stopped building HTML web apps after I started to transition my WebSQL apps to IndexedDB. I really really disliked the experience (messy code/overhead) and haven't had any desire to write another with a client side DB again. The bright side for is however it drove me to learn iOS and Android development... not such a great day for the web though as I suspect my experience isn't unique.

Because in the short term it sounds good, like eating takeaways. But in the long run its pathogenic. If you can't see the whole system and need a quick buck why not.

Theres a reason most of these industries have existed unregulated through out history, exploitation occurs, become regulated, and are now reappearing with a new tact and hitting up existing laws... and hence all the court cases where they are desperately trying to claim the services aren't illegal.

Theres a lot of consumer safety to be considered you rarely hear of, let alone what is technically stealing by reselling things you don't own. Theres a reason regulation happens, and its usually because exploitation occurs.

I mucked around with a few but found them quite restrictive and generally only pushed issues around as opposed to solving them. As soon as you're dealing with a nasty API you can generally find the limits of a framework and have to start writing your own work arounds to behave inside its designed parameters.

Essentially I've found jQuery the best option as a framework, and only because it reduces the verbosity of straight Javascript. Everything else, as noted above, usually ends up in the "good at first then in wish I didn't" basket.

At the end of the day, the majority of what I do is binding, validation, and event handling... and no framework really reduces what has to be done, they just stops other people from doing it differently.

2010 macbook pro and I can't scroll the page without serious lag and jumping :/

I loved it, but I'm bias as I love all of Mike Judges work. I don't really find most his his work boisterous comedy, more a charming satire that I can watch over and over and still enjoy.

I do find however when I try to retell scenes from his work I often choke up with laughter more in the retelling than the watching. I can't retell a scene from office space ending up gasping for air LOL I think thats the genius of his work, and I definitely got that feeling watching it.

His other strength is always the depth of his characters, their nuances, and subtly... so they get funnier the more you understand them. The characters from King of the Hill are some of the best thought out characters I've seen on television, the mannerism, reactions, interactions, just brilliant.

From what I saw of the characters there definitely was a lot of that to come, so hopefully as it develops it'll become something truly amazing.

I can't wait to see more of this show for that reason, everything looked promising, and everything looked balanced for great satire.

It's also about his ability to be a leader, if people lost the ability to respect him then he looses the ability to lead. That happened, he had to go.

I'm not sure how it differed from opening up any manual to anything. The reason you are opening up the manual is the key point. I think for me its was a progression from 'how' -> 'when' -> 'why' -> 'is there a better way'.

I'll frequently go days without Googling anything, weeks if its just CRUD work. When I started it was very different, I can remember writing entire database layers via copy and paste with no idea what anything did I just knew it worked and thats all I needed.

But I'm at a point now I smell bad code in my own work and want to get rid of it and I only got there because I did google... I did go to blogs... read the responses... reference pages/critiques... read white papers/specs/manuals.

And above all I wasn't intellectually lazy, I put in that little bit of effort to ask why, and then get it verify. Nothing wrong with reading source material, theres only problems if you fail to understand and retain what you are reading.

No thank you, its great to see such lateral thinking and particularly around something thats the potential to be quite beneficial to people who have live hard enough as it is.

You put a smile on a jaded mans face with this app, and towards tech news thats a rarity for me these days :)

Thanks, I opened 'zite' up on my tablet and it was mainly really uninspired/mundane/transparent/poorly executed attempts at humor and I was quite put off by it. Be glad for that crap not to surface here.

I haven't seen the term "pragmatism" in this thread. Thats a major difference I've noticed over the years. Something that used to drive me nuts when I was a junior dev, and something I get torture my underlings with these days.

I've found most junior debs I've worked with over the years (and have memories of my own behavior) of being too cock sure of approaches, to keen on new techniques etc...

Over engineering is a major problem I see from younger people, often leading to fragility and bugs, blowing out support in 6-12 months. The other issue is using frameworks for everything, which I've found on questioning reveals fundamental lacks of knowledge about the domain they are experts with (being instead framework experts). Using massive library packages for access to one util class is very very common.

Sometimes I deliberately ask for nonessential 3rd party framework changes, or the utility class to return it slightly different just to make sure that juniors have to look into the framework and understand the domain they are working with. Quite entertaining at times, even if you have to throw out there code and rewrite for them :)

From my point of view its management handling thats my issue. When I say week to update iOS, 3 days on the html version, 3 weeks for android, I get a massive push back... "android in one week".. "OK an extra few days for testing, but we need these out now"

Then I start to get really annoyed at the level of shit of I have to support for Android and the backwards and forwards on testing and just seriously wish the company didn't support it all.

Actually TBH, I only took up looking after the mobile suite as a learning thing. And what I learnt is I'd rather be doing other forms of software (almost exclusively due to time pressures and android). The experience has been less rewarding that other forms of development I've done.

I'd never work on Android products again without a proper team (project manager, QA etc...) so someone else could fight the battle of more development time every iteration instead of me.

What I instantly thought of shared experiences with the game recording features of the PS4, or even ghosting along other players in real time. Its the type of tech that could take the competitive gaming community to whole new levels of enjoyment and participation.

But yes second life applications... I don't see it at all.

Sony was about to steam roll them? and Microsoft in the next year as well?

The Sony morpheus system is already better than oculus feature wise, with better position tracking, and accessory tracking as well. And don't under estimate that, I've read some pretty strong "never again" comments from people using VR headsets and loosing grip of the controls and floundering and/or having to take the headset off to get the controls back into there grips again... even just moving your hand on the keyboard is apparently quite annoying.

Essentially without backing they will loose all market capabilities and be relegated to experimental hardware and not a mass market device.

Being brought out by other companies probably wouldn't of been a reality. MS probably have there own tech and wouldn't gain much more than branding... and xbox is a stronger brand anyway... and Valve would no doubt have chosen to partner rather than buy out... so waving $2bil in your face and the guarantee of ongoing funding and launch platform... its a no brainer.

Well for me its the fact Facebook is an overbearing controlling experience which abuses it market position for its own interests above those of its users (both paying and free).

Its also a very narrow sighted company that has moved into the clone or buy instead of innovate cycle that most big companies evolve into.

That sort of mindset in the upper ends of management would kill the potential of something like occulus, especially when occullus have essentially been trumped by Sony (standing vs sitting, supporting accessories, and a massive user base) in the last week and will be playing catch up... and no doubt the MS power house will be on full roll as well rolling out headsets in the same market space... so its market share is drastically shrinking before its ready for launch.

Theres no way Facebook management will be able to handle the company intelligently enough to prevent the product from faltering. IMO it's pretty much a death blow for occulus.