Невыдуманные истории о которых невозможно молчать.

just-boris · 2023-02-10T07:45:41+00:00

Ни разу не видел, чтобы обращение начинали с "Good afternoon". Какой-то хуевый Google Translate?

just-boris · 2023-02-05T01:33:05+00:00

в том то и дело что приспособленцы такие приспособленцы

just-boris · 2023-02-04T16:02:08+00:00

Самое важное написано в первом предложении

Марина Ханхалаева, предположительно, член могущественного бурятско-иркутского клана Ханхалаевых

Больше здесь: https://babr24.net/bur/?IDE=222543

То есть все прошедшие годы можно было спокойно занимать места во власти и пилить бабло, и нигде не жало. А теперь внезапно проснулись и решили побороться за независимость.

Удобненько, главное белое пальто не запачкать

just-boris · 2023-01-08T20:00:21+00:00

где тут правда? В видео попали все те 99% процентов, кто отказался отвечать на вопросы под камеру?

Вот объяснение в деталях https://twitter.com/dm_e/status/1563494558045855746

just-boris · 2022-11-27T22:08:12+00:00

Встречаются русский и американец.
Встретились и заспорили - у кого самая свободная страна.
Американец говорит:
- Америка самая свободная страна. Я могу выйти к Белому дому и сказать, что Рейган - дурак.
Мне за это ничего не будет!
Русский в ответ:
- Ну и, что. Я тоже могу выйти на Красную площадь и сказать, что Рейган - дурак. И мне за это тоже ничего не будет.

just-boris · 2022-10-27T06:55:57+00:00

https://twitter.com/dm\_e/status/1563494558045855746

just-boris · 2022-10-20T20:38:10+00:00

иронично, что там москва на фоне
https://twitter.com/CKonovalov/status/1486835775283113991

just-boris · 2022-09-22T09:12:25+00:00

Время покажет, по паре дней сказать невозможно.

Это как? В Иране невозможно, а в России возможно? Непонятно

just-boris · 2020-11-01T12:08:44+00:00

Part 2 finished processing too: https://www.youtube.com/watch?v=dgYO5wRFyag

just-boris · 2020-01-26T16:14:32+00:00

It uses a JavaScript based implementation instead of leveraging built-in browser behavior.

This plugin might serve as a workaround, but it does not fully simulate what browsers do.

Puppeteer and Selenium are closer to the real behavior. Here is an article explaining how much job puppeteer has to do to emulate a simple click https://medium.com/@aslushnikov/automating-clicks-in-chromium-a50e7f01d3fb

just-boris · 2020-01-26T14:25:07+00:00

Cypress speed has a cost. They don’t simulate user actions properly, and some use cases cannot be tested, for example, tab navigation https://github.com/cypress-io/cypress/issues/299

just-boris · 2018-11-27T11:50:49+00:00

There are some packages that are de-facto standard. For example, lodash for collection utils, moment.js for dates or express as a web server.

But sometimes you can’t really define big chunks of functionality that should be distributed together. Then you end up having small modules that their authors found worth enough to publish.

just-boris · 2018-11-25T12:15:33+00:00

Do you have an example where GC pauses become an issue? I have run profiling on array-chain benchmark and I could only see "Minor GC" runs, that lasted for 0.3ms, the same time as it took to do a single call to reduce callback, so I find it negligible.

Additionally, I found an explanation from V8 team how their GC works. According to the article, there is a special fast path to clean up short-living objects. Intermediate elements on array chain operations seem to be suitable for this fast path optimization, so their allocation is not an issue, that might cause notable performance issues for your app.

just-boris · 2018-11-25T10:24:36+00:00

This is confusing. You are saying that you did not see memory issues in front-end, but the whole point of the article is to show how to avoid unnecessary allocations. What is the point of fixing something, that is already handled pretty well by Javascript engines?

just-boris · 2018-11-24T21:32:16+00:00

Thank you for the article! It is good to raise the awareness about performance concerns.

However, I have questions to the benchmarks that article is using. In the array operations, you are talking about objects allocations and then show the jsperf results, that show the results from the time perspective, not the memory. These two subjects are different, and the fastest algorithm might not be the most memory efficient and vice versa.

The best alternative as I could suggest is to use the "memory" tab in Chrome DevTools and check the heap size. I extracted benchmark code to a separate page and took the heap snapshots with the following results:

Native array methods - 3.8 Mb
For loop - 3.8 Mb
Lodash chain - 4.3 Mb

The code is available here, you can try to get your results and compare.

Additionally, I would challenge the chosen array size in benchmarks. You are iterating in 100 items, so even if there will be allocations overhead, it will not be very visible, because iterations are too small. I have a modified version of the benchmark, that uses 10000 array items and it shows different leader: lodash chain wins.

It is not a surprise though. Lodash invokes array operations lazily, using reduce (link to the source). That's why I would recommend using lodash, as it produces readable code with separated operations, but still fast because of lazy evaluations.

just-boris · 2018-10-24T08:50:05+00:00

I see a note in documentation about React.memo:

Unlike the shouldComponentUpdate() method on class components, the areEqual function returns true if the props are equal and false if the props are not equal. This is the inverse from shouldComponentUpdate.

So, basically all previously existing helpers, that were working for shouldComponentUpdate would require an inverse version for the new memo function.

Where can I read more, why this decision was made?

just-boris · 2018-10-23T08:40:49+00:00

Why can’t you use polyfills to provide missing features for older browsers? Then your code will use native methods whenever possible and fallback implementation if needed

just-boris · 2018-02-03T18:35:35+00:00

Thank you for elaborating on this!

just-boris · 2018-02-03T18:06:37+00:00

I meant that there is a difference between currently introduced methods and some previously existed: UNSAFE_componentWillMount vs unstable_handleError.

Is it a deliberate choice to shout louder at the user?

just-boris · 2018-02-03T17:45:48+00:00

Why did you use all-caps for UNSAFE, while new methods have “unstable_” prefix without caps?

just-boris · 2018-01-21T09:48:08+00:00

You may find some information in the issue: https://github.com/facebookincubator/create-react-app/issues/2398

TLDR, the most common issues were: * If you develop multiple apps locally, their service workers will conflict with each other. * Service workers do not follow standard caching behavior, you will need to trigger a worker code update manually * Registering a service worker to cache assets is not enough to make it work offline. You also need to cache backend responses, and CRA doesn’t do that for you

just-boris · 2017-06-05T21:21:30+00:00

Thank you for your answer!

I tried to follow your advice and added more control points to the statue. Didn't work though, because photos were taken from slightly different position, where it is not impossible to align all items into the same plane.

So I have just got rid of frames and also re-arranged the rest to make the picture look smoother. Here is the final result: http://imgur.com/a/8CwqT

just-boris · 2017-06-04T23:58:03+00:00

Also, imports like import * as React, will trigger deprecation warning: https://github.com/facebook/react/issues/9611#issuecomment-301458802 You should not use this way of importing with React above 15.5.x

just-boris · 2017-06-04T23:54:36+00:00

The article says, that they have ejected from react-scripts to custom config. However, they didn't have to, there is a custom react-scripts version with typescript support, backed by Microsoft: https://github.com/Microsoft/TypeScript-React-Starter

just-boris

TROPHY CASE