Re: Dot net and all that

Tech-Archive recommends: Speed Up your PC by fixing your registry


"mayayana" <mayaXXyana1a@xxxxxxxxxxxxxxxx> wrote in message
news:ODKz%23jNRIHA.4400@xxxxxxxxxxxxxxxxxxxxxxx
Actually I'm thinking more of me. I don't want to further embrace vb6
if
Microsoft have broken it. Or trust Microsoft that they won't do it
again
(and again)


Oh. This discussion comes up periodically and people
often talk about switching to Delphi, RealBasic, etc.
I don't understand that logic. For the forseeable future,
VB is one of the best, most flexible ways to write software
on Windows. And for all practical purposes it has no
dependencies.

I don't mean to criticize other options,
like Delphi, but I wonder about the sense of changing
over before it's necessary. For me, at least, it takes a
long time to get proficient with a new tool. And in the
meantime, Vista has been a stunning flop ... The general
landscape is changing very fast ... It's unclear whether
3rd-party software will even be feasible on Windows,
down the line. How do we know that Delphi will be usable
for any longer than VB is?

Microsoft are clearly trying to talk a good game on
cross-platform "rich Internet software", while actually
working to lock Windows users into a convoluted mess
of Windows dependencies with .Net, Silverlight, etc.
The result they seem to be hoping for is a locked down
Windows OS with Windows developers writing
Silverlight trinkets for Live.com, etc. To my mind there's
no future of any kind on that sort of Windows OS.


For what it's worth, I'll add my 2cents of agreement to this observation.

I too never quite understood, why someone would migrate to non-microsoft
solutions within the Windows World. Not that MS tools are superior, often
quite the opposite for some tasks. I fully understand why they would like
to. <g>

During developing technologies, various tools have always appeared that
filled in the gaps, but it didn't seem to take long before these tools were
no longer needed. Either because the technology changed or comparable MS
tools appeared. IMHO, the detour was never worth the effort. BUT for others
it has been.

I don't believe any 3rd party tool that isn't based on the Framework (or
'frameworks') will have any long term future in Windows development.

But that is only an opinion.
-ralph


.

Relevant Pages

  • Re: Borlands linux strategy ?
    ... What would be so awful for Borland, as a company, from a strategic perspective, to start a new product line that targets non-asp.net, non-windows development? ... My point is that if you try to port Delphi, and what makes Delphi Delphi, to another development platform, it will fail. ... This is the main point of my argument for why Delphi is and should remain a Windows development tool. ... It's hard for a software vendor to make any money from dev tools alone, especially in the ISV market. ...
    (borland.public.delphi.non-technical)
  • Re: Borlands linux strategy ?
    ... Sorry, it's the general mentality of Borland, and reinforced by users who ... believe that Delphi should just remain a windows platform tool. ...
    (borland.public.delphi.non-technical)
  • Re: A cross-platform vision for Delphi
    ... Delphi IDE is simple: sometime the builds are so good, I mean SO GOOD, ... a tool that limits yourself to a 32-bit Windows platform. ... Great machine to install a modern Linux desktop. ... Now I credit Codegear ...
    (borland.public.delphi.non-technical)
  • Re: Borlands linux strategy ?
    ... the reason why Delphi can compete at all in the server-side market ... That's an extension to the opportunity for Borland. ... efforts depend on the notion that every developer includes Windows as ...
    (borland.public.delphi.non-technical)
  • FAQ: comp.lang.pascal.delphi.misc miniFAQ (full version)
    ... Why does the debugger show my For loop variable counting down, ... Does Delphi have an equivalent to the VB Split function? ... When using the TRegistry component under Windows NT, Windows 2000, or ... Newsgroups Etiquette ...
    (comp.lang.pascal.delphi.misc)