Predictions of the future in 2007 by the Center for Naval Analysis in USA:
https://www.cna.org/analyses/2007/national-security-and-the-threat-of-climate-change
A site devoted mostly to everything related to Information Technology under the sun - among other things.
Predictions of the future in 2007 by the Center for Naval Analysis in USA:
https://www.cna.org/analyses/2007/national-security-and-the-threat-of-climate-change
BBC
BBC
From Grauniad of the UK
BBC
Interesting ruminations on the potentialities inherent in AI technologies as well as their perils & larger meanings with useful ideas & promising paths.
The exploration of 'cognitive sovereignty' alone is also interesting as well as other hazardous arenas...
Find it @ Amazon.com: Customer reviews: The God Test: Artificial Intelligence and Our Coming Cosmic Reckoning
Ayatollah Alireza Arafi, member of the Assembly of Experts and former head of Islamic seminaries in Iran:
"I recently heard that Pope Leo XIV wrote an encyclical letter titled ‘Magnifica Humanitas’, calling for the disarmament of Artificial Intelligence.
I found the letter very good; humanity must rid itself of this AI, which defies all divine purpose and is used in evil ways the majority of times. We must be aware of this.
It is truly a worthy goal of a joint intellectual Jihad / Crusade, in which our Christian brethren can play an important role."
The encyclical may be found here:
https://www.vatican.va/content/leo-xiv/en/encyclicals/documents/20260515-magnifica-humanitas.html
From Grauniad of the UK
BBC
The fundamental irresolvable issue with LLMs is how can one have any confidence that an LLM system is not trained on maliciously false, slanted, and inaccurate corpus?
(Already, much of the Internet is, in a religious parlance, the Discourse of Satan, in any case...)
How do you know the LLM domiciled in the Jurisdiction ABC and accessed from Jurisdiction XYZ is not producing output for misinforming and misleading users in the XYZ Jurisdiction?
How do you know the LLM in Jurisdiction QWERTY is not lying about History, Economics, Philosophy, Engineering, etc.?
As you know, we have entered the world of the novel"1984", but on steroids. In such a world, publicly available data and information, are all Lies, they are all False to one degree or other, in order to sustain the Forever Wars being fought by the major powers.
LLMs had the potential to be a great research & exploration tool and supplier of information, but they are on their way to Suicide, if the present trends continue.
I suppose that the 168 school children and their teachers murdered at the Minab Shajarah Tayyebeh School by the United States on March 1, 2026, had been identified by Mr. Musk's Grok AI system as legitimate enemy targets.
Bravo Mr. Musk for demonstrating in a very concrete manner of flesh & blood, the shape of your brave new Tech-dominated world that has emerged.
The darkness drops again; but now I know
That twenty centuries of stony sleep
Were vexed to nightmare by a rocking cradle,
And what rough beast, its hour come round at last,
Slouches towards Bethlehem to be born?
Justice & Remembrance عدل و ذکر
________________________________________
There are many existing metrics for quantifying a body of computer code such a Cyclometric Complexity and Line of Executable Code, LOC.
Here I am suggesting that it could be useful to define a new Code Metric, the Aggregate Code Density - defined as:
Aggregate Code Density = log (Total Lines of Code) / Total Number of Files
This quantity is to be computed for a component, package, JAR/WAR file, system, or project with multiple subfolders and source code files. The Logarithm function is used in order to avoid very large numbers for this metric since a file could contains thousands, perhaps several tens of thousands of lines of code.
It is envisioned that by the phrase "Lines of Code" one includes the declarative statements in configuration files such as .xml, .yml, .yaml, .json, .properties, .envetc. In this manner, changes to the system's configurations copuld also be measured and tracked.
If more code is developed but the number of files is increased, then Aggregate Code Density increases - and both Cyclometric Complexity LOC will increase with it.
If code is added to the system is in new files, the increase in Aggregate Code Density could be smaller and its variation will have a smaller increase in slope as a function of time.
If the system is refactored, Aggregate Code Density, by necessity, must go down as both the number of lines of code and the number of files should have decreased due to the Refactoring process; if the Aggregate Code Density has remained the same or has increased - ten I imagine that the Refactoring effort was not successful!
If procedural code in Python (let us say) is Refactored into Object-Oriented code, then Aggregate Code Density would go down since eventhough the number of files could increase, the number of repetitive sections of code would decrease.
LOC gives us some of the same insights both at the file level as well as in the aggregate, this new metric is a slightly different one in that it only looks at the entire system and its configurations and not just LOC. This is an advantage since the deployment of a system into Cloud environments such as Kubernetes or Pivotal Cloud Factory adds significant complexity to the system and to the cost of its development and maintenance.
BBC