Maybe I'm just used to VS, but I think it's realllllyyyy ugly to have it in a giant block in the bottom. VS's red-underline-mouse-over error method is much cleaner, what do you think?
Maybe I'm just used to VS, but I think it's realllllyyyy ugly to have it in a giant block in the bottom. VS's red-underline-mouse-over error method is much cleaner, what do you think?
I don't use Ruby myself, but I'm really optimistic about Stripe handling this task. Their documentation alone for their API is amazing, examples being side-by-side with the documentation itself on...
I don't use Ruby myself, but I'm really optimistic about Stripe handling this task. Their documentation alone for their API is amazing, examples being side-by-side with the documentation itself on the same page and having examples in multiple programming languages, and these examples are often incredibly thorough. I set up Stripe transactions recently with very little effort just because they made it such a no-brainer to get everything up and running. I imagine that they will be putting the same or a similar level of care in making the type checker as easy as possible to set up and work with.
Maybe I'm just used to VS, but I think it's realllllyyyy ugly to have it in a giant block in the bottom. VS's red-underline-mouse-over error method is much cleaner, what do you think?
They can? Very nice!
I don't use Ruby myself, but I'm really optimistic about Stripe handling this task. Their documentation alone for their API is amazing, examples being side-by-side with the documentation itself on the same page and having examples in multiple programming languages, and these examples are often incredibly thorough. I set up Stripe transactions recently with very little effort just because they made it such a no-brainer to get everything up and running. I imagine that they will be putting the same or a similar level of care in making the type checker as easy as possible to set up and work with.