4 ms·
I like C# more than Java because: - The .NET Framework is a straightforward way to solve a problem vs pattern oriented solutions. This is not about the program
by wslh 13y ago
I like C# more than Java because:
- The .NET Framework is a straightforward way to solve a problem vs pattern oriented solutions. This is not about the programming language itself but how the people in that community think about a problem
- C# evolved more than Java and it was more pragmatic. There are no operators in Java.
- I really like the diversity and maturity of third party Java libs. That's why I use IKVM when I need to use a lib from Java in .NET and why I use Jython. Examples here: http://blog.databigbang.com/tag/ikvm/ http://blog.databigbang.com/tag/ikvm/ and here: http://blog.databigbang.com/tag/jython http://blog.databigbang.com/tag/jython
I don't like Javascript, I would like to replace it with a standard VM to run other programming languages like Python.
I like C++ for performance oriented applications and when good libraries are available. For example I like CryptoPP.
I like Objective-C and their additions like Grand Central Dispatch. I like XCode.
I love Python: it's straightforward to build stuff.
I don't like PHP but many times I prefer to build some web scripts using PHP.
I like Pascal for teaching algorithms. More than C, because is less ambiguous.
I don't like C anymore except for firmware.
- V-2 13y agoCollections in Java are awful. Guava helps a bit, but it's still poor man's substitute. No LINQ, no lambdas (and the upcoming Java streams API is ugly as well), no delegates, no events. Verbosity. C# is a very nice language, only WPF sucks big time.
- wslh 13y agoI forgot LINQ! I think nobody is using WPF for new project? I like that UI application feels native in C#/Windows.
- saw-lau 13y agoJust started using WPF for a home project here. :-)
- stinos 13y agoUsed WPF a couple of times, not that bad at all? What exactly do you think can be improved? Are there alternatives to it?
- et1337 13y agoFor me, WPF isn't the problem. I love MVVM, data binding, etc. The problem is XAML. More like FML, amirite?
- stinos 13y agomyeah it's a bit messy sometimes. But I yet have to encounter an UI design system that isn't? (ok, didn't try that many, and for example Labview is pretty nice since it gives you a working GUI with tons of features in no time, but for backend it's a disaster)
- dnissley 13y agoBasic binding works wonderfully, and the MVVM pattern is a good idea, but it just doesn't seem to work that well in practice. Some basic things seem overly difficult to do. I feel like there's a WPF way of doing things, but there is no reference for what that is. For example: I had a DataGrid, and I was trying to figure out how to respond to the KeyUp event on a specific row, but only when it was the Delete key. I ended up having to create a custom dependency property in order to do that. 80 lines of code and a new class with 7 members later, I was able to reference that in my view and connect it to a method in my viewmodel. It works, but my lord it took me hours of googling and trying different things out for what seems like should be very simple functionality.
- dfkf 13y agoXAML is the awful part of WPF. The reasoning behind it is understandable, but this whole "declarative ui" thing brings with itself a whole bunch of abstractions, like resource dictionaries, styles etc, that you wouldn't need if you do your ui in code. And sometimes code-only wpf is the only way to get good performance from it.
- 13y ago
- mercurial 13y agoWhat's a "pattern-oriented solution"? As opposed to what?
- wslh 13y agoMany libs in Java require to think about patterns instead of giving you a straightforward way to accomplish your goals.
- mercurial 13y agoDo you have more concrete examples of "pattern oriented solutions" that exist in Java and not in C#? Are you trying to say that C# is so expressive that it doesn't need, for instance, factories?
- wslh 13y agoI was clear enough in my opinion. I don't think it's an issue related to the programming language but how the community works. As ern said there are people in the .NET following this approach with stuff like the entity framework. For further information you can read: http://c2.com/cgi/wiki?PatternAbuse http://c2.com/cgi/wiki?PatternAbuse
- gutnor 13y agoMeh, I will guess that is the usual suspects: like XML libraries, anything JEE, ORM, ... Those are the things for which Java provide an API (sometimes a default implementation) and you chose your implementation between competing ones. The result is a mess of factories of generator of creator. Also, over the years best practice have evolved, meaning you get a variety of such mechanism in the JDK itself. With a single vendor, DotNet avoid a lot of that shit. Then there is a huge variety of OSS libraries that integrate with each other. So you get another layer of pattern on top of the JDK. OSS libraries are extremely popular in java, much more than in the DotNet world, so that contribute to the sentiment. Another usual suspect is a fashionable "Spring hate" or "Hibernate hate", ... Dependency injection, ORM and other patterns became mainstream on java and are very often used. Even less hated "pattern" like mocking and unit testing started there too. A lot of projects still use older style less modern implementation of those. EDIT: Also a lot of libraries are mature and implement the entirety of the specification they provide support for. Since java is mainly used for enterprise application, the most google-able libraries to solve problem X is generally the enterprisy one. For example if you search how to serialise to and from XML, you end up with Jaxb as the preferred solutions. You will not hear as much about XStream which is a more limited but much more straightforward approach.
- ern 13y agoThe .NET Framework is a straightforward way to solve a problem vs pattern oriented solutions. This is not about the programming language itself but how the people in that community think about a problem There are plenty of people who overengineer their .NET solutions. They wouldn't dream of starting a project without including the Unity Application Block, for example. It may be a symptom of Enterprise Syndrome rather than a specific language community.
- James_Duval 13y agoC#'s namespaces also make more sense to me than Java's packages.
- pkolaczk 13y agoJava packages is one of a few things that I like in Java more than in C#.