ccs specs - Forum - OpenEdge General - Progress Community

ccs specs

This question is not answered

Heard a rumour that the ccs specs are published. Now that the nda has been silently (!) dropped there's no restriction to publish and discuss them here now is there? ;-) In how far an eventual evolution to a micro services architecture (  will be kept in mind?

  I would be happy with a small brms included. Not an interface to that expensive and vast corticon, just a small one written in abl. Easy integration possibilities with an os solution like would be nice. Furthermore dynamic catalog generation for datasets with more than one table. I could use that for batchmode insert of orders f.e. (so not first save an order and afterwards save orderlines one by one). Mailed this link before with a demo:   nice eh?

Kind regards,
Stefan Houtzager
Houtzager ICT consultancy & development
All Replies
  • Come on Thomas, don't trust on our blindness. We got to make a living. Are you sponsored by psc or so?

  • Point being that new OpenEdge licenses are still being sold and are growing.

    Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice

  • Any new Partners or ISVs being signed up?

  • Sold to the garbagehauler? Don't make me laugh.


    Looks like a nice presentation from 2015 about some trends. Take advantage of this psc.

    This is what the speaker has to say about agile:

  • Dave Thomas, who was one of the writers of the agile manifesto in an interview:

    "What's wrong with current programming is something that almost everyone recognizes and most people hope will go away: Moore's Law still applies and for that to have happened, we find that the architectures of our machines have changed dramatically. So, we're looking at multicore, hyperthreading, off-loading processing on to GPUs, and so on. My laptop has a billion transistors in it, which is incredible. And no one can keep a billion transistors busy if they're doing sequential coding. You have to partition the work and do multiple pieces at the same time. And our tools for doing that at the moment are remarkably primitive. They're based on evolving old models. It's like we're saying we got here with object orientation and now we have to make it work concurrently — just slap a few more primitives in and hope. The reality is that doesn't work that well. Clearly, it works, but it takes a lot of effort and it's error-prone."

    Read the whole interview, it's worth your time.

  • FWIW, in 1967 I was programming in Tranquil, an Algol-like language which had two levels.  It was developed for the Illiac IV, the first massively parallel computer (which did not physically exist at that point).  IlliacIV had four quadrants, each with a master control processor and 64 slave processors.  Tranquil addressed both levels.  One could start and stop the individual processors in response to data and move data between them.

    However, programming in Tranquil was very hard!

    Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice

  • I'm working myself through a Dave Thomas tutorial for elixir 1.2. Using elixir/erlang in a docker container. If you're interested here's an intro: Elixir is not as hard to start working in as f.e. haskell. Times have changed since your tranquil + never too late to teach a dog a new trick eh Thomas? Whatever / anyway.  I will be learning the elixir phoenix web framework ( lateron. "Elixir allows for massive scalability without the headaches of callbacks" (goodbye node.js!)

    Communication between elixir processes is fast btw (google yourself for that). I think Dave Thomas is right: "Elixir is the next killer language. The future has to be functional, immutable data, and it has to be concurrent. It's the only way to grow. And very few of our current languages let us do that."

  • chapter 14 (concurrent programming) of Dave Thomas' tutorial (much enjoying the course) starts with:

    "One of Elixir’s key features is the idea of packaging code into small chunks that can be run independently and concurrently. If you’ve come from a conventional programming language, this may worry you. Concurrent programming is “known” to be difficult, and there’s a performance penalty to pay when you create lots of processes. Elixir doesn’t have these issues, thanks to the architecture of the Erlang VM on which it runs. [..]

    And each process can contain its own state - in a way, processes in Elixir are like objects in an object-oriented system (but they have a better sense of humor)."