Top Posts Tagged with #domain specific languages

Supporting Domain-Specific Programming in Web 2.0: a Case Study of Smart Devices

This is a short preview of the article: Abstract of Supporting Domain-Specific Programming in Web 2.0: a Case Study of Smart Devices Web 2.0 communities emerge regularly with the growing need for domain-specific programming over Web APIs. Even though Web mashups provide access to Web APIs, they ignore domain-specific programming

If you like it consider checking out the full version of the post at: Supporting Domain-Specific Programming in Web 2.0: a Case Study of Smart Devices

If you are looking for ideas for tweet or re-blog this post you may want to consider the following hashtags:

Hashtags: #CloudComputing, #DomainSpecificLanguages, #InternetOfThings, #Plugin, #PluginArchitecture, #SmartDevice, #UbiquitousComputing, #Web20, #Web20Communities, #WebServices

The Hashtags of the Categories are: #CloudComputing, #InternetofThings, #Publication

Supporting Domain-Specific Programming in Web 2.0: a Case Study of Smart Devices is available at the following link: https://francescolelli.info/cloud-computing/supporting-domain-specific-programming-in-web-2-0-a-case-study-of-smart-devices/ You will find more information, stories, examples, data, opinions and scientific papers as part of a collection of articles about Information Management, Computer Science, Economics, Finance and More.

The title of the full article is: Supporting Domain-Specific Programming in Web 2.0: a Case Study of Smart Devices

It belong to the following categories: Cloud Computing, Internet of Things, Publication

The most relevant keywords are: Cloud Computing, domain specific languages, internet of things, plugin, plugin architecture, smart device, ubiquitous computing, Web 2.0, Web 2.0 communities, Web Services

It has been published by Francesco Lelli at Francesco Lelli a blog about Information Management, Computer Science, Finance, Economics and nearby ideas and opinions

Abstract of Supporting Domain-Specific Programming in Web 2.0: a Case Study of Smart Devices Web 2.0 communities emerge regularly with the growing need for domain-specific programming over Web APIs. Even though Web mashups provide access to Web APIs, they ignore domain-specific programming

Hope you will find it interesting and that it will help you in your journey

If you like what you are reading please help us spread the word. Sharing is caring: If you like what you are reading please help us spread the word. Sharing is caring:

#Cloud Computing #domain specific languages #internet of things #plugin #plugin architecture #smart device #ubiquitous computing #Web 2.0 #Web 2.0 communities #Web Services

•18+ Adults Only

Watch Anya Live on Cam

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.

✓ Live Streaming✓ Interactive Chat✓ Private Shows✓ HD Quality✓ Free Actions

Free to watch • No registration required • HD streaming

Domain Specific Languages and Next Gen Functional Testing

I wrote a white paper for a webinar on next generational functional testing that we sponsored. The webinar consists of two very interesting talks by Jennitta Andrea and Ward Cunningham. You can view the archived webinar, which includes a small demo of the new testing product that we're building, albeit with a slight audio problem during that portion. The white paper I wrote is below. Sorry it's not in an RSS reader friendly format.

Domain Specific Languages for Functional Testing

#JustMigrated #Domain Specific Languages

It seemed to me that trying to make that imperative minilanguage more like English might make (fetchmail) easier to use. Now, although I'm a convinced partisan of the "make it a language" school of design as exemplified by Emacs and HTML and many database engines, I am not normally a big fan of "English-like" syntaxes. Traditionally programmers have tended to favor control syntaxes that are very precise and compact and have no redundancy at all. This is a cultural legacy from when computing resources were expensive. With cheap cycles and core, terseness should not be an end in itself. Nowadays it's more important for a language to be convenient for humans than to be cheap for the computer. There are, however, good reasons to be wary. One is the complexity cost of the parsing stage - you don't want to raise that to the point where it's a significant source of bugs and user confusion in itself. Another is that trying to make a language syntax English-like often demands that the "English'' it speaks be bent seriously out of shape, so much so that the superficial resemblance to natural language is as confusing as a traditional syntax would have been. The fetchmail control syntax seems to avoid these problems because the language domain is extremely restricted. It's nowhere near a general-purpose language; the things it says simply are not very complicated, so there's little potential for confusion in moving mentally between a tiny subset of English and the actual control language. I think there may be a wider lesson here: When your language is nowhere near Turing-complete, syntactic sugar can be your friend.

Eric Raymond, in The Cathedral and the Bazaar

#software design #domain specific languages