1.  

    I have a 10 year old iPad mini. Works absolutely fine. After the last update the Disney+ app doesn’t work on it and I can’t get Disney+ on the browser. Made me furious at Disney+ but not enough to walk away, so in the end I was not the change I hoped to be.

    1.  

      This response illustrates the number one reason I am not a fan of Zig: its proponents, like the proponents of Rust, are not entirely honest about it.

      In reality, Zig async functions do not suffer from function coloring.

      This is a lie. In fact, that article, while a great piece of persuasive writing, is also mostly a lie.

      It tells the truth in one question in the FAQ:

      Q: SO I DON’T EVEN HAVE TO THINK ABOUT NORMAL FUNCTIONS VS COROUTINES IN MY LIBRARY?

      No, occasionally you will have to. As an example, if you’re allowing your users to pass to your library function pointers at runtime, you will need to make sure to use the right calling convention based on whether the function is async or not. You normally don’t have to think about it because the compiler is able to do the work for you at compile-time, but that can’t happen for runtime-known values.

      In other words, Zig still suffers from the function coloring problem at runtime. If you do async in a static way, the compiler will be able to cheese the function coloring problem away. In essence, the compiler hides the function coloring problem from you when it can.

      But when you do it at runtime and the compiler can’t cheese it, you still have the function coloring problem.

      I think it is a good achievement to make the compiler able to hide it most of the time, but please be honest about it.

      1.  

        He’s very clearly addressing one specific way of using the MIT license and saying that it doesn’t legally work. He’s also directly responding to someone mentioning the usage he’s addressing.

        He’s not using that niche usage as a strawman to attack the general MIT license anywhere in the post. What line are you reading that turns this into a strawman attack on the general license?

        It’s a little concerning that you also clearly didn’t read the article and initially accused him of just wanting to promote his own license (which isn’t even mentioned in the article) before pivoting to calling this a strawman attack on the MIT License.

        If you have a bone to pick with someone please don’t bring that into the comments section of Lobsters. The guy wrote an article: come discuss the merits of that article if you want.

        1.  

          Indeed, it is all a big conspiracy to give devs free legal help with their licensing terms.

          1.  

            I wish more library authors took this approach where using the API is clear and obvious. I’m indifferent on the positional-only arguments even though it leads to cleaner-looking code, but keyword-only arguments benefit the clear and obvious usage.

            1.  

              Yes! 3.1 for Workgroups was also a thing, it was released a few months before 3.11 and… well, yep, it was a thing. If you’re curious, WinWorld PC has a copy. I’m not sure if it’s okay to post it here. It was a pretty interesting system, history-wise: it had a networking stack but IIRC it didn’t support TCP/IP, for example.

              1.  

                But wouldn’t it just be better to avoid that breaking in the first place? Or at least relegate breaks to when a person is intentionally attempting an upgrade, at least.

                1.  

                  I’ve read it. Both your post and the one you refer to put up a strawman (people use MIT license for non-commercial). This is not a reality with any projects with even slightly traction.

                  What I am trying to say is: this post is intellectually dishonest by putting a very niche if not non-existent misread of license (MIT license obviously is permissive and cannot be arbitrarily restricted) into focal point, then attacking it, trying to establish an alternative reality where “non-commercial” open-source is an widely acceptable open-source practice.

                  1.  

                    Also the Xbox Kinect, which was very popular when it first came out.

                    1.  

                      Nope https://www.zdnet.com/article/who-built-microsoft-typescript-and-why/

                      Funny thing is that article mentions the original Typescript team worked with an Office365 team for unspecified reasons. I think that’s referring to the people in Office who built a typed JS compiler that relied on typing in comments (this was well before Typescript’s release). I heard a rumor that Typescript was started from that codebase.

                      1.  

                        Remember the Clojure mindset: once it works, it always works.

                        Lein isn’t going away. I would consider lein going away to be a bad sign for the ecosystem as a whole. Just people are making more modern choices on NEW code, providing no pressure to update OLD code.

                        1.  

                          Cool!

                          So for deps, how would you replace something like https://github.com/yogthos/lein-asset-minifier in a way that could be seamless for my dep build?

                          1.  

                            I use OpenBSD on a lot of my machines, but it’s only a router where I can get at the machine from a non-ssh shell.

                            I work towards having all my machines be state managed anyway (I’m not there, but I work towards this goal), so rebuilding shouldn’t end up being such a pain.

                            1.  

                              I got the impression that the author was trying to get around the typical static vs dynamic typing debate by slightly changing terminology and focus.

                              1.  

                                Isn’t F# also from Microsoft’s (UK) research division?

                                1.  

                                  Twitter is so much more enjoyable when you start blocking. In this case blocking the word “wordle” should suffice.

                                  1.  

                                    It must be very annoying to browse the web then, because by that definition almost everything is noise.

                                    1.  

                                      Z3 SMT solver also comes to mind.

                                      1.  

                                        Lots of unsound things are very popular: gambling, porn etc.

                                        1.  

                                          Why do they want an expression? The function would behave the same if written with early return or with an if-tree.