Scalpers don't buy tickets and not sell them. The most scalped concerts are obviously the most attended

> fans can’t afford the tickets

See above. I assume what you are upset about is that rich fans are the ones going.

> less connection with the artists, less interest in music overall

I think you need to explain your logic here.

I agree. The question remains - why do U.S. municipalities universally and repeatedly fail to successfully implement rapid transit at an efficient price point? Buses, trains, and subways in America have ever-growing budgets (both in absolute and per customer mile terms) with ever-declining quality of service. Just asking for more tax revenue again and again is not the solution.

[1] https://www.citizen.org/article/biden-doj-2024-corporate-cri...

Epic's employees reaped the gains while it rained in the form of paychecks. While it sucks that people are losing their jobs, those individuals received (much of) the upside of this investment and their jobs never would have existed in the first place had the investment not been made. Their paychecks are not being clawed back. Shareholders (including executives who are largely paid via out-of-the money options) are bearing the costs. Consumers also benefit from increased competitive pressure on Valve and subsidized game prices.

Would it be "better" if Epic had not invested in the Epic Game Store and paid a dividend or conducted a share buyback?

Comments URL: https://news.ycombinator.com/item?id=47443844

Points: 2

# Comments: 1

> For a web service, that usually means one log event at the end of every request.

The point of a log, as I have seen it used, is to understand what's going on during a request. Yes, some of that is timing / success / failure information, but you also need:

- Logical tracing - at a high level, what decisions did we make (authz, business logic) when serving this request

- Partial failures or warnings - the request may have succeeded, but we may have failed or timed out a call to a dependent service and delivered a partially degraded response as a result

- Tracepoints to support active development - how often do we hit a certain codepath (to help developers roll out or deprecate features)

It's useful to distinguish between "context" (things we know about a request), timing, success, and plain old logging (using human language to describe to an operator what the system is doing). Context should be included with every line - I strongly agree with OP's proposal of wide events, don't make operators ever JOIN if you can avoid it - but it won't always be the same because we learn things about the request as we process it. Yes, if you wait until the end of a request, you will have maximal context, but at the loss of fine-grained detail during processing.

Unfortunately, the US and many other countries have chosen the other path (sporadic enforcement with severe punishment) largely because it's easier to implement. There's a lot of momentum to change this but it's politically difficult at least in America.

And presumably they wouldn’t be shy about telling us if they had.

Also HN: No, not like that

Comments URL: https://news.ycombinator.com/item?id=46346214

Points: 283

# Comments: 185