José Valim: If you look at the features listed by Kubernetes (#k8s) and compare it to languages that run on the Erlang VM, such as Erlang and Elixir, the impression is that they share many k eywords, such as “self-healing”, “horizontal scaling”, “distribution”, etc.
This sharing often leads to confusion. Do they provide distinct behaviors? Do they overlap? For instance, is there any purpose to #elixir’s fault tolerance if Kubernetes also provides self-healing?
In this article, I will go over many of these topics and show how they are mostly complementary and discuss the rare case where they do overlap.
This sharing often leads to confusion. Do they provide distinct behaviors? Do they overlap? For instance, is there any purpose to #elixir’s fault tolerance if Kubernetes also provides self-healing?
In this article, I will go over many of these topics and show how they are mostly complementary and discuss the rare case where they do overlap.
The strictest and most opinionated #python linter ever! Actually
https://github.com/wemake-services/wemake-python-styleguide
It focuses on enforcing consistent, easy (not complex), readable python code. And it goes with some extreme and hardcore checks inside.
We also made this linter to be legacy first with the help of
Also available as a Github Action: https://github.com/marketplace/actions/wemake-python-styleguide
By the way, we have a lot of #Hacktoberfest issues that need help: https://github.com/wemake-services/wemake-python-styleguide/issues?q=is%3Aissue+is%3Aopen+label%3AHacktoberfest
wemake-python-styleguide is just a flake8 plugin with lots of other plugins as dependencies.https://github.com/wemake-services/wemake-python-styleguide
It focuses on enforcing consistent, easy (not complex), readable python code. And it goes with some extreme and hardcore checks inside.
We also made this linter to be legacy first with the help of
flakehell. It means that you are allowed to have existing bad code, but you won't be allowed to write more bad code. Ever.Also available as a Github Action: https://github.com/marketplace/actions/wemake-python-styleguide
By the way, we have a lot of #Hacktoberfest issues that need help: https://github.com/wemake-services/wemake-python-styleguide/issues?q=is%3Aissue+is%3Aopen+label%3AHacktoberfest
DYC is a CLI tool that helps with documenting your #python source code. It will help keep you alert for new methods that were added and not documented. Also supports to build a reusable docstring template. Just answer the prompt questions in your terminal to see the effect on your files.
https://github.com/Zarad1993/dyc
https://github.com/Zarad1993/dyc
GitHub
GitHub - Zarad1993/dyc: Document Your Code
Document Your Code. Contribute to Zarad1993/dyc development by creating an account on GitHub.
A #rust crate for safe and ergonomic pin-projection.
https://crates.io/crates/pin-project
Honest question: do you understand what does
https://crates.io/crates/pin-project
Honest question: do you understand what does
Pin do?Excelent article about layers in your application.
> When designing any application, the question is inevitably raised: “where should this code go?” Many times this answer isn’t readily available, resulting in code that ends up in a project’s junk drawer (like utils or models). If this happens enough, the codebase becomes tangled and the team’s ability to maintain the software over time is significantly decreased. This is not a sign of developer inexperience or “naming is hard” — instead it’s most likely a symptom of an application’s lack of structure.
> When designing any application, the question is inevitably raised: “where should this code go?” Many times this answer isn’t readily available, resulting in code that ends up in a project’s junk drawer (like utils or models). If this happens enough, the codebase becomes tangled and the team’s ability to maintain the software over time is significantly decreased. This is not a sign of developer inexperience or “naming is hard” — instead it’s most likely a symptom of an application’s lack of structure.
3rd October 2019: PostgreSQL 12 Released! #sql
Changelog: https://www.postgresql.org/docs/12/release-12.html
Changelog: https://www.postgresql.org/docs/12/release-12.html
#strange
An awesome list of dev-related movies: https://github.com/aryaminus/dev-movies
In case you don't have enough of development at work!
An awesome list of dev-related movies: https://github.com/aryaminus/dev-movies
In case you don't have enough of development at work!
GitHub
GitHub - aryaminus/dev-movies: Movies and Series I've loved over the years, for the people with software development background…
Movies and Series I've loved over the years, for the people with software development background, IT Engineers or general people who love movies - GitHub - aryaminus/dev-movies: Movies and ...
rx is an extensible, modern and minimalist pixel editor and animator implemented in #rust. It's designed to have as little UI as possible, and instead takes inspiration from #vi's modal nature and command mode.
https://github.com/cloudhead/rx
https://github.com/cloudhead/rx
⚡ Breaking news!
TensorFlow 2.0 is released. It focuses on simplicity and ease of use, featuring updates like:
- Easy model building with Keras and eager execution.
- Robust model deployment in production on any platform.
- Powerful experimentation for research.
API simplification by reducing duplication and removing deprecated endpoints.
https://github.com/tensorflow/tensorflow/releases/tag/v2.0.0
TensorFlow 2.0 is released. It focuses on simplicity and ease of use, featuring updates like:
- Easy model building with Keras and eager execution.
- Robust model deployment in production on any platform.
- Powerful experimentation for research.
API simplification by reducing duplication and removing deprecated endpoints.
https://github.com/tensorflow/tensorflow/releases/tag/v2.0.0
GitHub
Release TensorFlow 2.0.0 · tensorflow/tensorflow
Release 2.0.0
Major Features and Improvements
TensorFlow 2.0 focuses on simplicity and ease of use, featuring updates like:
Easy model building with Keras and eager execution.
Robust model deploym...
Major Features and Improvements
TensorFlow 2.0 focuses on simplicity and ease of use, featuring updates like:
Easy model building with Keras and eager execution.
Robust model deploym...
Inboxkitten is an open-source disposable email #js service that you can freely deploy adopt on your own! https://github.com/uilicious/inboxkitten
Only takes 6 steps:
Only takes 6 steps:
clone "https://github.com/uilicious/inboxkitten.git"
cd inboxkitten
./config.sh
./build.sh
firebase login
./deploy/firebase/deploy.sh
GitHub
GitHub - uilicious/inboxkitten: Disposable email inbox powered by serverless mailgun kittens
Disposable email inbox powered by serverless mailgun kittens - uilicious/inboxkitten
A #rust actor-based framework for building modern, concurrent and resilient applications
https://riker.rs/
https://riker.rs/
ZIO from #scala is coming to #python! How cool is that?
https://github.com/harveywi/ziopy
Currently it is in the very beggining, but it is still interesting to watch.
https://github.com/harveywi/ziopy
Currently it is in the very beggining, but it is still interesting to watch.
GitHub
GitHub - miiohio/ziopy: ZIO for Python
ZIO for Python. Contribute to miiohio/ziopy development by creating an account on GitHub.
⚡Breaking news!
#django enhancement proposal to fully type annotate django's source code.
It is proposed to merge
More information: https://github.com/django/deps/pull/65
#django enhancement proposal to fully type annotate django's source code.
It is proposed to merge
django-stubs (https://github.com/typeddjango/django-stubs) into the core django. More information: https://github.com/django/deps/pull/65
GitHub
GitHub - typeddjango/django-stubs: PEP-484 stubs for Django
PEP-484 stubs for Django. Contribute to typeddjango/django-stubs development by creating an account on GitHub.
Typed functional programming with #swift
- Type classes
- IO
- Effects
https://bow-swift.io/docs/effects/overview/
- Type classes
- IO
- Effects
https://bow-swift.io/docs/effects/overview/
Quickly find publicly known security vulnerabilities in a website's #js libs.
https://github.com/lirantal/is-website-vulnerable
My wild guess is that everything is vulnerable 😮
https://github.com/lirantal/is-website-vulnerable
My wild guess is that everything is vulnerable 😮
GitHub
GitHub - lirantal/is-website-vulnerable: finds publicly known security vulnerabilities in a website's frontend JavaScript libraries
finds publicly known security vulnerabilities in a website's frontend JavaScript libraries - lirantal/is-website-vulnerable
Github Action to prevent cursing in issues and pull requests: https://github.com/sobolevn/restrict-cursing-action
#js #typescript #docker
#js #typescript #docker
To use optional chaining & nullish coalescing in #vue files today:
- Run
- Set
Useful for many DOM operations. For example,
https://github.com/vuejs/vetur
- Run
yarn add typescript@beta- Set
"vetur.useWorkspaceDependencies": trueUseful for many DOM operations. For example,
querySelector => Element | nulltextContent => string | null | undefinedhttps://github.com/vuejs/vetur
And as an #apple software developer, I live through the Summer beta periods. On my secondary machine. And, in recent years, within virtual machines that allow me to do more intricate testing. I’ve seen easy-going mostly spit and polish releases as well more substantial user-facing and under-the-hood ones.
But Catalina has been different in two particularly gruesome ways that get even worse when combined.
The first, is purely from a stability and functional standpoint. The early betas of Catalina were really, really broken. But that’s OK! That’s what betas are for. And while I can only speak for myself, I think most developers are more than happy to offer input to Apple and report bugs. So I’m totally fine using a wonky OS for a few months on a spare machine while I test my own software in addition to Apple’s.
But here’s the bad part ...
#macos
But Catalina has been different in two particularly gruesome ways that get even worse when combined.
The first, is purely from a stability and functional standpoint. The early betas of Catalina were really, really broken. But that’s OK! That’s what betas are for. And while I can only speak for myself, I think most developers are more than happy to offer input to Apple and report bugs. So I’m totally fine using a wonky OS for a few months on a spare machine while I test my own software in addition to Apple’s.
But here’s the bad part ...
#macos