Apparently, Apple filed for an software patent on an antifeature that uses a DRM-like system and a proprietary network services to lock down people's mobile phones.

• when, as a voter, one could clearly see polls were doctored massively as a means to influence the voters
• when the internet was crucial and almost the only means of spreading ideas for the campaign of a candidate, Remus Cernea
• in which an important internet news site, hotnews.ro, decided not to publish polls anymore
• when the public television didn't perform its duty to organise a debate with all the candidates at the same time
• when candidates were separated in two groups: "insignificant candidates" and "important candidates"
• when some candidates refused to participate in public debates, except on their own terms, as if it was a service done by them to others
• when candidates accused each other of being afraid to participate in face to face debates, while it was clear that this was true for many
  
• when a candidate, Remus Cernea, was kicked out of a debate where he was previously invited, without being given a reason
• when journalists' investigations found that all major parties had during the last year donations from at least 100 politicians with a declared income lower or identical to the donated sums totalling up to 91 millions of new lei (RON) (approximately 22 million euros)
• when we have proof directly from frauders that all major parties prepared to fraud the elections via electoral tourism, electoral bribes and vote purchase
• when a referendum was used as a electoral means by one of the candidates
• when opponents twisted and re-twisted others' electoral message
• when an illegitimate organisation organised a debate with only the first three candidates
• when it was announced that special polling stations were made to target people voting away from home, not allowing such voting on special lists in regular polling stations; also the special polling stations will be, for the first time, monitored via webcams which will record the voters when they insert the bulletin
• when some candidates clearly stole ideas from others mid-campaign
  
• when I decided I am going to vote out of conviction and cast a positive vote for Remus Cernea

• you're strentghning one of the adversaries
• your prefered candidate will be in a worse position to negotiate with others the implementation of some of the points on his platform in case he doesn't win
• you're canceling one of the votes somebody did vote for the one you prefer

• One possible first step towards avoiding random destruction is to start your script with #/bin/sh -e instead of #/bin/sh , this means that the script will exit on an unexpected error, which is generally better than continuing merrily along to destroy vast swathes of data. Of course sometimes you will expect an error, in which case you can use /usr/local/bin/command-might-fail true to make it not abort on a command that might fail.
• #!/bin/sh -e
  cd /tmp/whatever
  rm -rf * #!/bin/sh
  cd /tmp/whatever exit 1
  rm -rf * Instead of using the -e switch to the shell you can put exit 1 after a command that really should succeed. For example neither of the above scripts is likely to destroy your system, while the following script is very likely to destroy your system: #!/bin/sh
  cd /tmp/whatever
  rm -rf *
• Also consider using absolute paths. rm -rf /tmp/whatever/* is as safe as the above option but also easier to read avoiding confusion tends to improve the reliability of the system. Relative paths are most useful for humans doing typing, when a program is running there is no real down-side to using long absolute paths.
• Shell scripts that cross account boundaries are a potential cause of problems, for example if a script does cd /home/user1 instead of cd ~user1 then if someone in the sysadmin team moves the user s home directory to /home2/user1 (which is not uncommon when disk space runs low) then things can happen that you don t expect and we really don t want unexpected things happening as root! Most shells don t support cd ~$1 , but that doesn t force you to use cd /home/$1 , instead you can use some shell code such as the following: #!/bin/sh
  HOME= grep ^$1 /etc/passwd head -1 cut -f6 -d:
  if [ "$HOME" = "" ]; then
  echo "no home for $1"
  exit 1
  fi
  cd ~ I expect that someone can suggest a better way of doing that. My point is not to try and show the best way of solving the problem, merely to show that hard coding assumptions about paths is not necessary. You don t need to solve a problem in the ideal way, any way that doesn t have a significant probability of making a server unavailable and denying many people the ability to do their jobs will do. Also consider using different tools, zsh supports commands such as cd ~$1 .
• When using a command such as find make sure that you appropriately limit the results, in the case of find that means using options such as -xdev, -type, and -maxdepth. If you mistakenly believe that permission mode 666 is appropriate for all files in a directory then it won t do THAT much harm. But if your find command goes wrong and starts applying such permissions to directories and crosses filesystem boundaries then your users are going to be very unhappy.
• Finally when multiple scripts use the same data consider using a configuration file. If you feel compelled to do something grossly ugly such as writing a dozen expect scripts which use the root password then at least make it an entry in a configuration file so that it can be changed in one place. It seems that every time I get a job working on some systems that other people have maintained there is at least one database, LDAP directory, or Unix root account for which the password can t be changed because no-one knows how many scripts have it hard-coded. It s usually the most important server, database, or directory too.

Do not communicate by sharing memory; instead, share memory by communicating.

var sem = make(chan int, MaxOutstanding)
func handle(r *Request)  
    sem <- 1;    // Wait for active queue to drain.
    process(r);  // May take a long time.
    <-sem;       // Done; enable next request to run.
 
func Serve(queue chan *Request)  
    for  
        req := <-queue;
        go handle(req);  // Don't wait for handle to finish.
     
 

• Fully integrated, on-board GPS receiver and patch antenna, with support for off-board amplified antennas when airframe geometry or materials demand it.
• A change in the design of the circuit for firing e-matches to ignite ejection charges that will improve mechanical reliability, plus explicit support for using a separate pyro battery if desired.
• Inclusion of a "companion board interface" that we envision using for a pyro channel expansion board to support staging and air starts, among other things.
• Dramatic increase in the capacity of the on-board data logging memory.
• Changes in connector series to eliminate our dependency on expensive crimping tools for making cables.