News for hackers. Stuff that matters.
Re:Java is the COBOL of my generation and Go is its successor by azth on Friday May 02, 2014 @02:07PM (#7687175)
> What language created in the last 5 years has a feature that wasn't originally discovered in the 80s or earlier?

I may be wrong, but isn't Rust's static lifetime analysis to avoid GC something novel?

Re:Java is the COBOL of my generation and Go is its successor by pjmlp on Friday May 02, 2014 @03:49PM (#7687731)
Similar approaches do/did exist.

ATS uses theorem-proving, http://www.ats-lang.org/.

ParaSail uses regions, https://forge.open-do.org/plugins/moinmoin/parasail/

BitC used the type system, http://www.bitc-lang.org

Re:Java is the COBOL of my generation and Go is its successor by pcwalton on Tuesday May 06, 2014 @07:43PM (#7707836)
None of these have the borrow check. From what I've heard the borrow check is impossible to encode generically in ATS (though maybe that has changed).
Re:Java is the COBOL of my generation and Go is its successor by gress on Friday May 02, 2014 @03:21PM (#7687594)
Objective-C has it.
Re:Java is the COBOL of my generation and Go is its successor by azth on Friday May 02, 2014 @03:37PM (#7687666)
Do you have any references? Searching for "objective c lifetime analysis" turned up articles for ARC, which is not exactly the same thing.
Re:Java is the COBOL of my generation and Go is its successor by gress on Friday May 02, 2014 @04:44PM (#7687997)
I meant ARC. I know it's not exactly the same, but it's similar enough when we're talking about novelty in programming languages.
Re:Java is the COBOL of my generation and Go is its successor by plorkyeran on Friday May 02, 2014 @06:49PM (#7688631)
ARC doesn't involve any sort of nontrivial lifetime analysis. The compiler simply inserts calls to retain and release at all of the same places where explicit calls to them (hopefully) were with manual reference counting. The only vaguely novel part of any of it was successfully migrating a language from manual to automatic reference counting.
Re:Java is the COBOL of my generation and Go is its successor by gress on Friday May 02, 2014 @09:48PM (#7689184)
Actually that's not entirely true. Arc inserts the calls first, but then does an elimination phase that can identify lifetimes beyond method boundaries and remove unnecessary calls.

It's not particularly complex, but the architecture is there for further enhancement of this phase as they build out the static analyzer.

Re:Java is the COBOL of my generation and Go is its successor by pcwalton on Tuesday May 06, 2014 @07:44PM (#7707843)
That's nowhere near what the borrow check does. The borrow check is based on reasoning about ownership and inherited mutability, neither of which apply to Objective-C.