Timeline for "How are you spending your time on the computer?"
Current License: CC BY-SA 3.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:40 | history | edited | Community Bot |
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
|
|
| Jan 9, 2017 at 12:20 | comment | added | Cody Gray | @jeroen That's just not true. While I agree that most inefficiencies are introduced by the developer writing inefficient code/algorithms, managed languages just do not have the performance that native languages have—at least not yet. The theory is that they should, and maybe eventually can even surpass precompiled code, but we're just not at that reality yet. There is a massive penalty you pay for JIT compilation, and the result of that JIT compilation is still nowhere near as optimal as what an ahead-of-time compiler can do. I don't know what you mean by "framework inefficiencies". | |
| Jan 9, 2017 at 6:36 | answer | added | Heslacher | timeline score: 7 | |
| Jan 8, 2017 at 16:14 | comment | added | Denis | Thanks to CodyGray and t3chb0t (can't link 2 users) I've edited the question to address the fact that windows forms is not slow. Thanks for the positive way of showing me how it can work fast ! :) | |
| Jan 8, 2017 at 16:12 | history | edited | Denis | CC BY-SA 3.0 |
added 524 characters in body
|
| Jan 8, 2017 at 16:00 | comment | added | Cody Gray | The ListView flickers in WinForms. It is a bug. Lots of workarounds available online. Start here for sorting. Also see this blog post. I have my own implementation that fixes these bugs and more in a class library, so I can just use that instead. The other UI problems are caused by either inefficiently manipulating them or failing to use BeginUpdate/EndUpdate. If you do that correctly, you won't have a problem. No one needs 100+ controls on a form; that's a UX problem. | |
| Jan 8, 2017 at 14:40 | answer | added | t3chb0t | timeline score: 9 | |
| Jan 8, 2017 at 14:30 | vote | accept | Denis | ||
| Jan 8, 2017 at 10:07 | history | tweeted | twitter.com/StackCodeReview/status/818036376771948544 | ||
| Jan 8, 2017 at 9:17 | comment | added | realvictorprm | @t3chb0t I went through many GUI systems(java swing, javafx, Qt, wxWidgets, WinForms and WPF) and I can only agree that the raw OS functions for GUI function are the fastest. I draw Waveforms and I'm very strict about performance and after all, WinForms is perfect in case of performance. Conclusion: WinForms is not slow! | |
| Jan 8, 2017 at 9:14 | comment | added | t3chb0t | @ArthurM. the alternative would be MFC but WinForms is rarely an issue. Usually it's the poorly written code. I bet you can bring MFC to their knees either and C++ won't magically make your application fast when you write inefficient code. | |
| Jan 8, 2017 at 9:10 | comment | added | realvictorprm |
@t3chb0t So far I know there isn't any way around managed code if I want to use WinForms and C++, or am I wrong? If that's right WinForms using C++ should only run a bit faster than WinForms using C#. However WinForms do run very very fast, there shouldn't be any problem if people don't try stuff like mentioned in your answer (add(..) every refresh ._.).
|
|
| Jan 8, 2017 at 9:07 | comment | added | t3chb0t | @ArthurM. you mean C++/CLI? Yes. | |
| Jan 8, 2017 at 9:06 | comment | added | realvictorprm | If I'm using C++ WinForms they'll run managed too, isn't it? | |
| Jan 8, 2017 at 8:21 | comment | added | delete me | I'm a little triggered by your statement, @denis. WinForms is still powerful. | |
| Jan 8, 2017 at 7:28 | comment | added | t3chb0t | @CodyGray 100% agree. WinForms applications can be as fast as the wind. The reason why this one appears to be slow is named in my review. You cannot use two expression compiles in a sort function and expect it to be fast. Expression trees are cool but the cost of using them is very high. | |
| Jan 8, 2017 at 6:23 | answer | added | t3chb0t | timeline score: 51 | |
| Jan 8, 2017 at 6:18 | comment | added | Cody Gray | "winforms is not powerful" This is not at all true. There are two reasons why WinForms applications are slow: (1) the code is written inefficiently (as with everything), (2) it is a .NET framework, and managed applications still run inherently slower than unmanaged, native-compiled applications. Many of the inefficiencies here are just standard C#/.NET inefficiencies and have nothing to do with WinForms itself. | |
| Jan 8, 2017 at 4:12 | answer | added | Der Kommissar | timeline score: 15 | |
| Jan 8, 2017 at 4:05 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 3 characters in body; edited title
|
| Jan 8, 2017 at 4:00 | history | asked | Denis | CC BY-SA 3.0 |