Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Re:Maybe they shouldn't use Javascript ... (Score 1) 225

Which is of course, why you shouldn't be rendering anything on the CPU ;)

The CPU shouldn't be doing anything other than issuing draw calls to the graphics hardware.

Further to that. Your assertion is effectively equal to "it's reasonable to use all the CPU to do nothing but render the screen on 5 year old hardware".

That's clearly not true.

Comment Re:Maybe they shouldn't use Javascript ... (Score 1) 225

Why the hell would anything be in the CPU's memory when you're rendering the screen? All of this should be happening on the GPU, without any bitting of things from CPU memory.

If you're spending 2ms per frame to do nothing but render windows in a standard windowing environment, then you're wasting *huge* amounts of resources. 2ms is enough to render hundreds of draw calls with millions of polygons.

That's why you don't see your system sat their idling at 13% CPU usage as you drag a window around the screen.

Remember - your system today is roughly 10 times faster than the system you had 4 years ago. Are you trying to claim that 4 year old systems needed 100% of the CPU just to render windows on the screen?

Comment Re:Holy Blinking Cursor, Batman! (Score 1) 225

I mean, those 80s graphics books are well worth having, and excellent sources of how to take shortcuts when shortcuts are necessary.

However, it's worth remembering, that they're exactly that - shortcuts. The techniques used in those books are usually much less general than those used by modern windowing systems, and because of that, don't support all kinds of things that turn out to be important to user experience.

They don't support doing any kind of blending of layers, only blitting bits. They don't support any kinds of transforms on things that you're bitting. They don't support being able to smoothly animate things.

All of these are livable with, but not a great user experience. Hence why we've moved away from them, and to applying general purpose massively parallel compute to the embarrasingly parallel task of drawing things on a screen.

Comment Re:clearly the truckers are right (Score 3, Informative) 331

It's clearly not because they're a single item, or the previous item in the list would have had "or" instead of a comma.

If the intent had been that this was one item, the law would have said "The canning, processing, preserving, freezing, drying, marketing, storing or packing for shipment or distribution of: (1) Agricultural produce; (2) Meat and fish products; and (3) Perishable foods."

Comment Re:Scary stuff (Score 0) 279

We are already there, the problem is that there's a bunch of people who's opinion is "well, it doesn't affect my property, since that's all in oil that's well inland; thus the answer is we do nothing".

They all like to disguise the argument "we do nothing, and fuck everyone that isn't me" as "well, the evidence really isn't very strong, I mean, I'm not convinced it's really happening"

Comment Re:"universal" (Score 4, Insightful) 207

As soon as you introduce selective DRM for selected platforms and devices, it's not universal anymore.

Which is rather the point. By including DRM in the standard, you allow everyone to implement the exact same thing, and make it universally available on all devices.

By not including DRM, you would cause all the companies that wanted it to go away and implement it in some weird, proprietary way, that only works on the biggest platforms.

You get support for more devices by putting it in the standard, not fewer.

Comment SUBJECT REQUIRED (Score 4, Interesting) 82

With life being at least 83% as old as the planet according to this result, it makes me begin to wonder "has life been on earth ever since it formed?"

That's clearly not a question we're going to answer today, but it might have drastic impacts on the drake equation if there was some requirement for life that has to happen as the planet forms.

Comment Re:Perhaps a better method... (Score 1) 1001

1.) Who cares if someone knows bubble sort (or insertion or quick or merge or whatever you please). Particular algorithms are well defined tools that good programmers don't re-invent. Much better to determine if that person knows the right tool to use for a particular job. In other words, a question like "what type of sort would you use with sets of data that are nearly, but not completely in the desired order" or better yet "what different types of sorting are there, and why would you choose to use one over the other"? To put in in other terms, If you were interviewing a plumber, would you ask them how to make a pipe wrench or would you ask them what type of wrench to use to tighten a loose fitting?

That's rather the point - I'm not trying to hire a programmer - I'm trying to hire a software engineer.

If I were trying to hire a programmer, sure, your plumbing type questions make sense. But since I'm trying to hire someone who can do the software equivalent of designing pipe wrenches, I'd better ask them questions about that.

Comment Re:Perhaps a better method... (Score 1) 1001

If the interviewer is asking you trivia that they've got memorized, they're not going to be impressed at you flailing around trying to work it out from scratch.

Yup... that's why a good interview involves doing a problem on a whiteboard, not sitting there asking trivia.

Slashdot Top Deals

"An idealist is one who, on noticing that a rose smells better than a cabbage, concludes that it will also make better soup." - H.L. Mencken

Working...