A fool don't look at the reality.
as nodejs nowadays is popluar in server side programming,
the benefit is very obvious.
as kls said:
"""
I only have an anecdote to add: I've recently reimplemented a Java calc server (finance) in Javascript (nodejs v0.6.8). WRT development time, the Javascript implementation was a breeze compared to the original Java implementation with far fewer lines of code. It was a breath of fresh air, really.
The Javascript-based server is able to calc through 2.4k trades/sec whereas the Java server handles 400+/sec on the same hardware using less memory. I wouldn't attribute the speed increase to raw V8 vs. Java 7 performance but rather to the implementation. The Javascript implementation uses far fewer data structures, does an order of magnitude fewer method calls and takes a more straight-forward and terse approach.
Needless to say, I'm very happy with the performance of node.js. And this, coming from someone who was Java only for many (9) years.
"""
2014-05-12 16:30 GMT+08:00 Doug <beafdefx@gmail.com>:
Please, just stop. You are arguing with a fool!
On Sunday, May 11, 2014 10:30:22 PM UTC-7, Kristopher Micinski wrote:What are you even talking about: Any JavaScript program is also going
to have threads, too.
You seem to be making this argument: Java has multiple threads, and
that makes the programs slow.
It sounds like all of this is coming from a completely uneducated
viewpoint on systems design, but there are a number of
issues.
Please understand, however, that all of the issues in Java carry over
(and worse) to JavaScript, you still need multiple threads, you still
need a garbage collector.
Please also quit citing other Java products as evidence that it has
anything to do with Android. Forget Java, android doesn't run Java.
Android runs Dalvik. Which is completely different than Java. You
can translate anything into Dalvik, people usually translate Java,
there's no reason you couldn't also translate anything else.
Kris
On Mon, May 12, 2014 at 1:22 AM, 李白|字一日 <cali...@gmail.com> wrote:> 2014-05-12 11:22 GMT+08:00 bjv <bjve...@gmail.com>:
> the slow comes not just from the loading of java based apps. but the java
> itself and the bad programming guidance, which uses too many threads and
> classes which take a lot space. and what even worse is you will sometimes
> have to do deep inheritance.
>
> it adds extra overheads to make itself run.
> these are ignored while benchmark.
>
> i am by no means expert in languages. but it is true that java is slow to
> what ever products made by java.
>
> eclipse, android, j2me, netbeans, idea.
> none of them are famous for their speed and memory saving.
>
>
>
>>> To post to this group, send email to android-d...@googlegroups.com>>
>> Ugh! You don't get it and likely never will. There are so many things
>> wrong with your assumptions/statements in all of these threads. It really
>> isn't worth the time to debunk them all.
>>
>> But for what its worth, there is small overhead with respect to running
>> Java/Dalvik on Android. That said, it is mostly upfront. JS is an
>> interpreted language. Outside of the various ASM-JS experiments, Your
>> html5+JS likely will always be interpreted. In a broad comparison, it will
>> almost always be slower. Your thinking that you get to share all those JS
>> object goodies between various apps/components is in itself a cause for
>> concern.
>>
>> In an effort to remove the Dalvik overhead on Android, the Android guys
>> are now rolling out ART (a variant of llvm) that will transfer most of that
>> overhead to installation time. At that point, Java isn't going to be much
>> different than C++ from an execution perspective.
>>
>>
>> On Sunday, May 11, 2014 1:41:41 PM UTC-5, 李白，字一日 wrote:
>>>
>>> if it is not, why should you go native with c/c++ based ndk programming?
>>>
>>> it is surely related to the programming language.
>>>
>>> javascript 's speed acceleration is also related to the language and its
>>> optimization, which is almost always c/c++.
>>>
>>> i have never experienced the fast feeling of java technology both in
>>> desktop or server side.
>>>
>>> i never experienced fast feeling in android, eclipse, java ee, j2me. am
>>> i fooled?
>>>
>>> eclipse is famous for it's slow and memory consuming, though it is the
>>> greatest ide i ever used.
>>>
>>> javascript based ide, like local compiled c9.io is very fast and
>>> responsive, thought it is not that mature.
>>>
>>> why ? ? ?
>>>
>>> and if android ui design can be written directly in html + css, it has
>>> all the flexibility css and html have now. If you know the web technologies,
>>> you should know what i mean.
>>>
>>> it is meaningless to discuss about the languages' performance, but the
>>> trend is that javascript will play a more important role in server side
>>> programming, hardware based programming and browser side programming.
>>>
>>>
>>> 2014-05-12 1:03 GMT+08:00 Colin M <colin...@gmail.com>:
>>>
>>>> I'll ignore the unqualified claim that the slowness of Android is due to
>>>> Java.
>>>>
>>>> It sounds like your complaint is that you can't develop native apps in
>>>> your preferred language and that you're using an outdated claim about Java
>>>> to support your desire to change the current language of choice for Android
>>>> development.
>>>>
>>>> The XML based components can all be done via code. Do you have an
>>>> example of how they are "far from flexible"? There are many limitations,
>>>> but you are welcome to write your own custom Views to get around any
>>>> limitations. I have many of my own complaints about some of the UI system,
>>>> but I have no reason to believe the current state of things would be faster
>>>> or more flexible if it were in another language. That's not the thing
>>>> limiting flexibility or causing speed issues, that's more about the
>>>> implementations. I've created and seen many fast and fluid and complex UIs
>>>> on Android, but you sometimes have to do some real work to get them and they
>>>> don't always drop right out of the API in your lap :) A better argument
>>>> would be to single out issues with the UI libraries and talk about how to
>>>> improve them. This has little-to-nothing to do with implementation
>>>> language.
>>>>
>>>> On Saturday, May 10, 2014 10:50:44 AM UTC-7, 李白，字一日 wrote:
>>>>>
>>>>> Java-based Android is very slow and memory consuming.
>>>>> and the XML based UI components are far from flexible.
>>>>>
>>>>> if Android sdk provides an html5 + javascript alternative, it would
>>>>> greatly improve the android app possibilities.
>>>>>
>>>>> as we have seen more and more popular apps are written by html, css and
>>>>> javascript.
>>>>>
>>>>> i think it is a good time to provide a javascript based SDK,
>>>>>
>>>>> with a standardized Android UI framework like Twitter's bootstrap,
>>>>> every web developer can develope his app with ease.
>>>>>
>>>>> the webkit and v8 are every mature to google.
>>>>>
>>>>> why should we stille using java? which is slow and memory consuming?
>>>>>
>>>>>
>>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Android Developers" group.>> To unsubscribe from this group, send email to> To post to this group, send email to android-d...@googlegroups.com
>> android-developers+unsubscribe@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-developers?hl=en
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Android Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/android-developers/4UrtNOPympc/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> android-developers+unsubscribe@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.> To unsubscribe from this group, send email to
> android-developers+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-developers+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "Android Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-developers/4UrtNOPympc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment