Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Re:Wow, so yet another screen size (Score 1) 134

Actually, Dreamweaver is quite good at dynamic layouts and assisting you in proper website creation. The HTML is usually pretty clean.

But static HTML is so last millenium. ^^

Look at the code of that page (Warning: This was never finished, so expect bugs.), and count the number of HTML tags in there, compared to the actual content. ;))

Comment Re:Lessons Learned (Score 1) 222

I get what your saying but...c'mon. Artists shouldn't have to ask permission to do their work.

They're not doing THEIR work, they're adapting SOMEONE ELSE's work. And it's not like Nintendo is abusing a copyright that should have long-since expired by now, either... they're perfectly within their legal and moral right in this case.

If they wanted to make a fantasy movie, and more power to them, they could have made an *original* one, making it an original work. Then I might be able to respect the film.

The only reason they did a Zelda adaptation in the first place is to cash-in on the name recognition. Cha-ching.

Comment Re:Because obscurity... (Score 1) 379

You are missing the point.

They were trying to keep something a secret, and then someone sworn to keep that secret, leaked it. That is absolutely a cause for concern.

OK, that's an interesting point. I can't find anything in the memo that says anything about being secret. Indeed, from my reading of it, basically every aircraft operator and every person in security at every airport would have needed to read the memo to implement what was in it.

    So, we have a document, not labeled secret in any way that I can find, that hundreds of thousands of people must read and understand. By what reasoning do you conclude that everyone looking at the memo was sworn to secrecy?

Comment There are none so blind as... (Score 1) 257

those that refuse to see...

Some software lasts decades and has big side effects. Techniology management is ephemeral, with life-spans measured in months, rarely years.

Managers knowingly mandate stupid decisions, because there is no personal downside and a short term budget upside.

Y2K was because large organizations (or the incumbent management) repeatedly ignored technical advice to allow for 4 digit years, because it saved a few bytes storage for each date (which was significant back then) and they could argue "that problems still 15 years away, we will replace it", "that's still 10 years away, we may replace it", "that's still 5 years away, maybe we can fix it later", "that's still 2 years away, we are asking for a Y2K budget"...

Y2K? Oh Sh*t Fix that now..., then blame the developers!

Technology "management" typically refuses to see or respond to anything with an effect longer than their own Mayfly existence. At the same time mangers (as a group) are hypocritical and unethical enough to blame others, when the fertilizer hits the windmill... Couple that asshattery with a wilfully ignorant and fear mongering media, and you have the recipe for shifting the blame from chronic management incompetence to "the techies did it..." which is completely bogus.

There are few, if any, real technical issues remaining unsolved for most business purposes, and none that go completely unpredicted by systems analysts.

There are an enormous number of fundamentally incompetent CIO's and (worse) "Project managers", who should not be permitted the long term indirect technical influence they possess.

Their myopic decisions can cause potentially dangerous and expensive impacts on society, such as Y2K.

The negative influence, spin, and misleading media, continues; for example, the poor design of security in most commercial applications is directly attributable to short term "not my problem" management thinking.
Fortunately, we have better controls on building bridges than we have software, but the impact of some types of software is now much more serious and far reaching than mere mechanical and civil engineering.

Technology management needs a better professional accreditation and system of ethics, see acm.org for in depth discussions.
In particular, the ludicrous notion that you can manage construction of something you don't understand, (and don't attempt to understand) )by setting arbitrary dates and budgets, is commonplace in IT.

When the time comes to fix the next disaster, our failure to fix chronic management incompetence, will be the root cause.

Comment Re:Lessig on what plex is really important (Score 0, Flamebait) 106

No matter how much people hate Microsoft, comments like this may me despise the free software movement. Somehow, i have this idea that MS providing 50,000 jobs, Microsoft funneling BILLIONS into research and believe it or not, Microsoft making some great products is a *GOOD* thing. The FSF has its merits and should do more to be a leader of what MS could do rather than dividing the community into believers or non believers for all the wrong reasons.

As for codeplex itself, there is some amazing projects in there and i doubt MS is gonna piss away the effort. THey're just like google in many ways with their online presence where they test the waters and see if it sticks, but that *IS* business my friends.

Comment Re:Not suprised that Zilch is leading for now. (Score 1) 596

Rather than write them all off, you could simply have a look at their financials and decide for yourself. Most major charities publish this information and you can see how much of your donation will be used for administrative costs. Some of the better ones actually let you mark your donation such that it cannot be used for administrative costs.

While I appreciate the sentiment of your post, there exists economies of scale in relief efforts, so fragmenting everything locally for fear of administrative waste is foolish. Do a little homework and donate accordingly.

Slashdot Top Deals

Suggest you just sit there and wait till life gets easier.

Working...