Hi,
I found an interesting nugget at the end of http://www.forbes.com/sites/gilpress/2015/07/29/turing-award-winner-stonebra... which is the need to integrate data models in different databases. “If your application is managing what you want to think of as a single database which is in fact spread over multiple engines,” says Stonebraker, “with different data models, different transaction systems, different everything, than you want a next-generation federation mechanism to make it as simple as possible to program.”
This would seem to play to Smalltalk's strengths.
Sent from my iPhone
Eliot writes:
I found an interesting nugget at the end of [1] which is the need to integrate data models in different databases. “If your application is managing what you want to think of as a single database which is in fact spread over multiple engines,” says Stonebraker, “with different data models, different transaction systems, different everything, than you want a next-generation federation mechanism to make it as simple as possible to program.”
This would seem to play to Smalltalk's strengths.
Yes indeed!
-C
[1] https://tinyurl.com/o7nmvnv (forbes.com)
-- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)
Yes, integrating data from different models and systems a major strength of Smalltalk.
And what Phil described on Cuis list on the 24th of July
He uses Smalltalk for
1. data processing Lots of importers and exporters. The data I need is all over the place both on my local filesystem/network as well as from various Internet sources in just about every format ....
2. visualization/simulation Visualization/simulation: often I'm not just doing a simple data conversion, so once the data is in Cuis I might need to do some analysis to see what I'm dealing with, generate some charts/graphs, visualize relationships within a data set or the results of a simulation, etc. ......
3. prototyping. Prototyping: most of the 'production' code I'm dealing with is in other languages (Java for Android apps as an example). However, I find non-dynamic languages unpleasant to prototype in. So I find myself quite often playing around with my ideas in Cuis even though the implementation target might be a different language/environment.....
--Hannes
On 7/30/15, Craig Latta craig@netjam.org wrote:
Eliot writes:I found an interesting nugget at the end of [1] which is the need to integrate data models in different databases. “If your application is managing what you want to think of as a single database which is in fact spread over multiple engines,” says Stonebraker, “with different data models, different transaction systems, different everything, than you want a next-generation federation mechanism to make it as simple as possible to program.”
This would seem to play to Smalltalk's strengths.
Yes indeed!-C
[1] https://tinyurl.com/o7nmvnv (forbes.com)
-- Craig Latta netjam.org +31 6 2757 7177 (SMS ok)
- 1 415 287 3547 (no SMS)
Also note the
"Stonebraker Formula for Making a Difference"
1. Identify new solution to a data management problem; 2. Lead research project to develop a prototype; 3. Publish paper(s); 4. Publish software code on a public website; 5. Launch startup; 6. Repeat.
http://www.forbes.com/sites/gilpress/2015/07/29/turing-award-winner-stonebra...
On 7/30/15, H. Hirzel hannes.hirzel@gmail.com wrote:
Yes, integrating data from different models and systems a major strength of Smalltalk.
And what Phil described on Cuis list on the 24th of July
He uses Smalltalk for
- data processing
Lots of importers and exporters. The data I need is all over the place both on my local filesystem/network as well as from various Internet sources in just about every format ....
- visualization/simulation
Visualization/simulation: often I'm not just doing a simple data conversion, so once the data is in Cuis I might need to do some analysis to see what I'm dealing with, generate some charts/graphs, visualize relationships within a data set or the results of a simulation, etc. ......
- prototyping.
Prototyping: most of the 'production' code I'm dealing with is in other languages (Java for Android apps as an example). However, I find non-dynamic languages unpleasant to prototype in. So I find myself quite often playing around with my ideas in Cuis even though the implementation target might be a different language/environment.....
--Hannes
On 7/30/15, Craig Latta craig@netjam.org wrote:
Eliot writes:I found an interesting nugget at the end of [1] which is the need to integrate data models in different databases. “If your application is managing what you want to think of as a single database which is in fact spread over multiple engines,” says Stonebraker, “with different data models, different transaction systems, different everything, than you want a next-generation federation mechanism to make it as simple as possible to program.”
This would seem to play to Smalltalk's strengths.
Yes indeed!-C
[1] https://tinyurl.com/o7nmvnv (forbes.com)
-- Craig Latta netjam.org +31 6 2757 7177 (SMS ok)
- 1 415 287 3547 (no SMS)
squeak-dev@lists.squeakfoundation.org
-
Craig Latta -
Eliot Miranda -
H. Hirzel