|
How about the Microsoft Sphere?[^] I likey.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
This is why we can't have nice things[^].
Quote: Almost three years after Google released its WebM video encoding technology as a "free" and open alternative to the existing H.264 backed by Apple and others, it has admitted its position was wrong and that it would pay to license the patents WebM infringes.
--------------
TTFN - Kent
modified 13-Mar-13 10:02am.
|
|
|
|
|
It's about f***ing time that software patents were banned/outlawed/removed/destroyed.
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|
=====
===
=
|
|
|
|
|
Kent Sharkey wrote: This is why we can't have nice things[^].
404 Needs an "s" at the end.
http://appleinsider.com/articles/13/03/07/google-admits-its-vp8webm-codec-infringes-mpeg-h264-patents[^]
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Ta. Fixed
--------------
TTFN - Kent
|
|
|
|
|
It's probably impossible to create a sane video codec that doesn't infringe any patents. For example, I give you US20020064313[^], which essentially patents the combination of macroblocks and RDO. And US20050238100[^], which patents having I, P and B frames. And US5539467[^], which patents B frames with motion compensation.
Or at least, one could argue that they do, and that's enough to get you in trouble.
|
|
|
|
|
Why Microsoft is like the GOP[^]
Quote: Like the Republican Party, Microsoft’s leadership team never got the message that the landscape was rapidly changing to its disadvantage. The company’s fixation on the declining Windows platform reminds me of the Republican Party’s continuing focus on 18th-Century social values where no Internet existed, long-distance travel was done via horse and carriage, and Social Security and Medicare were not heard of.
--------------
TTFN - Kent
|
|
|
|
|
One of the devs at Khan Academy was wondering how Amazon's avoided the usual "good luck submenu" issues and noticed a simple geometric solution[^]. So, he's made the solution into a jQuery plugin[^]. Just the thing to help us semi-coordinated folk use your Web site.
As many of the people commented, this solution is actually ancient (and Apple). So, why doesn't everyone {cough}Microsoft{cough} use it for all their sub-menus (and sub-sub-menus, and sub-sub-sub-menus)?
--------------
TTFN - Kent
|
|
|
|
|
Nice!
/ravi
|
|
|
|
|
AWESOME!
R3J5cGhvbnMgYXJlIGF3ZXNvbWUuIEdyeXBob25zIHJ1bGUh
|
|
|
|
|
Well, Microsoft have just made it a lot easier by open sourcing the Kinect[^] code.
|
|
|
|
|
Probably because Microsoft didn't want the open source Kinect project that was released by some other people way before the Kinect SDK was, to overtake the official SDK.
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|
=====
===
=
|
|
|
|
|
That is "only" the samples and not the full SDK, not?
|
|
|
|
|
There’s a plethora of IoC containers for .NET. They’re all great tools, like StructureMap, Autofac, Ninject, Unity, etc. Don’t get me wrong, they’re powerful and they do a lot of things. But, they do a lot of things. What do I mean by “they do a lot of things”? Well, they’re all effectively designed to work with codebases that are not DI-friendly. They go out of their way to provide features to support DI in any imaginable design. “What’s wrong with that” you say? If you’ve got a brownfield project, that’s great—you can likely get testability with code not designed to be testable—which is a good thing. But, these abilities make us lazy. If you're injecting too much dependency, your control may be inverted.
|
|
|
|
|
A buddy of mine and I were discussing website building while downing some pints of Lucky Bucket the other night... The conversation turned to "should I give a rats patoot about the 3% of people who disable javascript when dipping into the joys of jquery and yui controls, or do I tell'em to eat a fudgicile?". Do you consider JavaScript a web requirement or a nice-to-have?
|
|
|
|
|
Requirement. Every browser worth targeting now has JS, and those who decide to turn it off can probably decide to turn it on if they want to use the site properly.
Same for cookies.
|
|
|
|
|
Far too often you'll be greeted with a blank page. But I don't recall seeing a deprecation notice for the <noscript> tag in any HTML 4.0 book.
Standards and best practices. Where are they?
Q. Hey man! have you sorted out the finite soup machine?
A. Why yes, it's celery or tomato.
|
|
|
|
|
Nice to have it but in current days its quite became a web requirement...
|
|
|
|
|
That's true. However if someone visits your site using the NoScript plugin with Firefox, and they report an error to you.
How do you differentiate a genuine site error (blank page) from plain and simple script-blocking if the visitor isn't made aware that your site requires javascript.
IOW they won't bother reporting a problem, and you won't start hunting down a phantom problem.
Q. Hey man! have you sorted out the finite soup machine?
A. Why yes, it's celery or tomato.
|
|
|
|
|
I can create a asynchronous call using java script and that request will fetch client details with that javascript on flag and if any user report error but i could not found javascript flag on that's mean the guy try to access my web site without enabling JS.
|
|
|
|
|
Doesn't server variables provide that (browser capabilities) info as soon as session is made with client?
If you provide non-JS web content that's absolutely great. I wish there were more like you.
Q. Hey man! have you sorted out the finite soup machine?
A. Why yes, it's celery or tomato.
|
|
|
|
|
You miss understand me...
When ever a Request is made by client that context also contains few details about client I was try to mean that.
|
|
|
|
|
yes. that's what I thought. Server gets the browser info as soon as the client requested any content.
No need for the server to make further tests of visitor's browser. But your original explanation seemed to suggest making further test of client's browser capabilities. --> "I can create a asynchronous call using java script"
Q. Hey man! have you sorted out the finite soup machine?
A. Why yes, it's celery or tomato.
|
|
|
|
|
In our scenario, we are mapping census data to show how similar geographic areas compare to each other in terms of population, income, race, or education level. Before you start writing any code, you’ve got design issues that matter not just to aesthetics, but to the reader’s comprehension of the presentation. So how do you choose color? What colors are the “right ones”? The key is that color is relational. In any composition or layout, a single color does not exist in a vacuum, but is always comprehended in relation to the other colors present. Maps are just one possible view of a dataset, and color choice can help decipher that map data.
|
|
|
|
|
FPGA technologies had 'leveled the playing field'. A kid can save up $50 to buy a devboard, load up some free software and create a never-before-seen brilliant new CPU design. And implement it, without a million-dollar fab cycle. And it will run at clock speeds of at least tens of MHz. So where are all the new brilliant CPU designs, from kids or grownups? Where are the original ideas and breakthroughs? Sure there are some improvements such as clever cache designs, branch prediction, out-of-order code execution. But most processors we see today are pretty much ripped from the pages of dusty old computer architecture books. I've been trying to find something new and exciting for a while. When I feel particularly clever I sit down with a clean FPGA and try to write 'The Great American Processor' (TGAP). It is a humbling experience, and I strongly suggest it to all of you, for those times you feel especially clever. Implementation notes and code for a slightly different kind of a CPU.
|
|
|
|