Jolie, the service-oriented programming language

Post by didibus » Tue, May 18, 2021, 5:54 PM UTC

Zababa wrote: post #70

didibus wrote: post #64

Earlier quoted context omitted.

I'm a french speaker, Jolie is a common woman name, yes it also means pretty, but that's like people called Lily or Prince. The logo is also a woman's eye + brow. It's possible the author was going for the meaning of pretty, but there still seem to be a strong personification happening with emphasis on it being a beautiful woman, and it's that aspect that unease me. Again, you can call your language however you choos…

> Jolie is a common woman name Where? It's not even on the INSEE tool https://www.insee.fr/fr/statistiques/3532172 , according to their "Fichier des prénoms" ( https://www.insee.fr/fr/statistiques/2540004 ), there are currently 39 persons named "Jolie" in France. This is not to dismiss the rest of what you said, I'm just curious as to where "Jolie" is a common woman name.

Post by wpietri » Tue, May 18, 2021, 6:50 PM UTC

fmontesi wrote: post #50

wpietri wrote: post #45

Earlier quoted context omitted.

Could you expand on this? I'm not seeing why the "duh" is warranted. > Jolie, you write code that maps directly to the concepts that matter. What are the important concepts? APIs, Access Points, and Services (duh..) are examples. I come out of the Domain Driven Design school of thought, where the true key concepts are the domain-related ones. E.g., if you're doing ecommerce, things like Product and Order are much mor…

I was indeed talking about implementation models, in particular models of service-oriented systems. These are usually formulated in terms of services, DTOs, APIs, business logic, etc., hence the value brought by Jolie in giving a direct syntactic representation. The model of an implementation can change often, so it's important to have code that resembles it closely (for readability, editing, etc.). You're talking ab…

Post by didibus » Wed, May 19, 2021, 1:36 AM UTC

Zababa wrote: post #75

didibus wrote: post #72

Earlier quoted context omitted.

Well, I had never really researched this, but I'm from Quebec, and I know 3 Jolie. Maybe it's more prevalent there, or maybe I happen to know a coincidentally large number of them. If the latter, I guess that is a good learning experience for how your own life experience can easily bias you in your opinions and understanding of some things.

I was curious about this so I searched around a bit and found the data for girls names from 1980 to 2020 [1]. I've found 269 people with first name containing "Jolie". Then I took the census data [1], found that 45% of Quebec females are under 40. So extrapolating from the first number, I find 524 females with Jolie in their names in Quebec. That means 1 in 7915 female in Quebec has Jolie in her name, compared to aro…

Post by sidecut » Wed, May 26, 2021, 5:08 PM UTC

rajinl wrote: post #35

klag wrote: post #30

Earlier quoted context omitted.

In jolie, develoeprs program services instead of classes or functions. I think this is the main novelty introduced by jolie. Everything is a service, and you can postpone the decision on how to deploy an application. You can deploy it as a monolith (so your services will play the roles of classes, because they are internal) or independent services.

thanks for the reply. My concern was people writing services that available on the network for trivial use cases, where a class or function would be faster and as reusable. You have addressed that concern. In light of your answer, is Jolie similar to an actor based pattern like Akka, with services being the abstraction rather than actors?