khuongduybui

Explain quantum computing in simple terms

Quantum computing is a type of computing that uses quantum mechanics, a branch of physics that deals with the behavior of subatomic particles, to perform calculations. Quantum computers are able to perform certain types of calculations much faster than classical computers, which use traditional bits to represent and store data.

Quantum computers use quantum bits, or qubits, to store and process information. Qubits can represent and store more information than classical bits, which can only store either a 0 or a 1. Qubits can exist in a superposition of both 0 and 1 simultaneously, which allows quantum computers to perform certain types of calculations much more efficiently.

Quantum computers are still in the early stages of development and are not yet widely available. However, they have the potential to revolutionize many fields, including cryptography, drug discovery, and financial modeling, by solving problems that are currently too complex for classical compu

aalmiramolla

# references:
#   Learning by doing: Writing your own traceroute in 8 easy steps (Ksplice Blog)
#   https://blogs.oracle.com/ksplice/entry/learning_by_doing_writing_your

# Edited by: Alejandro Almira <laboral at alejandroalmira.com>

import datetime
import socket
import sys

ityonemo

A half-hour to learn Zig

This is inspired by https://fasterthanli.me/blog/2020/a-half-hour-to-learn-rust/

Basics

the command zig run my_code.zig will compile and immediately run your Zig program. Each of these cells contains a zig program that you can try to run (some of them contain compile-time errors that you can comment out to play with)

graninas

At the beginning of 2030, I found this essay in my archives. From what I know today, I think it was very insightful at the moment of writing. And I feel it should be published because it can teach us, Rust developers, how to prevent that sad story from happening again.

---

What killed Haskell, could kill Rust, too

What killed Haskell, could kill Rust, too. Why would I even mention Haskell in this context? Well, Haskell and Rust are deeply related. Not because Rust is Haskell without HKTs. (Some of you know what that means, and the rest of you will wonder for a very long time). Much of the style of Rust is similar in many ways to the style of Haskell. In some sense Rust is a reincarnation of Haskell, with a little bit of C-ish like syntax, a very small amount.

Is Haskell dead?

afresh1

These examples all live in a default server block in your httpd.conf(5).

server "default" {
	listen on * port 80
	... # all the location blocks can together right here
}

We'll be using slowcgi(8) as the example, because with the -d flag it helpfully spits out the FastCGI environment it got from httpd(8) and what it's planning to do with that.

ausfestivus

List of Azure Regions

A list of all the region names and locations for Azure

Creating the list

You can recreate the list anytime using this command:

az account list-locations -o table

janlelis

ruby -e'_,__="",binding;loop do$><<">> "if$/>_
puts"=> %p"%[__.eval(_+=gets||exit!),_=""]
rescue Exception
puts"\e[31m%p\e[0m"%[$!,_=""]if/d e|ee/!~"#$!"end'

lisawolderiksen

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

matchai

PHP        6 hrs 51 mins  ████████████░░░░░░░░░  57.2%
Smarty     1 hr 21 mins   ██▍░░░░░░░░░░░░░░░░░░  11.4%
HTML       1 hr 16 mins   ██▏░░░░░░░░░░░░░░░░░░  10.6%
TypeScript 58 mins        █▋░░░░░░░░░░░░░░░░░░░   8.1%
Blade T... 26 mins        ▊░░░░░░░░░░░░░░░░░░░░   3.7%

william8th

# Set the control character to Ctrl+Spacebar (instead of Ctrl+B)
set -g prefix C-space
unbind-key C-b
bind-key C-space send-prefix

# Set new panes to open in current directory
bind c new-window -c "#{pane_current_path}"
bind '"' split-window -c "#{pane_current_path}"
bind % split-window -h -c "#{pane_current_path}"