A 4GL is any language that's specialised for a particular function, and abstracts around tasks necessary to perform that function.
By focussing on REST, you're specialising for web services. This isn't a language that would be used for a washing machine controller, or for managing a nuclear power plant, or writing an MP3 player application, it's designed with one specific goal in mind... and that's the definition of a 4GL, it simplifies and abstracts to a higher level, but in a specialised domain. On 7 September 2010 18:51, Ruben Reusser <rube...@gmail.com> wrote: > what makes it sound like a 4gl language? how about if for example method > calls can be restfull or directly linked with the language being able to > expose the call to the outside world and the concept of security built in to > the language to begin with (say these requests are only allowed from within > the app, these are tied to a security level, etc)? > > Ruben > > > On Tue, Sep 7, 2010 at 10:34 AM, Kevin Wright <kev.lee.wri...@gmail.com>wrote: > >> pros: It sounds like a 4GL >> cons: It sounds like a 4GL with no 3rd party recognition that could better >> be handled as a simple library/DSL in any language that supports such >> things. >> >> >> On 7 September 2010 18:16, Ruben Reusser <rube...@gmail.com> wrote: >> >>> hi there, >>> >>> now I know you guys like languages a lot and are constantly debating if >>> there is a replacement language for java. The whole discussion has been >>> bugging me for a while and I always thought it would be necessary for a new >>> language to bring something to the table that java does offer but that could >>> be done better for the sake of getting stuff done faster (I always felt the >>> network libraries in java (easier socket programming) was a good reason to >>> switch from c/c++ to java). >>> >>> In order to provide a business advantage to a new language that could >>> drive adoption, I have been thinking about a restfull language - if a >>> language incorporates rest into it's architecture and makes it easier to >>> develop restfull applications we might have a winner in my opinion. Say for >>> example if the language helps you to write restfull services that can easily >>> be integrated with each other and where the UI can be easily merged for >>> multiple applications we could potentially start building larger >>> applications where we have the ability to reuse application blocks and >>> create bigger applications faster. >>> >>> Would love to get some comments on it - pros or cons of course :-) >>> >>> Ruben >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "The Java Posse" group. >>> To post to this group, send email to javapo...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> javaposse+unsubscr...@googlegroups.com<javaposse%2bunsubscr...@googlegroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/javaposse?hl=en. >>> >> >> >> >> -- >> Kevin Wright >> >> -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to javapo...@googlegroups.com. > To unsubscribe from this group, send email to > javaposse+unsubscr...@googlegroups.com<javaposse%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- Kevin Wright mail / gtalk / msn : kev.lee.wri...@gmail.com pulse / skype: kev.lee.wright twitter: @thecoda -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
