|
Until IE supports what the other guys do, I'll keep blaming it. Get me CSS3 supported gradients instead of having to use SVG backgrounds. Get me web workers. Mobile browsers support more than IE9 does. Sure, those are in IE10 but that's not available unless you have Windows 8.
|
|
|
|
|
Terrence Dorsey wrote: if you build things correctly, your sites and applications work in them all.
That's not entirely true. If you handle all the nuances correctly, then it will work for all of them. But that's the thing, why should there have to be a single IF statement for checking which browser you're using in order to render the page correctly?
|
|
|
|
|
If they were supposed to work the same in every browser they'd be called standards. Oh, wait...
|
|
|
|
|
Master Wq was addressing some Vim novices. After his lecture on the many virtues of Vim, he asked if there were any questions. A young man raised his hand. “Master, by what means might one filter for the second column of a plaintext table for all rows that contain the string ‘tcp’?” Zen mind, newbie mind.
|
|
|
|
|
GUIs have even reinvented the world of software development, beginning with tools like Visual Basic, before extending coding tasks to the average joe with new-age tools such as Scratch and Google’s App Inventor. But among hardcore computer types the command line persists. If you’re a developer or a sysadmin, there are times when it makes more sense to use the command line interface, or “shell,” built into operating systems like Linux and UNIX. Do you get more done here? %
|
|
|
|
|
Yes. I spend most of my day in a DOS box -- it's where it's at.
There are very few tasks where a GUI is superior.
|
|
|
|
|
Does it make sense to carry around two, three, or more portable computing devices? I’m sure lots of people will carry more than one device. Me, I use the big laptop because I do multimedia grinding. I use the small tablet because it makes my hands and eyes happy. I carry a phone because it’s always online. How many devices do you carry during the day?
|
|
|
|
|
|
Terrence Dorsey wrote: How many devices do you carry during the day?
That depends on what I put in my backpack the night before!
Bill Gates is a very rich man today... and do you want to know why? The answer is one word: versions.
Dave Barry
Read more at BrainyQuote[ ^]
|
|
|
|
|
Technology is adapting, trying to keep up with our needs and how we handle things. How come then, that the email never really changed? When the first email was sent in the 1970s there was no big difference to the email we know today. ...or why I live at the inbox.
|
|
|
|
|
Probably the same reason that letters (snail-mail) haven't really changed much since 1840: they work. (Okay, not as popular because of email but still relatively unchanged from the time of the first postage stamp until now).
You can whack all sorts of work-flow and other goodies onto email but at the end of the day it's just a message.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
Before Linux was around there was a huge problem on the UNIX-based operating systems, since they were all proprietary and each OEM had their own version of the OS. Now, if you look carefully and you’ll notice that the same is happening with Android.... Everyday Android feels a lot more like vaporware for me. Interesting view from someone who thinks Blackberry is a compelling alternative.
|
|
|
|
|
I closed the page when I saw the usual crap about HTML 5 being the "future".
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|
=====
===
=
|
|
|
|
|
I have always half-jokingly taken credit for inventing the @reply on Twitter. Recently, user @rabble put together a blog post titled Origin of the @reply - Digging Through Twitter’s History, in which he did some research to show when it was first used. Only his research isn’t entirely correct and it doesn’t give fair credit to everyone involved. Those who forget history are condemned to @reply it.
|
|
|
|
|
Hadoop is firmly planted in the enterprise as the big data standard and will likely remain firmly entrenched for at least another decade. But, building on some previous discussion, I’m going to go out on a limb and ask, “Is the enterprise buying into a technology whose best day has already passed?” GFS, MapReduce and you.
|
|
|
|
|
Daily Code Drills is an experiment by Zed Shaw, creator of the Learn Code the Hard Way series of tutorials, to see if a daily drill in Python or Ruby helps build your coding muscles. Try to do this every day for as long as you can or until you can do the whole thing in 10 minutes. Where is your drill sergeant, men? Stack traced, sir!
|
|
|
|
|
The beaurocrats are taking over - oh yawn.
What about a daily drill of actual work - radical idea I know.
Peter Wasser
Art is making something out of nothing and selling it.
Frank Zappa
|
|
|
|
|
Self-publicist.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
We already know there are tools to measure how fast a program runs. There are programs called profilers which measure running time in milliseconds and can help us optimize our code by spotting bottlenecks. While this is a useful tool, it isn't really relevant to algorithm complexity. Algorithm complexity is something designed to compare two algorithms at the idea level — ignoring low-level details such as the implementation programming language, the hardware the algorithm runs on, or the instruction set of the given CPU. We want to compare algorithms in terms of just what they are: Ideas of how something is computed. Algorithm complexity is just a way to formally measure how fast a program or algorithm runs.
|
|
|
|
|
<algorithm complexity="" is="" just="" a="" way="" to="" formally="" measure="" how="" fast="" program="" or="" algorithm="" runs="">
Err... no, that's completely wrong.
Algorithm complexity has almost nothing to do with how fast the algorithm runs.
How fast an algorithm runs depends on the machine it's running on, the language it's written in, how well the algorithm has been coded, and many other factors besides.
Algorithm complexity is a measure of how difficult it is to derive the algorithm outputs from the inputs.
|
|
|
|
|
pt1401 wrote:
Algorithm complexity is a measure of how difficult it is to derive the algorithm outputs from the inputs.
but the main reason anybody cares about algorithmic complexity (outside of pure academic research) is because studying an algorithm, determining its complexity, and then searching for a simpler method, is a path to performance gains. end users, library callers and QA testers do not care how "difficult" the algorithm is, they just want the algorithm to turn input into output as fast as possible.
|
|
|
|
|
Complexity is a pretty generic term. Perhaps it's algorithm performance complexity vs algorithm design complexity. Though, the term "complexity" does imply nuance more than magnitude. Maybe a better term would be "algorithm efficiency".
|
|
|
|
|
Daniel Clifford recently gave a great talk at Google I/O 2012 called “Breaking the JavaScript Speed Limit with V8″. In it he goes in depth to explain 13 simple optimizations you can do in your JavaScript code to help Chrome’s V8 JavaScript engine compile / run your JavaScript code faster. In the talk he gives a lot of great explanations as to what they are and why they help, but if you just want the quick and dirty list, here goes... Better than it ran before. Better, stronger, faster...
|
|
|
|
|
Some developers waste time waiting for their employer to train them on new technology or complaining they aren’t getting the training to stay current. While companies continue to cut training budgets, every developer should take the initiative to educate themselves, especially with so many free resources available on the web. When a developer takes risks like this, everyone on a team benefits. You really need to come out of the dark ages of software development.
|
|
|
|
|
Somehow felt that the article was a smart ad for Scala :P
|
|
|
|