Slashdot Mirror
Programming Language for Corporate UI Research?
Daniel Wigdor asks: "I'm a PhD candidate doing an internship at a major American UI research lab. They distribute an input/output hardware device to research labs, along with a Java API for the development of 'concept pieces' (here's an example from a university). Java was chosen because it was simple, and seemed, at the time, to be the language of choice for UI researchers in both the corporate and academic worlds. There is now pressure to switch from Java to C#, since they don't have the resources to maintain an SDK for both. We're not at all concerned with system performance, since this is only for concept-development: it's really just about accessibility for newcomers to the hardware. Given that, what would the community advise by way of a choice between Java and C#?"
Carry on using Java if you can, and switch if you have to. No point in changing language if you can avoid it (especially given how similar Java and C# are).
Freedom is not increased by mere diminuation of government. Anarchy is freedom for the strong and slavery for the weak.
I realize that this probably isn't the kind of thing you were expecting (I'm guessing you expected to get answers like "C++"), but I think it's a good idea.
But of the two languages that you have now, I would stick with Java simply because it is completely cross platform (plus just about everyone getting out of school now knows Java because it was so popular/"language of the future", where as many don't know (or have only had an introduction to instead of a large amount of work with) C#.
But the great thing about Python is you could use it as an itermediary between toolkits and such. Without changing your API, you could replace the Python code so that it used Win32 instead of Swing or QT without making your users learn something new. You want to change the back end from C++ to C or to something else, the interface and the way they call things stays EXACTLY the same.
Just a though, from a guy who has recently discovered and fell in love with Python. And things will only get better with Python 3.0!
Comment forecast: Bits of genius surrounded by a sea of mediocrity.
C#/CLR is nice and has promise, but if you want UI consistency I would suggest sticking with Java/Swing for the meantime. With C#/CLR you have to pick between Microsoft's Windows Forms implementation, or Mono. As far as I know, Mono has an incomplete Windows Forms implementation at this time, and even if becomes complete I would expect at least some minor UI differences. At the current time I believe Mono has independent GTK, QT, etc. bindings. So if UI consistency is what you want, I'd stick with Java/Swing, and the default cross platform metal/ocean theme.
If and when Mono implements Windows Forms fully, so that they are sufficiently similar, you may want to re-evaluate at that time (depending on whatever other factors would influence your chioce).
It's 10 PM. Do you know if you're un-American?
You're asking Slashdot, where anti-MS sentiment is a given? Good luck getting anyone to recommend C#.
.NET, in general) on Mac and Linux is likely to play continual catch-up a la WINE, I'd say stick with Java. It has much wider support in terms of development environments, giving researches flexibility in their choice and tools.
Actually, if C# was supported under other platforms as well as it is under Windows, then I'd say, go forit.
However, since C# (and
When in doubt, go where there's more flexibility.
tasks(723) drafts(105) languages(484) examples(29106)
I put my vote on assembly. Sort the men from the boys.
C# is powerful in the right hands, but you loose platform independence. (Mono isn't there yet IMHO)
Pluspoints for Java
.NET languages
--------------------
+ more OS Platforms that you can run on
+ Eclipse as a terrific free IDE
+ huge number of free open source libraries
+ further away from MS (O.K. there is Mono too, but you only have one single second vendor that you can rely on)
Pluspoints for C#
-------------------
+ one single choice for UI development
+ more language features (this may be a minuspoint for corporate development, when you only want one way to write things)
+ one language standard, less dialects
+ believe it or not, it's an open standard and (on paper) less proprietary than Java, which is owned by Sun
+ easy GUI development for WinCE or windows mobile, including many mobile phones
+ possible easy interaction with other
+ easy direct interaction with Windows OS features
Now what do you prefer?
db4o - open source object database for Java and
Personally, i think that there is much to commend C# as a language, but I think you'll find that those pushing for C# are really pushing the .Net framework rather than the language. While I think it is one of the best things that Microsoft have come up with, it is not portable and unless you wish to have code that runs purely on Windows, Java is the way to go.
The advantage of Java is that it has a standard API that is tailored to multiple platforms.
I've you're used to Java's SWING layouting, you'll find C#/.NET ridiculous and primitive.
In .NET, you only have one, fixed layouting mechanism which uses either "Dock" or "Anchor" (read specifics in MSDN's Control class documentation, specifically the "Anchor" and "Dock" properties).
If you're doing UI prototypes I really think that this is a severe limitation.
Other arguments against C#:
My advice is to stick with what you've got now. That advice would also apply if you were using C# and wondering about switching to Java.
.NET equivalents to your scriptable Ant software build scripts, retrained people and maybe pissed off a few in the process, etc.) a lot more than $0
Honestly, the two languages are close enough in terms of capability that it really boils down to the cost and effort involved in switching.
Cost to remain with Java: $0
Cost to switch to C#: (by the time you've recoded all your "trivial" common routines you've created to work within your particular environment, built
Speak to people who've worked a lot with both languages. Get them to rank both languages out of 10 in terms that are relevant to you. Average the scores across a bunch of people. If C# averages >1.5 more than Java, then consider switching
'consider that Microsoft has not given Mono a legal blessing'
IANAL, and I have myself had reservations about this point...
However, it seems quite unlikely that MS would succeed in choking off core (C# + CLR) Mono development - for a lot of little reasons:
1. Novell appears to be Mono's primary backer and they appear to have real patent leverage w.r.t. MS.
2. Probably not many of the patents covering the core can hold water due to prior art. I think it's been suggested that MS + Sun together could launch a more effective patent attack. How likely is that? (things like WinForms, ASP, ADO would seem to be in greater danger)
3. Mono could still ship with the odd feature stripped or workaround mechanism in place.
4. MS can not simply beat up on who it feels like nowadays; not with the EU and others breathing down it's neck.
As an aside, can anyone think of a *language* implementation that was killed by patent litigation?
--
Mike Greaves
-- Mike Greaves