Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Re:Going for a run or a ride... (Score 1) 222

I find my efficiency increases by sequentializing the tasks into a stream. Research I've read seems to back this up. We're not meant to do a lot of context switching (the brain sucks at context switching). That's also why it's better to group tasks together by subject matter, even if that means you'll do a low priority task before a high priority one.

Comment Emulation? (Score 1) 426

Wouldn't it be better to use the emulation route? For example, writing a program for the original gameboy, and running it through the emulator. I remember at university we learned assembly on an emulated MIPS. We could focus on the individual instructions, on hardware that was simple and clean, but it all ran on the unix servers (x terminals).

Comment Re:Human nature (Score 2, Insightful) 276

Governments can't hold on to infrastructure that can be exploited commercially. Whether it's buildings or cable networks, eventually it gets sold off to balance that year's budget. The belgian government went on a decade-long selling spree to balance a structurally unbalanced budget, and the consequence is that now there are gigantic budget issues and the government needs to make the deepest cuts in the history of the country.

In other words, just another typical government.

Comment Re:Update often please! (Score 2, Insightful) 271

I'm glad they didn't implement those form elements, because once they implement a part of a standard, their implementation becomes the rule. If they implemented HTML5 form elements now, that essentially means marking the current HTML5 draft as finalized. I don't think that would be good for HTML5.

Comment Re:PNG too (Score 1) 271

PNG is also about 14 or 15 years old, but IE still cannot handle its color correction chunks (gAMA, iCCP) properly:
http://www.libpng.org/pub/png/png-gammatest.html

Only firefox renders that page correctly. All the other browsers fail in some way. Chrome doesn't even support color profiles at all.

IE9 's platform preview supposedly has full support for gamma, and v2 and v4 color profiles, but it has issues rendering that page. I'll report that page in their bugtracking system, so IE9 has fully accurate color rendering by release time.

Comment Re:IE turns 15... (Score 1) 271

And all of that for what? Pretty graphics (Aero) that will be turned off right after Autorun?

If they're pretty, why do you turn them off? They run on the graphics hardware, so they don't affect the performance of your apps.

Why is it that a linux system isn't configured well if it doesn't run compiz, but at the same time aero on windows is a bloated monstrosity that needs disabling?

Anyway, the main reason to run windows 7 is responsiveness. XP regularly blocks if you're multi-tasking, because it has lousy CPU scheduling and no IO scheduling. Windows 7 remains responsive in almost all situations (at least in my personal experience).

Comment Re:IE for other platforms (Score 1) 271

This isn't limited to IE though. Mac Office has vast incompatibilities with the windows version (most notably a lack of support for macro's, which they'll rectify in the next release).

It's because the mac team at microsoft is completely separate from everyone else.

Comment Re:Using the wrong benchmark... (Score 1) 222

So any web site which uses Javascript is open to compromise and therefore could become a mal-Javascript distributor.

XSS leverages javascript, sure, but there are many ways of breaking a site's security without using javascript. Javascript itself is not a security problem, since it runs in a sandbox. Security problems, even those manifested through javascript, are always caused by bad design on the back-end (not filtering user input correctly).

The overemphasis on how fast Javascript runs seems to be due to a lack of serious thought as to how to make browsers better at doing what they were designed to do -- which was *not* to run "web-apps". We used the Internet very successfully for over a decade to provide information -- not to run apps -- if it wasn't (isn't) broken why the emphasis on fixing(?) it?

Just like the purpose of land-line communication has changed from voice calls to data, so is the purpose of browsers changing from document viewing to applications. The browser as a rich app platform is a good thing. It takes a lot of worry away from end users (upgrading, security, installation, ...). In the long run, we're all going to have better and easier to use apps because of it. We're finally going to be able to get rid of our personal computer as a physical piece of hardware. A PC should be a metaphorical construct that follows you around as needed, regardless of the hardware involved. The web is the only credible way of doing that.

I note this with an aside that the U.S. Government (NIH NCBI) no longer allows complete access to its *public* databases, e.g. PubMed, by browsers which do not have Javascript enabled. (One is compelled to ask *who* for the most part paid for that information but can no longer access it?).

Javascript is as essential to a modern browser as HTML and CSS. Disabling javascript has no point anymore (ever since accessibility products learned to cope with ajax). If you're talking about using tools like curl to extract content, then I agree that ways have to be provided to easily obtain all the content from a site. That doesn't mean that these sites should cater to the lowest common denominator and give everyone a shitty experience to allow a corner case. It just means they need to implement the corner case as a separate solution. Ever used a web app without any javascript? It's always a lousy experience. I don't see why that should be foisted on all users.

Comment Re:Too little, too late... (Score 1) 222

The memory use was either misinterpretation of statistics (happens often), or plugins. Firefox itself doesn't have a memory problem, but its plugins and add-ons do have major memory and stability issues. A clean firefox install with a clean profile and no addons or plugins is almost invulnerable. You might argue that it's also near useless, but the reality is that the other browsers are just as vulnerable to plugin and addon issues.

Now that flash is running in a separate process (as of FF 3.6.4) we can finally see that it's the flash plugin that's taking up the majority of RAM (at least, that's what I see on my system).

Slashdot Top Deals

The trouble with being punctual is that people think you have nothing more important to do.

Working...