This statement is wrong.
Same person as @Gobbel2000@feddit.de, different instance.
This statement is wrong.
THE MORE YOU SAVE
That’s wrong, it calculates the surface distance not the distance through the earth, while claiming otherwise. From the geopy.distance.great_circle
documentation:
Use spherical geometry to calculate the surface distance between points.
This would be a correct calculation, using the formula for the chord length from here:
from math import *
# Coordinates for Atlanta, West Georgia
atlanta_coords = (33.7490, -84.3880)
# Coordinates for Tbilisi, Georgia
tbilisi_coords = (41.7151, 44.8271)
# Convert from degrees to radians
phi = (radians(atlanta_coords[0]), radians(tbilisi_coords[0]))
lambd = (radians(atlanta_coords[1]), radians(tbilisi_coords[1]))
# Spherical law of cosines
central_angle = acos(sin(phi[0]) * sin(phi[1]) + cos(phi[0]) * cos(phi[1]) * cos(lambd[1] - lambd[0]))
chord_length = 2 * sin(central_angle/2)
earth_radius = 6335.439 #km
print(f"Tunnel length: {chord_length * earth_radius:.3f}km")
A straight tunnel from Atlanta to Tbilisi would be 9060.898km long.
I must say I like the idea of having changes to files be bound to just the current branch, not the entire worktree (section 6.4.2), but other than that the points that are brought up don’t really seem too compelling. It certainly didn’t convince me that git has an inherently flawed design. For example, eliminating the staging area is a tempting point for simplifying git, but the authors already admit that it has some legitimate use cases.
But of course it is always nice to see some experimentation done in this space. I think the main reason why git sometimes is confusing, is because distributed version control really is a complex task, and git already does a very good job at making it tractable.
Huh? Hexagonal Architecture?
While there certainly is some overlap, Python is a scripting language and not a shell language. Some tasks that involve calling lots of different programs and juggling input and output streams are much easier done in bash than in Python.
This blog post goes into some specifics of Rust reusing Vec allocations and some of the consequences. I think it’s really worth a read to better understand Vecs. From what I understand, it is possible that Rust will reuse the allocation of vec_a
in your case, but it ultimately is quite complicated.
I won’t argue with you that bash is janky and easily insecure, but what shell language do you think should replace bash?
Jon Gjengset on Youtube is doing live coding where he uses neovim quite well. And you’ll learn about Rust while you’re at it.
A major political agenda of Vim is to support children in Uganda. A message about that is displayed whenever you open Vim’s start page. Bram Moolenaar insisted on users donating to the ICCF charity instead of to him, making Vim a very political editor in my view.