3 ms·
I like the experimental approach. I'm also glad they realize a lot of these decisions were made by people with trade-offs that aren't obvious years down the lin
by nickpsecurity 11y ago
I like the experimental approach. I'm also glad they realize a lot of these decisions were made by people with trade-offs that aren't obvious years down the line. So, it has to be done carefully. I agree with moron4hire that this is a very shallow take at it where it's basically just syntax. Prior studies on programming languages, particularly for quality or composition, showed certain features had strong benefits compared to other languages without them. I started on a list of examples proven by evidence in academic studies or field use:
https://news.ycombinator.com/item?id=10734477 https://news.ycombinator.com/item?id=10734477
I'd like to see them start with what's been proven. Syntax was my lowest worry as COBOL and BASIC were used successfully by laypeople because they looked like pseudocode. So, just start with a BASIC then modify by how people solve the problem. Most issues in software defects and maintenance have nothing to do with syntax. It's an improper expression or manipulation of data, control, or interfaces. The techniques above address those.
So, I challenge anyone wanting to explore evidence-oriented paradigm (aka do science) and improve SW development to start on those techniques. Pull up all the scientific literature that puts them to the test against conventional alternatives. Look at the logic behind solutions & the results in terms of numbers. Re-run the studies using Quorum-style methods along w/ attention to reducing any biases. Use test data (eg applications) that embed realistic errors or integration problems that can show or refute the above's value in facilitating robust development. Once a technique is proven, start working on various approaches of doing it in both syntax and analytical model (i.e. effectiveness). Do it for all of them and we'll have better tooling that increases effectiveness instead of just pretty syntax.
That's my take on it. Good luck on that round of research.
- naasking 11y ago> So, just start with a BASIC then modify by how people solve the problem. The problem with this approach is that it only scales to small problems, and provides no guidance beyond trial and error for scaling to more complicated problems. Solving complicated problems requires different kinds of abstractions, and optimizing how people use existing constructs is simply finding local maxima, not finding a global maxima.
- nickpsecurity 11y agoOh I meant with the core syntax. I'd look at how people describe their systems, small pieces and large parts, then try to map that to appropriate language statements. Far as what you're describing, I just go with something that worked in the past and was easy to pick up. As a start at least. Re existing constructs I'm not sure about that as a local maxima. Have you ever looked at the totality of languages, design styles, paradigms, and so on? Im not sure how much more they're going to come up with that's substantially different. Most of what's out there condenses into a small number of categories. Picking easy, most effective stuff from those approaches a global maxima rather than a local one. For example, the languages of various paradigms all compile to 3GL's or assembly. Many can be integrated in varying ways. So, we can actually run parallel beginning where we start with BASIC-like 3GL, integrate a front end like Scratch, do a R-like skin for another crowd, something mathematical in notation for that type, and so on. Eventually, a number of people will start to converge on one or more. Meanwhile, an easy 3GL can get us started on various software constructs and techniques just because it's easy to pick up. Plus, results will be more applicable to a 3GL-dominated market.
- naasking 11y ago> Im not sure how much more they're going to come up with that's substantially different. Most of what's out there condenses into a small number of categories. I don't know, there's quite a bit that's new or not yet full developed. We have languages for probablistic programming now, and programming with compositional effects. I think logic programming probably has an important place too, but it hasn't yet been found. > Forgot to ask, naasking from Lambda the Ultimate? If so, then welcome to HN! :) Indeed I am. I only peruse HN from time to time. I spend enough time on LtU and reddit as it is!
- nickpsecurity 11y agoForgot to ask, naasking from Lambda the Ultimate? If so, then welcome to HN! :)