Try out the world’s best machine translation.

Поднимите руку, если когда-нибудь сталкивались с такой ситуацией: вы получили текст со странными прямоугольниками или вопросительными знаками.

A job board that makes all open positions of Tallinn
tech companies available from a single page

kitty is designed for power keyboard users. To that end all its controls work with the keyboard (although it fully supports mouse interactions as well). Its configuration is a simple, human editable, single file for easy reproducibility (I like to store configuration in source control).

The code in kitty is designed to be simple, modular and hackable. It is written in a mix of C (for performance sensitive parts) and Python (for easy hackability of the UI). It does not depend on any large and complex UI toolkit, using only OpenGL for rendering everything.

В Spotify есть открытый API, и это позволяет разработчикам создавать свои дополнения-сервисы. Я выбрал и проверил 30 таких сервисов. Каждый из них может сделать ваше взаимодействие с музыкой интереснее!

Who is peeking over your shoulder while you work, watch videos, learn, explore, and shop on the internet? Enter the address of any website, and Blacklight will scan it and reveal the specific user-tracking technologies on the site—and who’s getting your data. You may be surprised at what you learn.

Рады представить вам историю создания проекта шрифтовой гарнитуры TT Marxiana.

перевод на русскую дореформенную орфографию и обратно

Configure your schema in JavaScript, and KeystoneJS will generate a powerful GraphQL API and CMS.

Easy to implement, 3D typography for the web. Works with every font.

I made a Chrome extension this weekend because I found I was doing the same task over and over and wanted to automate it. Plus, I’m a nerd living through a pandemic, so I spend my pent-up energy building things. I’ve made a few Chrome Extensions over the years, hope this post helps you get going, too. Let’s get started!

Art of Tea Санкт-Петербург - Лично выбираем образцы чая в Китае, затем повторно тестируем в России — привозим вам только самое свежее и актуальное. Собственноручно проверяем слив у всех чайников. Продаём только тот чай, который пьём сами.

Магазин сумок, кошельков, зонтов и подарков

Restore and save multi-display resolutions and arrangements on macOS

77 выдающихся травелогов от Афанасия Никитина до Эдуарда Лимонова

A gentle introduction to why Webpack exists, what problems it solves, and how to use it.

How an emerging CSS standard can fix old problems and raise the bar for web apps

When optimizing for long-term maintenance, we have a few choices. I like to bet on monorepo. A monolithic repository is a simple idea. You organize the code of all your services in a single repository. It has a few advantages over using a separate repository for each service.

Reusing code is easy. Once you abstract a coherent unit of code into a module, you can then import it from anywhere.

Continuous integration runs tests against the entire monorepo, so once PR is merged you bump the version of all sub-services and there is no doubt what versions are compatible with each other. Version 1.2 of service A is always compatible with version 1.2 of service B. This is why complex projects with multiple dependencies often use monorepo as well (Babel, React, Angular, Jest). Due to the very same reason, large-scale refactorings are also feasible.

You maintain one third-party dependencies tree. It's too easy, especially with all NPM goodies, to end up with two different versions of the same library and having to sync them across different repositories manually gives me a headache. Having one main package-lock.json is a real time-saver.

Monorepo forces collaboration, it encourages having the same coding style by having a single config for your linter/code formatter/module bundler and so on.

Custom Elements are the lynchpin in the Web Components specifications. They give developers the ability to define their own HTML elements. When coupled with Shadow DOM, Custom Elements should be able to work in any application. But things don't always work seamlessly.

This project runs a suite of tests against each framework to identify interoperability issues, and highlight potential fixes already implemented in other frameworks. If frameworks agree on how they will communicate with Custom Elements, it makes developers' jobs easier; they can author their elements to meet these expectations.

Custom Elements and Shadow DOM don't come with a pre-defined set of best practices. The tests in this project are a best guess as to how things should work, but they're by no means final. This project is also about driving discussion and finding consensus, so don't be afraid to open a GitHub issue to discuss places where the tests could be improved. ✌️

Unifying the frontend development toolchain