erik_seaberg

On call may page teammates for help, but they might be on airplanes or go camping or do other things that take them off the grid (primary and secondary must not). I would really hesitate before paging someone who's on vacation, but he would probably have his phone (not laptop).

gccgo supports dynamic linking and foreign functions, and allegedly generates better-optimized code. The default compiler can share OS threads between goroutines, but not other languages (I guess stacks are no longer segmented but they could be copied?)

Previously: https://news.ycombinator.com/item?id=41641324

I wish Common Lisp had integrated type declarations with TYPEP and CHECK-TYPE, instead of punting with "consequences are undefined if the value of the declared variable is not of the declared type," i.e., sucks to be you.

I don't think it's that easy because I've literally never found an apartment with it.

> A move only the reigning search engine king would dare.

It was a reskin of Limbo, which they had released at Bell Labs without a lot of traction.

> Most new languages never overcome basic performance issues.

Poor performance is a problem with an implementation. Poor expressiveness is a problem with the grammar and semantics of every implementation, especially when you don't let end users extend the language to their needs.

The customers voted for longer hours and wider selection. Now we see online shopping and home/locker delivery taking over.

It's typical for salaried positions in tech to be exempt. I was last paid hourly by a body shop nearly 20 years ago.

That's because apartments and houses have indoor power, which took a while. Neighborhood streets still don't have outdoor power at every curb.

Only with market discipline, by making that company compete with others representing pools of workers. A union chooses not to do that.

NASA had a FORTRAN bug in 1963 that

  DO 10 I=1.10

wasn't a loop but an initialization of DO10I. The decimal point (not comma) made the spaces not matter.

It's an average imperative OO language that has a lot of devs, a lot of libraries, and world-class optimization of GC and method dispatch (Sun had acqui-hired the StrongTalk team).

The server may or may not have seen the request, and the https://en.wikipedia.org/wiki/Two_Generals%27_Problem proves it impossible to know in every case (no matter how many acks, the last could be dropped). A request that alters state should be retried using the same idempotency key, and the server should try to ack with whether the requested work already happened.

That's hard to imagine. In big tech it's the team manager who decides that standups should happen and when (maybe this is an expectation from higher-ups). He always joins unless running late.

This book burning vibe is pretty extreme. I wish there were a reliable way for everyone to write pseudonymously. (I don't as a reminder that legal action against an employer could baselessly unprotect the whole team.)

But the cloud is just some other BOFH's computer.

I'm thinking of cases like Stream#flatMap where I might be prepared for what a lambda (probably a method ref) could throw, yet still can't use it because exception lists for the Stream interface methods had to be declared statically years ago.

> Since more than 82% of EV users in Norway charge their vehicles at home, housing associations can apply for grants that subsidize up to 50 percent of the cost of buying and installing communal chargers.

I'm familiar with parking in your own garage and charging, or parking on the street with no infrastructure, but I don't understand how far away these chargers would be and whether they're usable overnight.

Lambdas broke checked exceptions. You can't declare that you throw whatever a generic lambda might throw, so they quickly devolved to "I throw nothing (only unchecked)." The "I throw everything" alternative is rarely used because it spreads virally through every caller.

How many cars sold are new? How many owners have garages for charging?

Tire dust doesn't seem to contribute to smog. https://en.wikipedia.org/wiki/Smog only mentions burning tires.

It doesn't really matter so much. Company B needs to know whether to beat an offer from company C for $95k or only $80k. Your salary history only affects employers that aren't trying to compete effectively, because what you made then isn't what you could make now.

And the end of the ZIRP-driven shortage is telling us that what we used to make is not locked in forever.

I once half-assed a tool that summarized deployed builds, importing a CSV to Google Sheets as a team UI. Well, one day the import noticed one of those commit IDs must be a number because it doesn't contain any letters, and then a formula used exponential notation to create a hyperlink that didn't work.

Edit: Now that I think about it, it might have been only digits with a leading zero that was dropped.

This has been likened to a sorting hat for dads.

https://x.com/andykreed/status/1741888763083604090

I had never heard of "top byte ignore," but it reminds me of the macOS migration to "32-bit clean" software as the hardware began to support more than the low 24 address lines.

https://en.wikipedia.org/wiki/Classic_Mac_OS_memory_manageme...

The other approach is CompressedOops, where instead of wasting pointer bits (and maybe using them for tags), Java's HotSpot VM chooses to only store a 32-bit offset for an eight-aligned heap object if the entire heap is known to fit within 2^(32+3) which is 32 GB from its base address.

https://news.ycombinator.com/item?id=22398251

And didn't somebody write about creating a large aligned arena for each type and essentially grabbing the base address of the arena as a (non-unique) type tag for its objects? Then the moving GC would use these arenas as semispaces.

I have seen a linter that requires

  class User {
    public String getName() { ... }
  }

to have a doc comment explaining what getName does and also what it returns. Before git, they sometimes needed to see who wrote it and when.

That table is a self-limiting problem. It's true that failure is likely, but optimizing for that outcome never adds value, and it would probably make me quit.

Production-grade data needs to be redundant across regions to outlive a disaster. I was glad to hear that SQLite replication exists, but it's an add-on (Litestream) that isn't strongly consistent nor multi-master.

Also U+2012 FIGURE DASH (for things like phone numbers), and probably U+2212 MINUS SIGN (aligned with plus). Everyone usually defaults to hyphen-minus though, and all bets are off.

Having been on call 24/7 for production services, I found "git log" absolutely essential, almost more so than the latest code. We were usually expected to roll back rather than take additional risk fixing forward on outages, so the question was "roll back to what?"