Yes we know about Google's censorship, and we can read (and even write on)/. .
There's a lot of us who think that censorship is stupid. There's also a lot of people who desire that even more censorship happen. Sometimes they have the upper hand, sometimes we do. But we tend to have civilised discussions and can disagree.
The problem is when the political nuts get their hands on issues, and start inciting violence. The challenge is to support freedom of speech while not giving the nuts on any side too much fuel to make it into a major political issue.
Like (I suspect) computer code, the file should stand on it's own - a competent fellow professional should be able to fully understand it and be comfortable reaching the same conclusions
The magic word here is competent. If all programmers were equally competent, then things would be easy. They aren't.
Some people find one-liners easy to read. Others find that the one-liner is too complex. Some find it easy to work with immutable data structures and message passing. Others cannot live with complex, heavy objects, mutable data structures and method calling.
Given the level of variation in programmers (and the quality output), it is hard to follow a specific policy on comment quality.
Data transfer to/from the Amazon cloud is expensive. By using the signature of an embedded device, you get a much smaller and lighter page, which should also be easier to machine parse.
Using a factory when you have functional language style functions available is stupid. Take a look at Peter Norvig's presentation on design patterns in functional languages for what patterns from the GoF are redundant.
This depends on the language you are working with, but a general rule is to have a function do one thing, and do it well. Follow the same rules for functions as for Unix programs.
You may find it useful to learn about Object Oriented Programming (at least about encapsulation, composition and inheritance from OO).
Learn a functional programming language like Haskell, Scheme or LISP. Those teach you about being able to build abstractions even in your code structure and the benefits of encapsulating state.
Learn a message passing language like Erlang (or an event driven framework).
Being able to separate your code into small logical pieces makes it easier to understand, test and maintain.
Right. We should follow historical precedent and send our poor and criminals out of the country. Preferably to some place over the ocean. Might as well send them to the US. Ideally with measles and drug resistant TB infected blankets.
You assume that the time of release was a coincidence. It was not. Speaking of which, we need to switch to SSL and PGP for communication. KSP at FOSS.IN.
There was this little company named Compaq, which pretty much wrote the legal standards for clean room reverse engineering in court. They blew open the IBM PC Compatible market (aka clones), and Microsoft got lucky that anyone could run their software on a PC.
Microsoft made the monopoly money with Windows, but prior to that, there was a healthy PC market with lots of OS and hardware options.
The problem is that the scorched earth approach is the only one that truly works. You don't block by domain, you block by client IP. You whitelist regular correspondents, and large mail farms like Hotmail, or Yahoo!.
You end up with very few false positives and large bandwidth savings, especially from an ISP perspective where Bayesian filtering doesn't scale.
The biggest is India's money is fixed against the dollar and we are not screaming that it should be freed. Without a true free market, then it is IMPOSSIBLE for conditions to adjust. This is the worse thing that is happening. India has trade barriers against the west (interestingly, they allow most other nations to have free trade). With those barriers in place, free market can not adjust
The INR is actually pretty freely convertible. The RBI does try to prevent wild fluctuations, but does allow a fairly wide band for the exchange rate movement.
If you want free trade, how about lobbying to allow India to export labour^W services instead of materials? Get rid of the work visa requirement totally, so any Indian can travel to the US and get a job there. Oh, and get rid of those agricultural subsidies.
You can't have free trade only in the goods/services you produce.
IME, you don't need to refactor that much with dynamically typed languages. Also, your refactoring is likelier to be at an architectural/abstraction level rather than the stuff that Java programmers do.
This like changing the type of a method return aren't even likely to make sense in most dynamically types languages. By writing small amounts of code, and aggressively building libraries, your variable name scope is also fairly small.
You don't use a complex inheritance hierarchy, you instead compose your final class. Good coding practice triumphs most of the benefits of a statically typed language.
There are some things which typed languages protect you from, and those should be rare to encounter in practice if you can duck type.
Slashdot Mirror
Yes we know about Google's censorship, and we can read (and even write on) /. .
There's a lot of us who think that censorship is stupid. There's also a lot of people who desire that even more censorship happen. Sometimes they have the upper hand, sometimes we do. But we tend to have civilised discussions and can disagree.
The problem is when the political nuts get their hands on issues, and start inciting violence. The challenge is to support freedom of speech while not giving the nuts on any side too much fuel to make it into a major political issue.
Like (I suspect) computer code, the file should stand on it's own - a competent fellow professional should be able to fully understand it and be comfortable reaching the same conclusions
The magic word here is competent. If all programmers were equally competent, then things would be easy. They aren't.
Some people find one-liners easy to read. Others find that the one-liner is too complex.
Some find it easy to work with immutable data structures and message passing. Others cannot live with complex, heavy objects, mutable data structures and method calling.
Given the level of variation in programmers (and the quality output), it is hard to follow a specific policy on comment quality.
So why can't qsc get IP addresses from RIPE?
s/routable/routed/
RFC 3330 space is routable, it's just blocked by a lot of ISPs. If your ISP doesn't block this at the edge, your IPs can still be routed.
Data transfer to/from the Amazon cloud is expensive. By using the signature of an embedded device, you get a much smaller and lighter page, which should also be easier to machine parse.
Set him on Texas instead?
Using a factory when you have functional language style functions available is stupid. Take a look at Peter Norvig's presentation on design patterns in functional languages for what patterns from the GoF are redundant.
This depends on the language you are working with, but a general rule is to have a function do one thing, and do it well. Follow the same rules for functions as for Unix programs.
You may find it useful to learn about Object Oriented Programming (at least about encapsulation, composition and inheritance from OO).
Learn a functional programming language like Haskell, Scheme or LISP. Those teach you about being able to build abstractions even in your code structure and the benefits of encapsulating state.
Learn a message passing language like Erlang (or an event driven framework).
Being able to separate your code into small logical pieces makes it easier to understand, test and maintain.
Right. We should follow historical precedent and send our poor and criminals out of the country. Preferably to some place over the ocean. Might as well send them to the US. Ideally with measles and drug resistant TB infected blankets.
You assume that the time of release was a coincidence. It was not. Speaking of which, we need to switch to SSL and PGP for communication. KSP at FOSS.IN.
There was this little company named Compaq, which pretty much wrote the legal standards for clean room reverse engineering in court. They blew open the IBM PC Compatible market (aka clones), and Microsoft got lucky that anyone could run their software on a PC.
Microsoft made the monopoly money with Windows, but prior to that, there was a healthy PC market with lots of OS and hardware options.
If that's a GET request, it can be cached. GET semantics imply that the same URL will always return the same value.
Most large providers would need 10X the hardware just to handle current spam loads. I know ISPs whose spam filtering runs into 7 figures in USD.
SPF breaks forwarding. Oh, and SPF itself does nothing much to help stop spam.
It only dooms you puny humans who cannot live in the desert. Now, on to the sandtrouting.
Google: Sagans of servers.
Actually, you should be asking for a television set, not an ebook reader. A wall to wall TV screen.
Summary: "I am Chuck Norris".
Nah, we know who Kernighan is. We have also read 'Reflections on Trusting Trust'.
You are probably off by two orders of magnitude.
The problem is that the scorched earth approach is the only one that truly works. You don't block by domain, you block by client IP. You whitelist regular correspondents, and large mail farms like Hotmail, or Yahoo!.
You end up with very few false positives and large bandwidth savings, especially from an ISP perspective where Bayesian filtering doesn't scale.
The "ant" terminology comes from the chaos/complexity/emergent phenomena fields. Individual ants are stupid, but the behaviour of the colony is not.
It's a technical term from a non-computing field, not a metaphor.
The biggest is India's money is fixed against the dollar and we are not screaming that it should be freed. Without a true free market, then it is IMPOSSIBLE for conditions to adjust. This is the worse thing that is happening.
India has trade barriers against the west (interestingly, they allow most other nations to have free trade). With those barriers in place, free market can not adjust
The INR is actually pretty freely convertible. The RBI does try to prevent wild fluctuations, but does allow a fairly wide band for the exchange rate movement.
If you want free trade, how about lobbying to allow India to export labour^W services instead of materials? Get rid of the work visa requirement totally, so any Indian can travel to the US and get a job there. Oh, and get rid of those agricultural subsidies.
You can't have free trade only in the goods/services you produce.
IME, you don't need to refactor that much with dynamically typed languages. Also, your refactoring is likelier to be at an architectural/abstraction level rather than the stuff that Java programmers do.
This like changing the type of a method return aren't even likely to make sense in most dynamically types languages. By writing small amounts of code, and aggressively building libraries, your variable name scope is also fairly small.
You don't use a complex inheritance hierarchy, you instead compose your final class. Good coding practice triumphs most of the benefits of a statically typed language.
There are some things which typed languages protect you from, and those should be rare to encounter in practice if you can duck type.
There is no probability distribution, just a small Perl script.
Memory utilisation. Startup times. JVM suckage.