Cookwitter | Quetter | 関東渋滞
にらめったー(NearMetter)とは、気になる2人のTwitterユーザー対談が見られるツイ談(Twi談)サイトです。

Twitterユーザー名

vs

Twitterユーザー名

取得可能 (最終取得時間:2011-05-11 19:12:48)

headiusolov のツイ談  

olov

@headius you're asking the wrong question

2011-05-11 03:29:24 - 返信元ツイートを取得する

 

headius

@olov Ok, I'll bite...what's the right question?

2011-05-11 03:31:01 - 返信元ツイートを取得する

 

olov

@headius If the libraries on top of the JVM was designed around async from day 0, what would that mean? Kind of what happened with node.js

2011-05-11 03:36:31 - 返信元ツイートを取得する

 

にらめったーはご覧のスポンサード リンクの提供でお送りします

headius

@olov Node only exposes a small set of async libraries, and other libs will block all of V8. JVM has async options *and* threading too.

2011-05-11 03:39:01 - 返信元ツイートを取得する

 

olov

@headius not sure what you mean with other libs? in the ecosystem around node.js, everything is built around non-blocking

2011-05-11 03:41:43 - 返信元ツイートを取得する

 

headius

@olov Other libs bound into V8 that don't support async. Of course, you can really only use what Node.js gives you... not so on JVM.

2011-05-11 03:54:18 - 返信元ツイートを取得する

 

olov

@headius the ecosystem around node makes it hard (not impossible) to use blocking stuff (and easy to use non-blocking), that's the point

2011-05-11 04:02:28 - 返信元ツイートを取得する

 

olov

@headius not saying it can't be replicated elsewhere (like the JVM). Seems like V8 is kind of awesome in itself though

2011-05-11 04:03:47 - 返信元ツイートを取得する

 

headius

@olov V8 is just another VM that happens to be specific to JS. Fast, sure, but so is JVM. I'm positive Node.js could be done as well on JVM.

2011-05-11 04:08:36 - 返信元ツイートを取得する

 

olov

@headius v8 is not just another VM, it's an awesome one. In my book Bak and the v8 team is not far after Pall and his LuaJIT solo effort.

2011-05-11 05:33:16 - 返信元ツイートを取得する

 

olov

@headius Let's talk state of the art. Do you think that Lua could run as fast on top of the JVM as it does in LuaJIT2 (asm+c)? Just curious

2011-05-11 05:57:27 - 返信元ツイートを取得する

 

headius

@olov LuaJIT is also nowhere near as fast as JVM could be, in my estimation. Granted, we need to prove it now :)

2011-05-11 07:33:11 - 返信元ツイートを取得する

 

olov

@headius I hope you don't blame me for questioning that for now. LuaJIT and v8 speak for themselves (vs LuaJ and Rhino)

2011-05-11 08:00:32 - 返信元ツイートを取得する

 

headius

@olov LuaJ and Rhino are not representative of JVM's potential. Look at Remi Forax's PHPReboot, which runs as fast as Java for most things.

2011-05-11 08:20:40 - 返信元ツイートを取得する

 

olov

@headius to me, LuaJ and Rhino are more representative of the JVM's ability to run Lua and JS, than an impl of a PHP-like lang. YMMV

2011-05-11 08:41:05 - 返信元ツイートを取得する

 

headius

@olov Well, you don't know the JVM like I do :)

2011-05-11 08:47:40 - 返信元ツイートを取得する

 

headius

@hannesw @erikcorry @olov It may not even be using server mode, which is another 2-3x faster than client. Lots of room to improve.

2011-05-11 08:52:13 - 返信元ツイートを取得する

 

headius

@hannesw @erikcorry @olov I have spent a lot of time reading Hotspot assembly dumps. It's possible to make JS extremely fast if done right.

2011-05-11 08:54:03 - 返信元ツイートを取得する

 

headius

@olov Let me describe invokedynamic this way: dispatch methods any way you want, JVM optimizes them like Java. i.e. very well.

2011-05-11 12:18:51 - 返信元ツイートを取得する

 

にらめったーはご覧のスポンサード リンクの提供でお送りしました

「@だれだれ」をベースに自動生成されております。返信元ツイートを取得するは「上記ツイート」から辿ってください。
Twitter Search APIを通して最新@ユーザーの100件をストリーミング表示しています。

headiusolov のツイ談コメント一覧

headiusolov のツイ談を転送する


その他のツイ談