hopsoft

JavaScript Microtasks: A Developer's Guide

What Are Microtasks and Why Should You Care?

As a JavaScript developer, you're likely familiar with the event loop handling asynchronous operations. However, microtasks provide a crucial middle layer between synchronous code execution and the macrotask queue that can significantly impact your application's behavior.

Think of microtasks as high-priority tasks that JavaScript executes immediately after the current synchronous operation, but before the next macrotask (like setTimeout callbacks) or render updates.

Common Sources of Microtasks:

joeldrapper

class FuzzyIndex
  def initialize
    @index = Hash.new { |h, k| h[k] = Set.new }
  end
  
  def []=(key, value)
    trigrams(key).each { @index[it] << [key, value] }
  end
  
  def [](query)

AliOsm

KAMAL_REGISTRY_PASSWORD=dckr_pat_xXXxx_x0xXxXx-xX-XXX0xX0x-x
RAILS_MASTER_KEY=00x00xxx000xxx000000xx0x000x0x00
POSTGRES_PASSWORD=xXxxx0xXXx0
MEILI_MASTER_KEY=xXxxx0xXXx0
BLAZER_DATABASE_URL=postgres://service:{POSTGRES_PASSWORD}@service-name-postgres:5432/service_production

cpursley

PostgreSQL is Enough

• Simplify: move code into database functions
• Just Use Postgres for Everything
• Just use Postgres
• PostgreSQL is the worlds’ best database
• Postgres is eating the database world
• Hacker News discussion

Background and Cron Jobs

sampathshivakumar

AWS Event Driven Architecture

What is AWS Event Driven Architecture ?

• AWS Event-Driven Architecture is an approach that utilizes Amazon Web Services to build scalable and decoupled applications.
• It relies on events as the primary means of communication between components.
• The architecture includes event sources that generate events, an event bus for routing events, rules to filter and route events, and targets for actions triggered by events.
• Event Driven Architecture offers benefits such as scalability, loose coupling, flexibility, and real-time processing.

Prerequisites

• AWS Account

argami

https:// {
  log
  tls internal {
	  on_demand
  }
  reverse_proxy :3000
}

amirrajan

the-keeper-iteration-2.mp4

kddnewton

require "json"

struct = { "a" => 1, "b" => 2, "c" => [1, 2, 3], "d" => [{ "e" => 3 }, nil, false, true, [], {}] }
source = JSON.dump(struct)

tokens = []
index = 0

until source.empty?
  tokens <<

natematykiewicz

desc 'Find routes that will raise a routing error when requested'
task unroutable_routes: :environment do
  # A lot of this code was taken from how `rake routes` works
  # https://github.com/rails/rails/blob/f95c0b7e96eb36bc3efc0c5beffbb9e84ea664e4/railties/lib/rails/commands/routes/routes_command.rb

  require 'action_dispatch/routing/inspector'

  unroutables = Rails.application.routes.routes.
     map { |r| ActionDispatch::Routing::RouteWrapper.new(r) }.
     reject { |r| r.internal? || r.engine? || r.path.starts_with?('/rails/') || !r.controller }.

yahonda

Ruby 3.1 on Rails

Actions required to use Ruby 3.1.0 with Rails

Rails 7.0.Z

• Rails 7.0.1 is compatible with Ruby 3.1.0.
• Rails 7.0.1 addes net-smtp, net-imap and net-pop gems as Action Mailbox and Action Mailer dependency, you do not need to add them explicitly in your application Gemfile anymore.
• thor 1.2.1 has been released. You will not see DidYouMean::SPELL_CHECKERS.merge deprecate warnings anymore.

Rails 6.1.Z

• Use Rails 6.1.5 to support database.yml with aliases and secrets.yml with aliases.