Tag Archives: Top 6

What are Top 6 Characteristics Of A Successful Trading Strategy

What are Top 6 Characteristics Of A Successful Trading Strategy

Here is another gem from my NYC source so big thanks to him

Top 6 Characteristics Of A Successful Trading Strategy

See if we got them through our FREE newsletter

NOTE I now post my TRADING ALERTS into my personal FACEBOOK ACCOUNT and TWITTER. Don't worry as I don't post stupid cat videos or what I eat!

Top 6 reasons why I use Matlab over R with it draw backs when building HFT trading platform

Top 6 reasons why I use Matlab over R with it draw backs when building HFT trading platform

Learn more how I use Matlab over R for HFT. Join my FREE newsletter

No debugging IDEs like RStudio

R does not do FPGA

R models cannot be code generated into C++  but can be embedded as  R session but not fast enough  (Linux as well with RCPP)

Some R packages does have a full set of functionality like Econometrics (but that could change)

R packages might be vetted as well as compared to Mathworks QA. Can banks trust it?

Devcelopment time of coders and debugging vs buying it with Matlab?

 

 

NOTE I now post my TRADING ALERTS into my personal FACEBOOK ACCOUNT and TWITTER. Don't worry as I don't post stupid cat videos or what I eat!

Top 6 reasons why Google’s GWT is the best web framework to work with for any Java web application

Top 6 reasons why Google’s GWT is the best web framework to work with for any Java web application
1. There are numerous methods to deliver data messages from the server to the client browser. It seems best to have the server end deliver JSON messages since it is lighter and faster than traditional XML. Also, third party developers may be able to leverage off a server based JSON messaging service which results us developing a potential third party API in the future. We would be able to serve up with a third party client regardless if it is written in PHP, Python, etc. It is much faster to develop with and easier to maintain the code base as well.
2. GWT is highly secure as we can have the server based code render in obfuscated JavaScript. This will prevent potential users from stealing source code or even attempting to reverse engineer the application. They will have no way to reverse engineer the Java code sitting on the server as well.
3. Since GWT will deliver the client side code in 100% JavaScript, it enables us not to worry about maintaining separate code implementations or separate code fixes specific to certain major browsers like Internet Explorer or Firefox. This makes the client application much more lightweight as compared to JSF which can be pretty heavy.
4. As for mobile browser/development, we can have the server side detect the type of browser the client is using. If they are using any mobile device like an IPhone, we can have the server execute a special implementation of the code where we either fully limit the user from using the site or offering a limited capability of the site. Most GWT based applications are ready for Google Android as well. I still think a special Objective C based IPhone application will need to be developed if you want to sell it through ITunes.
5. GWT is no different than JSF where you can have widget based applications sitting on some sort of dashboard or panel within a browser session.
6. We could deploy this prototype onto Google’s App Engine fairly easily for initial development. As the initial code and data use will be fairly minimal, we should not anticipate any costs at all. As your application and data scales out, we can then implement onto our own server quite easily by generating our own WAR file for whatever Java container we decide to go with in the future.

NOTE I now post my TRADING ALERTS into my personal FACEBOOK ACCOUNT and TWITTER. Don't worry as I don't post stupid cat videos or what I eat!