Do you really think the oppressive government would do nothing to detect any suspicious radio activity? Especially considering a very poor country like Burma where not many people have a radio transmitter. A packet radio could very well put a freedom fighter in danger.
No, your images is just an often-cited example of what image inpainting could do. And image inpainting has nothing to do with the new resize algorithm talked about in the article, although similar effects are achieved in this specific case.
Five years ago the Linux desktop was all talk. The code was there, but few people treated it seriously.
Now it's being put into action. Instead of hot air we're having the real stuff on the market. (e.g. Dell selling Linux desktops due to popular request)
This would render the machine unusable.. until about a year back, when something changed - which leads me to suspect that the kernel has had protection against this sort of thing for a while now.
I guess they just put on a nproc limit on each user. It's just a trivial security measure against simple fork bombs. Assuming your Linux system uses PAM (most modern distros do), take a look at/etc/security/limits.conf.
If I were to write a summary of GPL for the general public, I would write something very similar to that.
The Slashdot summary, however, seems like a flame bait to me.
Re:FC5 should have been supported for 2 years!
on
Fedora 7 Released
·
· Score: 1
Writing a long passage does not change the fact you installed something experimental on a production server. Do you install a random CS research project from a university in your production server, and complain to that university when they are not supporting you? (say, because the Ph.D student who was responsible just graduated and went to Google)
It is ok for an open source project to do this because the open source project have never given you any guarantees in the first place. No guarantees, it is written clearly in the license. You have never paid anything for Fedora support in the first place. If you need industrial quality support buy RHEL from Redhat - it exists for a reason.
And when you're fighting a monopolist, every sale or install that you give up through rudeness, through arrogance and most especially through broken promises and lies is one install too many!
There are always unreasonable and crazy people who you can't satisfy. "Why can't Linux walk my dog? I want Linux to clean my toilet and walk my dog too!" Considering that the average open source project has no resource to hire enough customer supports to listen to profanities all day long, losing these people is actually a good thing.
The forum in question was inside the adult section of Uwants. There used to be a forum there that focuses on adult pictures, but that particular forum has been removed since the incident.
There are many little funny things that just happens when you're coding a web application in JavaScript without a framework/library/toolkit helping you. Unless you're really an AJAX/JavaScript wizard, coding an AJAX-enabled web application on your own and mixing online code receipts is a very dangerous thing to do.
Browser inconsistencies
This is the most obvious one, but only the entry to the rabbit hole. If you are not familiar with the example (maybe not exactly the same, but any AJAX web developer worth his salt should have seen one like that) I give below, then please, PLEASE, do yourself, your fellow developers and your users a favor, resist the urge to hack things together for once, use a mature AJAX framework.
An important part of AJAX is that you need to update what is displayed on the web browser in the client side (by JavaScript), without refreshing the page. This implies that you're very likely to have to create and destroy DOM nodes on the fly. Now, how do you create a radio button in JavaScript?
That's what you would do if you follow the DOM standard. But sorry, this does not work. Try to create a radio button with the above code segment in Internet Explorer 6, you'll get a broken radio button - you can't select it. The correct way to create a radio button by DOM manipulation is described in this MSDN article:
Memory leaks
The last one was easy. Do you know you can make a web application that leaks memory like a sieve in Internet Explorer 6 by making a simple circular reference like the following one?
var node = document.createElement("div"); node.someAttr = node;
If you're a good programmer, I might have sounded an alarm in your head right now - any circular references involving DOM nodes in IE6 results in memory leaks that persist after URL changes or page refreshes - unless you use an AJAX toolkit that takes care of the issue for you. Have you assigned a DOM as an attribute value under another DOM node in the past? Yes? Then you'd better check your web application for memory leaks with Drip, now.
What's more, it's not just assigning DOM nodes as attributes that would result in memory leaks, closures in JavaScript can also form circular references and cause memory leaks. What makes closures particularly dangerous is that circular references with closures are not easy to spot. For example, the following code segment leaks:
var node = document.createElement("div"); var clickHandler = function(){}; node.onclick = clickHandler;
Looks innocent enough, but you've already formed a leaky circular reference here. node->clickHandler->node.
The XMLHttpRequest object is not as simple as you think
Much of the magic of AJAX comes from the XMLHttpRequest object (or its ActiveX equivalent, or an iframe, etc.), right? Sure. If you're only doing something simple via AJAX (like, updating the server time), then you can just copy an XMLHttpRequest code snippet from sites like this and hack away, right?
Because there are many situations where you can't just run Ruby or J2EE at the web server. e.g. when you're developing a web admin UI for a router or any cheap embedded devices for that matter.
Both the Chinese test and the British test were only testing for elementary trigonometry stuff. The only difference being that the Chinese test requires you to be more careful and give more effort. It is just more tedious, but not difficult.
By the time the Professors reached out for him, it was already too late. He was already mentally ill by then, and much more than just "reaching out" had to be done to reverse it.
Last but not least, Wikipedia the doll!
*squeezes doll* - "May the Knowledge be with you!"
[to those who are not aware, parent was paraphrasing a quote from the movie Spaceballs, you can find the relevant quote here, how nobody recognized the humor (wake up mods, toilet paper??) and modded parent insightful was beyond me]
I kept hearing about the "stick to the standards and it will work everywhere!" argument in the replies. But in my experience, this advice only works when you're making simple websites. Try a little bit of good old DHTML or even AJAX and your "sticking to standards" web page breaks down in no time. I would go as far as to claim even things you taken for granted in a sane programming environment would often break down in IE without you noticing what went wrong, I won't prove this claim here, but an example is the memory leak problem in IE6.
First, lets see what's wrong with the "stick to the standards.." argument. If sticking to standards frees you from the troubles of IE, then why isn't the Acid2 test working on IE7? Acid2 sticks to the standards, specifically, it is a test for the CSS standards, and it's not working.
You may say Acid2 uses obscure CSS tags that nobody would use. Then let's try some common DOM alright? Say you want to create a radio button in Javascript via DOM methods. What's the standard way to do that?
var b = document.createElement("input"); b.type = "radio"; b.name = "..."; b.value = "..."; formNode.appendChild(b);
Try this in IE6 (still the dominant browser), the radio button is created, but it doesn't work - you cannot check it by clicking on it. The above code works perfectly in Firefox or Safari. Standard compliance frees you from trouble? My ass!
How, then, can you make a working radio button via Javascript in IE? You HAVE to use non-standard ways. This is how you make a radio button, from MSDN:
var newRadioButton = document.createElement("<INPUT TYPE='RADIO' NAME='RADIOTEST' VALUE='First Choice'>")
See? You cannot simply stick to the standards and expect a working web application.
Record mistakes happen in large bureaucracies all the time, they would be stupid if they don't allow a reasonable mechanism for correcting mistakes by the citizens.
Slashdot Mirror
Do you really think the oppressive government would do nothing to detect any suspicious radio activity? Especially considering a very poor country like Burma where not many people have a radio transmitter. A packet radio could very well put a freedom fighter in danger.
You can apply a known force to the mass and see how much it accelerates.
I stopped reading when you said astrology is a kind of science.
No, your images is just an often-cited example of what image inpainting could do. And image inpainting has nothing to do with the new resize algorithm talked about in the article, although similar effects are achieved in this specific case.
Five years ago the Linux desktop was all talk. The code was there, but few people treated it seriously.
Now it's being put into action. Instead of hot air we're having the real stuff on the market. (e.g. Dell selling Linux desktops due to popular request)
I don't think that's bad at all.
I guess they just put on a nproc limit on each user. It's just a trivial security measure against simple fork bombs. Assuming your Linux system uses PAM (most modern distros do), take a look at
If I were to write a summary of GPL for the general public, I would write something very similar to that.
The Slashdot summary, however, seems like a flame bait to me.
It is ok for an open source project to do this because the open source project have never given you any guarantees in the first place. No guarantees, it is written clearly in the license. You have never paid anything for Fedora support in the first place. If you need industrial quality support buy RHEL from Redhat - it exists for a reason.
There are always unreasonable and crazy people who you can't satisfy. "Why can't Linux walk my dog? I want Linux to clean my toilet and walk my dog too!" Considering that the average open source project has no resource to hire enough customer supports to listen to profanities all day long, losing these people is actually a good thing.
You can upgrade from Fedora 5 to Fedora 6 via yum
/ upgrade-fc5-to-fc6-with-yum/
http://www.ioncannon.net/system-administration/99
Why not? I'd be delighted to see how it works.
and Hong Kong has 1000Mbps to the home... 3 years ago
3 067
http://www.lightreading.com/document.asp?doc_id=6
Beryl doesn't need a high end video card at all, you can use a GeForce 6200A and play with any eye candy you want.
Same for H.264 decoding.
http://bestpractical.com/rt
It was what my previous employer used. It has lots of features, and is quite easy to use and setup.
If you can read Chinese, here is the local news entry:
http://hk.news.yahoo.com/070510/12/276r4.html
The forum in question was inside the adult section of Uwants. There used to be a forum there that focuses on adult pictures, but that particular forum has been removed since the incident.
Broadcasting makes sense when you're talking about wireless networks instead of wired networks. Isn't everybody getting wireless these days?
Browser inconsistencies
This is the most obvious one, but only the entry to the rabbit hole. If you are not familiar with the example (maybe not exactly the same, but any AJAX web developer worth his salt should have seen one like that) I give below, then please, PLEASE, do yourself, your fellow developers and your users a favor, resist the urge to hack things together for once, use a mature AJAX framework.
An important part of AJAX is that you need to update what is displayed on the web browser in the client side (by JavaScript), without refreshing the page. This implies that you're very likely to have to create and destroy DOM nodes on the fly. Now, how do you create a radio button in JavaScript?
How about...
That's what you would do if you follow the DOM standard. But sorry, this does not work. Try to create a radio button with the above code segment in Internet Explorer 6, you'll get a broken radio button - you can't select it. The correct way to create a radio button by DOM manipulation is described in this MSDN article:
Memory leaks
The last one was easy. Do you know you can make a web application that leaks memory like a sieve in Internet Explorer 6 by making a simple circular reference like the following one?
If you're a good programmer, I might have sounded an alarm in your head right now - any circular references involving DOM nodes in IE6 results in memory leaks that persist after URL changes or page refreshes - unless you use an AJAX toolkit that takes care of the issue for you. Have you assigned a DOM as an attribute value under another DOM node in the past? Yes? Then you'd better check your web application for memory leaks with Drip, now.
What's more, it's not just assigning DOM nodes as attributes that would result in memory leaks, closures in JavaScript can also form circular references and cause memory leaks. What makes closures particularly dangerous is that circular references with closures are not easy to spot. For example, the following code segment leaks:
Looks innocent enough, but you've already formed a leaky circular reference here. node->clickHandler->node.
For more information about memory leaks under IE6, read these:
Mihai Bazon's blog entry
MSDN's lengthy and confusing description of the problem
The XMLHttpRequest object is not as simple as you think
Much of the magic of AJAX comes from the XMLHttpRequest object (or its ActiveX equivalent, or an iframe, etc.), right? Sure. If you're only doing something simple via AJAX (like, updating the server time), then you can just copy an XMLHttpRequest code snippet from sites like this and hack away, right?
Because there are many situations where you can't just run Ruby or J2EE at the web server. e.g. when you're developing a web admin UI for a router or any cheap embedded devices for that matter.
What? I thought a billion is less than a million?
After all, why make billions when you can make... millions?
Both the Chinese test and the British test were only testing for elementary trigonometry stuff. The only difference being that the Chinese test requires you to be more careful and give more effort. It is just more tedious, but not difficult.
By the time the Professors reached out for him, it was already too late. He was already mentally ill by then, and much more than just "reaching out" had to be done to reverse it.
Load up an a 1GB array and sort it with your code, tell me, is it O(1) anymore?
I hate to say it but at least the I-reinvented-radix-sort kid did some experiments...
Last but not least, Wikipedia the doll!
*squeezes doll* - "May the Knowledge be with you!"
[to those who are not aware, parent was paraphrasing a quote from the movie Spaceballs, you can find the relevant quote here, how nobody recognized the humor (wake up mods, toilet paper??) and modded parent insightful was beyond me]
First, lets see what's wrong with the "stick to the standards.." argument. If sticking to standards frees you from the troubles of IE, then why isn't the Acid2 test working on IE7? Acid2 sticks to the standards, specifically, it is a test for the CSS standards, and it's not working.
You may say Acid2 uses obscure CSS tags that nobody would use. Then let's try some common DOM alright? Say you want to create a radio button in Javascript via DOM methods. What's the standard way to do that?
Try this in IE6 (still the dominant browser), the radio button is created, but it doesn't work - you cannot check it by clicking on it. The above code works perfectly in Firefox or Safari. Standard compliance frees you from trouble? My ass!
How, then, can you make a working radio button via Javascript in IE? You HAVE to use non-standard ways. This is how you make a radio button, from MSDN:
See? You cannot simply stick to the standards and expect a working web application.
Before the release date, a killer feature is clearly understood and completely unknown to a VP of Microsoft at the same time.
Record mistakes happen in large bureaucracies all the time, they would be stupid if they don't allow a reasonable mechanism for correcting mistakes by the citizens.