On a technical blog post by a software company about the details of solving an algorithmic complexity problem?
Careless, and showing that the author does not understand technical communication, where precision is of great importance.
On a technical blog post by a software company about the details of solving an algorithmic complexity problem?
Careless, and showing that the author does not understand technical communication, where precision is of great importance.
Marketing departments love to make a huge deal out of this kind of thing, because they only see the big number improvement and don't really understand that this was just some dev's Wednesday afternoon.
They make the same mistake further down the article:
However, the implementation of the command suffered from poor scalability related to reference count, creating a performance bottleneck. As repositories accumulated more references, processing time increased exponentially.
This article writer really loves bullet point lists, too. 🤨
Are you new to hackaday? This is 90% of their articles.
I don't mind it - they're bringing news about interesting things that makers are doing, and most of the time those makers have made videos about their process, so it makes sense to include it.
There is nothing to be “weary” of
I checked, and OP actually spelt "wary" correctly.
No rice
We don't use that term in this community, see rule 7
Just be patient for the inevitable uBlockOrigin update that will fix it.
@Scirocco@lemm.ee @sag@lemm.ee Any plans on moving this community to another instance?
maybe it's finished
Enjoy being mediocre.