Luiz “Felds” Liscia felds

Dark mode is not a feature — it’s a browser setting

It’s 2025, and we’re still building dark mode toggles with JavaScript like it’s 2019. This is a UX oversight. Mode preference — light or dark — is a personal, system-level setting, and browsers already know how to handle it. Yet, websites keep reinventing the wheel with janky toggles that often don’t persist, don’t sync with system changes, and can’t even influence CSS media queries. The result? Inconsistent UX, broken themes, and wasted developer time — all to replicate something that should be a native browser feature, just like zoom or autoplay controls.

There are plenty of practical and technical reasons why theme switching belongs in the browser, not in your app code. Here’s a breakdown of why this shift would be a win for users, developers, and the web platform as a whole:

1. Accessibility & UX Consistency

Native switches could be surfaced consistently across all sites, making them easier to find and use — especially for users relying on keyb

Pra começar, atualize o sistema:
```
sudo apt update
sudo apt upgrade -y
```

Intale o MariaDB:

sudo apt install -y mariadb-server
sudo mysql_secure_installation

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<title>Document</title>
	<meta name="color-scheme" content="dark light">
	<style>
	* {
	font-size: 32px;

	class Point {
	constructor(
	public x: number,
	public y: number,
	) {}
	serialize(): any {
	return {__type: this.constructor.name, x: this.x, y: this.y}
	}
	toString() {
	return `I'm a point: ${this.x}, ${this.y}`

	@use "sass:color";
	@use "sass:list";
	@use "sass:math";
	@use "sass:meta";

	// Create a list of numbers
	@function range($from, $to, $step: 1) {
	// validation
	@if meta.type-of($from) != "number" {
	@error "$from must be a number.";

	type SuspendStatus = "pending" \| "success" \| "error";
	export function suspend<T>(promise: Promise<T>) {
	let result: T;
	let error: Error;
	let status: SuspendStatus = "pending";

	let suspender = promise.then(
	(r) => {
	status = "success";
	result = r;

	<script>
	const forms = Array.from(document.querySelectorAll("form"))

	// disable browser validation
	forms.forEach(el => el.noValidate = true)

	// add unsaved data prompt
	let unsaved = false;
	window.addEventListener("beforeunload", (e) => {
	if (unsaved) {


	# IMPORTANT:
	# Dont forget to to replace the INSTANCE_NAME for the name
	# of the instance we created on step 2

	steps:
	- name: gcr.io/cloud-builders/docker
	args:
	- build
	- '-t'

	<?php

	/**
	* common settings for wp-config
	*/

	// dont try to connect via ftp for updates
	define( 'FS_METHOD', 'direct' );

	// force urls

	# EditorConfig is awesome: http://EditorConfig.org

	# top-most EditorConfig file
	root = true

	[*]
	charset = utf-8
	end_of_line = lf
	insert_final_newline = true
	indent_style = space