I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I'd love to see how you got Sorbet to work with Rails. I just tried and it didn't pick up any of the columns on the models, so I had 1000s of errors (method not found when calling model columns). I couldn't find any documentation or any quick way to fix.
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
up until yesterday the sorbet-rails only supported Rails 5.2 -- but 0.2 release also supports 5.1 .. if you were having issues using it, i'd recommend bumping the version and tryin again
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I feel the same as I feel about adding static typing to other high level dynamic languages (see mypy for Python for example) that weren't designed with static typing in the first place: meh.
I'm not for it, nor against it.
In a "philosophical" sense one of the main choices a developer has when picking a language is if they want static or dynamic typing.
Typing annotation for dynamically typed languages feels both a patch and a useful addition, hence my meh.
I agree with @6temeshere when he says that mindlessly adding types to bad code base does not improve such code. It makes the tool happy though, but that's another argument which is more about code quality and software design than typing.
Once a jobbing developer I have since moved into Management. I continue with a couple of hobby projects to ensure I don't go mad. I focus on iOS/Swift and ROR.
Too soon to have an opinion? :D
PR is already up LOL. I converted the entire ruby code base of DEV to Sorbet. 😜
I'd love to see how you got Sorbet to work with Rails. I just tried and it didn't pick up any of the columns on the models, so I had 1000s of errors (method not found when calling model columns). I couldn't find any documentation or any quick way to fix.
I was kidding about the PR. 😉 I'm still pretty new to Ruby.
There is a gem which create RBI files for ActiveRecord and URL helpers: github.com/chanzuckerberg/sorbet-r...
up until yesterday the sorbet-rails only supported Rails 5.2 -- but 0.2 release also supports 5.1 .. if you were having issues using it, i'd recommend bumping the version and tryin again
LOL
Il reword it to how to ruby devs feel about types in their code. 😎
I feel the same as I feel about adding static typing to other high level dynamic languages (see mypy for Python for example) that weren't designed with static typing in the first place: meh.
I'm not for it, nor against it.
In a "philosophical" sense one of the main choices a developer has when picking a language is if they want static or dynamic typing.
Typing annotation for dynamically typed languages feels both a patch and a useful addition, hence my meh.
I agree with @6temes here when he says that mindlessly adding types to bad code base does not improve such code. It makes the tool happy though, but that's another argument which is more about code quality and software design than typing.
:thumbs
☝ This.
Being the first to use some technology very rarely will give a competitive advantage to your company.
But, I am happy that people are trying static types in Ruby, so the rest can learn if it's worth it or not. ;)