“I'm basically giving myself a permanent vacation from being BDFL”

Post by boyter » Fri, Jul 13, 2018, 1:22 AM UTC

cutler wrote: post #559

secure wrote: post #242

Earlier quoted context omitted.

Yes, Larry Page’s first crawler was in Java, and Scott Hassan rewrote it in Python. From https://www.vanityfair.com/news/2018/07/valley-of-genius-exc... : > Scott Hassan: In the fall of ’95, for some reason, I started hanging out with Larry in his office. . . . At the time, Larry was trying to download a hundred pages simultaneously. And I was fixing some of the bugs that he was having with Java itself, and this went…

32,000 pages simultaneously - in 1995? Async has only recently been added to Python, no?

Post by cutler » Fri, Jul 13, 2018, 1:25 AM UTC

sametmax wrote: post #93

It's going to be very interesting to see if things like: - pattern matching - inline exception catching - path inclusion in the built in - more functional tooling - lazy keywors That were BDFL-blocked, will go back to be debated in the mailing list in the next months. And if yes, will the community stands by its root or create a new era ? The consequences of which we will only really see in 10 years. Guido as done an…

Post by wool_gather » Fri, Jul 13, 2018, 1:30 AM UTC

TooBrokeToBeg wrote: post #158

Waterluvian wrote: post #56

Earlier quoted context omitted.

I think that having strong opinions on how others should be developing software is how communities become toxic like this. "Shooting yourself in the foot is your fault for not using a linter that detects accidental misuse of assignment!"

I'm still puzzled to why would a compiler allow assignment in an explicit conditional (outside of loop syntax). It's like a baked-in blindspot that most people just want to ignore for some reason. Some languages actually guard against this well enough (eg Kotlin) and say "don't". Even with guards in place, it's not all that complicated to work around in the edge cases where you might want to do it.

    guard let value = myOptional else {
        // Handle absence
    }
    // Use value

    if let value = myOptional {
        // Use value
    }

Post by emmelaich » Fri, Jul 13, 2018, 1:36 AM UTC

TooBrokeToBeg wrote: post #158

Waterluvian wrote: post #56

Earlier quoted context omitted.

I think that having strong opinions on how others should be developing software is how communities become toxic like this. "Shooting yourself in the foot is your fault for not using a linter that detects accidental misuse of assignment!"

I'm still puzzled to why would a compiler allow assignment in an explicit conditional (outside of loop syntax). It's like a baked-in blindspot that most people just want to ignore for some reason. Some languages actually guard against this well enough (eg Kotlin) and say "don't". Even with guards in place, it's not all that complicated to work around in the edge cases where you might want to do it.

Post by skookumchuck » Fri, Jul 13, 2018, 1:39 AM UTC

dcosson wrote: post #475

TheMagicHorsey wrote: post #427

I don't know if it's just me, but if you read the forums and bug reports related to open source projects, it feels like programmers today are a really entitled lot. The tone that people take when filing bug reports for what is basically free software is reprehensible. People are doing work for FREE to benefit you, and you take a tone with them like you are a prince and they are your royal goblet holders? Who taught t…

I think what you're saying is true in the case of someone just throwing up some code they wrote online without any plan of supporting or developing it further. But once you call it an open-source project, and you have docs and a roadmap and an issues page and stuff, you're making an implicit contract with people who use it that it will do a reasonable job of solving the problem it claims to solve. The user is choosin…