1. 5

    Going to see the incredibles 2!

    1. 2

      Same! Really hyped, it’s been too long since the first one.

    1. 5

      I’d appreciate it if any NixOS users here could offer a little advice: I’ve played a little with Nix, and read about NixOS, and I’m interested in switching because there are enough things that tempt me:

      • Defining my workstation setup in a single, easily understood, interpretable file (I sort-of-but-not-really have this now with an org doc that contains notes + shell commands to be run on a new Fedora install).
      • Nix shell for ad-hoc (and not!) envs for work stuff (honestly, this alone might be the killer feature).
      • The apparent ease of writing my own nix packages.

      However, I’ve become used to the following and I don’t want to lose them:

      • Up-to-date kernels. I use the AMD opensource drivers and they’re a work-in-progress (I see the brand new Impala release has 4.14, the previous release was 4.9; my “old” Fedora 27 install already has 4.15).
      • Wayland, for all its foibles, has fixed my screen tearing woes and in its up-to-date Fedora/GNOME incarnation works very well for me. I don’t want to go back to X.
      • Things working; Fedora is boring in a good way, I can get on with my work with very little fiddling.

      Is NixOS for me? Would a combination of Fedora + Nix perhaps serve me better?

      1. 4
        • boot.kernelPackages = pkgs.linuxPackages_4_15; has worked for me in both 17.09 and 18.03
        • Not sure about wayland support, I think you need to start gnome-session with wayland manually? Anyways here is the tracking issue.
        • Things just work and stay working for me after I got my configuration.nix set up - not a lot of maintenance needed imo.
        1. 3

          This is exactly what I was looking for, thank you.

      1. 4

        The mention of (now deprecated) btrfs had me scroll up to check the date: 2015. Time flies!

        1. 5

          (now deprecated) btrfs

          Link to deprecation notice? I was under the impression that it was still under active development.

          1. 10

            I assume @varjag is referring to this redhat doc, stating that:

            Btrfs has been deprecated. The Btrfs file system has been in Technology Preview state since the initial release of Red Hat Enterprise Linux 6. Red Hat will not be moving Btrfs to a fully supported feature and it will be removed in a future major release of Red Hat Enterprise Linux. The Btrfs file system did receive numerous updates from the upstream in Red Hat Enterprise Linux 7.4 and will remain available in the Red Hat Enterprise Linux 7 series. However, this is the last planned update to this feature.

            1. 3

              Some people are still developing it, but Red Hat is no longer interested.

            2. 4

              SuSE still uses btrfs by default, AFAIR, so it’s not deprecated as such, but it also doesn’t have a lot to recommend it……

              There is bcachefs, still in development; but even if it is successful, I would assume it would be at least a decade before it would be a real competitor for even present-day ZFS (which presumably would not stand still).

            1. 1

              Cute! My only issue with it is that the aspect ratio of the screen is not the gameboy’s 1.11:1 ratio, instead being wider. This seems to result in the top of the screen getting cut off, as seen here. Otherwise, it looks great!

              1. 3

                Title reminded me of this talk on Emacs, titled “The Editor of a Lifetime”

                1. 5

                  It’s been that for me (well, I started using it in my early 20s).

                1. [Comment from banned user removed]

                  1. 14

                    Rubbish.

                    Direct access to all the XUL/XPCOM/whatever messy internals from extensions was a huge disadvantage. Firefox developers couldn’t change anything in the browser because some damn extension would break. Also these extensions barely worked in multi-process mode.

                    A well defined, standardized extension API is a massive improvement. (And it makes me extremely happy as an addon developer — same code works in Chromium, Firefox and Edge!!)

                    Actual technological advantages were added to Firefox recently, with Stylo, OMTP, and (not in release yet) WebRender. (In the future, WebRender will even render fonts and vector graphics on the GPU!)

                    1. [Comment from banned user removed]

                      1. 10

                        Advantages for developers directly translate to advantages for users. Namely, performance, security and reliability.

                        nobody gives a shit

                        This is literally false – Firefox has gained market share significantly with the “Quantum” release.

                        Statistically, nobody gives a shit about powerful extensions. (IIRC Mozilla telemetry reported about 50% Firefox users having zero extensions!) Most people only care about performance.

                        And yet, Mozilla is constantly adding new APIs to WebExtensions to help angry ungrateful nerds get their unnecessary features back. (Most recently, tab hiding has landed, allowing implementations of Tab Groups and such.)

                        1. 4

                          Statistically, nobody gives a shit about powerful extensions. (IIRC Mozilla telemetry reported about 50% Firefox users having zero extensions!)

                          That is a big leap there, the other 50% are users too, not to mention those that do not report telemetry.

                          The addon changes did make life easier from some extension developers because they get to use the same code for chrome and firefox. Not so much for others, extensions that shell out to the operating system or binary components - these are now much harder to do - just like in chrome.

                          While I appreciate the improved speed, and the new shiny features I hope they don’t lead down a path that, drops support for many other capabilities e.g. does supporting webrender mean dropping support for targets that lack opengl 3?

                          And yet, Mozilla is constantly adding new APIs to WebExtensions to help angry ungrateful nerds

                          This is hardly fair. Many times those ungrateful nerds implemented extensions for features that were later made part of firefox that put the browser ahead competition - adblocking, video autoplay block, decent password managers, etc. Not to mention the reason why they are adding new APIs is because they removed the old ones :)

                          1. 3

                            (IIRC Mozilla telemetry reported about 50% Firefox users having zero extensions!)

                            Not debating the rest of your points, but I would assume that the people who do use more “powerful extensions” are more apt to turn off Mozilla’s telemetry (I have no data to back this up, just a thought)

                    1. 2

                      I’m going to start reading The Little Schemer this week, and once I’ve finished that I’m probably going to dive into either The Seasoned Schemer or SICP

                      1. 2

                        Such a delightful book! He threatened to write The Little Javascripter for a long time. I wish he’d do it!

                      1. 4

                        Perhaps better named Russian Roulette Linux.

                        1. 4

                          Bash Russian Roulette is a thing:

                          [ $(( $RANDOM % 6 )) -eq 0 ] && rm --no-preserve-root -rf / || echo "click"