I replaced it with a tiny app that I built for myself, that just has the features of Pocket that I was using.
Readit Newsnithinbekal commented on Ask HN: What Pocket alternatives did you move to? · Posted by u/ahmedfromtunis
nithinbekal commented on Abstract Methods and NotImplementedError in Ruby nithinbekal.com/posts/abs... · Posted by u/nithinbekal
`UndefinedMethodError` perhaps? that way we can restore the distinction between method declaration (which assigns a name, within some namespace) and method definition/implementation which gives the function its ability.
Wouldn't that be too similar to NoMethodError? I recently came across the idiom in Smalltalk, where you would call subclassResponsibility:
someMethod:
self subclassResponsibility
Do you think Ruby could change something so fundamental as dynamic => static typing and still retain its beauty?
The only static typing solution I've seen for Ruby is Sorbet, and it's... not beautiful.
https://sorbet.org/docs/rbs-support