Re: "Team" members wanted

I'm really not bothered if it is JavaScript, ECMAScript, or even plain old
assembly language.

What I only need is an existing ecosystem of tools for dealing with much of
the issues I'll be facing of when building an application stack.

I'm really 'language agnostic' but as I'll be using lots of existing
frameworks that are Java frameworks I'd like to leverage them.

If you read the documents I've published so far my goal is to have an
'engine' of which any developer in any platform could benefit from a
semantic backend (connector architecture). And I'm sure there will be
developers having a benefit from that using JavaScript, PHP or whatever
language they choose.

We still discussing how to make Documents based Web applications while my
scope is to provide the Data based Web facilities which, in principle, has
nothing to do with presentation. It's more like a protocol...

Best,
Sebastián Samaruga
---
http://exampledotorg.blogspot.com

On Oct 28, 2017 10:40 AM, "Ruben Verborgh" <Ruben.Verborgh@ugent.be> wrote:

> > the problem is not the 'language' as long as it's turing complete and
> has the necessary libraries to work without re-inventing everything.
>
> It depends on what we, as a community, want to achieve.
>
> Yes, all of the aforementioned languages are Turing-complete,
> so anything can be written in each of these languages.
> Therefore, if the goal is “write application X”,
> there's nothing that stops someone from writing that application.
>
> However, it does depend on the definition of "someone”.
> If they are Web developers… nope.
> They don't do Java.
>
> > Java has a strong set of libraries for working with almost any paradigm
> and is fundamentally well suited when looking for developers with
> experience in the language.
>
>
> Don't get me wrong, Java is great
> for many enterprise purposes
> and behind-the-scenes work.
>
> But for visible, front-facing applications?
> Making the SemWeb available in JavaScript
> seems crucial to have any chance of adoption.
> Nobody runs Java applets anymore.
>
> >> As you wish. To me what is unproductive and pointless is plugging
> JavaScript at every turn.
>
> More productive would be writing JavaScript libraries :-)
>
> >> https://hackernoon.com/how-it-feels-to-learn-javascript-in-
> 2016-d3a717dd577f
>
> That's assuming you have to know all the underlying technologies.
> Most of the devs don't; they write high-level JavaScript,
> which is exactly why we should make things easy for them.
>
> Best,
>
> Ruben