News for hackers. Stuff that matters.
Re:What science says about naming in programming by wruza on Sunday January 08, 2017 @05:14AM (#13349125)
What we need is better tooling. First of all, stop pretending that structured (one of world's most complex structured) description of commands and expressions is "just a text". If programming environments stored sources as structured items, it would be easy to give an entity many names (e.g. human description, full qualified name, short name in current module, and shortest scope/mind-local alias). And then switch modes from 'first time reading' to 'familiar development' (or 'lawyer style', where descriptive names appear only in appropriate places and assertions are visible). Similar issues we have with formatting, ridiculous tabs-vs-spaces wars, encodings, even with line endings.

Try to open raw html/css instead of using browser to view modern website. Hard to get the picture? Yeah, and that's where we are in programming today.

Re:What science says about naming in programming by tacostakohashi on Sunday January 08, 2017 @02:51PM (#13351578)
This isn't a million miles from what you get with Javadoc + Eclipse, where if you hover over an item you see the snippet of Javadoc attached to it where it was defined (i.e., in some other sourcefile, or jar).

A few key points that make this useful:

The documentation snippets are attached to specific methods, parameters, classes, etc - like in Javadoc or Doxygen. You don't have to wade through stuff you care about to find out about the the thing you care about (under your mouse).

Re:What science says about naming in programming by alistproducer2 on Sunday January 08, 2017 @11:08AM (#13350321)
upvote for the interesting idea. To your knowledge is there any IDE out there with such a feature?
Re:What science says about naming in programming by wruza on Sunday January 08, 2017 @11:29AM (#13350453)
Nope. At least my annual efforts to dig into that direction always fail. It seems, that there is something: literal programming, html-based prolog posted here recently (someone please help to recall its name). But it is not exactly that. And it always contains esoterics under the hood. I want C, C++, Perl, Java, anything mainstream; not Prolog.

I'm too busy and too single to make prototype on my own (and more related ideas on top of that in thoughts.txt). I've posted this in forum comments for years, and sometimes got critics that made me temporarily think it is just another view on existing techniques (as of company-wide, not person-wide). Now I run the company and this got only more demand.

Honestly, maybe I'm just doing existing things wrong, idk.

Re:What science says about naming in programming by wruza on Monday January 09, 2017 @11:41AM (#13357592)
Word 'Jetbrains' in this list looks very promising, I'll definitely give it a try on spare time. Thanks!
Re:What science says about naming in programming by MarisaKirisame on Monday January 09, 2017 @01:09PM (#13358326)
The html based prolog thing you mention is probably eve.
Re:What science says about naming in programming by wruza on Monday January 09, 2017 @07:54PM (#13361562)
Re:What science says about naming in programming by alistproducer2 on Sunday January 08, 2017 @11:35AM (#13350495)
I could see this being an eclipse or notepad++ plug in.
Re:What science says about naming in programming by TeMPOraL on Sunday January 08, 2017 @12:57PM (#13350954)
Closest aspects I saw that touch this idea:

- automatic refactors in Java IDEs, especially "rename" - they understand what you mean by "this variable" or "this function", at least most of the time

- Paredit mode in Emacs, for working with Lisp code; if you learn it, you start feeling you're actually working with a tree, and not its textual representation

Re:What science says about naming in programming by gohrt on Sunday January 08, 2017 @12:29PM (#13350808)
Charles Simonyi has been trying for over 20 years

https://www.microsoft.com/en-us/research/publication/the-dea...

http://www.intentsoft.com/us/ <-- in "stealth mode" for 10 years!