Re: Threading in VB

On 2009-08-19, Dos-Man 64 <ChairShot@xxxxxxxx> wrote:
On Aug 19, 1:06 am, Tom Shelton <tom_shel...@xxxxxxxxxxxxxxxxxx>
wrote:
On 2009-08-19, Dos-Man 64 <ChairS...@xxxxxxxx> wrote:

On Aug 18, 9:42 pm, Tom Shelton <tom_shel...@xxxxxxxxxxxxxxxxxx>
wrote:
On 2009-08-19, Dos-Man 64 <ChairS...@xxxxxxxx> wrote:


Next is Java. Yes, it's popular online. But that popularity is now
fading. It has never caught on with win32 applications programmers,
nor with application users. I've never downloaded a single java
application: no screen capture utilities, no text editors, no video
games, no process killers, nothing. If I see the word java in the
description of an "application", I head for the next program in the
list.

Nope.  Java never caught on for windows desktop apps - though they are much
more common in the *nix world.  But, workign for a company that is in the
top 50 of the fortune 500, I happen to know that it is used for quite a lot
of our enterprise apps.



Yes, and there's nothing wrong with that. Businesses often have
different goals than individual authors.


Of course, you know one of the more popular c/c++ ide's in the linux world is
eclipse - written in Java.  



No. I haven't done much C programming in Linux yet. I don't know
enough about the underlying architecure of X. That's the main thing I
need to start catching up on. I've heard terms like "widget" and
"window manager" and whatnot. But there is right now a huge difference
between win32 me and linux me :(


Doing stuff on Linux is a different animal for sure. And doing it in C, well
that is a whole other level. The problem is that things very from distro to
distro. Just because you get something working on RH, doesn't mean it work on
Gentoo. There are a lot of small incompatabilities. That's why Java and
other runtime based langauges are more popular in that world then in Windows -
you can write it once and have a reasonalby good chance of it working.

In fact, that's why each distro will have it's own repositories and package
management - they take a popular app and then tailor it to their particular
system. In windows world, you write the app on 9x there is a reasonable
chance that it will work properly on XP and up, etc, etc.


I'm not gonna let that fact stop me from doing the right thing though.
Down with Vista!




C#: Well, I don't know much about this, but I'm always hesitant to use
something that is not in a fully mature state. The whole .NET concept
seems to be in a sort of "work in progress" mode. I would prefer to
use something that is fully matured, as opposed to something that
could undergo massive changes in a hurry. A windows 3.1 programmer I
ain't :)

That makes no sense.  Is it evolving - sure.  So is C++.





It's the speed at which it (.NET) is "evolving" which is a concern.
Would you want your mechanic servicing your car while you are driving
it?


Well considering that overall, it's remained very compatible with each new
version, it hasn't been an issue. Every version upgrade for me has been
pretty much open it in the new vs format, let the ide upgrade the project
format, recompile - and then maybe tweak a few warnings due to a couple of
classes or methods being marked obsolete (not removed, just attributed to
generate compiler warnings). New code gets new features.


Well, I haven't used Python and I don't remember which of the other
programs that you mentioned, but the point is clear: there's no
substitute for low-level power. Yes, it's non-portable. Probably
always will be. Yes, it requires an in-depth knowledge of a specific
platform's architecture. It can be nasty (c++) and cryptic
(assembler.)  But that's always been the trade-off. In my case, I'm
not interested in writing wimp java apps that don't do much and
require the user to have a 50 megabyte runtime library installed. I
want low level power. It's worth the effort.

It's worth effort in certain situations, but when it comes to line of buisness
or enterprise applications (you know the ones that make up like 80% of the
programming world) - C/C++ is not even an option.

If what you said was even remotely true - no one would be using anything else,
certainly not VB.CLASSIC.

--
Tom Shelton


Well, classic vb was used in a lot of situations where it wasn't the
most well-equipped tool for the job, IMO. There's nothing wrong it.
It's just that when you push a language further than it was originally
intended to go it can really pose problems when the time comes to do
the inevitable rewrite/port/upgrade.

I certainly wouldn't disagree with that. That's why the upgrade to .NET was
so appealing.

--
Tom Shelton
.

Relevant Pages

  • Re: VB 8 Standard and Professional
    ... JIT-compiled like Java, ... C++ programmers. ... away from the Windows API and toward their fantasy ... on the latest platforms, including the Web, Windows Vista, the 2007 ...
    (microsoft.public.vb.general.discussion)
  • Re: grabbing text from non-edit java window
    ... > Java programmers. ... We don't know about Windows APIs. ... Some programmers have a little broader experience then a single development ... > component is one of the text components or a container. ...
    (comp.lang.java.gui)
  • Re: .NET vs Java
    ... .Net is platform-specific (to Windows) so if you're doing cross-platform ... the point of Java was to make Windows irrelevant, ... keyboard interface by default so the programmers don't have to do anything. ... Does Visual Basic have ROI and TCO values? ...
    (comp.programming)
  • Re: Threading in VB
    ... It has never caught on with win32 applications programmers, ... I've never downloaded a single java ... of our enterprise apps. ...
    (microsoft.public.vb.general.discussion)
  • Re: What Borland should stop wasting their time on
    ... > concept is pioneered by Delphi and Java. ... Not better than Delphi or VB6, ... C/C++ programmers have to integrate such code into their projects. ... as far I remember all windows program runs on virtual ...
    (borland.public.delphi.non-technical)
Loading