@MichaelArnaldi@YuvarajMadineni I wasn't trying to be negative at all, I was panicked so I'm sorry. yes we can port all the code over ourselves. that's probably what we'd do instead of dropping effect. but still I'd rather not see Service die
@MichaelArnaldi@YuvarajMadineni for us that means dropping effect I think. which will be real hard after the next two refactors (schema & http) go in. so basically actually we have to decide now.
I've already been told once this month by the CEO that I made a terrible choice in choosing Scala 15 years ago
@MichaelArnaldi@YuvarajMadineni I mean... our server cleanly uses hundreds of Services. accessors are used heavily in test code. It was already a pretty big deal to get us to adopt effect, if I'm coming in and saying "sorry here's another 2k file MR because I built on a seemingly solid surface that wasn't..."
@unclebobmartin Agree. First you get a thrill, but then you realize your job is now conversing with a super powerful toddler genius who needs babysitting and constant repetition. You get tired of โtalkingโ. Not everybody is gonna like that job.
@MichaelArnaldi omg please tell me this is effect-native oauth and I get to delete my home grown implementation? and that it works seamlessly with effect-platform's http builder? ๐
@kitlangton we seem to be following similar tech-life arcs - have you also been nix-pilled? anyway here's my nvim setup for effect https://t.co/mhqn3TWqhf
@gitlab who can I talk to about recovering my https://t.co/nA1teO3SpR account? I "successfully" did the automated recovery and am still denied login with new pw. not sure where to go if I can't sign in.
@kitlangton@EffectTS_ i guess that's not the point of this, but I got our entire backend ported to effect and I've only had time to do one teaching session and I didn't really cover the layers at all, just told them to read the docs. if I could send some team leads to this....
@MichaelArnaldi@WickyNilliams@CampuzanoJoe@kitlangton@SubtleGradient โ๐ปcan confirm, just got done with that final cleanup on our codebase. ~550 changed files, 2-300 effect services. still a ways to go, though, until we're able to switch to -schema and then (finally!) -http. but the team is already excited