Ultimately, the goal is for Tapioca to replace all `srb rbi` tooling and `sorbet-rails`. Right now, we exclusively use Tapioca for gem RBIs and we don't use any `srb rbi` tooling at Shopify. That works perfectly fine, but you don't get any `sorbet-typed` RBIs, which, right now is not a concern for us.
The DSL generators are not 100% complete to fully replace `sorbet-rails` right now, but we are preparing a 1.0 release of the gem that should be able to do that.
One of the challenges sorbet-rails faced [1] was with the usage of method_missing in certain places. The one that bit me was Rails automatically piping a class method from Model into the Model's CollectionProxy, effectively making class methods into scopes. We use this pretty extensively at work for complex scopes, so this is one of the reasons I've not been able to get complete buy-in for sorbet. Is that better in tapioca?
(Also: Thank you for sorbet! It's the biggest reason I continue to use Ruby for my personal projects.)
I am afraid that is a shared concern for what Tapioca is doing as well. There are ways of mitigating that concern, by, for example, lifting all static methods on a model to be methods on the collection proxy in RBI files. This is certainly doable, and we are less interested in the correct signatures for such methods than having the method definitions in place, in the first place. On the other hand, we also have some Sorbet feature ideas that we want to experiment with where we might be able to annotate that a certain type delegates all missing methods to another type, for example.
This is indeed a problem in our codebase as well, and so far our team has been suggesting that people add shim (i.e. manual) RBI definitions for the methods that they find are missing from the types they've expected them on. This is a good stop-gap measure to solve a problem that is not very common with an easy solution to implement.
> but you don't get any `sorbet-typed` RBIs, which, right now is not a concern for us.
Ahh ok! I think this might have been a bit I missed, cause I was commonly trying to do both which likely caused issues for me.
> The DSL generators are not 100% complete to fully replace `sorbet-rails` right now, but we are preparing a 1.0 release of the gem that should be able to do that.
I've had the pleasure of reaching out to Dependabot a few times when I've had issues or problems and you guys have always been super responsive and quick to fix any bugs!
Congrats again on joining Github! And excited to see whats next for Dependabot!
I am in the exact same boat as you are, and would love some feedback as well! I have been considering Kubernetes so that I can allow horizontal scaling, but haven't done it yet.
For my use case I am VERY well aware that Kubernetes is overkill, but I don't see a great middle ground between Dokku where I am now, and Kubernetes.
I've started experimenting with Swarm myself but I know one guy who has a histamine reaction every time I mention it. I haven't gotten (or really tried to get) a straight answer out of him about why it's a bad thing.
If you have a countable number of instances of a couple dozen services and one or two "lots of instances" services it seems like it should suffice just fine. And really, my brief sojourn into Kubernetes left me feeling like I bumped into road blocks for anything more complicated than that. Especially with sidecars, or if your tool chain uses multiprocessing instead of threading (Rails, Node, Python?, etc) to deal with concurrency.
This is my first time hearing about `SetApp` but it sounds like an interesting concept.
How do you feel about it? How many apps from it so you use often/daily?
Worth the $10 a month?
I had a trial and found the selection for developers wasn't worth the $10.
There are a few little utilities, like the Regex tester, that are definitely neat and well made, but given the once a month I actually need that functionality, I'll just use a crappy web app for it.
Most of the software I found to be the 3rd best in its category (or worse), for example, It doesn't have OmniFocus or Things, it has a bunch of to-do list apps I've never heard of that all have poor design and UX. Besides that there's a lot of the soft of system enhancer software that I thought made my computer go faster when I was younger but that I've now realised is mostly pointless.
For me to resubscribe to SetApp, I'd want to see best-in-class apps like Things, OmniFocus, SublimeText (or even BBEdit, I'm not a fan, but it's a good Mac app), RapidWeaver (again, not for me, but good for many), Transmit, Coda, Delicious Library, etc. I'd probably pay more than $10 for that sort of selection.
Oh apologies. I'd expect that's not a like-for-like comparison. Paw is a paid app, and then has team-sync subscriptions, the former is in SetApp, the latter is not.
‣ HazeOver (dims any window without focus by a simply-configurable amount)
‣ Mosaic (window position/size management), TextSoap (quick text-cleansing recipes)
‣ Timing (track time spent in all apps/paths for client billing)
‣ Marked (Markdown editor with live preview)
‣ Paw
I'm gonna test it out on a much smaller scale, and slightly different setup. I just grabbed 3 images from a rarely used server hosted with DigitalOcean, with a custom domain, and put them in a new Google Sheet using the same =image(url) technique the author mentioned. The access logs show Feedfetcher-Google; (+http://www.google.com/feedfetcher.html)" grabbed each of the images once immediately which makes sense. I'll check back in a few hours and see if there are any other requests.
Edit: I also grabbed 3 different images and put them in a separate sheet. I'm gonna leave one open on my desktop and not open the other and see if that changes the requests.
One Hour Later: I think that Google is probably grabbing images On-Demand now. There are 12 total requests on my 6 images. The first 6 are sporadic, which correspond to when I added the images to the sheets. Then the next 3 are in the same second, which come from opening the sheet on my desktop. And the last 3 also came in the same second, again from opening that sheet on my desktop. I kept one open and closed the other and neither have had the images requested since.
I'm pretty sure they fixed it. I don't remember whether that was already in the original discussion of this story or a little bit later, but I remember the comment that one can't use it anymore as an attack tool since the feedfetcher behaviour changed.
Regarding this, does anyone have tips on how best to do curses layouts that support different window sizes? I'm working on a procedurally generated console game in my free time, using Python + curses, and this is an issue I run into as well.
I've been considering taking some time to try to write some sort of "fluid" or "dynamic" layout framework for curses (i.e. specify percents for width / height, and have it automatically expand). Seems like a giant pain though...
https://www.cnbc.com/2019/01/08/fintech-start-up-plaid-to-bu...