Codename One
proposal
Codename One | proposal | |
---|---|---|
88 | 46 | |
1,647 | 3,290 | |
0.7% | 0.4% | |
8.5 | 4.4 | |
7 days ago | about 2 months ago | |
Java | Go | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Codename One
-
A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
codenameone.com — Open source, cross-platform, mobile app development toolchain for Java/Kotlin developers. Free for commercial use with an unlimited number of projects
-
Android Play Billing Needs updating
This was resolved in this issue: https://github.com/codenameone/CodenameOne/issues/3706
-
Backward Compatibility, Go 1.21, and Go 2
Naturally depends on the use case, yet they work good enough to be in business for 20 years.
https://www.ptc.com/en/products/developer-tools/perc
https://www.aicas.com/wp/products-services/jamaicavm-tools/
https://www.codenameone.com/
Android 5 & 6 (only changed back into JIT/AOT due to long compile times), https://www.infoq.com/news/2014/07/art-runtime/
Unfortunely the best well known, Excelsior JET, is no longer in business, most likely due to GraalVM and OpenJ9 being available as free beer, while PTC, Aicas Codename One are safe in their domains.
There is also RoboVM (https://github.com/MobiVM/robovm) as free beer, however it actually started as a commercial product, and the acquisition from Xamarin kind of stagnated it (naturally).
-
Can't Reproduce a Bug?
At Codename One, we were using App Engine when our daily billing suddenly skyrocketed from a few dollars to hundreds. The potential cost was so high it threatened to bankrupt us within a month. Despite our best efforts, including educated guesses and fixing everything we could, we were never able to pinpoint the specific bug. Instead, we had to solve the problem through brute force.
-
Mobile Apps with Java
We don't use GraalVM since our project was developed prior to its existence and we aimed for deeper native integration than it can offer: https://github.com/codenameone/CodenameOne
-
Developing cross platform mobile application [closed]
XMLVM, Codename One and iSpectrum (cross compile Java code from an Android app or creating one from scratch
-
Apple Offer Codes
I suggest filing an RFE in the issue tracker.
-
Play Billing Library Version Deprecation
Thanks. It's always good to get another reminder. Yes, it was reported. u/shannah78 is working on this but we have time until November.
-
Problems compilint to android side
please check this issue https://github.com/codenameone/CodenameOne/issues/3686
-
The Holy Grail of Java Performance
We use ParparVM which we wrote. It compiles a subset of Java 8 (sort of) to native by translating the bytecode to C and passing that through XCode. The reason we took this path and not the path of "direct to native", is that it allows for future compatibility.
proposal
-
Does Go Have Subtyping?
The conclusion is pretty weird to me.
Go does rely on monomorphization for generics, just like C++ and Rust. The only difference is that this is an implementation detail, so Go can group multiple monomorphizations without worrying about anything else [1]. This form of hybrid monomorphization is being increasingly common, GHC does that and Rust is also trying to do so [2], so nothing special for Go here.
On the other hand, explaining variance as a lifted polymorphism is---while not incorrect per se---also weird in part because a lack of variance is at worst just an annoyance. You can always make an adopter to unify heterogeneous types. Rust calls it `Box`, Go happens to call it an interface type instead. Both languages even do not allow heterogeneous concrete (or runtime) types in a single slice! So variance has no use in both languages because no concrete types are eligible for variance anyway.
I think the conclusion got weird because the term "subtyping" is being misused. Subtyping, in the broadest sense, is just a non-trivial type relation. Many languages thus have a multiple notion of subtyping, often (almost) identical to each other but sometimes not. Go in particular has a lot of them, and even some relation like "T implements U" is a straightforward record subtyping. It is no surprise that the non-uniform value representation has the largest influence, and only monomorphization schemes and hetero-to-homogeneous adapters vary in this particular group.
[1] https://github.com/golang/proposal/blob/master/design/generi...
[2] https://rust-lang.github.io/compiler-team/working-groups/pol...
- Backward Compatibility, Go 1.21, and Go 2
-
Defining interfaces in C++ with ‘concepts’ (C++20)
https://github.com/golang/proposal/blob/master/design/generi...
-
Why Turborepo is migrating from Go to Rust – Vercel
Go Team wanted generics since the start. It was always a problem implementing them without severely hurting compile time and creating compilation bloat. Rust chose to ignore this problem, by relying on LLVM backend for optimizations and dead code elimination.
-
Are you a real programmer if you use VS Code? No Says OP in the byte sized drama
Hold up, did the members actually push this forward or was support just often memed about and suddenly this proposal was made: https://github.com/golang/proposal/blob/master/design/43651-type-parameters.md
-
Major standard library changes in Go 1.20
As far as I can tell, the consensus for generics was "it will happen, but we really want to get this right, and it's taking time."
I know some people did the knee-jerk attacks like "Go sucks, it should have had generics long ago" or "Go is fine, it doesn't need generics". I don't think we ever needed to take those attitudes seriously.
> Will error handling be overhauled or not?
Error handling is a thorny issue. It's the biggest complaint people have about Go, but I don't think that exceptions are obviously better, and the discriminated unions that power errors in Rust and some other languages are conspicuously absent from Go. So you end up with a bunch of different proposals for Go error handling that are either too radical or little more than syntactic sugar. The syntactic sugar proposals leave much to be desired. It looks like people are slowly grinding through these proposals until one is found with the right balance to it.
I honestly don't know what kind of changes to error handling would appear in Go 2 if/when it lands, and I think the only reasonable answer right now is "wait and find out". You can see a more reasonable proposal here:
https://github.com/golang/proposal/blob/master/design/go2dra...
Characterizing it as a "lack of vision" does not seem fair here--I started using Rust back in the days when boxed pointers had ~ on them, and it seemed like it took Rust a lot of iterations to get to the current design. Which is fine. I am also never quite sure what is going to get added to future versions of C#.
I am also not quite sure why Go gets so much hate on Hacker News--as far as I can tell, people have more or less given up on criticizing Java and C# (it's not like they've ossified), and C++ is enough of a dumpster fire that it seems gauche to point it out.
-
Go's Future v2 and Go's Versioning
There will almost certainly not be a Go 2 in that sense. There is a Go 2 transition doc which extensively discusses what "Go 2" means. The conclusion is
-
What's the status of the various "Go 2" proposals?
As it says on that page - those were not proposals. They were draft ideas to get feedback on. You can see the list of proposals in this repository: https://github.com/golang/proposal
-
An alternative memory limiter for Go based on GC tuning and request throttling
Approximately a year ago we faced with a necessity of limiting Go runtime memory consumption and started work on our own memory limiter. At the same time, Michael Knyszek published his well-known proposal. Now we have our own implementation quite similar to what has been released in 1.18, but there are two key differences:
- Shaving 40% off Google’s B-Tree Implementation with Go Generics
What are some alternatives?
Multi-OS Engine - Multi-OS Engine: Create iOS Apps in Java (or Kotlin ... etc.)
go - The Go programming language
Design Patterns - Design patterns implemented in Java
vscode-gremlins - Gremlins tracker for Visual Studio Code: reveals invisible whitespace and other annoying characters
J2ObjC - A Java to iOS Objective-C translation tool and runtime.
avendish - declarative polyamorous cross-system intermedia objects
sitemapgen4j - SitemapGen4j is a library to generate XML sitemaps in Java.
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
Maven Wrapper - The easiest way to integrate Maven into your project!
go-generic-optional - Implementation of Optionals in Go using Generics
Modern Java - A Guide to Java 8 - Modern Java - A Guide to Java 8
go_chainable - With generics, allowing chainable .Map(func(...)).Reduce(func(...)) syntax in go