bambanxx has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
bambanxx has joined #ruby
bambanxx has quit [Client Quit]
dalan0382283 has quit [Ping timeout: 255 seconds]
dalan03822833 has joined #ruby
hightower2 has quit [Read error: Connection reset by peer]
hightower2 has joined #ruby
dalan03822833 has quit [Quit: dalan03822833]
dalan03822833 has joined #ruby
dalan03822833 has quit [Client Quit]
dalan03822833 has joined #ruby
vigumnov has joined #ruby
victori has quit [Ping timeout: 264 seconds]
Linux_Kerio has joined #ruby
fercell has joined #ruby
schne1der has joined #ruby
schne1der has quit [Quit: schne1der]
brokkoli_origin has quit [Ping timeout: 258 seconds]
brokkoli_origin has joined #ruby
_ht has joined #ruby
Vonter has quit [Ping timeout: 240 seconds]
Vonter has joined #ruby
szkl has joined #ruby
grenierm has joined #ruby
razetime has joined #ruby
Seldon898 has joined #ruby
<Seldon898>
Hi, I have to update connectivity_plus to 5.0.1 due to a bug, but my current version of amplify_api (1.5.0) depends on connectivity_plus 4.0.2. - any ideas what to do now?
Linux_Kerio has quit [Ping timeout: 255 seconds]
<Seldon898>
further to the issue, using default dependencies in my project, I get the following when I try to launch the App on iPhone: [VERBOSE-2:FlutterDarwinContextMetalImpeller.mm(37)] Using the Impeller rendering backend.
<Seldon898>
the suggested fix is to remove, or upgrade connectivity_plus - which is not an explicit dependency in my project, it's needed by amplify_api
<Seldon898>
can I explicitly omit it?
Vonter has quit [Ping timeout: 252 seconds]
otisolsen70 has joined #ruby
razetime has quit [Remote host closed the connection]
razetime has quit [Quit: Go back to your cringe 9 to 5. I'll be gaming.]
brokkoli_origin has quit [Remote host closed the connection]
brokkoli_origin has joined #ruby
CO2 has quit [Quit: WeeChat 4.1.0]
constxqt has joined #ruby
<constxqt>
what do u guys say to haters and losers who think dynamic typing is bad
<constxqt>
u would think pointing to the plethora of fortune 500 companies who make extensive use of dynamic languages would be enough to shut them up
graywolf has quit [Quit: WeeChat 4.0.4]
CO2 has joined #ruby
devmes has quit [Ping timeout: 272 seconds]
_ht has joined #ruby
<aesthetikx>
its tough, a never ending battle
<aesthetikx>
sometimes I think that AI might change things a bit, for better or worse -- the AI doesn't care if there are types or not, it would be smart enough to statically check everything anyway
<aesthetikx>
maybe AI will destroy the industry and then the only reason people will write code will be for enjoyment again, and then maybe at that point there will be no question that its more fun to write ruby than rust
otisolsen70 has quit [Quit: Leaving]
CrazyEddy has left #ruby [#ruby]
CrazyEddy has joined #ruby
CO2 has quit [Quit: WeeChat 4.1.1]
polishdub has quit [Ping timeout: 255 seconds]
howdoi has joined #ruby
Vonter has quit [Ping timeout: 258 seconds]
Vonter has joined #ruby
reset has quit [Quit: reset]
caedmon has joined #ruby
CO2 has joined #ruby
Aminda has quit [Ping timeout: 256 seconds]
caedmon has quit [Ping timeout: 248 seconds]
Aminda has joined #ruby
justache is now known as justHaunted
bambanxx has joined #ruby
entropie has quit [Ping timeout: 255 seconds]
entropie has joined #ruby
<adam12>
A lot of the time when someone says something about dynamic typing in Ruby, I see a lot of bits about NoMethodError. Which I guess makes sense if you are using bits like `Enumerable.find` and the like. It would be nice to solve this a bit easier (I don't dare say a monad but perhaps something similar to one)
<adam12>
And a lot of newer dev's like the IDE/intellisense experience. If you grew up in vim/Textmate/whatever, as a lot of longer Ruby devs did, then you never became reliant on Intellisense.
<adam12>
When people talk about large refactors only being possible with static types, I wonder what kinds of things they have that are so cross-cutting that they can only do it reliably with types.
<adam12>
I might have a few "god" classes in my project, but most of the time it's an object talking to another object. The interface is reasonably well known at that point.
<weaksauc_>
you can't win the debate
<weaksauc_>
people love typescript until it gets int the way of moving faster than they can with it
<adam12>
Exactly. I know people flip-flop on this.
<adam12>
Ruby 100% needs way better intellisense if it wants to stay current, because that's the "new" developer that the world has. Not the people cutting themselves on a C64 writing Basic. They're not really used to "pain".
<adam12>
I think Justin Searls had a good article that touched on this; the 10x developer.
<adam12>
I suggest teams write YARD tags when I work with them, not that I care a lot about the types, but it forces people to give some thought of their API. If you're just passing around unstructured Hash's everywhere, of course it's painful to refactor.
<adam12>
I'm in a ranty mood apparently.
<weaksauc_>
yeah moving away from hashes is a good thing but it requires devs to think about the structure of the app and it locks you in
<adam12>
I think Data.define was a good step forward. Nicer, "real" objects.
<weaksauc_>
i do remember working on my first rails app and the views all were just using json basically and instead of morphing that into a proper container of things i was stuck with nils and errors and all that fun
<adam12>
Yep. Exactly.
<weaksauc_>
after encapsulating it everything was so much saner and more sensible
<weaksauc_>
it was actually json being used by that rails app for a phone app and the phone app was the one that didn't encapsulate the data well
<weaksauc_>
s/used/sent
<weaksauc_>
but it still is the same thing
<weaksauc_>
i do think everything coalescing behind ruby-lsp from shopify is probably a good thing
<weaksauc_>
wrt the intellisense
user23 has quit [Remote host closed the connection]