__float

This might be true for the most part as an end user, but from a licensing perspective regarding the original binaries, this is irrelevant.

You must be able to modify and change the code, not merely append to the PATH:

> Tivoization: Some companies have created various different kinds of devices that run GPLed software, and then rigged the hardware so that they can change the software that's running, but you cannot.

from https://www.gnu.org/licenses/quick-guide-gplv3.en.html

While the GUI is somewhat helpful, at the end of the day it's not the key piece, and it could easily be rebuilt.

This was discussed somewhat recently in https://news.ycombinator.com/item?id=42855258

The lifetime warranty clearly was valuable to many people here.

The problem though, is the _misleading_ marketing around "better sound" and similar that is false and does not justify charging more to basic home consumers who don't know any better.

I can't really fault them too much for hopping on the latest bandwagon, if their software is general enough at running workflows for it to fit.

They do seem to have a nice "quickstart for CI" they haven't abandoned, yet: https://docs.dagger.io/ci/quickstart

(As much as I personally like working with CI and build systems, it's true there's not a ton of money in it!)

TeamCity's "config as code" feels a bit like an afterthought to me. (It's very Windows-style, where PowerShell got bolted on, and you're still fighting a bit of an upstream current getting clickops users out of old habits. I've also only experienced it at .NET-stack jobs, though, so I might be a bit biased :-)

(I don't recall _loving_ it, though I don't have as many bad memories of it as I do for VSTS/TFS, GitLab, GH Actions, Jenkins Groovyfiles, ...)

Yeah, I've come back around to this: you do not want "end users" writing Groovy, because the tooling around it is horrible.

You'll have to explain the weird CPS transformations, you'll probably end up reading the Jenkins plugins' code, and there's nothing fun down this path.

It's common (see: S3, private GitHub repos) to return 404 instead of unauthorized to avoid even leaking existence of a resource at URL.

How many of those can you realistically bypass by DIYing? I understand it saves a bit on taxes and you don't need a license yourself, but the rest?

I mean, there was the obvious solution of paying the money to have it captioned, which was the original order.

Berkeley instead offered this alternative solution, because they did not want to pay.

Well, that commenter seems to have chosen it as their single pet peeve against Jellyfin.

+1 to this. Remembering the schema is kind of a big barrier when you're just jumping in, and that's when you want to be able to explore at random the most.

(I also struggled with the schema because crime_scene was singular and suspects was plural!)

I'm not entirely convinced they meant to truly make a public hall of shame.

It sounded to me like a list of "friends who want to get more involved, I'll let you know who to avoid". Then, I read the interactions that sparked that post, and I could totally understand the frustration from OP's part.

Linus being unwilling to take a real stand on maintainers blocking Rust just because doesn't really help.

Is Zig really a simpler language? It has a ton of features!

Uv supports this: https://docs.astral.sh/uv/guides/scripts/#declaring-script-d...

(Though, this is more general than uv for Python script deps: https://packaging.python.org/en/latest/specifications/inline...)

Yes, unless you're using persistent workers. Then you may very well run into the same issues they mention.

What is "proper Quake mode"? Have you tried https://ghostty.org/docs/config/keybind/reference#toggle_qui...? (I don't have the habit to use this feature, but I'd like to!)

The others do sound useful too -- I personally hit a lot of spurious "tab output indicator" notifications in iTerm2, but if it _did_ work I could see how giving it up would be painful.

It looks like they work at Google, based on their GitHub (assuming the same username) -- so no, it's sadly not open source :(

A real shame, I think Bazel's lack of good IDE options definitely hampers its adoption.

> I saw tradeoffs that I didn't like. I saw features that I wanted. I saw performance that I could improve. I saw stagnation. There are many fantastic terminals out there and you should use them if they work for you. But I wanted something different and thought maybe others did too.

This motivation is pretty clearly stated in the article.

Some people use "fancy TUIs" (the famous editors vim and emacs surely count) and if you don't, feel free to ignore this new option.

The prompt for the honey video mentions ending with a shot of an orange. The orange just...isn't there, though?

I can't help but feel this is a somewhat veiled complaint about the Rust community instead of anything substantive with the language :/

This was just one example, maybe not a perfect one. I found it to be relatable, though.

Sometimes the "add the missing tests" step depends on other work on your branch.

Do you think interviewers at a company this size are deciding how interviews are run? They're basically just following a script.

Yes, you can use your own editor. It's not generally _offered_ for the first (pre "onsite") interview but is an option if you ask. It's made clear (recommended, even) for the onsite that you have that option.

I'm not sure how many people are like me, but my attempts to use Copilot have largely been the context of writing code as usual, occasionally getting end-of-line or handful-of-lines completions from it. I suspect there's probably a bigger shift needed, but I haven't seen anyone (besides AI "influencers" I don't trust..?) showing what their day-to-day workflows look like.

Is there a Vimcasts equivalent for learning the AI editor tips and tricks?

It's unfortunate because there _is_ an existing large ecosystem around the official Visual Studio Code product. (The extension "store" cannot be used with forks.)

The VS Code team has kept some APIs in this "preview" mode for many many years. https://github.com/microsoft/vscode/issues/59921 is just one example, which has been requested since early 2018!

I _loved_ my Kindle Voyage for its adjusting backlight and glass display.

I wish it were less destructible! I upgraded to a Paperwhite (2021) when the Voyage's power button broke. Water resistance is nice, but having to get the "signature" edition for a light sensor and an easily scratched plastic display is quite disappointing.

Yes, I understand that. I was just pointing out someone else publicly made this connection, several months prior.

Whenever I’ve converted books to mobi in Calibre it seems they fall back to a slightly worse experience - using “location” markers instead of real page numbers as official Kindle books display, cover art is tricky to get working on the lock screen, etc.

Is this a poor Calibre configuration or are there real limitations to reading books side-loaded on Kindles?

It's also been called that in a software engineering context[0], though it looks the post didn't get much traction on HN when it was submitted[1].

[0] https://lethain.com/no-wrong-doors/

[1] https://news.ycombinator.com/item?id=40450485