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.

Sign up for GitHub

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

Jump to bottom

x/mobile: use less Java #60603

Closed
MatejMagat305 opened this issue Jun 5, 2023 · 5 comments
Closed

x/mobile: use less Java #60603

MatejMagat305 opened this issue Jun 5, 2023 · 5 comments
Labels
mobile Android, iOS, and x/mobile NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unreleased

Comments

@MatejMagat305
Copy link

MatejMagat305 commented Jun 5, 2023 •
edited
Loading

this is mainly for discussion

Author background

I consider myself a intermediate
I have experience with C, C++, Java, Kotlin, Pascal, Haskell, Assembly, Vlang, Rust and Prolog

Related proposals

Proposal

  • What is the proposed change?
  • based gomobile
  • which aspect of golang proposal solve?
  • it has potencial reduce binary size of apk (binary of android) it also can reduce call java, but it is not mainly goal (benefit) and in practical maybe unmeasured, although it seems like avoid dalvik and it's GC, it couldn't have effect to go bind , it can brings more control and better debug ...
  • how make it?
  • use cgo to bind https://github.com/cnlohr/rawdrawandroid
@gopherbot gopherbot added this to the Proposal milestone Jun 5, 2023
@ianlancetaylor
Copy link
Contributor

I'm sorry, I don't understand the actual proposal here.

@ianlancetaylor ianlancetaylor added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Jun 5, 2023
@MatejMagat305
Copy link
Author

the gomobile use java code which use NativeActivity and load binary (.so), which has of course advantage too, but it is big binary size (pure C estimate 1-2MB) and at debug it is terible ... so The discusion and proposal is: there is technology, which allow reduce binary size to 25-45KB(at C side), better debug and have more control on code (it is without java code)..., so why do not use it in gomobile?

@ianlancetaylor
Copy link
Contributor

Thanks. This doesn't sound like it has to be a proposal, so taking it out of the proposal process.

@ianlancetaylor ianlancetaylor changed the title proposal: change based gomobile build mobile: use less Java Jun 5, 2023
@ianlancetaylor ianlancetaylor added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. mobile Android, iOS, and x/mobile and removed Proposal WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Jun 5, 2023
@ianlancetaylor ianlancetaylor modified the milestones: Proposal, Unreleased Jun 5, 2023
@MatejMagat305
Copy link
Author

ok, sorry for bad mark ...

@seankhliao seankhliao changed the title mobile: use less Java x/mobile: use less Java Jun 19, 2023
@MatejMagat305
Copy link
Author

MatejMagat305 commented Jun 30, 2024 •
edited
Loading

No sence, when we have raylib-go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
mobile Android, iOS, and x/mobile NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@ianlancetaylor @gopherbot @MatejMagat305