1,591 karma · joined October 18, 2020
SBCL, which is a very popular Common Lisp implementation, is indeed strongly typed. Coalton, which is an addon, is even statically typed
infringing on copyleft is like stealing from the poor
its the difference between robin hood and government corruption
ive also seen what western interefernce looks like when the west wants there to be a war. for example compare this to boris johnson torpedoing the peace agreement between Russia and Ukraine in 2022
On 18 March 1992, all three sides signed the agreement; Alija Izetbegović for the Bosniaks, Radovan Karadžić for the Bosnian Serbs and Mate Boban for the Bosnian Croats. The plan had assigned each of the 109 municipalities to be divided amongst the three ethnic sides. The allocation of the municipalities was mostly based off the results of the 1991 population census that was completed a year before the signing of the agreement. The agreement had stipulated that the Bosniak and Serb cantons would each have covered 44% of the country's territory, with the Croat canton covering the remaining 12%.[3]
On 28 March 1992, after a meeting with US ambassador to Yugoslavia Warren Zimmermann in Sarajevo, Izetbegović withdrew his signature and declared his opposition to any division of Bosnia. What was said and by whom remains unclear. Zimmermann denied that he told Izetbegović that if he withdrew his signature, the United States would grant recognition to Bosnia as an independent state. What is indisputable is that on the same day, Izetbegović withdrew his signature and renounced the agreement.[4][5]
https://en.m.wikipedia.org/wiki/Peace_plans_proposed_before_...Ukranians should take note that the Bosniak side came out even worse after that war, while the Serbian side today controls half of the country in a defacto almost independent state
and even though static languages can have "repls" as an afterthought (eg GHCi), rest assured that their static typing property is a completely unnecessary cognitive load (at least cognitive but very likely a performance one too) to their functioning
bool function1(x y z):
bool function2(x y z)
immagine function2 besides returning true/false mutates x in some major way. this is a far bigger and more common problem than typing. a dynamic language with capabilities of runtime debugging is far better equiped to inspect code like thisalso i am not saying that typing is worse than no type information. im saying that typing should be optional as far as the compiler is concerned and typing information should be like documentation that is useful to the compiler. common lisp can be an example of a language that is both dynamic and strongly typed (see SBCL) to the extent that you can implement a statically typed language (ala ML) in it
Ive never ever run into this problem in the years of writing common lisp. Can you show me an example code that has this? I wager you cannot and you are writing poopoo about something you know poo about and want it to be true just because you are too lazy to move beyond knowing poo
> But this kind of power just isn't conducive to maintainable code.
I can usually run code decades old in common lisp. In fact this is one of its well known features. How much more maintainable can it possibly get :)