Programming Languages

1167 readers

5 users here now

Hello!

This is the current Lemmy equivalent of https://www.reddit.com/r/ProgrammingLanguages/.

The content and rules are the same here as they are over there. Taken directly from the /r/ProgrammingLanguages overview:

This community is dedicated to the theory, design and implementation of programming languages.

Be nice to each other. Flame wars and rants are not welcomed. Please also put some effort into your post.

This isn't the right place to ask questions such as "What language should I use for X", "what language should I learn", and "what's your favorite language". Such questions should be posted in /c/learn_programming or /c/programming.

This is the right place for posts like the following:

"Check out this new language I've been working on!"
"Here's a blog post on how I implemented static type checking into this compiler"
"I want to write a compiler, where do I start?"
"How does the Java compiler work? How does it handle forward declarations/imports/targeting multiple platforms/?"
"How should I test my compiler? How are other compilers and interpreters like gcc, Java, and python tested?"
"What are the pros/cons of ?"
"Compare and contrast vs. "
"Confused about the semantics of this language"
"Proceedings from PLDI / OOPSLA / ICFP / "

See /r/ProgrammingLanguages for specific examples

Related online communities

founded 1 year ago

MODERATORS

[email protected]

Jolie, the service-oriented programming language (www.jolie-lang.org)

submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

From the homepage:

Thinking in services

Jolie crystallises the programming concepts of service-oriented computing as linguistic constructs. The basic building blocks of software are not objects or functions, but rather services that can be relocated and replicated as needed. A composition of services is a service.

Tailored for microservices and APIs

Jolie is a contract-first programming language, which puts API design at the forefront. It supports both synchronous and asynchronous communication. Data models are defined by types that support refinement [...], and DTO (Data Transfer Objects) transformations are transparently managed by the interpreter.

From vision:

Our vision is to design a programming language with a different trade-off: instead of optimising for computation, the aim of Jolie is to offer native abstractions for the creation and composition of services.

By shifting the focus on services from libraries and frameworks to the programming language, we can change significantly how programmers manage their knowledge regarding service programming. The key idea is that the important abstractions for service programming should be crystallised in the programming language, translating to an easier learning curve for new service developers and less knowledge to be managed.

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 5 points 6 months ago

That's a cool idea, though obviously you need functions and objects to actually make services do useful stuff. And lots of libraries. I achieve most of what they describe quite easily using GRPC/protobufs with Go, and so I have doubts that this is going to be better. Plus GRPC/protobufs have the benefit of working seamlessly with other languages, and with some small added code, you can add annotations that handle auth, routing, validation, etc

[–] [email protected] -1 points 6 months ago (1 children)

https://www.gnu.org/philosophy/who-does-that-server-really-serve.html

[–] [email protected] 3 points 6 months ago

Service-oriented architecture does not imply SaaS.

Obviously plenty of FOSS software uses servers. IRC, Mastodon, Email, NTP, X11... There are plenty of good uses for service-oriented architecture in FOSS.