Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm trying to improve the clarity of my communication with other developers.
There has been times I've found when I'm describing to other developers to use the # symbol in code and found that I hesitate then say its name three different ways. I say pound, hashtag and octothorpe (but it doesn't stop there, as it's sometimes sharp in the case of music and C#).
Some examples of its use are in C++ for includes, used in SQL for comments, and used in Java's EL as #{}
I like things to be done simply and consistently. I am curious if there is a standard way (or more universal way) of referencing the symbol by name, and if so what it is. Or is there a different standard for referencing it by different languages, or even SQL?
It's not pound, that's £
It's not hashtag, that's Twitter.
It is "hash" though. And in the case of the language "sharp".
It's all based on what you choose to call it where other developers will understand. It's up to the user to decide what you choose to call it and if you are working with others it's up to you guys to have good enough chemistry to know what each other is talking about.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 years ago.
Improve this question
I know that Robust is a Feature of java programming language. But I don't know what is the exact meaning of it and how to any programmer benefited by it.
It's a generic adjective that means different things for different people. There's no measure of robustness, so you can't say "this language is more robust than that".
It might be used to differentiate a language from a "toy" language, that isn't meant for general purpose programming, but you aren't going to find any clear definitions, because there isn't one.
Robust simply means heavy and strong and Java has a lot of facilities for programmers such as memory management, security features, networking features etc.
For details regarding exact meaning of feature "Robust", you can follow this link https://www.javatpoint.com/features-of-java
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
There are lots of programming languages available in the market then how do we decide what programming language we should use for our products?
What are the key factors we should consider before using any programming language?
What are the capabilities of language we should check for long term?
Please share your views
Let me start with your 2nd Question - "Long Term", well dont assume the Programming Language alone will help you for the long term. Of course Language will have its impact but take a look at the Architecture when you want to think about Long Term.
Both Java and JavaScript are very capable languages, you must identify your Software Requirement and decide on what language is the best for you.
e.g. If its a Quick project (such as an Adacemic assignment) making use of Node will get you off the ground faster.
Pay attention to the Quality Attributes and think what is the best choice for you...
Performance: You'll find various benchmarks stating Node may not be the best choice if you wants to do heavy lifting.
In General for Factors for the choice of Language go through https://www.uniassignment.com/essay-samples/information-technology/the-factors-influencing-choice-of-programming-language-information-technology-essay.php
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have written front-end of my application in SWT/JFace. It working well but problem is that all of the front-end goes in a few classes and some classes grow more than 10000 lines of code. Tell me is it normal to have classes in Java with more than thousands of lines of code or how can I reduce it?
It is definitely not good practice to have such huge classes and a signal to better refactor your code. See http://clean-code-developer.com for a clean code guideline.
You can't judge a java class on lines number. No standard can tell you about the preferable number of code lines.
The important thing to keep in mind is that classes should be designed according to proper OOP design using: encapsulation, polymorphism ...etc and java best practices.
But a Class with >1000 lines of code it's probably unreadable and have a bad loosely coupled approach.
If your number of code line start to increase quickly try to optimize your code and use dedicated design pattern like Strategy pattern and many others one.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Java appears to force a programmer to use OOP the way I see it, while C++ does not so far as I am concerned....
I wish to know whether this is syntactically true for Java and C++
That is like saying Haskell forces programmer to use recursive calls. You can program procedurally in Java, and you can program with OOP mindset in C++. So neither answer is correct. But the concept is that in Java you should use OOP at all times and in C++ not, only if you wish so, but there is no one that can enforce it on you. (Maybe your boss by firing you, or SO being mean to you)
It is like firing a gun. You can either fire with the muzzle pointing at someone else (using OOP in Java) or look straight into the barrel while pulling the trigger (not using OOP in Java)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
My question is fairly simple, I haven't found a direct answer to it.
Is redundant code between two or more packages to achieve package independence considered as a good or bad practice, for instance I have two packages one does a download-and-cache , the other is for readfromserver-and-cache. while cached data and mechanism are completely different but have some common classes/methods.
Shall I create a third package which holds commons, and break package in-dependency?
Or shall I continue with two packages and will result in redundant code?
Lastly, to go deep in design and dependency, I'd appreciate it if you suggest me good material to read.
*Please note : I write in java , common code is not that much
I think that you go for creating an interface for the Cache. If the cache is not the same for both packages then common code can be in a abstract class and the individual packages can implement the rest.
Of course if the code is identical, then strip it out to its own jar.