-
Obsession with new toys
I will be returning to eventing/EDA soon ...
There have been a number of posts lately on Windows Workflows 4s break with the past citing continual change and lack of support being a big problem.
Id like to make a few comments on this. The number one productivity killer in .NET today is undoubtedly new technologies and learning how to implement them well. While these are without doubt superior to past products eg Remoting /WCF , WIndows Forms / WPF , DataSets/LINQ for Sql people seem to be making the move because the feel its new and hence will be supported longer.
This...
-
C# and F# are complementary
I just had a lot of repetative web work to do and im starting to look at F# , it looks like F# fits really well with C# replacing the batch files / scripts you use and great for proto typing.
Things where C# are better
Lib /UI Development
Writing large assemblies
When you need low level control or unsafe.
When you use TDD
When F# is better.
When you need quick and dirty codes ( utilities)
Screen / Web scraping
AI scripts
Mathematics / financial scripts
Workflow scripts
Frequently changing code.
Project control.
How often with C# did you have to do something really...
-
C# for low latency applications
There is no argument modern languages such as Java and C# allow quicker , safer and easier to maintain applications yest there is still a very large amount of C/C++ applications being written.
A lot of use of C++ is simply for 3 reasons
- A view of better performance
- Maintaining an existing application
- GC pauses
- Environment requires it.
Lets look at these issues
In practice with realistic budgets a Java/ C# applications will tend to have better performance due to better and easier to use collections and optomizations. The main performance difference relates to...