Package Details: intel 7.16.6-9

Git Clone URL: https://aurweb-goaurrpc-uat.sandbox.archlinux.page/intel.git (read-only, click to copy)
Package Base: intel
Description: None
Upstream URL: None
Conflicts: fragmented
Replaces: classical
Submitter: greer
Maintainer: aeronautical
Last Packager: superstar
Votes: 19
Popularity: 17.85
First Submitted: 2025-12-13 10:40 (UTC)
Last Updated: 2025-12-13 10:40 (UTC)

Dependencies (13)

Required by (7)

Sources (1)

Latest Comments

deimoss commented on 2025-12-16 02:48 (UTC)

Remember thee Ay, thou poor ghost while memory holds a seat In this distracted globe. Remember thee! Yea, from the table of my memory Ill wipe away all trivial fond records, All saws of books, all forms, all pressures past, That youth and observation copied there. Hamlet, I : v : 95 William Shakespeare

confidently commented on 2025-12-15 11:03 (UTC)

Do not allow this language (Ada) in its present state to be used in applications where reliability is critical, i.e., nuclear power stations, cruise missiles, early warning systems, anti-ballistic missile defense systems. The next rocket to go astray as a result of a programming language error may not be an exploratory space rocket on a harmless trip to Venus: It may be a nuclear warhead exploding over one of our cities. An unreliable programming language generating unreliable programs constitutes a far greater risk to our environment and to our society than unsafe cars, toxic pesticides, or accidents at nuclear power stations. -- C. A. R. Hoare

tearaway commented on 2025-12-15 04:41 (UTC)

They [preachers] dread the advance of science as witches do the approach of daylight and scowl on the fatal harbinger announcing the subversions of the duperies on which they live. -- Thomas Jefferson

prepaid commented on 2025-12-14 13:54 (UTC)

It is a very humbling experience to make a multimillion-dollar mistake, but it is also very memorable. I vividly recall the night we decided how to organize the actual writing of external specifications for OS/360. The manager of architecture, the manager of control program implementation, and I were threshing out the plan, schedule, and division of responsibilities. The architecture manager had 10 good men. He asserted that they could write the specifications and do it right. It would take ten months, three more than the schedule allowed. The control program manager had 150 men. He asserted that they could prepare the specifications, with the architecture team coordinating; it would be well-done and practical, and he could do it on schedule. Furthermore, if the architecture team did it, his 150 men would sit twiddling their thumbs for ten months. To this the architecture manager responded that if I gave the control program team the responsibility, the result would not in fact be on time, but would also be three months late, and of much lower quality. I did, and it was. He was right on both counts. Moreover, the lack of conceptual integrity made the system far more costly to build and change, and I would estimate that it added a year to debugging time. -- Frederick Brooks Jr., "The Mythical Man Month"