Jan 26 2012

Java stuff that you should know:What are the differences between C++ and Java?

Category: English posts,Miscellaneous,TechnicalIuliana @ 16:48

Java vs. C++ Because somebody brought up this subject here I decided that this is the question I should answer next. I am a developer from the old generation,at least this is how we call it here in Romania. Turbo Pascal was my first, (red cheeks :D) then I learned C, C++, Php, Java and .Net. With Java and C++ I have had the longest and most stable relationships. So I think I am able to answer this one, though I have to mention that nowadays you could be asked to compare Java to other languages too.

Again this can considered to be a difficult question mostly because there are a lot of differences between these two languages. That’s why you want to start your answer with the differences that remove any doubt that you know both languages pretty well, and usually this means getting technical. This is the how I would answer this question:

  • Java is multi-threaded, C++ is not
  • In Java primitive and reference data types are always passed by value, C++ uses also references and pointers.
  • Java has no pointers, C++ does
  • Java has implicit memory management through garbage collector, in C++ memory management is explicit
  • Java does not allow operator overloading,  C++ does
  • Java does not need destructors, C++ does
  • Java does not have type struct and union, C++ does
  • In Java, types cannot be overridden, in C++ we can do that.
  • Java does not provide multiple inheritance using classes (or virtual inheritance), C++ does
  • In Java, arrays have fixed sizes and attempt to read from an index bigger that size -1, will cause an exception. In C++ attempt to read from an index bigger that size-1 might even succeed and the value returned is the current value stored int that memory block.
  • Java programming model is totally compatible with OOP programming. C++ also supports functional programming, procedural and template programming.
  • Java is a WORA/WORE – write once run anywhere/everywhere (any compatible JRE ) , C++ is a WOCA – write once compile anywhere
  • Java has built-in support for comment documentation
  • Java has no native support for unsigned arithmetic, C++ does. (Has anybody used that in C++, ever?)
  • In Java there is no need for scope resolution operator (::)

Of course there’s more, but this should be enough at an interview. Fell free to add anything you might consider important. As always I am eager to learn new stuff.

Tags: ,

Jan 19 2012

Java stuff that you should know: difference between abstract classes and interfaces

Category: English posts,Miscellaneous,TechnicalIuliana @ 17:14

Many times after a Java Interview I have asked myself if my answers were correct, if the person interviewing me realized that I understand a certain concept and if I was able to express my knowledge in order to achieve that. So I will start writing on my blog how I would answer some common Java Interview questions.

So, in Java what are the differences between an abstract class and an interface?
This is a question with one big answer, not only because there are that many differences between abstract classes and interfaces, but because there are so many ways to say it. So, here is what I would say about interfaces:

  1. Interfaces are equivalent to protocols. They basically represent an agreed-upon behavior (a contract) to facilitate interaction between unrelated objects.
  2. Interfaces are a capsule for a group of methods with empty bodies or prototypes (abstract methods ) and implicitly final static members (constants).
  3. Interfaces have all members public impilicitly.
  4. Interfaces are declared like this:
    public interface TestIntf {}
  5. Interfaces can only extend other interfaces and keyword implements does not apply to them.
  6. Interfaces can extend more interfaces.
  7. If an interface has no direct superinterfaces, then the interface implicitly declares a public abstract member method m with signature s, return type r, and throws clause t corresponding to each public instance method m with signature s, return type r, and throws clause t declared in Object, unless a method with the same signature, same return type, and a compatible throws clause is explicitly declared by the interface.
  8. Interfaces are considered to be slower because they require extra indirection to find the corresponding method in the class implementing them.
  9. Interfaces support only public and default access modifiers.
  10. Interfaces can be declared abstract, so the Java compiler would not complain if your declaration would look like below, but the abstract modifier is redundant as interfaces are implicitly abstract.
    public abstract interface TestIntf {}

Here is what I would say about abstract classes:

  1. Abstract Classes are the middle ground between interfaces and classes. They can have both abstract and non-abstract methods and constant and non-constant fields.
  2. Abstract Classes can have constructor, but it can never be called directly. It can only be called using super in the extending class or is automatically called by the jvm.
  3. Abstract Classes support all access modifiers.
  4. Abstract classes can be declared like this:
    [access_modifier] abstract class TestAC {  [ implementation]    }
  5. Abstract Classes can implement any number of interfaces, can extend only one class (which can be abstract or not – the condition is not to be final) and implicitly extend class Object.
  6. Abstract Classes can have only non-abstract methods (but what would be the point?). Abstract Classes which have only abstract methods and constant fields are called fully abstract.

And what would I say about both of them:

  1. Java supports multiple inheritance only through interfaces.(Some say it is limited. I say it is practical.) Why? Because extending multiple classes may lead to problems when they have methods with identical signatures. (Remember C?)
  2. The use of interfaces or abstract classes is determined by the project requirements and design.
  3. Using abstract classes affects the flexibility of your code, because class extension rips away class individuality.

If you have anything else to add, or something here needs correction, your effort will be kindly appreciated.

Tags: , ,

Dec 24 2011

VirtualBox with Gentoo(3)

Category: English posts,TechnicalIuliana @ 3:35

Well, we have a VM with Gentoo and an interface. Let’s make the virtual machine more flexible and more cooperative with the operating system on your computer. For this we have to install VirtualBox drivers on your Gentoo. After restarting your system upon setting up the interface you can log on to your desktop interface. But for installing other tools you will still  need the console. For the purpose of this tutorial we will use the Kde terminal named konsole.

To open a terminal: click the button on the left corner of the screen (the “K” button) and in the menu that is displayed at the top there is a text field. Type konsole and click on one of the results returned. (print-screen) Or press Alt +F2 and the same text field will appear at the top of your desktop. You can use it to start any application you want. You will be logged in with the normal user so in order to install things you need root access. So, in the terminal you need to use the su command:

# su -

You will be asked for the root password which you will type and then you can start installing. (By the way if any emerge process happens to fail, you can force to continue by using: # emerge –resume)
Continue reading “VirtualBox with Gentoo(3)”

Tags: , , , , ,

Apr 13 2011

Project Development steps (best practices)

Category: English posts,TechnicalIuliana @ 14:18

You’ll find the internet a lot of opinions regarding this matter, but I really want to post here the way I do it, because it might be useful to someone. Being a Java developer, of course I’ll be referring to Java projects, but the steps are common to all projects, regardless of the technology used to develop them.

This is how I do it:

  1. I decide de name of the project. Any project has to have a name that tells a first time user what it does. The name mustn’t be too long or too complicated. The last project I worked on was called Expenses Manager. Well, what do you think? Can you easily infer what it does?
  2. Based on the name of the project I name my packages. Any JBoss package name has jboss in them, any Hibernate package name has hibernate in it and so on. But when the project name is long, like mine was, it is recommended to create a short name composed of the starting letter of the words which compose the project name – in my case em. For example one package of my application was called jj.em.test, jj is my nickname and test is the scope of the classes inside this package, in this case, classes used for testing. Some developers precede package names with com or org. Anyway you decide to name your packages the main purpose is to help a first time developer looking at your code understand the way the project was organized and why.
  3. I Define a logger for my project. Although there are a few logging libraries on the web, my recommendation is to keep things simple and not make your jar bigger than it needs to be or to complicate yourself with classpath  stuff. How do you keep things simple? By using java.util.logging.Logger the logger class provided by the jdk.  If you want an example here is a console simple logger implementation and here is a simple file logger implementation. (I dare you to do better!)  Why would you need a logger? Because you might need to see outputs, values of your variables at a specific step in development without switching to debug and using breakpoints and stuff, because this might slow you down. When you no longer need the logger, you can just turn it off and all the gibberish disappears.
  4. I set up a testing environment or module. Your application will need testing, no matter how small you might consider it to be. It is better to start with a few test classes which you will grow in parallel with your application by adding new test methods. Same as internationalization (point 5), starting to develop the test module when your application is already done might be a pain in the ass.
  5. I Internationalize! You might ask, why is this a key step and why is it really needed? Well, my dear readers, any time you start a project you must think that might be useful not only to you but to people that one day might actually pay for it. Look at the big picture, and internationalize at the beginning, because if you need to do this later, it will be a big pain in your smart ass!
  6. I Use a building tools like Ant or Maven. Ant for small projects, Maven for big ones which have a lot of dependencies. Also, you might want to check out JRebel.

Tags: , , , , , ,

Mar 23 2011

Eclipse best practices

Category: English posts,Miscellaneous,TechnicalIuliana @ 16:23

1. Put in eclipse.ini (after -starup line and it’s argument)

eclipse.ini sample:

c:\Program Files\Java\jdk1.6.0_24\bin\javaw.exe

Continue reading “Eclipse best practices”

Tags: , , ,

Feb 17 2011

De-a web designeru’

Category: Miscellaneous,TechnicalIuliana @ 16:36

Zilele astea mă joc de-a web designeru’. Mai exact, refac interfața unui proiect mai vechi de-al meu la care  am lucrat pe când eram un developer bine definit care se credea atoateștiutor și s-a băgat și în webdesign.

Developerii au impresia că web designerii sunt chelea sulii și că la nevoie ar putea face treaba unuia fără probleme. Din păcate și majoritatea companiilor cred la fel, ceea ce este cea mai mare greșeală posibilă. Eu am dat cu turul meu cel sexy de pământ, când interfața mea a început să se comporte haotic și pentru că nu aveam timp de pierdut, dar aveam și web designer la îndemână (de la care învăț tot ce pot acum)  m-am apucat să îl asist pe geniu în repararea prostiilor mele.

Am fost oarecum jignită când a numit html-ul cod. Cum să numești html-ul cod??? Dar treptat-treptat și agasând-ul cu întrebări idioate mi-am dat seama că exact cum pentru mine lucrurile sunt simple și se leagă pur și simplu în programare, așa pentru el se leagă html-ul, css-ul și js (js mai știu și eu, la nivel de programator desigur…) și practic ceea ce face el, nici nu poate fi design, ci aduce mai mult aduce a proiectare.

Am scris toate astea pentru că am citit astăzi un articol numit Six things JavaScript needs to learn from Java și fiind încă prinsă în experiența de mai sus am și eu o părere despre asta. Eu vreau să rămână JavaScriptul așa cum este sau să evolueze fără să se inspire de la limbajele Top Level, pentru că este un limbaj simplu și flexibil ce a fost  creat pentru dezvoltarea aplicațiilor web. Și așa trebuie să rămână, simplu și flexibil. Dacă vreau structurare și chestii bătute în cuie, pot alege oricând un limbaj Top Level și tehnologiile aferente (JSP sau ASP).

Și apropos’ chiar dacă am spus mai devreme că este simplu, nu înseamnă că nu poți face chestii super-inteligente cu el. Aruncați doar o privire aici, când aveți timp.

Tags: ,

Jan 24 2011


Category: TechnicalIuliana @ 1:08

Acum câţiva ani pe când eram o proaspătă speriată studentă la o facultate la care nu aş fi dorit să fiu, trebuia ca orice student să îmi aleg tehnologia în care urma să fac carieră. Trebuia aleasă una pe care să o ştiu la superlativ la sfârşitul facultăţii, pentru că  un Jack of all trades and master of none  nu e chiar aşa de apreciat în domeniul IT.

Până în anul III, când am reuşit să îmi cumpăr primul calculator, la facultate ni se prezentaseră foarte succint şi abstract câteva limbaje de programare C, C++ şi Java, un tip de baze de date (SQL) şi limbajul de programare asociat PLSQL. Mai studiasem singură Php şi HTML pentru că cercurile prin care mă învârteam erau compuse din oameni care ştiau dintr-astea şi nu voiam să mă simt pe dinafară. Era clar că habar nu aveam pe care dintre ele să mă axez.

La şcoală se vorbea intens despre platforma .Net şi C#. Calculatorul meu nu avea putere pentru aşa ceva. Aşa că am ales Java. Am terminat facultatea destul de bută în domeniu totuşi, dar am avut şansa de atunci să învăţ, să cresc.

Au trecut 4 ani de atunci, pe 7 februarie încep oficial să lucrez prima oară ca Java Senior Developer. Mă întreb uneori unde aş fi fost acum dacă alegeam oricare dintre alternativele de mai sus. Dar mă bucur că am făcut alegerea asta.

Mai ales după ce am citit studiul acesta şi am aflat că Java este cel mai popular limbaj de programare începând cu 2006 şi că încă de la apariţia lui, n-a fost niciodată mai jos de locul 5 ca popularitate. C#, alegerea multor foşti colegi de facultate, deşi a fost creat prin numeroase împrumuturi de la cele mai performante limbaje de programare, n-a urcat niciodată mai sus de locul 6.

Tags: , ,