bla3

It's called the "short string optimization".

It's a joke, not a proof. I thought it was funny.

The advantage of a monorepo in this particular case is that it makes easy things easy: if you want to remove a parameter of a function in some library and that function has just a few callers in dependent executables, you can just do that in a single commit. Without a monorepo, you have to do the full-blown iterative rollout described in the OP even for small changes, if they cross VCS boundaries.

> "Proof by contradiction. Assume P=NP. Let y be a proof that P=NP. The proof y can be verified in polynomial time by a competent computer scientist, the existence of which we assert. However, since P=NP, the proof y can be generated in polynomial time by such computer scientists. Since this generation has not yet occurred (despite attempts by such computer scientists to produce a proof), we have a contradiction."

Love this :)

Hint: It's much easier if you don't know linear algebra.

You must be a macOS or iOS user.

If the headline being the valuable content is true, it suggests there could be a business that's like a newspaper that only publishes headlines without articles.

I'm not saying this to refute your comment! This might actually be a valid idea.

Isn't this missing a leading " to terminate the string it's interpolated into?

(2012)

GitHub Excited Intern

It's amazing what we can achieve if we set our minds to it!

Dude was done with Google at around comic 280 and didn't notice for almost 100 more comics.

You can read them as hit pieces, or as investing advice :)

No.

Electron and Edge Webview2 are basically the same: they both wrap Chromium in the end, possibly with some downstream changes. So this is primarily a branding exercise, and maybe and admission that Microsoft isn't upstreaming some improvements to Chromium.

All social media, be it Tinder or elsewhere, is people's (possibly exaggerated) highlight reels. Don't compare your day-to-day average to that. The only thing worth comparing yourself is past you, to see if you're moving in the right direction. (But stop doing that once you get older :) )

Go spends a lot of effort on making sure the language is backwards compatible. Which is great! Weird they're so nonchalant about tooling changes.

There are a few good YouTube channels of strong system programmers doing live coding. Watching videos takes time, but you can pick up lots of techniques, big and small, by watching people work.

Since you're looking at rust, https://www.youtube.com/user/gamozolabs/videos could be a good fit.

> it's now clearly within reach that graph ends more than 20 years ago and implies that some important threshold should've been crossed 15 years ago. Did that happen?

At least it was founders who benefit from doing this, instead of salaried folks working to enrich their boss.

D'oh, you're right.

This is Java, not JavaScript. The exponents table was likely of integer type. Then it works.

> At the very least, the loop based code could be cleaned up significantly.

Seems like the loop based code wasn't so bad after all...

I like Mary Schnich's sunscreen speech mentioned at the start: https://www.chicagotribune.com/columns/chi-schmich-sunscreen...

> after so, so many years.

The location permissions system preferences behavior changes in more macOS updates than not. The current system hasn't been around for that long.

"To prepare for the 4-week release cycle starting in M96, we'll move from our current 6-week release cycle to a 10-week release cycle for M95."

Sounds funny, but stuff happens :)

Seems like a good thing to match the chrome cycle.

Sounds like we'd describe a linker the same way :)

A simple linker doesn't need symbols for a link plan, or even a link plan (assuming you just load all input files and ignore static library indices). It doesn't even need a symbol table, it can do a full scan of all input files every time it needs a symbol during relocation processing. The symbol table is just a performance optimization.

Again, this changes for a real linker with weak symbols, comdats, section gc, etc.

I baselessly claim that a simple linker that doesn't need to read elf can be < 200 lines :) If you want to do elf, I think that becomes difficult.

I wouldn't lead with symbols in an article focused on understandability.

A linker in first approximation just concatenates files.

In second approximation, it splits every input file into N parts (code and data, basically), then concatenates the corresponding parts in each input file, and writes all concatenated parts ("sections") to the output file.

It needs to fix up references at the end and it needs symbols for that, but that's kind of an implementation detail.

Even diagnosing duplicate symbols is a convenience feature if you look at things this way.

Symbols become more important if you want to write a "real" linker that supports weak symbols and symbols imported from dynamic libraries. But for the understanding the basics, it helps to deemphasize symbols, in my opinion.

Sounds like you learned a valuable lesson about believing things you read on the internet today :)

Taking it down means others won't be able to learn this lesson.

It's the first release by a new release manager as far as I can tell: https://www.phoronix.com/scan.php?page=news_item&px=Tom-Stel...

So hopefully just temporary transition pain while the new manager learns the ropes.