Oracle continues to move Java EE into more open-source friendly realms. Who would have believed it?
24 plus ones
Shared publicly•View activity
View 8 previous comments
- I don't hire anyone to do Java programming if they don't come out of a C language background.
Java was and is doing just fine in the enterprise space. I have replaced lots of interestingly stupid and insecure applications with Java. If Java had security problems, they emerged in the wake of its massive acceptance. And if they weren't fixed effectively, that falls under the rubric of the aforementioned Dog's Dinner and Oracle might have fixed them.
If you don't think a sandbox approach is secure, tell me of any programming language which doesn't have stack overflow issues. Just now, it seems Linux is plagued with Bluetooth security issues.
I'll expect anything you have to say further to tell me which language is both fast and whose stack pointers are entirely safe.
Android Java isn't Java, let's just make that plain. It certainly isn't created with a javac. It doesn't run in a JVM. Those who write to an NDK face all the hurdles of every platform-specific development strategy, with few of its advantages. Deployment is a nightmare.
I am no Java Fanboi. I come from C and assembly languages. I am no technology zealot and I have been at this a very long time. I architect enterprise stuff which processes a million health care claims a day and supports a star topology to 36 franchises and hundreds of thousands of external endpoints. My stuff runs on mainframes in dedicated Java hardware. I don't think IBM and Red Hat have backed Java this far, especially not Red Hat with JBoss SOA / EAP - to say the nails are in the door for Java, just yet.2w
- if you don't think Java has issues with Stack Overflows and other issues traditionally asserted to be C/C++ issues then you have very little real Java experience.2w
- You failed my little test. You didn't mention which language was both fast and had safe stack pointers.
I've been writing C since 1977 at Bell Labs. I started writing Java the first night it was available for download from Sun Micro. I've taught C, C++ and Java. Hurl your cardboard thunderbolts elsewhere.2w
- and yet Java still has those same issues and more...you still use pointers in Java, you just don't know it (which IMHO is worse)2w
- That's really enough out of you. You fail again. Which language has perfectly safe stack pointers? This time, do fire a few neurons and answer the question you were asked.2w
- technically no language - despite many claims to the contrary - has perfectly safe stack pointers b/c there is no such thing. Once you introduce the concept of a pointer you throw safety out the window. You may make it harder to work with the pointer and manipulate it, but you do not create safety.
If you care about correctness, types, etc - then you'd be using Erlang, Ada, or another highly contracted language - but even they can have pointer issues.
No language can fully protect against a bad programmer, and the only secure computer is one that is turned off, disconnected from everything. Everything else is a compromise between different factors.2w
Add a comment...