Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #58065
| Subject | Re: Dropbox rant |
|---|---|
| References | <7c24bccb-bc9e-450c-bb8f-9424e06f6209@googlegroups.com> <odg8ge$amg$1@dont-email.me> <SaidnZEcTP1_5WHFnZ2dnUU7-cednZ2d@supernews.com> <64620e3b-5207-432e-b007-fade6cc2b8de@googlegroups.com> <c8c2ebb0-f5ae-4eca-a28a-b5c742ebafde@googlegroups.com> |
| Newsgroups | comp.lang.forth |
| From | "Elizabeth D. Rather" <erather@forth.com> |
| Organization | FORTH, Inc. |
| Date | 2017-04-24 21:26 -1000 |
| Message-ID | <mJOdnfVoXsSSZ2PFnZ2dnUU7-ffNnZ2d@supernews.com> (permalink) |
On 4/24/17 3:06 PM, foxaudioresearch@gmail.com wrote: > On Sunday, April 23, 2017 at 9:58:03 AM UTC-4, Julian Fondren wrote: >> On Sunday, April 23, 2017 at 4:50:31 AM UTC-5, Andrew Haley wrote: >>> >>> The times they are a changin'. If you run servers in the cloud you >>> pay for processors and you pay for bytes, so there is a considerable >>> renewed interest in fast and compact systems and protocols. >>> >>> Andrew. >> >> I have a little script in Perl that continuously makes HTTP requests. >> It's actual function is to serialize internal requests to an >> application that tends to fall over if it gets asked 20 expensive >> questions at once. The script itself doesn't actually accept >> HTTP requests. It's one half of the solution. The other half is a CGI >> script that either says "oh yeah here's your (cached) answer >> immediately" or "you want what? never heard of it. enjoy your error. >> (psst-- they want this new thing now. I've added it to the list!)" >> >> This little script grows by ONE MEGABYTE each request. Permanently. I >> have no idea why. I tried switching out LWP, I tried not checking for >> the JSON-validity of the data it was fetching. The only other thing >> the script does is log! In the end I resolved things well enough (that >> I can't now justify spending any more time on the matter) by having it >> kill itself after it bloats past 200MB. >> >> This was a server with 8GB of memory. This was in 2017. This was with >> a relatively nice high level language. And the entire time I was >> trying to find out what was going on, I was thinking, maaan, if only >> this were in Forth... >> >> In Forth I would've tested the JSON with a streaming validator working >> in fixed memory, writing to a file as fast as I got more JSON from the >> remote server. It's inconceivable that I'd find myself worrying about >> a similar Forth program taking 7.1G of RAM, or that I'd have any >> trouble pinning down where that came from. > > What would you say has prevented Forth from being applied to this problem > domain? The fact that no of the organizations that were using Forth were working in this problem domain, and the organizations that were working on it didn't know about Forth. > My own prejudiced opinion is that a raw Forth solution would be in- > comprehensible to the majority of IT people, but some kind of application > specific language tailored to the problem could be made palatable I suspect and > also be efficient. The whole methodology of working with Forth is based on developing an application-oriented language for the domain in question. > However most Forth professionals are busy solving a completely different set of > problems, so perhaps there is just not the critical mass of Forth people to > to get activity in these other areas. (?) It's not so much a problem of finding a "critical mass of Forth people" to work on a particular application domain, it's a matter of finding a funding source for it. Programmers, like other people, expect to eat dinner every day. Chuck's early work was funded by NRAO. He worked on the applications they paid him to do. When he and I founded FORTH, Inc., we made a living writing the applications our customers wanted. Cheers, Elizabeth -- Elizabeth D. Rather FORTH, Inc. 6080 Center Drive, Suite 600 Los Angeles, CA 90045 USA
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Dropbox rant Mark Wills <markwills1970@gmail.com> - 2017-04-22 11:24 -0700
Re: Dropbox rant Cecil Bayona <cbayona@cbayona.com> - 2017-04-22 13:50 -0500
Re: Dropbox rant Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-04-23 04:50 -0500
Re: Dropbox rant Julian Fondren <julian.fondren@gmail.com> - 2017-04-23 06:58 -0700
Re: Dropbox rant foxaudioresearch@gmail.com - 2017-04-24 18:06 -0700
Re: Dropbox rant Julian Fondren <julian.fondren@gmail.com> - 2017-04-24 20:30 -0700
Re: Dropbox rant foxaudioresearch@gmail.com - 2017-04-24 22:02 -0700
Re: Dropbox rant "Elizabeth D. Rather" <erather@forth.com> - 2017-04-24 21:52 -1000
Re: Dropbox rant Julian Fondren <julian.fondren@gmail.com> - 2017-04-25 16:38 -0700
Re: Dropbox rant hughaguilar96@gmail.com - 2017-04-25 16:55 -0700
Re: Dropbox rant Julian Fondren <julian.fondren@gmail.com> - 2017-05-28 17:50 -0700
Re: Dropbox rant "Elizabeth D. Rather" <erather@forth.com> - 2017-04-24 21:26 -1000
Re: Dropbox rant john <anon@example.com> - 2017-04-25 10:22 +0100
Re: Dropbox rant lehs <skydda.barnen@gmail.com> - 2017-04-25 04:14 -0700
Re: Dropbox rant hughaguilar96@gmail.com - 2017-04-25 11:25 -0700
Re: Dropbox rant Alex <alex@rivadpm.com> - 2017-04-26 15:57 +0100
Re: Dropbox rant Ron Aaron <rambamist@gmail.com> - 2017-04-26 18:41 +0300
Re: Dropbox rant Alex <alex@rivadpm.com> - 2017-04-26 17:59 +0100
Re: Dropbox rant Ron Aaron <rambamist@gmail.com> - 2017-04-26 21:38 +0300
Re: Dropbox rant rickman <gnuarm@gmail.com> - 2017-04-26 17:48 -0400
Re: Dropbox rant hughaguilar96@gmail.com - 2017-04-26 12:42 -0700
Re: Dropbox rant Ron Aaron <rambamist@gmail.com> - 2017-04-27 06:57 +0300
Re: Dropbox rant hughaguilar96@gmail.com - 2017-04-26 21:20 -0700
OT: Hugh's in need of help (was Re: Dropbox rant) Ron Aaron <rambamist@gmail.com> - 2017-04-27 07:45 +0300
Re: OT: Hugh's in need of help (was Re: Dropbox rant) rickman <gnuarm@gmail.com> - 2017-04-27 01:31 -0400
Re: OT: Hugh's in need of help (was Re: Dropbox rant) Ron Aaron <rambamist@gmail.com> - 2017-04-27 08:43 +0300
Re: OT: Hugh's in need of help (was Re: Dropbox rant) rickman <gnuarm@gmail.com> - 2017-04-27 01:56 -0400
Re: OT: Hugh's in need of help (was Re: Dropbox rant) hughaguilar96@gmail.com - 2017-04-27 13:17 -0700
Re: OT: Hugh's in need of help (was Re: Dropbox rant) rickman <gnuarm@gmail.com> - 2017-04-27 16:31 -0400
Re: OT: Hugh's in need of help (was Re: Dropbox rant) Ron Aaron <rambamist@gmail.com> - 2017-04-28 07:48 +0300
Re: OT: Hugh's in need of help (was Re: Dropbox rant) Ron Aaron <rambamist@gmail.com> - 2017-04-28 10:22 +0300
Re: OT: Hugh's in need of help (was Re: Dropbox rant) "HAA" <someone@microsoft.com> - 2017-04-30 11:09 +1000
Re: OT: Hugh's in need of help (was Re: Dropbox rant) hughaguilar96@gmail.com - 2017-04-29 21:52 -0700
Re: OT: Hugh's in need of help (was Re: Dropbox rant) Ron Aaron <rambamist@gmail.com> - 2017-04-30 08:24 +0300
Re: OT: Hugh's in need of help (was Re: Dropbox rant) rickman <gnuarm@gmail.com> - 2017-04-30 01:54 -0400
Re: OT: Hugh's in need of help (was Re: Dropbox rant) Ron Aaron <rambamist@gmail.com> - 2017-04-30 09:04 +0300
Re: OT: Hugh's in need of help (was Re: Dropbox rant) rickman <gnuarm@gmail.com> - 2017-04-30 02:19 -0400
Re: OT: Hugh's in need of help (was Re: Dropbox rant) lehs <skydda.barnen@gmail.com> - 2017-04-30 00:41 -0700
Re: OT: Hugh's in need of help (was Re: Dropbox rant) Ron Aaron <rambamist@gmail.com> - 2017-04-30 11:01 +0300
Re: OT: Hugh's in need of help (was Re: Dropbox rant) lehs <skydda.barnen@gmail.com> - 2017-04-30 01:24 -0700
Re: OT: Hugh's in need of help (was Re: Dropbox rant) Mark Wills <markwills1970@gmail.com> - 2017-04-30 03:33 -0700
Re: OT: Hugh's in need of help (was Re: Dropbox rant) jenfhaomndgfwutc@murmic.plus.com - 2017-04-30 16:19 +0100
Re: OT: Hugh's in need of help (was Re: Dropbox rant) Cecil Bayona <cbayona@cbayona.com> - 2017-04-30 16:46 -0500
Re: Dropbox rant "HAA" <someone@microsoft.com> - 2017-05-02 11:33 +1000
Back on-topic: what attracted you to Forth?' (was: OT: Hugh's in need of help ...) Ron Aaron <rambamist@gmail.com> - 2017-04-30 08:42 +0300
csiph-web