Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Comment: Re:Least common denominator (Score 1) 54

by Lumpy (#49562497) Attached to: Has the Native Vs. HTML5 Mobile Debate Changed?

Unless you are ok with that app not working at times.

Web based is 105% crap when connectivity is flakey.

If you are making "free" apps, go for it, but if you are charging a customer $29.95 for the app, it had damn well better be a native app that works even with all radios turned off.

And I have a couple of $29.95 apps. Hell I have one for room audio tuning that was $59.95

Comment: Yes, Please!!! (Score 2) 54

by rockmuelle (#49562415) Attached to: Has the Native Vs. HTML5 Mobile Debate Changed?

For 99% of the applications out there, there's no reason not to do it in the browser if you're starting from scratch today. Most (useful) mobile apps simply display remote content in a way that's contextually relevant to the moment (Yelp, shopping (ordering and product reviews), *Maps, news sites, social media, etc). There's no reason for any of those to be app based. Most apps that aggregate content are poorly designed and not updated frequently. Couple that with the fact that most do not have useful offline modes (the only reason to have an app for content, IMHO), it just makes sense to optimize for the mobile browser rather than spend all the time and effort on an app. Hell, even most games I play casually have no reason being written as apps any more - any word game or puzzler would work fine in the browser.

Instead, put the effort into good mobile design and development practices. Hire good developers to optimize for JavaScript. Hire good developers to optimize your backend operations to reduce latency. Find what features are missing in HTML/JavaScript (e.g., a good client side persistence layer) and encourage the browser vendors to improve there so everyone can benefit.

For context, I develop complex scientific software. We use the browser (desktop) as our client and push the limits of what you can do there. Mobile is not far behind and should be the first choice for new development.


Comment: Re:This never works (Score 1) 296

by Muad'Dave (#49562123) Attached to: Microsoft, Chip Makers Working On Hardware DRM For Windows 10 PCs

Actually the studios axed DiVX. The agreements were for so many movies per year, and as the studios didn't want to hurt DVD sales or their own (nonexistent) streaming services, they began to provide movies like "I'm Gonna Git You Sucker", I kid you not. The DiVX platform was way ahead of its time - it was a tiny embedded JVM on its own processor that had a standard interface for the DVD player system to interact with. The same hardware ran on every single DiVX player - write (and build) once, run anywhere.

Supposedly the concept of the 'jar' file was a direct result of DiVX research.

It was a really cool idea - I could buy a disk from 7-11, toss it on the shelf, and watch it when I wanted to - no timeout on the first viewing. You could watch it as many times as you wanted to within 48 hours of the initial viewing, and be charged a buck or two thereafter (including on someone else's device). Each disk was individually serialized, so the backend always knew which disk had already been played.

Comment: Decent idea (Score 1) 280

by Muad'Dave (#49561697) Attached to: Tesla To Announce Battery-Based Energy Storage For Homes

I hope these monsters are UL-listed and won't jack up my homeowner's insurance because they're a fire risk.

At 10 kW * hr, I wonder what size inverter they supply? My house has a 20 kW generator and that will run everything, including the 2 AC units (mostly startup current). If their inverter is the same size, that battery will last _maybe_ 3-4 hours in the summertime.

Comment: Too cool! (Score 1) 125

by Muad'Dave (#49561313) Attached to: Liquid Mercury Found Under Mexican Pyramid

I'd love to don an airtight suit and try to walk/crawl on that river.

According to these documents, I'd displace .0092 m^3 (9195 cm^3) of mercury (yes, I weigh in at nearly 125 kg).

By using the largest values for foot, calf, and thigh volumes, the second document tells me that I could stand up in the mercury, and that it would come up 15% of the length of my thighs or so.

Assuming I'm vaguely rectangular when I'm supine (41 cm wide by 183 cm tall), I'd float in 1.2 cm of mercury.

Comment: Re:Not enough resourcees (Score 4, Insightful) 282

by Jeremi (#49560283) Attached to: Audi Creates "Fuel of the Future" Using Just Carbon Dioxide and Water

There isn't enough CO2 in the atmosphere to make this work.

That's okay, because they are unlikely to be taking the CO2 out of the atmosphere anyway. It would be much cheaper and easier to capture and reuse the outputs of an existing CO2 source (e.g. a coal plant) than it would be to suck CO2 out of the ambient air.

Comment: No need to overthink this (Score 5, Insightful) 296

by Jeremi (#49557801) Attached to: Google Insiders Talk About Why Google+ Failed

Google's social networking features remain marginal for the same reason all of the other social networking sites remain marginal: the value of a social networking application is proportional to the number of people who are already using it. And Facebook hit critical mass first, which means that anyone who wants to "socialize" online with all of their buddies is going to want to do that on Facebook, because that's where all of their buddies are to be found online.

Asking people to also sign up for a second social-networking service is a losing proposition, because it inconveniences them (now they have to check two sites every day) without providing any compensating benefit (why talk to their friends on site B when they could already do that on site A?).

If it happens once, it's a bug. If it happens twice, it's a feature. If it happens more than twice, it's a design philosophy.