Yep. You can see Google Earth-style photogrammetry artifacts (e.g. around power lines and pylons,) with AI artifacts layered on top, and also the edges of different tiles don't always align so sometimes you get a "double vision" effect.
But consider “tiler” (someone who lays tiles on a floor) vs “tiller” (someone who tills farmland). The single or double ‘l’ results in a long or short ‘i’ in the pronunciation.
Or “hater” vs “hatter”. “Hoping” vs “hopping”. “Later” vs “latter”. Etc
Yep. He is trying to stir up public opinion after his legal options petered out.
Admitting the status of his original shares is not a good look either way. Either he sold, and the additional shares aren't technically worth $1B because he'd have sold them too. Otherwise he held, and is another unsatisfied greedy billionaire in the world.
I think the migration can be made pretty easy for users with deprecation notices and the `go fix` tool. Better explained in [1] (I have not tried it myself).
The idea is: the package maintainer pushes a final version of the old package that is a shim, and which has a deprecation notice. The shim imports the new package, and forwards all calls to the new package (and I suppose type aliases and variable aliases as well). The shim includes `//go:fix inline` annotations on all exported symbols, so that when users run `go fix` it rewrites their code to use the new package, by inlining their usages of the old package (which is now simply a shim that references the new package).
Not perfect. There is still a bit of a discoverability problem. Not all tooling warns on deprecated packages/functions (go toolchain doesn't, but gopls and staticcheck do). And users need to know to run `go fix`.
This landing page is not good. It's mired in out-of-context jargon and implementation detail. (What does "virtualize the worktree" mean? Git already has "effectively free" branching. What does branching "mid-run" mean? How does a teammate "join while the work is happening"? What/where are they joining?).
What actually is it and what value do I get out of it?
Reading the linked blog posts: It's a layer on top of git for CRDT-based collaborative editing that captures addressable code deltas + agent conversations. I could have real-time collaborative humans + agents development and can resume any agent conversation from any point in history, because it is all stored (powered by DeltaDB). I guess?
I actually might want this, but wouldn't know it from the landing page.
I went a bit far in saying there's a "missing" sense of taste, but did mean that it's not important to apply it when buying huge amounts of groceries, so I agree.
What I was thinking of more broadly was the cookie cutter nature of many suburbs. You get a stamped out template of a neighborhood with the same franchises. Houses over here, parking lot over there.
Right. License pulls happen extremely rarely for digital video games[1]
And delisting a game from a store isn't a license pull. Delisting prevents new purchases of the game, but owners of a game prior to delisting can still download and play[2]
For example, even though Sony is closing the PS3 store to new purchases after 20 years, existing owners of digital games can still download their digital copies. So my entire PSN digital library for the past 20 years is still downloadable and playable. Same for Steam.
I love GOG, and prefer a DRM-free digital copy for PC that I can backup redundantly, as it is the most future-proof option, IMO. Physical media can get damaged or lost and digital storefronts won't last forever (even Steam could shut down one day). Even my hard drives can fail and lose data. But even so, when I purchase a digital license for a game, I have good confidence it will be playable for years and years to come.
---
1. Of course, many online multiplayer games have had their servers shut down, after which the game becomes effectively unplayable. But this is a separate problem that isn't solved by choosing physical over digital media.
2. As long as the digital storefront exists and as long the console hardware still works, if I purchased it for a console.
This more a dig at Sony than a reason Valve can’t also sell their hardware as a loss leader. They are massively profitable from their cut of Steam sales anyway. And part of PS Plus is a catalog of games and monthly games, similar to Gamepass. Valve could easily have a profitable subscription model for games or services if they wanted to.
AFAIK, Golang's module system (mentioned in the article) protects against this. From [1],
The revision must be an ancestor of one of the module repository’s branches or tags. This prevents attackers from referring to unapproved changes or pull requests.
if you go look at any real Go projects they usually use tons of dependencies and they're usually pinned to random git hashes
No, they are usually pinned to a git tag, which is usually a version string representing a released version. And the tag is locked to a hash to detect if the tag is later modified.
1. https://www.justinchavez.com/blog/isometric-sf/
reply