Posts by NicolasRinaudo@functional.cafe
 (DIR) Post #AXpMIR6Xn51EnKcJaC by NicolasRinaudo@functional.cafe
       2023-07-18T18:42:02Z
       
       0 likes, 0 repeats
       
       @finlaydag33k @lan I, again, disagree that his reply was indecent. His project, his time, his rules. You might disagree, and might conduct yourself differently in his position, as his perfectly your right. I suspect he wouldn’t call you a muppet in a public space if you did.
       
 (DIR) Post #AXpOIgsEIHiTi1nur2 by NicolasRinaudo@functional.cafe
       2023-07-18T19:04:37Z
       
       0 likes, 0 repeats
       
       @finlaydag33k he is being addressed by name though. This is not a case of somebody asking "the project maintainers" to work for free quia nominor leo, but of asking *this specific individual* to do so.Another aspect that I feel is worth considering is that he merely told them no (quite firmly). You insulted him.
       
 (DIR) Post #AXpOnQg4YoVISGm7Wa by NicolasRinaudo@functional.cafe
       2023-07-18T19:10:10Z
       
       0 likes, 0 repeats
       
       @finlaydag33k ... did you crop out the message *just* above the first one in your screenshot intentionally?
       
 (DIR) Post #AXpPN7XPCPUrWEjwky by NicolasRinaudo@functional.cafe
       2023-07-18T19:16:25Z
       
       0 likes, 0 repeats
       
       @finlaydag33k I'm merely going to repeat my earlier point that he was addressed directly, and did not in fact participate in that discussion before. The thing you were trying to disprove by showing an incomplete and misleading screenshot.Also, the fact that he merely denied an offer to work for free, while you insulted him.
       
 (DIR) Post #AZrKkqxivVdyuBfVAm by NicolasRinaudo@functional.cafe
       2023-09-16T09:57:04Z
       
       0 likes, 0 repeats
       
       One of the (many) things I found interesting at ScalaDays was this slide (picture by Jamie Thompson, whom I don't think is on mastodon).There has been a lot of complaints that Scala was paying more attention to the academic side of things than the industrial one, and I think this makes it clear exactly why that is the case.
       
 (DIR) Post #AZrKkt0zILRXGtD8XQ by NicolasRinaudo@functional.cafe
       2023-09-16T10:26:58Z
       
       0 likes, 0 repeats
       
       @IsomorphicDude in a way I feel that’s fine. If industrial actors won’t put their money where their mouth is, I’m not sure why Scala development shouldn’t be directed by those who actually pay for it.
       
 (DIR) Post #AZrKkuFugKyb7TCZRQ by NicolasRinaudo@functional.cafe
       2023-09-16T20:22:49Z
       
       0 likes, 0 repeats
       
       @IsomorphicDude I don’t think it’s fair to researchers, who write a language for research purposes, to tell them to focus on the needs of people who will not help instead. There’s a way for companies to get what they want, they’re just not using it. And still complaining, by the way.
       
 (DIR) Post #AZrKkvrAjING5Jdq9g by NicolasRinaudo@functional.cafe
       2023-09-16T20:50:37Z
       
       0 likes, 0 repeats
       
       @SusanPotter @IsomorphicDude that’s completely fair but also a little besides the point - I’m not saying industrials should invest more in Scala, which is really not for me to say. My point is that you can’t both complain about the language not being developed the way you’d like while at the same time not paying for it to be developed the way you’d like.
       
 (DIR) Post #AZrKkxDBgvZwHsww6q by NicolasRinaudo@functional.cafe
       2023-09-17T09:55:28Z
       
       0 likes, 0 repeats
       
       @SusanPotter @IsomorphicDude oh I don’t think anybody expects either money or contributions to the Scala language, not from individuals. I’m sure everybody’s grateful when it happens, but it’s not expected. I’m specifically talking about companies, or company owners, complaining about the (recent?) academic focus of the language, and there has been a few. Some financial institutions, ziverge, …
       
 (DIR) Post #AZrKkxrbGfuAJDrD6G by NicolasRinaudo@functional.cafe
       2023-09-17T09:57:50Z
       
       0 likes, 0 repeats
       
       @SusanPotter @IsomorphicDude I’m being very careful here to speak specifically of the Scala language, not its open source ecosystem, which are two very different beasts. Not sure where the bit about expecting individual contributions came from, don’t think it was stated or implied anywhere, so I can only assume the scope of your argument is larger than mine.
       
 (DIR) Post #AZrKl0FQP49Phh1GVs by NicolasRinaudo@functional.cafe
       2023-09-17T11:27:21Z
       
       0 likes, 0 repeats
       
       @SusanPotter @IsomorphicDude all valid points but again: I’m specifically talking about the complaints that scala is focusing on academia (because that’s who’s paying the bill). Whether or not that focus (real or not) is the cause of scala’s perceived decline is an interesting conversation, but a completely different one, isn’t it?
       
 (DIR) Post #Ab2B8DcPCWmXx5hahk by NicolasRinaudo@functional.cafe
       2023-10-22T15:03:26Z
       
       0 likes, 1 repeats
       
       Here's the video of my ScalaDays talk on the expression problem: https://www.youtube.com/watch?v=GAERiuRRZhUHad a lot of fun with that one and, even if it's not the most advanced topic I've covered, I think it's quite important.
       
 (DIR) Post #AczWEf8xwdYuDg8B8a by NicolasRinaudo@functional.cafe
       2023-12-18T21:19:17Z
       
       0 likes, 0 repeats
       
       Slightly confused by something very silly - ; in rust. My current model is, it's used to separate statements. This seems simple enough, but the bit that I find hard to get used to is, since it separates statements, your last statement cannot be followed by a ;, else it means a statement comes after - which rustc will infer to be (), apparently?
       
 (DIR) Post #AczWEoSRJbUF6gJMEy by NicolasRinaudo@functional.cafe
       2023-12-18T21:31:41Z
       
       0 likes, 0 repeats
       
       It doesn't help that the rust book seems to finish all of its unit-returning blocks with a ;. Aren't they optional? Or is that a convention?Is there anything I can read on the subject? I know it's a weird thing to get stuck on, but I don't like it when things I should understand keep behaving in ways I don't expect.
       
 (DIR) Post #AczWEoVd7k2TGZnuDI by NicolasRinaudo@functional.cafe
       2023-12-19T22:10:30Z
       
       0 likes, 0 repeats
       
       @kubukoz no they're allowed, just not *always* necessary, and that's the bit that I struggle to get my head around
       
 (DIR) Post #AczWRABwKpQrzKTzs0 by NicolasRinaudo@functional.cafe
       2023-12-20T05:43:21Z
       
       0 likes, 0 repeats
       
       @alexelcu @kubukoz but then why the convention of adding one after the last expression in a block, if that last expression evaluates to unit?It can’t be for consistency’s sake, since you must not add one if your last expression does not evaluate to unit.
       
 (DIR) Post #AczXB3HIN7AJrnrwhc by NicolasRinaudo@functional.cafe
       2023-12-20T05:51:43Z
       
       0 likes, 0 repeats
       
       @alexelcu @kubukoz i would get that, if it wasn’t sometimes a type error. This is the part that bothers me, the inconsistency.
       
 (DIR) Post #AczXjCQiqpag65YroG by NicolasRinaudo@functional.cafe
       2023-12-20T05:57:51Z
       
       0 likes, 0 repeats
       
       @alexelcu @kubukoz sure - if you write a function that returns,say, u32, and your last expression terminates with a semicolon, that’s a type error. The compiler will reject it, because you’re trying to return unit.So for functions, you must not use trailing semicolons. For procedures, you should by convention.
       
 (DIR) Post #AczZJQ9xNkkd3eYTBI by NicolasRinaudo@functional.cafe
       2023-12-20T06:15:35Z
       
       0 likes, 0 repeats
       
       @alexelcu @kubukoz no i mean exactly that. And i do find it confusing, that you sometimes can use a semicolon, sometimes should , and sometimes absolutely must not, depending on the return type of your function’s type. I’ll get used to it, but it feels inconsistent at the moment
       
 (DIR) Post #AcziKsp3CPR7paY3rE by NicolasRinaudo@functional.cafe
       2023-12-20T07:56:42Z
       
       0 likes, 0 repeats
       
       @alexelcu @kubukoz I understand the compiler's behaviour given the constraint it has, yes, and given these constraints it makes sense.I just don't really understand the constraints. The fact that, depending on the return type of your function, you should (but don't have to!) or absolutely must not use a semicolon to terminate your last expression feels counter intuitive to me.I'm not saying it is in general, maybe absolutely everybody in the entire world finds this perfectly natural and reasonable. Maybe I will, too, with practice! Just, at this point in time, I find that design decision hard to understand and would love a concrete reason for it. It feels like there must be one.