Here's the problem, as I see it:
You write a perfectly decent solution to a software problem, but the
language and runtime you choose is superseded by the manufacturer, vendor
or community.
What should you do?
--
Ted Roche
Ted Roche & Associates, LLC
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4v+sVLyJ+rS6WmkG7DN3yrJUQq0s2vwwmYBXwtc=EhPjQ@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Stephen Russell
Posted: 2014-02-20 12:17:49 Link
On Thu, Feb 20, 2014 at 11:51 AM, Ted Roche <tedroche@gmail.com> wrote:
> Here's the problem, as I see it:
>
> You write a perfectly decent solution to a software problem, but the
> language and runtime you choose is superseded by the manufacturer, vendor
> or community.
>
> What should you do?
> -----------
Sounds like a derivation problem where I have a function for revenue and I
want to determine how it could be altered as the firm remains contemporary
with the industry and lay over the same function not putting in resources
to stay current.
In the short term you find yourself in acceptable positions, but over a few
years you can trend your loss of revenue and see when you might be in
danger.
Now you have to decide if you take on expenses for currency as a long term
capital improvement or do you see it as a waste of time for productive
employees.
My current mgr is so stuck on the don't change anything because we have too
much stuff to do, and making it contemporary will define it as
unsupportable if only "you" can do it. We do .NET code with VS2005 code
compiled under 2012 ide. I did a demo of MVC and the look from him as he
said where are the controls, all I see is code.
--
Stephen Russell
Sr. Analyst
Ring Container Technology
Oakland TN
901.246-0159 cell
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAJidMYK=j3sfc+uRCbPKc1xyGdXA2EN0ZnBiWQWCHOikswa7hA@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Ted,
An excellent simple statement of the problem, although I think I'd add hardware to your 'superseded' list.
There's only one absolute part of the answer, Talk with your user! Everything else is 'maybe'.
Fact: nothing lasts forever. Fact: keeping up with the latest is expensive. This is a classic engineering problem, to find some intermediate point where you avoid the functional and maintenance costs of an outdated system, and don't spend excess time and money dealing with the teething pains of an immature technology. A clear analogy is when to replace your aging automobile.
You're the expert on cost and difficulty, your user is the expert on functionality and budget. Look at the situation periodically and decide together when its time to jump ship.
I think most developers (myself included) tend to push upgrading a bit too early, probably because we've already had to upgrade our tools. Most owners/users tend to delay upgrading too long, because they fear the unknown factor of change.
Dan
> Date: Thu, 20 Feb 2014 12:51:22 -0500
> Subject: Our Love Affair with Old Software continues
> From: tedroche@gmail.com
> To: profoxtech@leafe.com
>
> Here's the problem, as I see it:
>
> You write a perfectly decent solution to a software problem, but the
> language and runtime you choose is superseded by the manufacturer, vendor
> or community.
>
> What should you do?
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/BAY169-W96AF80DA05DC4618465D70909A0@phx.gbl
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
>Here's the problem, as I see it:
>
>You write a perfectly decent solution to a software problem, but the
>language and runtime you choose is superseded by the manufacturer, vendor
>or community.
>
>What should you do?
What is software, what is a problem? That has to be defined first.
Some kinds of software (and hardware) are as ephemeral the color palette
that the French designers have already forced on clothing buyers for the
2014 spring season. You know what? I don't think that's a "problem" in any
meaningful sense of the word. If you are the kind of person who can't
survive without the latest color, or fashion, or phone, then you deserve
what you get. Go ahead and blow your disposable income on that crap if you
like.
Other kinds of software (and hardware) are as basic, and enduring in their
purpose, as a block and tackle, a gear, or a lever, and need to be changed
as much as those tools do. Word processing, spreadsheets, email: these fall
into this category. I should not be forced to replace them, ever, unless I
personally want them to do something else that they do not already do. (And
by "do not already do", I do not mean, "work on my current hardware and OS".)
The overriding problem is that it is in the profitable interest of computer
hardware and software producers to try to convince everybody that these
fundamental differences do not exist, and that everybody has to buy new
stuff every 12-to-18 months for everything.
This is bogus. The first problem is to separate truth from marketing.
When we do that, these other questions get a whole lot easier to answer.
Here's one:
Why isn't a 4-bit int a 4-bit int no matter how much bandwidth the OS
offers? Why shouldn't software that uses 4-bit ints work just as well on an
8-bit, 16-bit, 32-bit, or 64-bit OS, without any messing around with
"adapters" or "VMs" or anything else?
Here's another one:
Why shouldn't OS designers assume that 20 years from now everybody will
want a 512-bit-wide pipe, and build it into the OS RIGHT NOW, so people
don't have to "upgrade" when the 512-bit software arrives?
Ken Dibble
www.stic-cil.org
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/5.2.1.1.1.20140220142125.02563490@POP-Server.stny.rr.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Adam Buckland
Posted: 2014-02-20 15:20:43 Link
In my case Ted with a "one man band² supplier who died whilst creating a
Windows version of his great DOS product for my printing Company.. Buy 6
desktops that run Win XP and 2 servers that run Win 2003 Server.. Then
look for an alternative product that doesn¹t need a dongle etc...
On 20/02/2014 17:51, "Ted Roche" <tedroche@gmail.com> wrote:
Here's the problem, as I see it:
You write a perfectly decent solution to a software problem, but the
language and runtime you choose is superseded by the manufacturer, vendor
or community.
What should you do?
--
Ted Roche
Ted Roche & Associates, LLC
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CF2C21AB.404FD%adam.buckland@eurohill.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On Thu, Feb 20, 2014 at 2:32 PM, Ken Dibble <krdibble@stny.rr.com> wrote:
>
> What is software, what is a problem? That has to be defined first.
>
Oh, no, that leads us down the path to "What does "is" mean?" Start your
own thread! :)
>
> Some kinds of software (and hardware) are as ephemeral
>
> Other kinds of software (and hardware) are as basic, and enduring
>
Like order processing, inventory control, line-of-business applications.
Agreed.
> The overriding problem is that it is in the profitable interest of
> computer hardware and software producers to try to convince everybody that
> these fundamental differences do not exist, and that everybody has to buy
> new stuff every 12-to-18 months for everything.
>
Which vendors are that? Most Apple users I know keep their machines for 5
years or more.
Android is a hot mess. I picked up a Lenovo K1 tablet and no sooner had I
plunked my money down than the vendor announced no new upgrades. And
3rd-party "jailbroken" ROM firmware is catch-as-catch-can, vaguely
supported and possibly sketchy. Once burned, twice shy.
Perhaps you need to find new vendors. Ubuntu and Red Hat make long-term
versions with stable support for 3 and 5 years, iirc. Perl, Python, PHP and
Ruby have much longer version ramp-up times. Linux on the desktop is a not
a pretty story, but you can get by.
Perhaps you need to find a vendor whose values are more aligned with yours.
And here, with all due respect, we veer off bad vendor practices and jump
into computer
> Why isn't a 4-bit int a 4-bit int no matter how much bandwidth the OS
> offers?
Yeah, it is. Zero to fifteen or -7 to +8, depending on whether it's signed
or unsigned.
> Why shouldn't software that uses 4-bit ints work just as well on an 8-bit,
> 16-bit, 32-bit, or 64-bit OS, without any messing around with "adapters" or
> "VMs" or anything else?
>
Apps written to interact with the underlying OS via a 16-bit interface need
to have that interface supported. YOUR choice of vendor made Win32s a
work-around for a short period, but it is not in THEIR business interest to
have you run old apps. Other vendors have compilers that support a lot of
older software. However, when the vendor changes platforms (as Apple did in
the PowerPC to Intel migration), all bets are off.
Why shouldn't OS designers assume that 20 years from now everybody will
> want a 512-bit-wide pipe, and build it into the OS RIGHT NOW, so people
> don't have to "upgrade" when the 512-bit software arrives?
>
There are several good reasons. First, there are lots of visions of the
future, but few of them come true, or we'd have flying cards and food
replicators by now (I was really counting on that one, "Earl Grey, hot.")
Second, the whole arbitrary 8-bit, 16, 32, 64, 128 bit thing is based on
real physical limitations of the current crops of chips. Increasing these
means a lot of cost in hardware manufacture as well as software. It's
easier to amortize that cost over time than make the leap all at once.
Making current hardware work with 512-bitness would mean, roughly, making
current applications 8 times slower, larger and less efficient, for no
apparent gain. It just doesn't make business sense.
Third, it's not clear that "bitness" is going to continue to climb, as
there are some strong pressures to go in other directions. The Internet of
Things make it likely that we are going to be integrating more
ultra-low-power sensors, like FitBits and Bluetooth devices and Google
Glass and Nest thermostats, in small device orchestration. Databases can
already manage petabytes with 64-bits, and that's too much information for
me, thankyouverymuch.
Finally, there is always going to be change, and change inevitably leads to
frictions and incompatibilities. There will always be a need for us
technies who can glom together disparate parts to make a whole.
Recently, I had to update MY choice of OS/distros (Fedora 19) to run Ruby
2.0 for a project. The distro's supplied Ruby is older than that, so I
needed to build a copy from source. (Yay, Open Source!) Well, the source
would not compile on my machine. Ruby has some dependencies in crypto
libraries, and Fedora disabled one of the elliptical curve algorithms due
to a potential weakness. The Ruby library made the naive assumption that
library would always be available, even though it really didn't need to
hard code it. A patch is in the works but not yet released to verify the
count of algorithms is one or more, rather than search for one specific
algorithm. So, I had to research the issue, find a solution (there was a
patch), manually apply that patch, rebuild the software to create my very
own custom Ruby.
So, to summarize a much TL;DR response: Some vendors are just in it for the
bucks and don't care about customer satisfaction; choose the vendors who
support your values; Open Source wins, at a cost.
--
Ted Roche
Ted Roche & Associates, LLC
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4vKgovJjyvM4fP6V-TeRtyJqHjkd2bXG+LPDck1zBbEwQ@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Jeff Johnson
Posted: 2014-02-21 07:15:32 Link
On 2/21/2014 5:52 AM, Ted Roche wrote:
> On Thu, Feb 20, 2014 at 2:32 PM, Ken Dibble <krdibble@stny.rr.com> wrote:
>
>> Some kinds of software (and hardware) are as ephemeral
>>
>
> ^1 ephem·er·al
>
> /adjective/ \i-?fem-r?l, -?fe-m-; -?fe-m?-, -?fe--\
>
> : lasting a very short time
>
>
> Full Definition of /EPHEMERAL/
>
> 1
> *:* lasting one day only <an /ephemeral/ fever>
> 2
> *:* lasting a very short time </ephemeral/ pleasures>
>> Other kinds of software (and hardware) are as basic, and enduring
>>
> Like order processing, inventory control, line-of-business applications.
> Agreed.
>
>
Just helping out. ;^)
--
Jeff
Jeff Johnson
jeff@san-dc.com
SanDC, Inc.
623-582-0323
Fax 623-869-0675
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/53075174.8020808@san-dc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On Fri, Feb 21, 2014 at 8:15 AM, Jeff Johnson <jeff@san-dc.com> wrote:
>
> Just helping out. ;^)
>
>
Thanks, Jeff:
Ephemeral examples: Flappy Birds, candy Crush, Microsoft Bob, Windows At
Work (r)
Long-term examples: Visual FoxPro, Internet Explorer 6, LAMP
;)
--
Ted Roche
Ted Roche & Associates, LLC
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4vjBKCwoX_pHf3p2=ijgHsq06uuzOZANjjmWJkzbP8C+g@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On Thu, Feb 20, 2014 at 4:20 PM, Adam Buckland
<Adam.Buckland@eurohill.com>wrote:
> In my case Ted with a "one man band² supplier who died whilst creating a
> Windows version of his great DOS product for my printing Company.. Buy 6
> desktops that run Win XP and 2 servers that run Win 2003 Server.. Then
> look for an alternative product that doesn¹t need a dongle etc...
Oh, boy, that's another category I hadn't considered. I was really thinking
of software that won't run on a newer OS, but Orphanware is another aspect
of this.
We support two software apps that were abandoned by the original authors,
though fortunately not by death: one sold and supported the transition to
us, one had left the customer in the lurch and we picked it up. (Do you
know how hard it is to find FoxPro support? It's a comment I hear over and
over again from potential customers.)
Orphanware, especially software with hardware (9-pin serial ports, for
example, or Okidata 393 printers and NCR paper) or OS requirements can be a
real problem for clients. There's only so far you want to take emulators
and kludgy solutions.
Caveat emptor applies, of course, but as a one-man-band developer, I'd hope
my clients would be left better off.
--
Ted Roche
Ted Roche & Associates, LLC
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4shBO-iVsCarDO3qhz7V0itvJO25vXOFpTY7E9nzE_Gtg@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Stephen Russell
Posted: 2014-02-21 10:49:34 Link
On Fri, Feb 21, 2014 at 9:33 AM, Ted Roche <tedroche@gmail.com> wrote:
> On Thu, Feb 20, 2014 at 4:20 PM, Adam Buckland
> <Adam.Buckland@eurohill.com>wrote:
>
> > In my case Ted with a "one man band² supplier who died whilst creating a
> > Windows version of his great DOS product for my printing Company.. Buy 6
> > desktops that run Win XP and 2 servers that run Win 2003 Server.. Then
> > look for an alternative product that doesn¹t need a dongle etc...
>
> Orphanware, especially software with hardware (9-pin serial ports, for
> example, or Okidata 393 printers and NCR paper) or OS requirements can be a
> real problem for clients. There's only so far you want to take emulators
> and kludgy solutions.
> -------------
>
I just found an Oki 393 printer in my attic when I had to move EVERYTHING
out of the way for a replacement furnace.
Has that wonderful Parallel port as well.
--
Stephen Russell
Sr. Analyst
Ring Container Technology
Oakland TN
901.246-0159 cell
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAJidMYLpJHq6dAXPPMi_gGQ=xSZC8ditKaMFwXHkDp+MJrusnw@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.