Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delete JS tooling #378

Open
hohwille opened this issue Apr 16, 2021 · 4 comments
Open

Delete JS tooling #378

hohwille opened this issue Apr 16, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@hohwille
Copy link
Member

As suggested by @maybeec in issue #344 we should drop this section from the documentation:
https://github.com/devonfw/devon4j/blob/master/documentation/guide-client-layer.asciidoc#javascript-for-java-developers

Any feedback if that is common sense and not needed by anyone anymore, or is missplaced in our Java stack devon4j is welcome as well as feedback that you find this valuable and vote against dropping it.

@hohwille hohwille added the enhancement New feature or request label Apr 16, 2021
@amarinso
Copy link
Member

Maybe devon4j is not the place people will look for this info if trying to make sense of the JavaScript ecosystem... I would vote for not dedicating effort here...

@hohwille
Copy link
Member Author

As it explains the JS ecosystem for Java developers I would not know where else to put it. Also I think we should not waste effort here. So either do nothing or simply delete.

@baumeister25
Copy link

I would also vote for deleting this section. I do not see the benefit. If someone searches for such a comparison he'll find with a few clicks. https://blog.angular-university.io/javascript-for-java-developers/
This even shows that there's more than excahnging jvm with node.js and mvn with npm

@hohwille
Copy link
Member Author

IMHO https://blog.angular-university.io/javascript-for-java-developers/ is an example for a bad hit as it comes with a long text explaining what is the difference between java and javascript while the section discussed here gives you an overview of the ecosystem and tooling at a glance. In the end with this argument we can delete the entire devonfw documentation as you can find all the knowledge somewhere already on the web if you search hard enough...

However, I am happy to approve and merge a PR removing the section if someone feels like doing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants