fxn

Ruby: The future of frozen string literals

What is a literal?

In programming languages, literals are textual representations of values in the source code. This is a syntactical concept.

Some examples:

7 # integer literal

amkisko

if ENV["DEBUG_CALLBACKS"]
  Rails.application.eager_load!

  ActiveRecord::Callbacks::CALLBACKS.each do |callback_type|
    ApplicationRecord.descendants.each do |model|
      kind, name = callback_type.to_s.split("_")
      chain = model.__callbacks[name.to_sym]&.send(:chain)
      filtered = chain&.select { |chain_callback| chain_callback.kind == kind.to_sym }
      $callbacks_counter ||= {}
      $callbacks_counter[model.name] ||= {}

amkisko

# NOTE: partial content required for Gemfile

gem "rails"
gem "propshaft"
gem "importmap-rails"
gem "stimulus-rails"
gem "tailwindcss-rails"

gem "action_policy"

dhh

# THIS LINUX SETUP SCRIPT HAS MORPHED INTO A WHOLE PROJECT: HTTPS://OMAKUB.ORG
# PLEASE CHECKOUT THAT PROJECT INSTEAD OF THIS OUTDATED SETUP SCRIPT.
#
#

# Libraries and infrastructure
sudo apt update -y
sudo apt install -y \
	docker.io docker-buildx \
	build-essential pkg-config autoconf bison rustc cargo clang \

mitchellh

I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.

I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:

amkisko

# PATH: config/initializers/sidekiq_alive.rb
# AUTHOR: Andrei Makarov (github.com/amkisko)

# NOTE: now available as gem sidekiq_status_monitor (https://rubygems.org/gems/sidekiq_status_monitor)

class SidekiqAliveServer
  attr_accessor :workers_size_threshold,
                :process_set_size_threshold,
                :queues_size_threshold,
                :queue_latency_threshold,

amkisko

Rails views with stimulusjs opinion

References

Known component/view patterns:

• https://stimulus.hotwired.dev/handbook/introduction
• https://backbonejs.org/#View
• https://docs.angularjs.org/tutorial/step_02
• https://docs.angularjs.org/tutorial/step_03
• https://angular.io/guide/component-overview

amkisko

<%=
  button_to(omniauth_authorize_path(resource_name, provider),
            method: :post,
            style: "margin:1rem;align-items:center;color:#fff;background-color:#4A154B;border:0;border-radius:48px;display:inline-flex;font-family:Lato, sans-serif;font-size:16px;font-weight:600;height:48px;justify-content:center;text-decoration:none;width:256px",
            "data-turbo": false) do
%>
  <svg
    xmlns="http://www.w3.org/2000/svg"
    style="height:20px;width:20px;margin-right:12px"
    viewBox="0 0 122.8 122.8"

kaspth

class Object::Proxy < SimpleDelegator
  def initialize(object, **values)
    super(object)
    @values = values
  end

  def method_missing(name, ...)
    @values.fetch(name) { super }
  end
end

tannerlinsley

This middleware does a few interesting things:

• Ensures a url shape in the zustand store, where we'll store URL information.
• Assumes we will be storing our url state slice in the ?state search parameter after it has been stringified and base 64 encoded.
• On creation, decodes stores state from the ?state search parameter into the url slice of our store.
• After each state update, updates the ?state search parameter with the new url state slice.
• Sets up an event listener that listens for popstate and re-decodes the state from the URL into our store.