fill in the blank -The best cross platform programming language is
What language do you think is best for cross platform development?
why?
Web Development
What language do you think is best for cross platform development?
why?
by Jay Garmon
by jaqui
you are saying that Beginners Allpurpose Symbolic Instruction Code is the best language. [ BASIC ]
it is little more than english. :p
by apotheon
COBOL is :-)
English is pretty lousy across platforms. Try to port it to an Asian system. You'll have to completely recompile...
by jaqui
Because, when done right, it has significant performance benefits and is one of the more powerfull languages available. C++ can be used to control the hardware, unlike most other languages.
While this means that C++ can damage the system, it also means that it has capabilities that other languages lack.
by csotelo
by csotelo
In addition, the idea of Java "non-virtual" machines (see Azul line, or possible developments in the T Series of SunFire Servers) makes it easier than ever to scale Java to handle XXL sized loads.
P.S. and no, I'm not working for either Sun or Azul... :)
by jaqui
since when does incompatable jvm's and conflicts between different java apps jvm requirements make it a reliable cross platform language?
I actually refuse to install any jvm, or any application that requires java, since the conflicts in the runtime environments are prohibitive. one interpreter for every java application, I will concider it, until then, stick java where the sun don't shine.
by justin james
Calling Java "cross platform compatable" is a sad joke. Java isn't even backwards compatable with itself half of the time. You can take Java code written for Sun's JVM five years ago and it probably won't work on the Sun JVM today. .Net has more backwards compatability, which is really sorry, when you think about it.
J.Ja
by apotheon
by csotelo
I looked at your answers, and even though I felt the temptation to shove some of them "where the sun don't shine" on the authors, I feel I still have a point and that a "rational" response is better suited and will create more value than a heated personal defense.
I've been using Java as a cross-platform development tool for line of business applications for quite a while now.
Yes, I do realize that careful version control has to be kept, that JVM's are not the same across all platforms and that for particular applications other languages are better suited (driver/kernel do use C, or windows in which .net is a no brainer).
But careful programming will render an application that can easily be taken around most platforms without any changes whatsoever and current JVM's do not suffer from most of the problems we had on the past.
Older "standarized" languages (such as Cobol or Fortran or C) do have compilers that run on every platform, but here, as well, every compiler has its nuances and there's no guarantee code compiled correctly on a given platform will compile unmodified in another platform unless you go to great lenghts to proofread your code and ensure this compatibility yourself, just like in Java.
Plus, from the business standpoint it is much cheaper to get Java coders than C or even C++, unless you go to the visual crowd who can only program for windows - those do come real cheap - but then again that's not a cross-platform way to build code, is it?
by pennatomcat
by georgeou
by x-marcap
If you can't rewind before the file to browse/fix the previous file the language has lost something...
Pre Ansi-C K&R C is much more portable than C++.
And if you are doing Gui, use Smalltalk.
If Apotheon and I agree on it, you can probably cahs it at the bank...
by x-marcap
If you can't rewind before the file to browse/fix the previous file, the language has lost something... Today to fix this kind of issue you now need to write assmembly language or use a debugger...
Pre Ansi-C, K&R C is much more portable than C++.
And if you are doing Gui, use Smalltalk.
by dryflies
There is no single answer to the question.
The language is irrelevant to the platform. The runtime API is what makes cross platform development possible. The language should be selected for the application not the platform. for example, I would not think of writing a web app in C. nor would I write a statistical analysis program in PHP. There will be no device drivers in basic - unless you are really looking for punishment. writing a compiler? try snobol. a filter? perl. dynamic web page? PHP. embedded control? C/C++
by apotheon
I've seen websites put together using C/C++ that really needed something like that (for instance, The Spark used to be designed in that manner, before it was bought). PHP might be the language of choice for "a dynamic web page" if you just want to whip up something vaguely functional in half an hour, but for serious dynamic web development I'd use something else -- like Perl or Ruby. Many compilers are written in the language they compile, and with good reason. Perl's compiler (yes, it's compiled, not interpreted -- but it's JIT compiled) is written in C, though (and also with good reason).
. . . but your main point is a good one. Too bad the runtime API for some languages sucks and that for others is great. Too bad libraries, runtimes, and linguistic quirks can conspire to ensure that some languages aren't as portable as others. For instance, Java programming tends to rely heavily on platform-specific libraries for anything more significant than applets and prototypes, which the reverse is true for Perl: sysadmins tend to execute platform-specific utilities and commands from within administration scripts written in Perl, but for more substantial programming Perl is very platform-agnostic.
There are social aspects to languages that can contribute to, or detract from, cross-platform compatibility as well as technical aspects to their implementations. Yeah, there's lots of stuff that can affect real-world portability related to the language chosen. Would you use Visual Basic to write software for a Mac?
In theory, you're right. In practice, it's not so simple.
by justin james
C++ w/standard libs comes in a close second.
I find it amazingly... odd? unusual? ironic? that Perl & C++ are much more cross platform than Java with its "write once run anywhere" promise. What a lie...
J.Ja
by jaqui
perl, php, python have it hands down over java, since any current interpreter for each will run all programs / scripts from all versions, unlike java that requires specific, conflicting, jvms.
C and C++ are os agnostic, since they are the languages used to develop the os itself most often.
C++, the stl and standard libs for the language is usefull cross platform, it's the gui widgets that aren't usually cross platform, specially the mfc, that is strictly microsoft systems. gtk/gdk is a better option for that, as it is available for all os options, as is QT and wxWidgets.
by david_s
by apotheon
by apotheon
Specifically, UCBLogo: it's available for a fair number of platforms, and doesn't really do platform-specific stuff at all. Logo is a surprisingly excellent language, with the accessibility of BASIC but a lot of the power and flexibility of Lisp dialects like Scheme. Everybody seems to think it's just a toy language for Turtle Graphics, but the truth is that it's an amazingly nice language in its own right. There's even a third-party .NET compiler for Logo.
I'm planning to revisit Logo in the near future, in fact, and gain a little expertise in the language (using the UCBLogo implementation, of course). Have a look at the succinct power of Logo in a short sample program:
http://www.cs.berkeley.edu/~bh/logo-sample.html
As it says at the end, "Let's see you do [i]that[/i] in four lines of Java!"
by wdewey
I don't see that being especially useful.
Bill
by jmgarvin
I do like C++, but it isn't as portable due to various wonky headers that Windows sometimes needs.
With the mono project, I suppose I'll also vote for .Net ;-)
Oh, Perl for its bitchen string parsing and cool built-ins. I'm all over that...
by apotheon
1. Windows sure does demand some wonkiness from C++.
2. Disturbingly, the .NET framework (created by Microsoft, the king of noncompatibility) has been made widely compatible by Mono and other third-party implementations. This makes it ironically more portable than Java in many ways.
3. You're too right about Perl. She's my baby, and I love her so.
by justin james
SQL is less cross platform than anything else I have ever touched! It is a major undertaking to switch from Oracle to MS SQL Server to MySQL to PostgreSQL to whatever! Even the data types and how they are handled is different. This is a major reason why stored procedures are so important, have your installer create the right set of stored procedures, instead of switching the statements within your code on a platform-by-platform basis.
Even using the results of a SQL statement differ radically, depending on if they got filtered through ODBC, JDBC, a direct connection, etc.
J.Ja
by apotheon
by gdaley
With support on all the Microsoft platforms you'll ever want to support, C# wins hands down.
And, with Mono, you can even use it on non-Microsoft platforms too!
by justin james
Unfortunately, too much of the .Net Framework is tied to the Windows API to make anything that is closely tied to .Net really cross-platform compatable. Yes, Mono can compile and run straight C# code, but is C# a good language without the .Net Framework? I really do not think so. The power of C# (and VB.Net) stems not from the strength of the language itself, but the comprehensive nature of the .Net Framework. C# by itself is not a language that I find particularly attractive.
J.Ja
by apotheon
"[i]With support on all the Microsoft platforms you'll ever want to support[/i]"
What the heck does that have to do with it? You have a funny definition of "portable" or "cross-platform". Maybe you work for the Microsoft marketing division.
Read J.Ja's response to your post. He's on the money.
In fact, of the .NET languages available, I'd go with Python (since that's now going to be included in the lineup of languages available for .NET) if I were to choose a .NET language. I don't even like Python.
by joeaaa22
COBOL.
Yes, you heard me. COBOL!
For developing applications that manage data there is still no better languges. Period. And it runs on every platform you could imagine that needs to do any kind of data manipulation.
Now, for GUI or Web or Systems programming the answer would be much different, obviouslly. But the question was left so open ended that it's really difficult to get any kind of real answer to it. Afterall, one of the most cross platform things you can do is to have -
#! /bin/sh
as the first line of your program.
by john.a.wills
by justin james
I learned COBOL sometime around 1993, on an aging NCR mainframe with green screens. I will say, despite the sheer amount of work to go into writing COBOL code, it was very solid, and I would imagine that its age (plus the lack of upheaval in the programming world then) gave it a chance for the various implementations to all reach the same level of compatability. This is how Perl (and C, and C++) was too. Years between releases, not this "new 'innovation' on a weekly basis" attitude, and so on led to an extremely stable set of implementations.
In retrospect, what is really hurting cross platform with the modern languages is the rate of "progress" and "innovation." Every one is looking for an edge and a differentiating factor so they can reap the financial rewards of selling the tools and software to create and run the code. As a result, everyone seems to be doing what Microsoft is hated for, "embrace and extend." Look at the Java spplication server market. JBoss, Tomcat, WebSphere, all of these are completely incompatable. .Net is more or less useless outside of the Windows environment, SQL is heavily dependent upon which RDBMS (and version of which) you use, cross platform is really not a prime concern anymore, for whatever reason.
J.Ja
by apotheon
COBOL is legalese.
"The party of the first part shall not, in concert with and by contract with, the party of the fourth parth, engage, without the party of the second part, services provided therewith to the party of the third part, inasmuch as . . ."
BASIC is baby-talk.
"Would-ums wike a lollipop? Would-ums wike a print statement?"
VisualBasic is ebonics.
I'll let you imagine your own example of this one.
(edit: typo)
Java is geek-speak
C# is the geek promoted to management
Ruby is a Zen koan
by rlcf
by apotheon
Your mention of FORTH brings up an important problem: we don't know what was meant by "platform", or by "cross-platform".
[b]platform[/b]: Are we talking Windows vs. OS/400 vs. NetBSD vs. MacOS 7 vs. CPM vs. Solaris vs. ULTRIX? Are we talking x86 vs. AS/400 vs. x86-64 vs. Motorola G5 Mac vs. 8088 vs. SPARC vs. DEC Alpha?
[b]cross-platform[/b]: Are we talking about a language that works on different platforms? Are we talking about a language that can be ported from one platform to another without changing any core code, though some libraries have to be swapped out? Are we talking about a language that can be moved between platforms without having to change a single character of code or any libraries? Are we talking about a language that can be run on more than one platform in bytecode form to be run in a VM? Are we talking about a language that compiles to binary code once and runs on multiple platforms? Are we talking about a language that runs on multiple platforms with a JIT compiler? Are we talking about a language that runs on multiple platforms with an interpreter?
We need to know what category of "platform" you mean, Jaqui, and we need to know what the minimum requirements are for something to be "cross-platform" before we can give you an answer to "best".
All things considered, some flavor of Lisp might be best, as long as you don't require that part of "best" is "everybody knows it".
by dawgit
by justin james
AJAX is hardly cross platform. Between it using JavaScript (many inconsistencies between browsers) and HTML (many inconsistencies between browsers), it is barely cross platform. And in terms of using it as a technique? Hope you enjoy writing the same code five times, once on the server (to accomodate those without JavaScript) and four times on the client (to accomodate all of the various browsers out there). Sorry, but trying to write AJAX is like trying to drown a hungry crocodile, as far as I am concerned.
J.Ja
by apotheon
Who ever said anything about disqualifying a dialect? Sure, if you're counting languages, you could make a case for different dialects of the same general language being counted only once as a group, but you can't just randomly decide that one dialect doesn't get to be what it is any longer since there's another significantly like it. That's like saying a white woman isn't a woman because black women exist.
As for "programming language" definitions, I tend to figure that something that isn't Turing complete doesn't qualify. That rules out SQL. That's not to say that it has to be a Turing machine, per se -- just that it has to be capable of everything a Turing machine can do. SQL is more like a protocol than a programming language, in some ways.
I was under the impression, based on my memory of pre-1.0 versions, that XSLT wasn't Turing complete. It turns out that it is. That being the case, I'll concede that part of your point.
I still wouldn't consider it anywhere near the category of "best cross-platform" programming languages, though.
by onbliss
by apotheon
by jaqui
cross platform is operating system and hardware.
this lets Microsoft's visual products right out of the running.
if at most an application written in the language needs to be compiled to run on another operating system it is cross platform.
if the sources for the application require ANY alteration it is not cross platform.
[ in this, I include editing the shebang in a perl script, since if perl was installed correctly that edit is not required ]
minimum requirement to be cross platform, is that one source for the language itself will work for all operating systems, like PERL, PHP, PYTHON, GCC [ yes they have a port for windows besides the cygwin etc ones ],
by apotheon
My answer stands:
https://www.techrepublic.com.com/5208-6230-0.html?forumID=87&threadID=194492&messageID=2007473
Thanks for the definitions.
by jamesaaa8
by apotheon
by jamesaaa8
My quick examples included:
1) Windows DLLs
Granted, this is obviously platform specific. But my point here was actually more about how keeping track of DLLs on even a single Windows machine was as bad or worse as keeping track of JVM implementations.
2) STL implementations
I fail to see how the STL can possibly be qualified as platfrom-specific. Different implentations can have wildly different behaviors.
3) POSIX libraries
Granted, POSIX is in fact itself a kind of platform. But the idea of POSIX is to allow applications that conform to the standard to run on platforms that conform to the standard. Nonetheless, "POSIX" code that works perfectly well on QNX might not work on VxWorks or Linux or Solaris, even though they all claim POSIX compliance. Again, this is to counter the earlier point about tracking JVMs; tracking POSIX implementations is just as bad.
4) different C compilers
Again, this can't possibly be considered platform specific. The fact is, two different compilers (C or C++, and probably other languages as well) can interpret the ANSI spec in ways that your code works on one and is broken on the other. I have generally found that C code I compiled with GCC works when compiled with GCC on another platfrom. But I have found plenty of times where code that worked fine with GCC on Linux was broken when compiled with Borland bcc on Windows. And I'm talking "Hello, world!" code.
I'm still not a 100% sure I've said anything "worth discussing," but my 2 cents is that, despite the overwhelming disparagement cross-platform Java has taken in this thread, Java has mostly fulfilled it's promise of "write once (carefully), run anywhere (within reason)."
by x-marcap
by apotheon
"[i]1) Windows DLLs
Granted, this is obviously platform specific.[/i]"
Full stop. That sums it up. Thank you for playing.
"[i]But my point here was actually more about how keeping track of DLLs on even a single Windows machine was as bad or worse as keeping track of JVM implementations.[/i]"
Blame Microsoft, not the language.
"[i]I fail to see how the STL can possibly be qualified as platfrom-specific. Different implentations can have wildly different behaviors.[/i]"
It's no more platform-specific than JVM implementations. It's no more subject to differing behaviors across implementations than JVM implementations.
"[i]Again, this is to counter the earlier point about tracking JVMs; tracking POSIX implementations is just as bad.[/i]"
Actually . . . that's not true. It's not "just as bad". It's bad sometimes, and certainly not perfect, but it's usually not as bad as differing JVM implementations often are. Much of that could be solved by opening the Sun Java source, of course, but that hasn't happened yet.
"[i]4) different C compilers
Again, this can't possibly be considered platform specific.[/i]"
Nonsense. Compare the VS compiler for C/C++ to, well, any other compiler. It's about as platform-specific as you can get.
"[i]I have generally found that C code I compiled with GCC works when compiled with GCC on another platfrom. But I have found plenty of times where code that worked fine with GCC on Linux was broken when compiled with Borland bcc on Windows.[/i]"
Meanwhile, I've seen stuff that runs on Blackdown fail on Sun's JVM and vice-versa -- and, even worse, I've seen stuff that runs on Sun's JVM on one platform fail to run on Sun's JVM on another platform. Furthermore, you can always port GCC to a new platform, but you can't do that with Sun's JVM.
My point isn't that C/C++ is necessarily more portable than Java so much as that Java isn't really more portable than most other languages -- languages that, according to the Java-portability glee club, aren't portable. Perl is more portable than Java, as is Smalltalk.
by jamesaaa8
Me: "Windows DLLs ... [are] obviously platform specific."
apotheon: "Full stop. That sums it up."
Not quite. If you want to include Windows in your cross-platform development, you'll have to deal with it.
As to the STL, I think we both agree that there can be issues. Apparently we don't agree on wheter STL implementations or JVM implementations are "worse" or "better," but I certainly see your point.
I'm not sure why you're busting my chops for pointing out that various C compilers can interpret ANSI differently, regardless of platform. We can even take VC++ out of the equation if you like. In fact, the example I used was GCC & bcc.
apotheon: "Java isn't really more portable than most other languages"
Well, I'm not sure how we're going to define "most" here. I would argue that C & C++ make up a good chunk of what's in use today, and if someone held a gun to my head a said "write a program that runs on Linux, Windows, AIX, Max OS X, and VxWorks" I'd pick Java. Obviously I wouldn't pick Visual Basic, and despite the success of Mono I wouldn't pick anything .Net. (Mono running on OSE or QNX yet?) I'll actually agree that Perl is more portable... but I would consider it a domain specific language, rather than a full blown language like C. As for Smalltalk, you're back to the virtual machine implementation problem, so I can't see how it would be any better than Java. In fact, last I checked there was no standardized GUI API for Smalltalk.
apotheon: "Furthermore, you can always port GCC to a new platform, but you can't do that with Sun's JVM."
This is true. Of course, there are other JVMs you COULD port. Your point remains; Java should be truly open. Actually, I don't care if Sun open sources their own Java code or not. What I care about is that a 3rd party can create an open or closed Java implementation (meaining JVM, libraries, compiler, etc.) without needing a license from Sun.
Changed my mind; I do think this was interesting.
by apotheon
We've pretty much argued it to death at this point. I could still debate the finer points with you, of course -- for instance:
1. If you're programming with MS DLLs, you're not doing cross-platform programming, period.
2. I'm only debating C portability to point out that Java isn't really any better than C -- or, alternatively, that C isn't any better than Java.
3. By "most languages" I'm referring to languages, not programs written in a language. Scheme equals one language. Perl equals one language. Java equals one language. C equals one language. The fact that any (worthwhile) driver code is written in C these days, and that most application software is written in C++, doesn't mean that C and C++, all by themselves, are "most languages".
4. I think you're selling Perl short. You can do GUI programming in Perl, but GUIs weren't even what we were talking about: we were talking about the "best" language for cross-platform development. It's a very general question. Because of the generality of it, I listed several languages rather than just one in my answer -- and because of that, I didn't list a single language (like Java) that is mediocre at almost everything and excellent at almost nothing.
5. If a "full blown language" is "like C", then Java doesn't qualify anyway. Would you write an OS or a driver in Java?
6. There's no (useful) standardized GUI API for anything. That's not a shortcoming of Smalltalk. Any (major) language has multiple GUI APIs that it can employ. Personally, I consider that a good thing. For the record, anything more widely applicable and applied than, say, Javascript qualifies as a "major" language for these purposes.
7. Unfortunately, the other JVMs aren't anything like widely used (for the world of Java). GCC is one of the most widely used compilers, period. In any case, the problems between C compilers aren't nearly as bad as those between JVMs in most cases. At least, that has been my experience. Maybe yours has been different.
So, yeah, there's always more we could argue -- but there really isn't much more to accomplish. C'est la vie.
---------
About Smalltalk:
The virtual machine implementations for Smalltalk are actually pretty widely ported. There are some portability issues due in large part to the fact that the language hasn't been subjected to the same widespread stress-testing as Java, but the portability issues that don't arise (but do with Java) are more telling, as they're the sort of thing that depend more on the language than on the implementation. In any case, even if portability issues at the same level of popularity ended up being equivalent, Smalltalk would still be a far better language. The inventor of what was to become Java, before it had that name, has even been known to refer to Java as SmalltalkMinusMinus, or Smalltalk--, in a bit of a pun on C++. He, like anyone else of whom I've ever heard who has had as much experience with Smalltalk as with Java, has a definite preference for the elder of the two languages.
The guys who created Croquet (originally known as Tea) started out trying to write it in Java, in part because of the language's popularity. They eventually gave it up in favor of Smalltalk because Java was getting in their way significantly. Kind of an indicator, I think.
by jamesaaa8
by x-marcap
If you don't include stuff like AS-400's in that mix.
Yuck!!!! I don't want to tell you how bad AS400's ANSI C was...
I don't know why they labeled it C even...
by x-marcap
Once a VM is available Smalltalk is the best.
I can write in X windows on HPUX, move the source to Bill's POS-OS and run it, and over to Solaris and have all the apps work and access an Oracle DB server.
If you really want cross platform, Smalltalk is the best for Gui. Get it at Cincom.com
by apotheon
by x-marcap
by x-marcap
I should have noticed your VM post. I was just giving people info without giving them too much reason to try to think. (no reason to strain delicate parts.)
Think of talking to my dog... Sit! Stay! Good dog!
Smalltalk Gui! Command line C... Good programmer.
It works!!!
by apotheon
by x-marcap
I got interrupted by real work and left it sit ready to send. I never did read your post...
Amazing how intelligent you are... (in this I'm sure we agree.)
Smalltalk for Gui...
C for OS level...
My opinion with a finger on the scale...
by apotheon
C for relatively low-level code (OS, drivers, high performance utilities, et cetera)
Smalltalk for OOP GUI stuff
something like Lisp, Perl, Ruby, et cetera, for most of the rest of what you might do
edit: Whoops, my finger slipped. I fixed a typo in the title.
by justin james
... never consider beta or "futureware". Consider the here and now reality. Vista, when it was futureware, had a lot of exciting and cool features. As Vista gets closer to the here and now, it is less and less interesting to me, since so many of the real goodies are stripped out. C# as futureware sounds OK. It still isn't too cross platform capatable, so so much of its usefulness relies upon a one platform library (.Net Framework).
J.Ja
by jmgarvin
It is a powerful language and filled a lot of the gaps in Java. It is also a good language for developing more powerful apps and works well with the other portions of the Visual Studio suite.
What I really like about C# is that they have streamlined a bunch of the kludgy OOP stuff in Java and they've made it easier to plug right into an API.
It is also pretty quick. The JiT is pretty well done and everything runs smoothly (mostly).
As far as cross-platform goes, there is Mono, but MS hasn't thought beyond their platform...
by akalinowski
by apotheon
1. Assembly language is different for every single hardware platform, so it's not portable AT ALL.
2. Assembly language is more like a one-for-one secret decoder ring binary octets than straight binary. For instance, a Hello World for IBM-PC Assembly looks something like this:
http://www2.latech.edu/~acm/helloworld/asm.html
by apotheon
The program in and of itself isn't a whole lot of useful all by itself, but it demonstrates how absurdly simple it is to write a procedure in Logo for iteratively self-generating lists. The principles demonstrated in that program can be used in menu generation from configuration files or option definitions, for anagram calculations, and for calculating factorials, among other programming tasks. Hell, this sort of technique could be used for brute-force password cracking.
As for the language, I'd have to hear why you think it's not "especially useful" before I knew how to respond. I don't see any reason it wouldn't be "especially useful".
by wdewey
I got the program mixed up with the menu. Sorry.
I don't really understand this programming language, so why aren't the ultra and chocolate considered two different entries?
Bill
by apotheon
The [ultra chocolate] list doesn't get all its members operated on individually because no operation (aka "operator function") explicitly targets it. The list within which that shorter list resides is the target of the nearest operation, so that sublist is treated as an atomic member. Erm, I hope that makes sense.
Are you at all familiar with functional programming language syntax? If not, that might help explain your confusion. I'll direct you at some online books for learning Logo if you're interested.
by apotheon
I'm sure you know more about the quality of documentation available in commercial implementations of Smalltalk than I do. Of course, there are other ways to charge for development than a percentage of licensing cost, so I don't see how your "10%" really suits as a justification. In fact, it strikes me as a conflict of interst: it's in your best interest, according to such a pricing model, to ensure that the client is gouged for as much as possible. I prefer to provide my clients the best value possible.
One of these days, I'll actually become really competent with Smalltalk. Really I will. At the moment, I'm working on a Lisp dialect.
by x-marcap
I believe the best documentation on the language is necessary. I have had clients bring in two or three people to do large scale revamps, and editions, ans some have found it desirable to teach staff members Smalltalk, not just bring in consultants who leave with the knowledge. I write custom apps that end up in an insurance company's homegrown products, and they have a staff of 80 Smalltalk coders...
Do you have any clue how many calls to "Move a field about 10 Pixels even though everything is left justified are saved by the client who can drop into the gui and drag the field to where they want it?
The point is, it isn't just in my interest to do it that way, I believe it is in my clients' best interest to have good commercial documentation for their staff. I may make more $$$ up front, and I only do jobs that will make money. I have no use for busy work... I am in business to make money.
I also believe that if the client has any staff Smalltalk is easy to build apps with and it looks pretty darn nice.
I charge 10% markup on all hardware and software.
That is my business model. I charge hourly for installation and configuration. If it is a Symmetrix DMX that costs $4-800,000.00 the 10% for setup will include things like base training, powerpath install on main servers, site survey power analysis, AC analysys, rack layout, etc.... The process to sell one takes a month or more or sometimes over a year. Definitely not a drop and go. For a 2500.00 server, there is no profit by the time you drive to the clients, and load the base OS, but the clients who buy smaller servers tend to need some handholding, so they soak up more hourly cost... Mostly because they don't know what they really want, and they don't want suggestions about what they need...
by x-marcap
My point is there is rarely the smaller 10% deals out there as we have headed into the mass market world. the larger deals are not only difficult to close, but take much longer lead time...
Long gone are the days of 10,000.00 PC and 30% markup... You could write an application and market it vertically and make the bundle on the combination of hardware and software... I really miss the good old days...
by justin james
... C# today is an OK language. What I was calling "futureware" are the features proposed for C# 3.0. Who knows what the final release will actually have in it...
J.Ja
by jmgarvin
If C# 3.0 actually has what is promised (it won't), it'll be an AMAZING programming language. It will take OOP (or so it seems) to the next level...
I do think MS is heading down the right track for a development IDE though. It is clean, functional, and integrates the rest of the suite seamlessly.
I wish Linux had a powerful, unified, and clean IDE (I hate most of the IDEs that are out there) that integrated some languages and made life a little easier.
by justin james
RoR, prototype.js, etc. are all well and good, but they are not a "langauge." AJAX is not even a "language" it is a *technique*. These frameworks are not languages, they are tranlators. That's like if I write Pascal code, put it through p2c and claim I wrote C code.
J.Ja
by x-marcap
by dryflies
by tommy higbee
I know what some of you are saying (those who are not saying, "What's TCL/TK?") It's a scripting language, not something you would use in developing major applications.
But within its scope, a TCL/TK program will run on Windows, multiple versions of Unix/Linux, and Macintosh. It will also run on the AS400 under the PASE environment. There's probably no quicker or easier way to script a moderately complex action that executes on your chosen platform, with a GUI or without (your choice). Perl is also cross-platform, but doesn't hide the underlying platform as well as TCL. Plus, TCL offers the ultra-handy "starkit" packed programs, where all scripts and libraries are in a single archive, and installation of your program consists of copying over the archive and a platform-specific runtime to the target computer. If that's too much installation effort, you can embed the archive into the runtime and run it like a regular executable.
If you want to develop a huge project, you'll need something like C/C++, Java, COBOL, etc. But for a lot of little projects, TCL/TK may be the fastest way to get there.
by onbliss
by apotheon
by jaqui
by jaqui
because My sites don't use javascript or any other dynamic clientside scripting.
I design them to be static html/xhtml on the client side. :)
by justin james
As I wrote a few days ago (https://www.techrepublic.com.com/5254-6257-0.html?forumID=99&threadID=184332&messageID=2023082&id=2926438), if your site is usable in Lynx, you are doing it right! Not that anyone uses Lynx, but it's a great way to validate that even the most downwards capable browser can use your site. More importantly, it means that a *search engine* can index your site. The article has a lot in it, relevant to the AJAX end of this discussion.
J.Ja
by justin james
Static HTML/XHTML on the client side; I occassionally add a small bit of JavaScript validation that is replicated on the server side, because that is something users are used to and is shown to slightly increase usability. Outside of that, I avoid JavaScript, Flash, etc. Why write all of that code in JavaScript, when I have to repeat it all on the server end anyways for the downscale browsers? If I wanted to work my butt off, I would be digging ditches for a living... to quote myself, "AJAX is the Yugo of programming techniques"...
J.Ja
by jaqui
1) lynx supports javascript unless it's turned off.
2) I use it. :p
by m_a_r_k
How often does one really need to develop a cross-platform application? Not very often. For truly powerful and efficient applications, the software will almost always need to access some OS- or platform- or compiler-specific features. That throws a curveball at cross-platformability (is that a real word?) if you are hoping to simply recompile the code with no changes.
C and C++ are definitely NOT cross-platform unless you use only POSIX-compliant features and/or only features specified in the official C and C++ standards. Have you ever noticed all the #if macros littered throughout C or C++ code that is meant to run on different platforms?
by m_a_r_k
Or little utility programs? A few hundred lines of code or tens of thousand? What in the world is Synergy/DE?
I don't know of any large apps (pick any--MS Office, TCP/IP stack, web browser,.... (the list would be long), that are cross-platform with no #if's. If you are careful, you can probably use object-oriented design to come up with something that is pretty close to cross-platform. You'll have different classes for each platform, but that's OK and is one of the uses of OO.
Sort by Trending