chucke

9 ms·

31.
by chucke 2y ago
Claiming "plenty of bugs" without stating any, doesn't really open the thread for constructive discussion, and frankly sounds like unnecessary FUD. Claiming that the ruby community doesn't care about correctness is borde
32.
by chucke 2y ago
That's disingenuous. Python 3 was released around 2008, rails popularity was still rising. The community refused to upgrade for at least 10y, and several prominent libraries took as much to provide first grade python 3 support. Ruby 1.
33.
by chucke 2y ago
Mentioning 1.9 migration and ruby being slow? Python 2 to 3 was waaaaay worse and more negatively impactful, and equally slow (slower in most cases). Ruby never had US market penetrative as perl or python, which were basically invented in t
34.
by chucke 2y ago
Bear in mind that this article is old. Since then, ruby support a [handle_interrupt mechanism not far from the method described as working in java]( https://rubyapi.org/3.3/o/thread#method-c-handle_interrupt )
35.
by chucke 2y ago
How is the CONTINUATION frame issue handled? Max number of continuations per stream?
36.
by chucke 2y ago
It isn't a big win compared to just calling the method with it: meth(foo: 1, bar: 2) # even if multiline meth( foo: 1, bar: 2 ) while needlessly allocating an hash (kwargs optimize that).
37.
by chucke 2y ago
1. About Verbosity: that's not common nor idiomatic ruby. You'd much more often see a case statement there, and nowadays with pattern matching. It look like idiomatic python though... 2. About Long Expressions to Detect nil: rails
38.
by chucke 2y ago
!-suffixed being dangerous is a rails convention (throws exception). !-suffixed methods are a ruby convention for instance mutation. Calling mutation dangerous isn't a justification for your argument, as there are intrinsic benefits to
39.
by chucke 3y ago
For payments, not for billing, right? I'd be very surprised otherwise, considering how Stripe's offer for billing is quite inflexible and (at least 6 months ago) offering experimental features.
40.
by chucke 3y ago
That's quite the history lesson, thx for the info. I agree that H2 is defacto better than H1, and easier to implement when compared to H3. However, I'll call out the 2 biggest time sinks of the RFC: stream prioritisation and serve
41.
by chucke 3y ago
As much as the default behaviour is questionable, I don't fully agree with the assessment: this is in fact a curl documentation problem. As a multi-protocol lib, curl does not in fact implement all of them directly, instead relying on
42.
by chucke 3y ago
> I didn't mean as it's the same thing, I meant there's significant overlap across the ecosystem for both. The most obvious example is numpy, and the role of narray as an almost native type. > According to the 2023 Stac
43.
by chucke 3y ago
Most other languages don't have knifes at all. What do you call the interface{} madness in go?
44.
by chucke 3y ago
Yes, it is only machine learning. Trying to separate it from the scientific community is creating a wall that does not exist. Besides, barely anyone uses python for 2d games or microcontrollers (out of hobbyist programs, and ruby also has a
45.
by chucke 3y ago
> OIDC solves problems for OAuth2 like "every Identity Provider has different endpoints" with OpenID Connect Discovery Not really: https://www.rfc-editor.org/rfc/rfc8414.html
46.
by chucke 3y ago
And security (basic auth is as good as sending clear text passwords).
47.
by chucke 3y ago
Metasploit? Logstash? Docker-sync? Vagrant? Jekyll?
48.
by chucke 3y ago
> If you rewrite it anyway, might as well use something else than ruby. You just said the company is a rails shop, why would you force a new language on everyone who already invested in understanding ruby?
49.
by chucke 3y ago
The getaddrinfo interface does not expose the fd so you can monitor for readiness. Several languages have the same problem with it, some with similar solutions (go outsources getaddrinfo calls to a thread pool)
50.
by chucke 3y ago
Pry and byebug paved the way in a lot of ways for this work, but they break in fundamental ways across a range of use cases, such as multithreading, multifiber, or quirk around exception handling. While these are all fixable, so we're
51.
by chucke 3y ago
You're spot on. You can see its influence in a lot of tooling coming after, such as several package managers (from yarn to cargo), java collections syntax, go structural typing, python's gunicorn, JVMs invokedynamic (introduced fo
52.
by chucke 3y ago
I agree, with the implicit "build it in-house with OIDC certified 3rd party dependencies ". The foundation already goes a long way towards providing conformance suites and several certificates. I don't understand how we came
53.
by chucke 3y ago
Skip tests. Thank you for coming to my Ted talk.
54.
by chucke 3y ago
It sounds like programming is a "means to an end" and you don't cate that much about the plumbing as you do about the outcome, so you use python out of convenience and not out of taste? If that's so, fine, but you don&#x
55.
by chucke 3y ago
And I never heard of TypeORM until now, which means that it's not boring tech in my eyes. I find it hard to classify anything in the node world as boring, considering the infamous churn rate. Popular yes, boring no.
56.
by chucke 3y ago
SQS limits you further in other ways. For instance, scheduled tasks are capped to 15m (delaySconds knob), so you'll be stuck when implementing the "cancel account if not verified in 7 days" workflow. You'll either reenqu
57.
by chucke 3y ago
You're implying that those languages made actual building products easier. I think we know by now they didn't. Go is a language which preaches building your boilerplate than reusing it. Produces very little of the economies of sca
58.
by chucke 3y ago
Evan Phoenix is saying it for even longer, and created rubinius as a means to prove it :) (it has since been abandoned, but Chris's truffleruby ported rubinius core and stdlib implementations, so it's great that they've all b
59.
by chucke 3y ago
Great point. Not just writing ruby, but writing more performant ruby. I found that we several "here's how to implemented this GoF pattern in ruby" to "thank" for a lot of the unoptimized code we see around.
60.
by chucke 3y ago
I'd assume that the benchmark is showcasing the gains of the async model, more than making a point that native python is faster than C. The issue is ultimately: how much of the functionality available through libpq is not yet backporte

More ›