[delayed]
It's just a Lisp dialect at the end of the day and not much more complicated to learn than Javascript. The only unusual aspect is its prevalent use of dynamic scoping, although nowadays lexical scoping is also available…
It looks like it very much should never have happened like this. The actually hard and awkward questions have not been asked beforehand, and the SC doesn't like their hands being forced, and rightly so.
Getting a JIT right is hard work because time spent by the JIT is time not spent doing actual work, and finding the correct tradeoffs is very much an empirical problem.
> Further, America has definitely been pumping money into Microsoft, for instance with hefty defense and public administration contracts. It is incredibly naive to believe that the US allowed the Microsoft monopoly to…
In the best case that's a one-time cost though.
Expect problems as soon as the people who made and maintain them are gone.
I get where these places are coming from - it is really easy to get started implementing these workflows in Excel and just grow it from there. But they are really fragile and hard to audit - who knows whether they work…
It doesn't matter whether the bug is in the borrow checker or not. A comparable bug in a C++ compiler would be compiling a program that should not typecheck according to the C++ standard and then causes a segfault or a…
It requires heavy trade-offs.
As I have already written above, one will reliably make errors with memory unsafe features even if one is cartel. Therefore, it's not the same thing.
People using a tool in the wrong way is not necessarily an argument against the tool though. There's always the potential for misuse. (Of course, this misuse should be sharply distinguished from the errors caused by my…
That's not how "unsafe" works at all. If "unsafe" is so commonplace in a code base that your statement becomes relevant then the project is badly run, and memory safety is just another problem among many others. Similar…
It is well known that proof assistants can be wrong. Fortunately, the theories underlying formal methods are usually simple enough that it is feasible to write verifiers for these proofs.
[delayed]
It's just a Lisp dialect at the end of the day and not much more complicated to learn than Javascript. The only unusual aspect is its prevalent use of dynamic scoping, although nowadays lexical scoping is also available…
[delayed]
It looks like it very much should never have happened like this. The actually hard and awkward questions have not been asked beforehand, and the SC doesn't like their hands being forced, and rightly so.
Getting a JIT right is hard work because time spent by the JIT is time not spent doing actual work, and finding the correct tradeoffs is very much an empirical problem.
[delayed]
[delayed]
[delayed]
[delayed]
> Further, America has definitely been pumping money into Microsoft, for instance with hefty defense and public administration contracts. It is incredibly naive to believe that the US allowed the Microsoft monopoly to…
[delayed]
[delayed]
In the best case that's a one-time cost though.
Expect problems as soon as the people who made and maintain them are gone.
I get where these places are coming from - it is really easy to get started implementing these workflows in Excel and just grow it from there. But they are really fragile and hard to audit - who knows whether they work…
[delayed]
It doesn't matter whether the bug is in the borrow checker or not. A comparable bug in a C++ compiler would be compiling a program that should not typecheck according to the C++ standard and then causes a segfault or a…
[delayed]
It requires heavy trade-offs.
As I have already written above, one will reliably make errors with memory unsafe features even if one is cartel. Therefore, it's not the same thing.
People using a tool in the wrong way is not necessarily an argument against the tool though. There's always the potential for misuse. (Of course, this misuse should be sharply distinguished from the errors caused by my…
[delayed]
That's not how "unsafe" works at all. If "unsafe" is so commonplace in a code base that your statement becomes relevant then the project is badly run, and memory safety is just another problem among many others. Similar…
[delayed]
It is well known that proof assistants can be wrong. Fortunately, the theories underlying formal methods are usually simple enough that it is feasible to write verifiers for these proofs.