Support Board
Date/Time: Fri, 22 Nov 2024 07:05:16 +0000
Development and Suggestions
View Count: 3865
| [2013-04-20 01:35:43] |
| |
|
Hello, We are very busy at this time with critical development for Sierra Chart. We ask that you keep your questions directed towards us to a minimum. User Discussions are fine. We will keep out of those. Once a thread is marked "User Discussion", we do not look at it again. As far as feature requests go we will not be responding to those. We are not able to focus on any feature requests at this time unless they are something relatively simple and just take us a matter of 20 or 30 minutes. We are in the process of completing development of the new spreadsheet functionality and removing the Microsoft .NET completely from the project. Sierra Chart will be free from the .NET plague once and for all. We are also removing all external API components into separate processes. In regards to client-side API components, we discuss this here: http://www.sierrachart.com/index.php?l=doc/helpdetails76.html The overall objective of this, is to have 100% full control over all code, make Sierra Chart 100% stable, and as fast as can be. Sierra Chart will also statically link with the necessary C++ and development framework libraries we use so there will not be a need for these Microsoft redistributable packages. So once again, please keep your questions directed towards us to a minimum, and please avoid asking us any unnecessary questions. You will probably notice, that we have stopped responding to requests where responses are not deemed necessary. We simply do not have the time for unnecessary discussion here. We are not ignoring you, we simply do not have the time for unnecessary discussion. We are always here to help with basic usage issues and taking care of critical features. We do not have time for programming or alert help and you are unlikely to get a response from us on those, unless there is some kind of problem we need to resolve in Sierra Chart ACSIL or elsewhere, or some improvement that we see is needed. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2013-04-22 07:18:10
|
| [2013-04-30 08:39:46] |
| |
|
For those of you who may not understand the comment about .NET being a plague, need to understand that it is from a programming perspective. Not that Sierra Chart at this time has a significant problem because of it. It does not. Although from a programming perspective, it is not pure 100 percent native machine code in its entirety and we are not happy about that. So this comment is from a technical perspective and from the perspective having consistent well-organized code. Sierra Chart is not a .NET program. We are not .NET programmers. Sierra Chart primarily is what is known as a native C++ program which is specifically for Windows and current CPUs. .NET, is some marketing term ( Just another ridiculous name Microsoft has come up with) for the Common Language Runtime from Microsoft which provides a managed programming environment with a just-in-time compiler. It is something that Sierra Chart in the past did not use, but has some limited support for recently to interface to certain components that use it. We are removing these components. One of these components is the current spreadsheet functionality which we are building ourselves. We do not like .NET, because it complicates our programming, in the area where there is .NET code, we are working with a different kind of language and programming method., it adds some amount of additional CPU usage., increased memory use, is hard to debug, very slow to compile, sometimes cause occasional problems among users when it comes to starting Sierra Chart, and is proprietary and locks us into Windows. .NET also is a highly proprietary heavyweight Microsoft software technology. We do not see it as the future and it may not have a very good future. We are going to be proceeding to supporting other operating systems and .NET is not the path towards that. Programmers are locked into Microsoft Windows if they use .NET. So while our competitors use .NET, we see it as an evil plague that needs to be gotten rid of for good, from Sierra Chart that is. If programmers find it useful, then great. It's not for us though. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2013-05-01 07:30:52
|
| [2013-05-13 04:48:07] |
| |
|
This is a very busy time development for us. A lot of critical low-level development going on which will carry the Sierra Chart project forward for the coming years. Our goal is to create an extremely solid and fast piece of software with very good quality and reliable integration to trading and data services. We do thank you for keeping your questions to a minimum and we do our best to answer everything that we see that does require an answer. For the time being we cannot take any new suggestions now which require any significant amount of work. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2013-05-13 04:48:36
|
To post a message in this thread, you need to log in with your Sierra Chart account: