Pythons can spend about 3 weeks digesting a meal. During this time they are extremely slow, in fact they are not moving at all.
On the other hand, Python gives the programmers quite a bit of freedom on how to attempt to solve a problem, so Python programmers do not feel constricted.
He will surely have the missing parts of the rat's DNA stored in the Omnitrix
Here is one for the graybeards out there:
Remember the BitBoys ? https://en.wikipedia.org/wiki/...
Got aquired by ATI but later AMD sold them to Qualcomm.
We should petition AMD to call the new GPU Glaze3D, just for old time's sake.
With the COVID lockdown it was always assumed that chess players are not affected, they can play on-line as well as over-the-board.
However, speaking to a few players (2000-2300 ELO range) they all complain about the number of cheaters on platforms like Lichess.
Many of them have moved from 10min + 5sec rapidplay format to 3min + 0s blitz simply because it is harder for cheaters to play in that format.
The cheaters input the opponent's moves into some chess engine and then play the engine's reply against the opponent.
Even a free chess engine you can get on a phone can play at grandmaster level.
On the 3min + 0sec format at least you have a chance to win on time against a cheater.
Catching cheaters would be a much better use of AI than de-anonymising human players.
Remember that Edward Teller was the second choice to lead the development of the hydrogen bomb.
The number one choice was Hans Bethe, but he refused to work on this project arguing that the kiloton fission bombs were alreay powerful enough and that the megaton hydrogen bombs were not needed.
Teller was alway obsessed that he coud not do as good a job as Bethe and in the end the design he came up with was mostly the work of Stanislaw Ulam. See how he treated Ulam after the design proved successful.
In order to compensate, he took the easy route of pushing for "bigger is better"
In 2004 Microsoft was run by Ballmer, and you may remember him characterizing Linux as a "cancer".
Also back in 2003, the city of Munich started their much-advertised Linux migration and Ballmer deployed his army of sales people to stop it. It only took one large city to do the migration and the fear was that it will open the floodgates.
After that, people did not "move on". It was ok to run Linux, but only where it cannot be seen: in some server room, but not on the desktop.
As for Azure running on Linux, Microsoft has no qualms about taking advantage of something they threaten. The Azure on Linux is also something that happened only after Ballmer was replaced as CEO.
They may "Love Linux" now, but for them it is only unpaid development work they can take advantage of.
Remember the Microsoft Open Source License? You can make any changes to their code as long as you license them free of charge back to Microsoft.
I call it the Napoleon License: "I am the Community".
I am surprised that this is considered a victory. The whole point of the lawsuit was not to win, but to make sure that every corporate lawyer learns that Linux is a legal risk.
Use Linux, get sued.
Sure, you can win the lawsuit or have it dismissed 18 years later, but in the meantime your clients will learn that your company is getting into legal trouble and will move their business elsewhere.
And long after your company is dead and forgotten, you may hold a piece of paper pronouning victory.
The other problem is that Microsoft made sure that the SCO vs IBM lawsuit is included as an example in the textbooks of all MBAs. These people will get in positions to make purchasing decisions at various companies and when they see Linux they remember "legal risk".
The SCO lawsuit started in 2003. The year 2004 was declared the (now much-derided) "Year of the Linux Desktop". The naming was correct. While before that year you had to make a pretty strong argument to use Linux on the Desktop, from 2004 onwards one had to work hard to find a reason not to use it.
Microsoft bankrolled SCO's lawsuit to offer that reason: Legal Risk.
I was hoping this has become quite commonplace by now:
https://www.theonion.com/new-e...
In such situations the solution is to show that "they did something". For example when Google slurped WiFi passwords illegally, there was a lot of outrage from the public, so something had to be done.
What was done is that Google destroyed a few hard-disks and, presto, problem solved. Of course, no word about the data being copied in a whole bunch of other locations.
When it comes to gangs running ranswomware attacks on this scale, it should be clear that they work hand-in-hand with the corrupt law enforcement and that equally corrup politicians get their cut from the proceeds.
I remember that during the war in former Yugoslavia, the oil embargo imposed on that country made some people in Romania very rich. The fuel-smuggling gangs could afford to bribe the border guard such amounts of money, that the watch towers along the Danube were manned by the gang members.
Then someone in the West complained about the smuggling and a raid was conducted to show that "they did something". The ones that were caught were the small-time smugglers that were carrying a couple of barrels in a motor boat, while the big shots shipping the fuel by train (to the tune of 60 tanker train cars in one go) were warned of the raid and laid low.
You'll be surprised how many people are not aware of this trivial fact, that software runs on hardware. There are times when all you want from a language is to expose the functionality provided by the hardware and run as fast as the hardware allows it. Most scientific simulation code has very simple structure: Load data from file, run nested loops, write result to file. FORTRAN is still used for this kind of work as it is good at what its name says: FORmula TRANslator. Also the resulting code is very fast.
Then there are situations where you want to think of the problem and not worry about the hardware. Here is where languates like Python truly shine. However, as long as these two opposite requirements exist we will have specialize languages that address one situation or the other.
This kind of software would not pass even the most basic User Acceptance Testing, yet the Universities pay for it without any testing.
The main reason to pay for this is to outsource responsibility of proctoring remotely: Computer says you cheated, if you have a problem take it up with the computer, not with us.
Same with everyone moving their e-mail to the Azure cloud. If a leak happens it is Microsoft's fault, and they are experts at defleting any responsibility.
It was all laid bare in the early 2000's when Linux has become mature enough to be used in various corporate systems. The management refused to migrate to Linux as they did not get an answer to the question:
"If something goes wrong, who do I sue ?"
... that you are an extremist. Therefore no human can be blamed for the decisions that follow.
Same with the anti-cheating software that universities used during the lock-down for exams taken from home: Computer says you cheated. You cannot sue the university, go ahead and sue the computer.
Then a 16 ton weight will indeed fall on your head.
I guess the remaining 50 tons will continue to orbit.
What is impressive about this helicopter is that it was built with off-the-shelf parts. Its on-board processor was described as "100 times more powerful" than the one on the rover, which means that it is not a radiation-hardened processor. Also the batteries are very vulnerable to low temperatures, and at night they can reach -90 C. The heating has to work very well to keep the batteries alive.
Adding aerial imagery to future missions will be a huge plus. Right now we have up-close images or satellite images, the aerial images fill a science gap where there is still a lot of speculation.
The seasonal changes in color of the gullies spotted by the satellites cannot be explored by the rovers, and here is where a helicopter will be ideal. At the moment there is a lot of speculation of whether or not those changes are due to water flowing on the surface.
than Transparent Aluminium:
If you want to put yourself on the map, publish your own map.
