1. 3

    I agree with the conclusion at the end: inner curiosity of one of the greatest drivers for excellence in lots of things, true for coding too.

    1. 1

      I wonder if there is an easy option in MySQL to turn off fsync?

      1. 4

        docker run --mount type=tmpfs,destination=/var/lib/mysql -e mysql is one way: stores the data in a RAM disk. There’s a bunch of configuration options too, but this is easier.

      1. 1

        Interesting! I wonder if there will packages/libs building around pwnedkeys apis to provide security scanning of the TLS certs/GPG keys.

        1. 4

          I’ve got a 9360 model with the QHD screen, after years of hating on laptops because of the sub-par characteristics. Very satisfied with it.

          My criteria is pretty much just:

          • A screen resolution that isn’t 1377x768 (It’s 2018! Why are these still shipping?)
          • Screen must not have adaptive brightness, or at least have the ability to completely disable this
          • WiFi/Bluetooth must not be Broadcom. Linux support is a crapshoot when it comes to these chips.
          • User upgradeable components (Thankfully, Dell provides an user manual describing how to replace the M2 hard drive and wireless chip)
          • Standard UEFI implementation (i.e. ability to disable Secure Boot)
          • Standard keyboard layout (funky layouts are a pain)

          Unfortunately, laptop vendors are only in the game to make a buck, and their offerings aren’t acceptable. At least Apple does this right.

          1. 2

            Screen must not have adaptive brightness

            Isn’t that a completely software thing? Are there implementations of adaptive brightness directly in firmware now?

              1. 1

                As bwasti has commented, it was enabled implemented in firmware. However, you were unable to enable/disable the functionality until a recent firmware update made it available. I find that crazy!

              2. 2

                Standard UEFI implementation (i.e. ability to disable Secure Boot)

                Any laptop that ships with Windows (or can ship with Windows) and is using x86 architecture must have “disable Secure Boot” option:

                (…) Intel-based systems certified for Windows 8 must allow secure boot to enter custom mode or be disabled

                Source: https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Secure_boot_criticism

                1. 2

                  Or even better, add your own key to the chain of trust, remove the ones that aren’t yours, and sign your own kernel.

                  1. 2

                    Exactly. That’s what I do (with sbupdate), additionally booting directly kernel as an EFI application (so kernel acts as a bootloader, no GRUB necessary!).

                2. 2

                  A screen resolution that isn’t 1377x768 (It’s 2018! Why are these still shipping?)

                  I bought one of these recently for development. Since my environment is command line based, extra pixels don’t really help much; they can make everything smaller, but there are practical limits on what’s comfortable/what my eyes can do. Probably my “ideal” resolution would be a little higher, but 1080p on a 13” laptop really requires software scaling to be usable, which introduces its own share of bugs and quirks, so it’s not as simple as “more is better.”

                  The unexpected/unplanned bonus is that it can run VMs at 1024x768 which allows it to run legacy systems without scaling, making them much nicer. I don’t spend that much time emulating legacy systems, but I do use them to test my software on older environments, and it’s kind of a feature to have them work so well. It also needs less GPU/uses less power/has better battery life.

                  Not saying it’s the right thing for everyone, but maybe the answer to “why?” is because some of us actually want them.

                  1. 1

                    Maybe they (1377x768) are shipping because people still like them? I’d prefer my x230 for work on the go over both of the T4x0p I’ve used any day. So yeah, it’s a bit apples to oranges, but afaik the XPS 13 has a similar resolution compared to what the T4x0p has on 14” - I find it cramped and small.

                    1. 2

                      The X200s isn’t really any bigger than the X230 but has a much better 1440x900 display.

                      1. 2

                        Not saying stuff can’t be improved, but this was re: QHD ( 2560 × 1440 ) - and I’m absolutely not a fan of huge resolutions. At least until the support in Linux (with external screens) is on the level of OSX. Not that I’m a huge fan of OSX, but I’ve never seen any problems with Retina MBP + Normal screen vs Linux on HiDPI + normal screen.

                      2. 1

                        1377x76

                        Sorry for being nitpick here, but it’s actually 1366×768. It still exists because it’s much cheaper than a FHD (1920x1080) screen. In a extremely low margin laptop business, leveling the parts cost is major revenue optimization strategy (even for Apple). Same reason why low-powered crappy netbooks still exist.

                    1. 9

                      One thing I always want to tell people about commit messages:

                      There’s no length limit.

                      In fact, write as much as you can. Go crazy. Write some more. Explain. Talk about how your day went. Tell us how you found the problem. Put benchmarks that show why your change makes things faster. Show the stack trace or test output that you’re fixing. Quote other people. Put an email chain in the commit message.

                      In a well-curated commit history, commit messages become source-level documentation available via an annotate/blame operation. Most people hate writing documentation, but commit messages are about the only time when our tools force us to write something. Take this opportunity to really write something. It’s the only time when writing is really required in any way. There’s no need for a length limit because most of the time the commit messages are hidden away, and most interfaces will hide the full commit message anyway (or can easily be configured to do so).

                      If you want practice jamming lots of information into a small amount of space, that’s what the first line of the commit message is, but after that, don’t feel constrained by length limits.

                      These are examples of my favourite kind of commits:

                      https://www.mercurial-scm.org/repo/hg/rev/4fb2bb61597c?style=gitweb

                      https://www.mercurial-scm.org/repo/hg/rev/ed5b25874d99

                      https://www.mercurial-scm.org/repo/hg/rev/1423ff45c322

                      https://www.mercurial-scm.org/repo/hg/rev/dd028bca9221

                      https://www.mercurial-scm.org/repo/hg/rev/8d5584d8345b

                      1. 1

                        I agree in that length limit hinders rich information being put into the commit to better explain the intent and reasons of the changes. However, GitHub/GitLab hasn’t really make it easy to read long commit messages in their UI, which is a bummer.

                      1. 2

                        Dr. Kai-Fu Lee is on his book tour - this Wired piece is probably part of that. I’ve been to one of his book tour event in NYC. Two of major points he raised were: all exist AI models requires massive amount of data to train, China currently has more internet users so bigger data set and also have more user data per user due to lack of privacy legislations/concerns thus far. So combining those two aspects, it’s clearly an advantage for China to implement / iterate AI models faster.