My tone doesn't make me wrong

Hi,

I wrote a blog post about the ordeal I went through from 2012 to 2014
to fix a bug in DateTime.strptime:

It's a good example of how a meek and polite tone doesn't always work,
sometimes you have to be bold and combative if you want results.

Cheers.

···

--
Felipe Contreras

Wonderful! Thanks for posting your experience. I think you were assertive
in the right way!

saji

···

On Sun, Aug 21, 2022 at 4:16 PM Felipe Contreras <felipe.contreras@gmail.com> wrote:

Hi,

I wrote a blog post about the ordeal I went through from 2012 to 2014
to fix a bug in DateTime.strptime:

My tone doesn’t make me wrong, or how I convinced the Ruby project to fix an inconsistency – Felipe Contreras

It's a good example of how a meek and polite tone doesn't always work,
sometimes you have to be bold and combative if you want results.

Cheers.

--
Felipe Contreras

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk&gt;

--

Yikes. Being abusive towards a maintainer ain't it mate. This is sold grade
A "alpha male" toxicity and you really need to take a step back and reflect
on it.

···

On Sun, Aug 21, 2022, 12:16 AM Felipe Contreras <felipe.contreras@gmail.com> wrote:

Hi,

I wrote a blog post about the ordeal I went through from 2012 to 2014
to fix a bug in DateTime.strptime:

My tone doesn’t make me wrong, or how I convinced the Ruby project to fix an inconsistency – Felipe Contreras

It's a good example of how a meek and polite tone doesn't always work,
sometimes you have to be bold and combative if you want results.

Cheers.

--
Felipe Contreras

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk&gt;

Hello,

   Wow. Thanks for the write-up and lesson why tolerance is so
important (guess what with all your authority, yes, you might be
wrong!).

    Your patience is incredible in this ordeal. Holy cow!

   Anyways, sad to see my good old friends that make my live in
rubyland miserable to this day:

   Eric Hodel - for sure outstanding contributor to ruby in the past
- but somehow lost his mind not sure why and when and become a justice
warrior

  and Brandon Weaver - not sure why he has a free license to insult
all critics in rubyland
and call for bans in the name of making rubyland a "safe space"
according to his utopia

  Anyways, for the record here's my archived series of the CSV
library / gem write-up
    titled "Why the CSV standard library is broken (and how to fix it)" [1]

As an update now some years later (I have long given up) - the good
news - the csv library / gem is no longer an orphan and lovely updated
& patched by Sutou Kouhei (kou)
- you are a hero! the "parser" that never was is now fixed and - yes
- is a real parser.

   However, the csv model itself is still broken - it should return an
array simply or an hash and NOT it's own custom table and such and so
on.

   Anways, the saga continued with my pixel art libraries / gem that
are funnily off-blockchain and
a parody of crypto art - but that of course gets lost by over eager
"save spacers" that want me banned
  for promoting crypto or such. Anyways, see the planetruby archive
[2] for background.

  To conclude - allow me to call for more tolerance again and - yes
- dare to crack some jokes even if there a danger that some take it
serious. Be a mensch. (that 's my aspiration and code of conduct
policy -see the Choose A Conduct org [3] to get your own copy.

  Cheers. Prost.

[1] csvreader/docs at master · rubycocos/csvreader · GitHub
[2] All About Programming Ruby
[3] Choose-A-Conduct · GitHub

Hi,

Thx for sharing your story.

Datetime library has been deprecated in ruby 3, without a clear
replacement. Did the aftermath of this story play a role, directly or not,
in this decision?

escreveu:

···

A domingo, 21/08/2022, 08:16, Felipe Contreras <felipe.contreras@gmail.com>

Hi,

I wrote a blog post about the ordeal I went through from 2012 to 2014
to fix a bug in DateTime.strptime:

My tone doesn’t make me wrong, or how I convinced the Ruby project to fix an inconsistency – Felipe Contreras

It's a good example of how a meek and polite tone doesn't always work,
sometimes you have to be bold and combative if you want results.

Cheers.

--
Felipe Contreras

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk&gt;

Hi,

Yikes. Being abusive towards a maintainer ain't it mate. This is sold grade A "alpha male" toxicity and you really need to take a step back and reflect on it.

Did you see the part of the story where being polite didn't work for years?

And the reason I wrote the story is that it's happening again, except
this time it's not a minor bug, but a huge issue affecting tons of
people. I am being ignored again, so I'm being forced to blow the horn
on the issue, and the behavior of maintainers.

Also, I wouldn't call taking the ego of a person down a notch or two
"being abusive".

Cheers.

···

On Sun, Aug 21, 2022 at 11:07 AM Brandon Weaver <keystonelemur@gmail.com> wrote:

--
Felipe Contreras

I *believe* that `Time` in Ruby 3 has been sufficiently enhanced to mostly
replace `DateTime`. I’ve been doing some work which previously relied on
`DateTime`, and everything that I was using it for is now present in `Time`
(although you *must* `require 'time'` in the way that you would have
required `datetime` previously).

-a

···

On Sun, Aug 21, 2022 at 2:44 PM Tiago Cardoso <honeyryderchuck@gmail.com> wrote:

Datetime library has been deprecated in ruby 3, without a clear
replacement. Did the aftermath of this story play a role, directly or not,
in this decision?

--
Austin Ziegler • halostatue@gmail.com • austin@halostatue.ca
http://www.halostatue.ca/http://twitter.com/halostatue

The ruby documentation says <https://ruby-doc.org/stdlib/libdoc/date/rdoc/DateTime.html&gt;:

DateTime <https://ruby-doc.org/stdlib-3.0.2/libdoc/date/rdoc/DateTime.html&gt; class is considered deprecated. Use Time <https://ruby-doc.org/stdlib-3.0.2/libdoc/date/rdoc/Time.html&gt; class.

So no, I think the the replacement is very clear.
However, I agree that the documentation on why `DateTime` is deprecated and how to migrate code to use `Time` instead could be more articulate.

For example, if you have a specific use-case for `DateTime` that (you believe) cannot be resolved by the `Time` class, then this is definitely worth raising.

···

On 21 Aug 2022, at 19:43, Tiago Cardoso <honeyryderchuck@gmail.com> wrote:

Datetime library has been deprecated in ruby 3, without a clear replacement.

The (deprecated) datetime documentation contains this section:

.

Can you perform the same type of calculations using Time?

Tom Lord <lord.thom@gmail.com> escreveu no dia segunda, 22/08/2022 à(s)
09:31:

···

The ruby documentation says
<https://ruby-doc.org/stdlib/libdoc/date/rdoc/DateTime.html&gt;:

DateTime
<https://ruby-doc.org/stdlib-3.0.2/libdoc/date/rdoc/DateTime.html&gt; class
is considered deprecated. Use Time
<https://ruby-doc.org/stdlib-3.0.2/libdoc/date/rdoc/Time.html&gt; class.

So no, I think the the replacement is very clear.
However, I agree that the documentation on *why* `DateTime` is deprecated
and *how *to migrate code to use `Time` instead could be more articulate.

For example, if you have a *specific use-case* for `DateTime` that (you
believe) cannot be resolved by the `Time` class, then this is definitely
worth raising.

On 21 Aug 2022, at 19:43, Tiago Cardoso <honeyryderchuck@gmail.com> wrote:

Datetime library has been deprecated in ruby 3, without a clear
replacement.

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk&gt;

The same calculations can be performed with `Date`, instead of `DateTime`.
You lose time of day from that, at least in part, but people were using
`DateTime` for things that do not require the distinction between calendars
in that changed in England in 1752 or so.

I absolutely believe that Ruby’s time / datetime handling needs
improvement, but it should be OK for most purposes unless one is doing
astronomical calculations BCE.

···

On Mon, Aug 22, 2022 at 4:35 AM Tiago Cardoso <honeyryderchuck@gmail.com> wrote:

The (deprecated) datetime documentation contains this section:
Class: DateTime (Ruby 3.1.2)
.

Can you perform the same type of calculations using Time?

Tom Lord <lord.thom@gmail.com> escreveu no dia segunda, 22/08/2022 à(s)
09:31:

The ruby documentation says
<https://ruby-doc.org/stdlib/libdoc/date/rdoc/DateTime.html&gt;:

DateTime
<https://ruby-doc.org/stdlib-3.0.2/libdoc/date/rdoc/DateTime.html&gt; class
is considered deprecated. Use Time
<https://ruby-doc.org/stdlib-3.0.2/libdoc/date/rdoc/Time.html&gt; class.

So no, I think the the replacement is very clear.
However, I agree that the documentation on *why* `DateTime` is
deprecated and *how *to migrate code to use `Time` instead could be more
articulate.

For example, if you have a *specific use-case* for `DateTime` that (you
believe) cannot be resolved by the `Time` class, then this is definitely
worth raising.

On 21 Aug 2022, at 19:43, Tiago Cardoso <honeyryderchuck@gmail.com> >> wrote:

Datetime library has been deprecated in ruby 3, without a clear
replacement.

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk&gt;

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk&gt;

--
Austin Ziegler • halostatue@gmail.com • austin@halostatue.ca
http://www.halostatue.ca/http://twitter.com/halostatue