Java Card applet development: OO or C-style?

Recently, the 2.0 EDEP of the PBoC was reconstructed, and dozens of details were changed according to customer's needs.

The object-oriented understanding is somewhat deepened during the change process.

For example, to avoid two class interdependencies, you can use a interface center as a decoupling.

Due to the limited space in the card, resource shortage, in the design should be careful to avoid the inheritance hierarchy too deep.

Personal feelings, due to limited resources, are unlikely to be used in a large number of design patterns.

There are only two design patterns in the Javacard API: Singleton mode, builder mode.

The two models are also used to conserve resources and to block the underlying hardware details for applet developers.

Shanghai has a chip company, has tried to develop 100%java card chip, and finally because the cost is too high to give up.

Some friends still recommend the C style to develop Java card applets, but I think I can at least make full use of the try Catch finally this C does not have Java syntax, so that the code logic can become clearer.

There are also friends who recommend that you do not divide multiple package, otherwise, when applied to the TSM platform, will be bored to death.

Java Card applet development: OO or C-style?