sanjiva
Please compare processing JSON in Java vs. Ballerina, typing network data in Java vs. Ballerina, writing HTTP/GraphQL/WebSocket/gRPC etc. services etc. in Java vs. Ballerina, calling network services in Java vs. Ballerina and then you'll see the difference between whatever your favorite Java framework (or rather combination of them) vs. Ballerina.
(I'm the founder & CEO of WSO2 and one of the lead language designers.)
I called and said what had happened and within a short time we had police, ambulance and a fire person show up (I guess they were all bored).
IMO that's part of the problem in US policing: The assumption is that the people are bad (in my case that I had hit my wife I guess - I was interviewed by the cops before she was taken to hospital for a checkup). I called 911 for a medical emergency, not a criminal issue so why do cops have to come and treat me like a criminal. If you think that something is wrong then you find a way to find something wrong.
I wrote a blog about US policing a few years ago because I feared for my son's safety: https://medium.com/@sanjiva.weerawarana/police-in-us-need-to....
Release blog: https://blog.ballerina.io/posts/announcing-ballerina-swan-la...
Short tutorial on how to write a service in Ballerina: https://www.youtube.com/watch?v=NxyIKoHl3Dw&ab_channel=Balle...
In-depth slide deck: https://ballerina.io/learn/language-concepts/Ballerina_Langu...
Video presentation of these slides: https://ballerina.io/learn/language-concepts/
Moving production is much more complex and requires long term policies and strategies- something most countries (other than China) seem unable to muster.
We can do both, just like anyone else in any country.
We will soon publish a playground widget which will let you run the same code in the browser so you can see source and the diagram as you wish (or not!).
I'm sorry but I cannot accept the argument that because its a feminine word its not an appropriate name for the language. Gender balance has been a problem for this industry and making it so all names are male so people won't feel bad to say they like it is ridiculous. I worked hard in WSO2 to create an open workplace for women and 30% engineers are women - so it is possible to make it better if you try hard. Isolating tech to male-only names is not the solution.
As James noted, I updated the blog I wrote (even though the words were not meant the way you presented them) to remove that offending bit. And indeed your points about incorporating "do not sexualize the name" are great and we'll put them into our terms of conduct.
The XML programming model is rather different from DOM and others for a lot of reasons. I hope reading this proposal will help.
Ballerina is in its first GA release. Please elaborate on what features you see as "almost complete"?
And regards to your comment about WSO2's inability to produce market-ready products, we have 500+ customers from all over the world for our products. What do we need to become "market-ready"?
We'll work on it.
A Go-like full screen online playground is coming.
WSO2 is an enterprise software product company with 500+ customers in 70+ countries and 600 employees globally.
We promoted Ballerina like that because we are proud of the work we do and wanted to show it off to people. You may not like the work we produce but trying to say its to get "consultancy work in India" is rather racist.
However, after you're done, if to see the flow of your entire program (not just one function) as a sequence diagram then you can get that done.
The language syntax is "normal" syntax and has all the power o a modern language. Try it and see- feedback welcome.
Disclaimer: I'm the one who started the project and leading it as the product manager now.
Its a real language :-). Please check the spec out here: https://ballerina.io/res/Ballerina-Language-Specification-WD....
Feedback welcome!
Making that perform at the same level as a TCP driver written in C could be a bit challenging .. but not impossible.
In fact, expressing network interaction protocols is one motivation for the sequence diagram approach, but the expectation was higher level stuff like OpenID or SAML type interactions.
Ballerina's design point is to be a language with semantically equivalent text and graphic syntaxes. Its not a "visual language" really .. its a language with alternative syntaxes, one text and one graphic.
That approach eliminates the "hit-the-wall" phenomenon of visual languages. And as other commenters have said, a lot of the graphical view is useful to understand overall structure and less to write lots of code. However, parallel code is much better visualized graphically as sequence diagrams are dead simple to grok.
In terms of speed of the current Composer .. still WIP. Help is welcome :).
Only time will tell whether we get the mix right.
Absolutely no Java semantics or concepts are leaked to the language.
If you meant debugging type stuff yes there's debugging already, including from the Idea plugin.