brain freeze. SS1 used Rhino ... SS2.0 uses ??? a...
# suitescript
d
brain freeze. SS1 used Rhino ... SS2.0 uses ??? and SS2.1 uses ??? (I assume S2.x use the same engine)
s
GraalVM
e
SS2.0 is also Rhino
SS2.1 is GraalVM 19?
s
that's right Eric, I forgot 2.0 is still Rhino 🙂
e
Much sadness there 😞
d
Thanks gents. Trying to polish off a document for client to migrate a SS1 SuiteApp to SS2. Filling in the technical pros/cons.
What ever happened to 'trust your dev partner'?
e
Too many bad dev partners.
d
That statement sums it up @erictgrubaugh
s
I'd be curious to see your pros/cons list. My list is weird because it includes NFT-SS2 which is a big leap (forward) over NFT-SS1 in many ways.
d
Well, its being directed to some C-levels, so I have to 'dumb it down a shade'
I'm stressing things like performance, segmentation of code, new API modules, robust script types (M/R).
This is a wildly successful SuiteApp, so management is like .. "why would I change anything?" [I get that stance too]
s
I haven't seen any giant like-for-like performance differences between SS1 and 2
another thought is SS2.x should have reduced maintenance time/cost do to the module system and more consistency of APIs (kinda part of your 'segmentation of code' point)
d
Ya. They just don't see their own tech-debt (@erictgrubaugh know, he review it for us)
e
I assumed that's the app we were referring to 🙂
🤔 1
👍 1
d
One major thing I also need to balance is the fact that the bundle has been out in the wild for 8+ yrs and is approaching 3000 install base. We can't start fresh ... we have to navigate within that bundle id.
s
does NS have a good story for how to migrate from bundle to SDF for SuiteApps?
d
And migrate 3000 existing users ... that's a hard no
s
Or are you not thinking of SDF here, only moving the code from SS1 to SS2 (keeping status quo for bundles)?
d
Yes, sorry ... phase one is a straight SS1 -> SS2 move
Its in the right direction
s
it's exactly that sort of situation that would make me expect NS to have a very good story for migrating from bundles to SDF
d
And they don't. We did this with a very new SDN partner. NetSuite said 'Suck it up'. Uninstall the first bundle and install the new shiny SDF SuiteApp
😮 1
FYI, I've launched a few using the new SuiteApp Control Center. It is night and day! So nice to use
s
that's good to hear. Hopefully next time i'm working on a SuiteApp it'll be in that shiny new world.
s
Yeah the bundle to sdf transition could really use some love for this exact scenario... essentially punishing the bundles that have been around for a long time
d
It's a real showstopper for those successful bundles. They can'y improve themselves and evolve with NetSuite. It's really confusing how that was missed.
p
I dont think it was missed, but i suspect its not a trivial task. It would be good for NetSuite Dev to provide an update on the status of bundle migration. As you say its not viable to uninstall the suitebundle and install the shiny new SDF suiteapp on a large and established customer base!