the problem is not the people who want impulse satisfaction, comfort, and convenience - these are all perfectly normal human desires. the problem is that we as a society have allowed predators to tie these needs to surveillance and addiction engineering. there is no intrinsic reason that couldn't have been regulated against - look at some of the absolutely idiotic things the government is willing to spend time and money in micromanaging.
the claude giveth and the claude taketh away. I could definitely use claude in a tightly directed manner to clean up a slopified codebase (and I would enjoy doing so), you just need to think of it as closer to a power tool than an agent.
imagine not 2% of users not being able to use the site, but any given user not being able to use the site 2% of the time, and see if that changes the calculus for you.
I know what they meant, I was saying that imo the ergonomic name is has_not_been_viewed_much. it's directly expressing the property you are interested in, as opposed to expressing the negative property and comparing it to false.
this is a really nice looking language! the central focus on using effects to get zero cost abstractions is a very attractive one; I really hope the language makes it out of the experimental toy compiler stage.
I think cory doctorow had the best lens through which to view the issue: "who does this technology do things for and who does it do them to?"
even tech enthusiasts can see that a major chunk of the populace is increasingly falling on the "to" side, so championing resistance makes a lot of sense.
my speculation is that not having written the original text means you don't have a mental history of all the decisions that went into writing it, and the context from being immersed in the work, making it a lot harder and less motivating to go write the next draft.
surprised to see that, I've long held tree balancing up as practically the poster child for ML syntax being the best way to express certain algorithms. it directly says what shape of nodes goes to what other shape.
in order to use third party code within google it needs to be copied into the monorepo, and projects that depend on it need to import the internal version. this requires at the very least setting it up to build via blaze (google's internal build system, open sourced as bazel), and frequently adjusting its directory layout to fit the monorepo conventions.
this "mirror and use the local copy" dance is exactly how "any other third party tool" works within google.
it's useful for cases like google's, where they mirror internal code to github or vice versa, and the two versions need a bit of mechanical work every time they are synced (e.g. slightly different tree layout conventions, internal code or docs that you don't want to include in the github version, stripping of references to other internal stuff like bug IDs from comments, etc).
"Before explaining my setup in more detail, I want to clarify, that I still use a second phone. It is an older stock Android phone, with all Google stuff on it. I need still need to use banking and other apps, that don't work on custom roms."
sad, I didn't realise that because their website has an "install from f-droid" link. it does reinforce my point that android is a proper platform with a viable distribution mechanism though, if they can self host a third party repository.