lf94

import cadquery as cq
# Parameters for the bearing
outer_diameter = 22.0  # Outer diameter of the bearing
inner_diameter = 8.0   # Inner diameter of the bearing
width = 7.0            # Width of the bearing
ball_diameter = 4.0    # Diameter of the bearing balls
number_of_balls = 7    # Number of balls in the bearing
# Create the outer race
outer_race = (
    cq.Workplane("XY")

lf94

import cadquery as cq
# Parameters for the cylinder
cylinder_height = 50.0
cylinder_radius = 20.0
# Parameters for the rectangular cutouts
cutout_width = 5.0
cutout_height = 10.0
cutout_depth = 10.0
# Create the base cylinder
cylinder = cq.Workplane("XY").cylinder(cylinder_height, cylinder_radius)

lf94

import cadquery as cq
# Parameters
diameter = 10.0  # Diameter of the flowerpot
height = 10.0    # Height of the flowerpot
thickness = 0.5  # Wall thickness of the flowerpot
bottom_thickness = 0.5  # Bottom thickness of the flowerpot
# Create the outer shell of the flowerpot
outer_shell = cq.Workplane("XY").circle(diameter / 2).extrude(height)
# Create the inner cavity by offsetting the outer shell inwards
inner_shell = (

lf94

static void
DrawLights(void)
{
	int l, i, j, k;

	vif1SetZWrite(0);
	vif1SetZTest(0);
	vif1SetTexture(&textures[TEXID_CRBL]);

	for(l = 0; l < 4; l++) {

lf94

GitHub changed the world of open-source.

In the beginning it brought together the disconnected programmers who always wanted to work on something with other like-minded people.

In the present it's no longer the foreground. Businesses and professionals connect and the profiles become a bragging ground.

The GH PR system is stretched to its limits. During the early days this was ok: PRs were few and far between. It worked.

I've changed, and so has GitHub. As I grow older I care more about my impact and personal data responsibility. I care about FOSS work being used for profit.

lf94

<canvas id="canvas" width="800" height="600"></canvas>

<script>
const canvas = document.getElementById("canvas");
const context = canvas.getContext('2d');
const rgbs = {};

// color is in 565 format
function toRGB(color) {
  const rgb = rgbs[color];

lf94

// P = (1−t)2P1 + 2(1−t)tP2 + t2P3

function bezier3(points, segments) = let (
    s = 1 / segments
) [
for(t = 0; t <= 1 + s; t = t + s)
    pow((1 - t), 2) * points[0]
    + 2 * (1 - t) * t * points[1]
    + pow(t, 2) * points[2]
];

lf94

RE: WHEN WILL WEB BROWSERS BE COMPLETE?
2020-10-31 02:46PM
A follow-up.

There has been some great conversation around the opinion piece. Having read all
200+ comments on YCombinator and Gist GitHub, I think it's most productive to
respond to them all in this follow-up piece.

The piece will be structured by looking at what I think are the most relevant
critiques and comments, followed by adding context to others' comments, and

lf94

WHEN WILL BROWSERS BE COMPLETE?
A short exploration into the end game of web browsers.

This article may seem to be about bashing Google but it isn't. It's just about
reflecting on the current state and how much longer we should see ourselves
here.

So what is the Web? Well we can agree the Web is a conglomerate of standards
proposed by the W3C. So what do those standards define?

lf94

Theorem andb_eq_orb :
forall (b c : bool),
(andb b c = orb b c) ->
b = c.

Proof.
intros b c.
destruct b eqn:Eb.
  - destruct c eqn:Ec.
    + reflexivity.