Posted: Tue Jul 22, 2025 2:49 pmPosted: Thu Jul 24, 2025 10:14 ampricerc wrote:I've noticed that our invoices from Jiwa over the past several months appear to be generated from a Jiwa 8 instance, complete with pretty flag for the currency.
How far away is it from being suitable for Jiwa partners to start "dogfooding" for internal use ?
Posted: Fri Jul 25, 2025 9:28 am
Posted: Fri Jul 25, 2025 1:03 pmpricerc wrote:Thanks Mike.
We're not currently using Jiwa for "production", so existing data isn't a problem.
We do quite a lot of trans-tasman business, so we decided on holding out for the multi-currency support.
Posted: Mon Jul 28, 2025 7:10 amPosted: Wed Jul 30, 2025 6:47 pmpricerc wrote:At some point I'll want to try upgrading customer databases to assess the impacts on our library of plugins.
Posted: Thu Aug 07, 2025 5:18 pm
Posted: Thu Aug 07, 2025 7:10 pmpricerc wrote:the two first entries brought a wry smile to my face.
JiwaGrid.GridText
CustomSettingValues.ItemFromSettingName
One that breaks VB code and one that breaks C# code.
So everyone can be equally offended
Posted: Mon Aug 11, 2025 10:00 amMike.Sheen wrote:pricerc wrote:the two first entries brought a wry smile to my face.
JiwaGrid.GridText
CustomSettingValues.ItemFromSettingName
One that breaks VB code and one that breaks C# code.
So everyone can be equally offended
Oh, I made sure some people will be more offended than others - Plugin Maintenance now has a button to convert VB.NET plugins to C#, but we don't have one going the other way.
Posted: Mon Aug 11, 2025 11:21 ampricerc wrote:lol.
As much as I like VB, I don't blame you.
Unless I'm doing extensive XML manipulation, which VB's XML literals make easy to read, I generally choose C# over VB for new projects.
C# - VB
In most cases, if you aren't absolutely sure it's right for your situation, I wouldn't recommend moving serious production code from C# to VB en masse.
The language is a second class citizen with fewer features, tools and developers. It also has a whole collection of subtle quirks which can hide issues and make it very hard to write reliable, maintainable, performant code
Surveys show it's one of the most 'dreaded' languages.
Because of the above, there has been less demand for conversion in this direction and hence the conversion quality is worse (e.g. Recent c# features aren't well supported)