Short LINQ syntax
-
The bloke who wrote the article probably does. Me? I think there is enough confusion available in LINQ without needing extra compact stuff that looks like a regex - i.e. unreadable without a good long look.
You looking for sympathy? You'll find it in the dictionary, between sympathomimetic and sympatric (Page 1788, if it helps)
OriginalGriff wrote:
Me? I think there is enough confusion available in LINQ without needing extra compact stuff that looks like a regex - i.e. unreadable without a good long look.
It's like the rule 34 of coding: Within two years of its creation, a programming language that is easily usable will have been turned into a writhing mess of ridiculous complications. [edit] I typoed "writhing", fer cryin' out loud!
I wanna be a eunuchs developer! Pass me a bread knife!
-
This approach refers to a Bitwise combinations syntax, precisely the opposite way of Natural Language. Regards
Member 10277067 wrote:
This approach refers to a Bitwise combinations syntax,
precisely the opposite way of Natural Language.I understand that, but the point of a natural language syntax is that it is readable, more or less, without an internal translation layer on the part of the reader. Like any syntax, it probably could become second nature (like how | is a bitwise OR and || is a logical OR), but I completely fail to see the advantage of using the syntax in your short LINQ examples. Marc
Automating Semantic Mapping of a Document With Natural Language Processing
-
-
No; a developer must write as clearly as possible so that the next developer can think less. Effort "saved" up front often leads to greater effort later.
PIEBALDconsult wrote:
No; a developer must write as clearly as possible so that the next developer can think less.
Very well said! Marc
Automating Semantic Mapping of a Document With Natural Language Processing
-
No; a developer must write as clearly as possible so that the next developer can think less. Effort "saved" up front often leads to greater effort later.
:thumbsup: At times like this, I wish I could hit the upvote button a couple of dozen times...
You looking for sympathy? You'll find it in the dictionary, between sympathomimetic and sympatric (Page 1788, if it helps)
-
Hi, Tks for your reply. Why community currently uses JQuery in large scale ? THINK MORE. WRITE LESS ! ;-) Regards
You aren't comparing like with like. jQuery serves a purpose - making DOM manipulation consistent across browsers. You might want to think more before you pick your analogies.
-
No; a developer must write as clearly as possible so that the next developer can think less. Effort "saved" up front often leads to greater effort later.
PIEBALDconsult Please, The issue here is the discussion of a new possible concept, we can discuss about best practices of coding in another post. :zzz: Read the things before show yourself to the readers ! Regards.
-
:thumbsup: At times like this, I wish I could hit the upvote button a couple of dozen times...
You looking for sympathy? You'll find it in the dictionary, between sympathomimetic and sympatric (Page 1788, if it helps)
I respect your point of view. Thank you!
-
You aren't comparing like with like. jQuery serves a purpose - making DOM manipulation consistent across browsers. You might want to think more before you pick your analogies.
The slogan says itself : jQuery => Write Less, Do More ;-) The analogy was cited in this regard. Thanks for your comment.
-
The slogan says itself : jQuery => Write Less, Do More ;-) The analogy was cited in this regard. Thanks for your comment.
Have you ever heard of an elevator pitch? You have a product that you're trying to get us interested in here. You have 60 seconds to tell us what problem you're trying to solve here and how it does it. Taking jQuery as an example - the problem is different browsers have different HTML implementations; jQuery provides a consistent API that works regardless of the underlying browser. That's an easy problem domain to define, and an easy solution to sell. What problem are you trying to solve? What can I not do today that this will solve for me?
-
Have you ever heard of an elevator pitch? You have a product that you're trying to get us interested in here. You have 60 seconds to tell us what problem you're trying to solve here and how it does it. Taking jQuery as an example - the problem is different browsers have different HTML implementations; jQuery provides a consistent API that works regardless of the underlying browser. That's an easy problem domain to define, and an easy solution to sell. What problem are you trying to solve? What can I not do today that this will solve for me?
Did u read the Project proposal ? - Smart Data Mining - Flex Data Formats Interchange Cross Platforms And more... Are some of the problems that it solves. Read more please. Download the test console and then give your opinion :-) Thanks
-
Did u read the Project proposal ? - Smart Data Mining - Flex Data Formats Interchange Cross Platforms And more... Are some of the problems that it solves. Read more please. Download the test console and then give your opinion :-) Thanks
I read your proposal and I watched the YouTube video. At the end of it I was no further forward. Throwing phrases like Flex Data Formats Interchange Cross Platforms tells me nothing. Seriously. Write your proposal in English, not technical shorthand. Your refusal to understand that we aren't going to just download a spam posting isn't doing you any favours. Tell you what. Why don't you write an article about this? This is, after all, what CodeProject is all about. If you write an article clearly showing what this solves, you might actually find that people are more receptive. Right now, you're winning no friends here.
-
The slogan says itself : jQuery => Write Less, Do More ;-) The analogy was cited in this regard. Thanks for your comment.
-
Anyone know this new short syntax method of LINQ queries ? http://bwqs.codeplex.com
I honestly don't see what this accomplishes other than obfuscation. This reminds me of why I learned to hate Perl: easy to write, a right pain to read and maintain. If a junior programmer can't understand the code within a few minutes, you're doing something terrible to the maintenance programmers, killing productivity and inviting bugs (and making enemies). Code that is opaque for no good reason is worse than no code at all.
-
No; a developer must write as clearly as possible so that the next developer can think less. Effort "saved" up front often leads to greater effort later.
Eloquently - and accurately - phrased!
According to my calculations, I should be able to retire about 5 years after I die.
-
The slogan says itself : jQuery => Write Less, Do More ;-) The analogy was cited in this regard. Thanks for your comment.
Member 10277067 wrote:
Write Less, Do More
You keep using these words, I don't think they mean what you think they mean. JQuery allows us to write code that works across browsers, prior to that we had to write different versions of JavaScript for different browsers. JQuery also provides simple ways to do common tasks which would otherwise require a fair amount of JavaScript code. That's what the "write less" part means, it doesn't literally mean to make code as terse as possible. Typing is not a bottleneck in programming (unless you're doing it wrong).
-
I honestly don't see what this accomplishes other than obfuscation. This reminds me of why I learned to hate Perl: easy to write, a right pain to read and maintain. If a junior programmer can't understand the code within a few minutes, you're doing something terrible to the maintenance programmers, killing productivity and inviting bugs (and making enemies). Code that is opaque for no good reason is worse than no code at all.
StatementTerminator wrote:
If a junior programmer can't understand the code within a few minutes,
Well we'd better stop writing any code then. Or the junior programmers you've met are smarter than the ones I've met. Give them something trivial and they struggle for hours.
-
StatementTerminator wrote:
If a junior programmer can't understand the code within a few minutes,
Well we'd better stop writing any code then. Or the junior programmers you've met are smarter than the ones I've met. Give them something trivial and they struggle for hours.
For better or worse, junior programmers are often the maintenance programmers fixing the bugs, at least where I've worked. Granted, there's going to be some code that they need a senior programmer's help with now and again, but the code should be as transparent as possible. If you write code that is so clever that the maintenance programmers can't easily read it, then you'd better be willing to maintain it yourself or do a lot of hand-holding. Sometimes that's inevitable, but it shouldn't be done without good reason.
-
Marc Clifton wrote:
Yuck.
I agree. when looking at the example, the readability went to hell. Not 100% sure what the example query was going to return as a result.
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
-
PIEBALDconsult Please, The issue here is the discussion of a new possible concept, we can discuss about best practices of coding in another post. :zzz: Read the things before show yourself to the readers ! Regards.
Member 10277067 wrote:
discussion of a new possible concept
Understandable.
Member 10277067 wrote:
discuss about best practices of coding in another post
Not so. If a new concept does not adhere to good or best coding practices, then it will not make it very far since people will be less motivated to using it.
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
