|
Parno and a team of researchers recently published a new coding language and tool for high-performance concurrent programs that ensures that programs are provably-correct—that is, that the code is mathematically proven to compute correctly. As opposed to just computing as written
|
|
|
|
|
Right. That's been around for over 20 years.
"Coq is an interactive theorem prover first released in 1989... It allows for the expression of mathematical assertions, mechanically checks proofs of these assertions, helps to find formal proofs, and extracts a certified program from the constructive proof of its formal specification. ...When viewed as a programming language, Coq implements a dependently typed functional programming language;..."
Coq - Wikipedia[^]
|
|
|
|
|
A slow burn to perfection then? 
TTFN - Kent
|
|
|
|
|
Parno... Coq...
Are they trying to make you break the KSS rules in the insider news? 
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
private void main() {
Debug.Print(generateWinningLotteryNumbers());
}
private string generateWinningLotteryNumbers() {
return "1,2,3,4,5,6";
}
Now, go do your stuff, compiler!  
|
|
|
|
|
Cornell Tech researchers identified a problem that holds the key to whether all encryption can be broken—as well as a surprising connection to a mathematical concept that aims to define and measure randomness. Roll D20 for security (and initiative)
|
|
|
|
|
Under the premise that there is nothing 100% random in the digital world... then we are screwed about security
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Not due until March 2021, next Java upgrade kicks off with support for C++ 14 language features in JDK source code and HotSpot VM "And I do anything for my sweet sixteen"
|
|
|
|
|
|
Funny that the big leap forward is to use C++ features that have been around for, does advanced math, six years!
|
|
|
|
|
A Microsoft engineer is proposing the Trampoline File Descriptor "TRAMPFD" as a new kernel API for securely dealing with trampoline code on systems. ...aaaaand I need a new irony meter again
|
|
|
|
|
Kent Sharkey wrote: ...aaaaand I need a new irony meter again
Not only that... I need a new vocabulary as well as I don't recognise many of the new bullsh1t bingo fuzzwords
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
what in the world is a Microsoft engineer doing fiddling with linux....
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
New landing page is for Windows developers using Node.js, React, Java, Kotlin, Python, Xamarin, and Android Studio. Who are you, and what did you do with my Microsoft?
|
|
|
|
|
And one wannabe mixed OS to rule them all or at least try it and bind them to the darkness...
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
"
Microsoft will only be accepting developer-related performance issues on Windows
"
I see no evidence that they are going to fix any of the many actual bugs.
|
|
|
|
|
The .NET Productivity team (a.k.a. Roslyn) is constantly thinking of new ways to make .NET developers more productive. "Every day, in every way, I'm getting better and better"
|
|
|
|
|
Kent Sharkey wrote: new ways to make .NET developers more productive.
specially with new icons.
I hope they stay away from the windows update team 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
An interesting, at times philosophical, essay: [^]
Quote: Microsoft’s love-hate relationship with AOP
Microsoft has had a long love-hate relationship with aspect-oriented programming.
As all large corporations, Microsoft has the psychology of a dragon with many heads – each with its own eyes, mouth and brain. No wonder they are not always synchronized.
On one side, many teams have added AOP-ish features into their own product:
Microsoft Transaction Server, later renamed COM+
Custom behaviors in WCF
Interceptors in Unity
Action Filters in ASP.NET MVC and ASP.NET MVC Core
These teams didn’t just add these features because they were fun, but because they were useful. In all these technology stacks, aspects can be applied only at the boundaries of a component because the technology brokers the call between the client and the component. Neither the compiler nor the runtime engine was involved there, only the service host.
Another example of technology that vitally needs aspect-oriented programming is WPF. The amount of code required to implement INotifyPropertyChanged, dependency properties or command is colossal. This is why INotifyPropertyChanged is cited as a use case of source generators. Because it’s so useful.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
BillWoodruff wrote: Another example of technology that vitally needs aspect-oriented programming is WPF. The amount of code required to implement INotifyPropertyChanged, dependency properties or command is colossal. This is why INotifyPropertyChanged is cited as a use case of source generators.
Winforms controls are no better in this regard. I've made source generators for it before, but nothing aspect oriented, because none of microsoft's frameworks aside from COM+ really gives you anything like proper AOP
Real programmers use butterflies
|
|
|
|
|
The RFC may be the ARPANET’s most enduring legacy Just in case any would care to comment
|
|
|
|
|
Today's sciences still rely on a BC-era protocol: Books 
|
|
|
|
|
Not to nitpick, but BC-era writings were on scrolls. 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Daniel Pfeffer wrote: Not to nitpick,
Liar  
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Fair enough I'm accurate to within a human lifespan though since we have codices dating back to the turn of the 1st century.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
