> If you downgraded to 5.x because v7 felt too hands-off, this is a good time to check back
Well, I checked and downgraded back. My team will continue working with the FULLY transparent and controllable Kilo workflow. v7 is still raw. Much better than a month ago, yes, at least it can be played with without the WTF moments. The direction looks right - restoration of the killed features, though that sounds crazy for a product that got 1M+ installs.
What's the stat, guys? How many independent devs and companies adopted v7 to their d2d processes?
Speaking of the upgrading: the history loss is a stopper too. Not a critical one, but still. Create some export-import or an archiving tool, that will decrease some of v5->v7 friction.
> If you downgraded to 5.x because v7 felt too hands-off, this is a good time to check back
Well, I checked and downgraded back. My team will continue working with the FULLY transparent and controllable Kilo workflow. v7 is still raw. Much better than a month ago, yes, at least it can be played with without the WTF moments. The direction looks right - restoration of the killed features, though that sounds crazy for a product that got 1M+ installs.
What's the stat, guys? How many independent devs and companies adopted v7 to their d2d processes?
Speaking of the upgrading: the history loss is a stopper too. Not a critical one, but still. Create some export-import or an archiving tool, that will decrease some of v5->v7 friction.