Comments URL: https://news.ycombinator.com/item?id=48089853

Points: 13

# Comments: 0

    "There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies."

- do not believe in Allāh or in the Last Day

- do not consider unlawful what Allāh and His Messenger have made unlawful

- do not adopt the religion of truth (doesn't necessarily mean Islam, since true Christianity and Judaism believe in one God)

- from those who were given the Scripture. That includes Muslims themselves by the way, since they were given a scripture. Elsewhere in the Quran when it refers to Christians and Jews it says "People of the scripture". In other areas it mentions "Those who were given the scripture", which includes Muslims.

What it essentially says: if you do not follow the law of the land, whether you are a Christian, Jew, or a Muslim, there are consequences. Every nation has laws, and if you break those laws you will be prosecuted. In this case it says those will have to pay a "fine".

Imagine the opposite: an Arab group was planted to occupy part of Europe, occasionally gets into wars with its neighbours, and builds one of the largest weapons arsenals in the world, including nukes. How would Europeans feel about that?

https://www.youtube.com/shorts/na2hwj4vB_A

Remind me, which country was the only one in the world that actually used nukes to kill hundreds of thousands of unarmed civilians?

Please quote this part from the Quran. I'd like to learn more.

The same thing happened in the late 50s / early 60s when high-level programming languages and compilers started to appear. Almost all software at that time was hand-written assembly. Compilers took a decade to reach the same quality (sometimes even better) of hand-written assembly. Programmers adapted and started thinking at a higher level of abstraction.

Another example is virtual memory. Up until the late 1960s most software used manual physical memory management techniques (mainly overlays) to decide which part of the program should reside in memory at certain points of time. Everyone was skeptical and thought that virtual memory would be less optimal than manually-designed overlays. There was a lot of research in that area during the time to prove that virtual memory can have the same or even better performance than hand-rolled approaches.

The point is: AI may well be disruptive to the way we develop software, but we're still in a transition phase where trust in AI output is very shaky. It's impressive, but it hasn't established itself yet as an abstraction we can trust and build on without thinking about what it's producing. It will take time, and humans will always have more work to do no matter how technology advances.