gabesullice

I made a simple Firefox add-on that copies and pastes URL paths between tabs, ignoring or preserving the tab's origin (i.e., its scheme, host, and port). This is useful when you need to visit the same path on different domains or ports (e.g. on staging and production).

So many parallels with my experience moving from the US to France. Things aren't as easy to get done here. I'm pretty hot today with my struggling, portable AC. We have to wait for our laundry to air dry. I miss having a garage for tools and equipment. I missed American customer service. But: I can stroll to a bakery here. The vegetables taste. I walk my son to school and we hold hands and talk. It took me a while, but I don't start panicking when someone in the family needs to see a doctor or visit an urgent care center. And that customer service I missed? I realized that it often (but not always) manufactures a feeling of (in)superiority. I now assume loud cracks are engine backfires, not gunshots. On the other hand, I recognize that I was lucky to start life in the US. I wasn't the best student and I dropped out of college (albeit for financial reasons I may not have had here), but I was still able to get a good job in software development—credentials aren't as important in the US as they are in France, in my experience.

It's been confusing to me that so many people have treated markdown as the lingua franca for agent instructions when their training corpus must be dramatically biased to HTML instead of Mardown.

Markdown only makes sense for us meatbags becuse it's easy for us to edit and version control, but if you're sharing anything where the audience is an agent publicly, HTML must be just as interpretable.

To be clear, I'm not wishing for evidence of whether RTO is good or bad.

I want evidence that proves "it's about cheap layoffs" or "it's about real estate" or "it's because they want to monitor people" or "<insert any speculative reason on this thread>"

Once we have evidence"it's about layoffs" then we can debate whether it's ultimately helpful or harmful to cull headcount that way.

I'm genuinely interested in why RTO is trending. I searched Harvard Business Review, Gartner, and other sources just last week trying to find the rationale, but I wasn't successful. In fact, I found those sources to be a little cautionary. E.g., they say "if you do switch to in-office or hybrid, make sure you actually have metrics to evaluate the effects" and "ensure it makes sense for the actual work to be done by each role".

I also found results suggesting flexible working policies had positive properties like higher employee satisfaction, retention , and a wider applicant pool.

I'm not interested in hearing why the choir here at HN thinks companies are making these decisions, I want to see evidence of their rationale so I can put myself in management's shoes.

I might be too late for you to see this, but I'm curious why your final example requires the function "f" to receive the canWrite channel. I must be missing something. Couldn't the Ordered map signature be:

  func OrderedLoop[A, B any](in <-chan A, done chan<- B, n int, f func(a A))

Instead of:

  func OrderedLoop[A, B any](in <-chan A, done chan<- B, n int, f func(a A, canWrite <-chan struct{}))

Or is there a reason that "f" can't be wrapped in an anonymous function to handle the blocking logic?

I love this post style. Never stop learning friend!

Offline is good for things like your ball sort game or a calculator. But the developers of that sort of thing want to make money, so they sell apps in the app store.

Offline order history is only a marginal improvement on the e-commerce experience from a customer and business perspective, so it's more appealing to us engineers who appreciate it as a feat of engineering prowess.

In other words, offline isn't PWAs killer feature. Besides, native apps can do it too.

PWA's killer features are circumventing the app store and the app store tax and not maintaining two codebases for Android and iOS.

Another Hacker News client would be a good example of a good PWA that you might install to your phone. It could have niceties like "save for later" or special styles applied to your favorite commenters. Offline support would be useful too, of course but not the main reason to develop a PWA.

Uncensored, paid content is another significant use case.

"So... Taxes?"

If we're talking about wealth not income, then no, not really. We don't usually think of asset seizure as "taxes". In other words, one "taxes" flows (like capital gains and wages) and "siezes" stocks (like bank deposits and equity).

"You seem to be positing that it's entirely expected and understandable"

I wasn't making value judgement, but yes, if you look at it with the assumption these wealthy individuals are cold, calculating, self-interested actors, then it's "expected and understandable" to me.

"That seems counterintuitive to me, at least."

I think you're using "intuitive" as a shorthand for "the way things ought to work in a righteous world", where I find incentives and disincentives to be a more intuitive way of understanding the world.

"wealthy individuals in well functioning systems should commit fraud to the detriment of the system that brought them their wealth"

To be fair, it's not necessarily fraudulent to have offshore accounts or to conceal your identity (it can certainly be depending on the circumstances). Technically I have an "offshore" account, I just happen to be living outside the US and a US citizen. I also use mechanisms to conceal my identity when registering domain names, for example. Is it the same thing, no, but these people might not technically be doing anything illegal.

It isn't necessarily true that those systems "brought them their wealth" either. Plenty of them likely inherited wealth that was accumulated long before the current systems were put in place (granted, it could very well have been accumulated illegitimately 300 years ago).

(Again, I'm not saying any of this is how the world should work, I'm trying to look at the world dispassionately and describe how things seem to be)

At the level of wealth we're discussing, these individuals probably have to think about "diversifying" among nation-states. Instead of worrying about whether to short the tech sector, they're worried about a country being invaded and the new puppet regime deciding to nationalize the hydroelectric dam they financed. Or they may be worrying about whether their country of residence will pass a law that the biggest national telcom must sell the government a majority stake (i.e., their share) at a government-mandated price denominated in an inflating currency... with expert bureaucratic efficiency.

So... no, not really taxes.

The authors write that it's "counterintuitive " that in states with low crime and efficient beaurocracies, the uberrich tend to conceal or relocate their wealth more. See:

  "This suggests a counterintuitive result: use of offshore finance is driven not only by negative political conditions such as corruption and lack of civil justice, but by positive conditions, such as regulatory enforcement and civil justice."

But it's not counterintuitive at all. Those people aren't concerned about getting mugged and they're definitely not concerned about how long it takes to get a construction permit in a corrupt country. They're concerned about state-sponsored expropriation.

Given so many of the comments here about tracking the offshore accounts down and confiscating the contents, it's no surprise.

Irrespective of whether their practices are immoral, unethical, unfair, or unjust, they're definitely not counterintuitive.

It's genuinely hard for me to understand how the authors could believe otherwise.

> If you are building a public API for external developers you don’t control, invest in HATEOAS. If you are building a backend for a single frontend controlled by your own team, a simpler RPC-style API may be the more practical choice.

My conclusion is exactly the opposite. In-house developers can be expected (read: cajoled) to do things the "right" way, like follow links at runtime. You can run tests against your client and server. Internally, flexible REST makes independent evolution of the front end and back end easy.

Externally, you must cater to somebody who hard-coded a URL into their curl command that runs on cron and whose code can't tolerate the slightest deviation from exactly what existed when the script was written. In that case, an RPC-like call is great and easy to document. Increment from `/v1/` to `/v2/`, writer a BC layer between them and move on.