Ayyar

I'm using an OLED Thinkpad X1 Yoga as my primary laptop, and I was afraid of burnin, though almost two years in I have not had any problems.

Admittedly, I was very concious of the burnin issue from day zero and have the screen setup to hide toolbars etc off the screen. I always go into full screen mode with the terminal.

The colors are gorgeous and I feel such a raw sense of visceral delight when using the OLED screen.

At least at the two year mark, I see no problems. Separately I've had an OLED TV for 4 years and I have seen no burnin problems there either.

I have wanted to switch to a newer laptop but I dread going back to a non OLED screen.

This is a great development, and if the choice is between me being a bit more concious of tweaking software settings to go fullscreen and hide toolbars vs. amazing colors, that's a limitation I'm willing to deal with.

Macbook Pro to X1 Carbon convert.

I could not disagree more with you as a developer.

- The X1 Carbon lets me use Nvidia GPUs using an eGPU.

- It has a much, much better keyboard. On my MBP, I hit this problem: https://youtu.be/4QDsqWkUvXQ

- The high end models don't force you to get a touchbar.

- I love having more port diversity and number of slots vs. the MBP. No dongle life for me.

- As an added bonus, I got the X1 Carbon Yoga, which has an OLED display. The display is gorgeous with fabulously dark blacks.

The one thing that I miss from the Macbook pro is it has a much better trackpad. But overall, I am very happy with the switch, and it's overly simplistic to just say "Macbooks stand on their own".

Though overall, I couldn't be happier with the switch.

As a Linux user, I am happy about this change because Nouveau is just not an acceptable driver.

I hope that this puts pressure on both Nvidia and Ubuntu to have a better default.

Thank you for the reply, appreciate you reading the comments so thoroughly.

My top piece of feedback is considering some form of a strict mode, where your vision is not best effort support support for some legacy tool for a language, but fabulously amazing knock your socks off good support for users who take the time to invest in making their build friendly with your search index.

It might seem tempting to go after the longest common denominator audience here, but personally I think it's far more valuable to show users how code search can be amazing if they do their part to invest in it, vs. code search being "kind of sort of useful" if you have a fallback.

And maybe my Xoogler experiences are showing here, though Bazel / Kythe are in my opinion the perfect vehicles to realize that vision.

My understanding of this is the Google approach is to have all builds in the cloud using Forge i.e. infrastructure that lets you cloud builds.

This means you can do hermetic builds, and thousands of other engineers can reuse the build artifacts you produce.

And in the particular context of tools such as code searching, your build artifacts update the code searching index pretty quickly post committing a change.

Xoogler here.

Internally as Google, you have a substantially power powerful version of Codesearch, which is semantic, i.e. it relies on actual binary artifacts produced by builds to index code. All of the code base uses Blaze ( open sourced as Bazel) to express the rules.

The version of code search here is cute, but it's still not a full blown structured semantic code search, which I really miss. Searching for and browsing code on Github feels underwhelming in comparison, because you wan't really find or explore code the way you think of it.

You can see a demo of semantic Codesearch tech externalized here at:

https://blog.bazel.build/2017/12/14/introducing-bazel-code-s... http://cs.chromium.org

For example if you click on a header or a symbol, you can get proper cross references to a symbol.

https://cs.chromium.org/chromium/src/pdf/document_loader_imp...

I really wish they add structured code search to Cloud Repos, even if it comes with some heavy restrictions such you must use Bazel as a build system.

It would be a killer feature, and to my knowledge there is no equivalent to such a product. IDEs offer some similar overlapping functionality, though other code search engines still operate in terms of strings rather than actually real binary symbols ( I think Sourcegraph is trying here but that still does not seem to use some kind of accurate and structured information like you have in the code, it still seems not use build rules).

This is Deep Learning 101 level material, rather than an advanced insider technique.

It's even listed in the Tensorflow tutorials: https://codelabs.developers.google.com/codelabs/tensorflow-f...