I thought I understood recursion
functional.christmas
I thought I understood recursion
1–10 of 124 posts
Re: I thought I understood recursion
#2What's up with the influx of christmas domains here on HN?
Re: I thought I understood recursion
#3What's up with the influx of christmas domains here on HN?
Perhaps it correlates to the influx of Christmas?
Re: I thought I understood recursion
#4What's up with the influx of christmas domains here on HN?
I wondered the same, eventually found https://bekk.christmas/ with some more information.
Re: I thought I understood recursion
#5What's up with the influx of christmas domains here on HN?
It's a collection of advent calendars from a norwegian agency with fun TLDs: https://blogg.bekk.no/introducing-bekk-christmas-ad01660ccad...
Re: I thought I understood recursion
#6What's up with the influx of christmas domains here on HN?
‘Tis the season
Re: I thought I understood recursion
#7> My background is in OO programming, mostly using C#. C# being the versatile language it is, I have had the perception that whatever you do in other programming languages, you can with a little more code and hassle achieve in C# as well. If need be, I can program C# using a functional paradigm. And, of course I use recursion all the time. I know all there is to know about recursion.
IME there are two kinds of programmers: ones who learned a single language deeply and have almost religious confidence that it's the best thing ever, even if they try to approach other languages with an open mind (i don't blame them, i was like that a couple decades ago, too) and some who understand that tools are just that - tools, which you should pick accordingly to the problem you want to solve, because the other way ends up in a tail-wags-dog situation. the blog post sounds like the author has realized that and started a journey from the first type to the second type, which is to be commended. good job.
Re: I thought I understood recursion
#8Ooh, what's the time and space complexity of `primes`?
Re: I thought I understood recursion
#9> My background is in OO programming, mostly using C#. C# being the versatile language it is, I have had the perception that whatever you do in other programming languages, you can with a little more code and hassle achieve in C# as well. If need be, I can program C# using a functional paradigm. And, of course I use recursion all the time. I know all there is to know about recursion. IME there are two kinds of progra…
So if you consider some stack to be inferior (maybe because its highly inconsistent in its design or it only runs on closed and locked down platforms or whatever) you still should just dismiss it as 'oh its just a tool' instead of accepting that it's shitty and makes you miserable when working with it? Why wouldn't I want to work with best thing ever if it helps me keep my sanity every day?
Do you want to use something that makes you miserable? Is any language including those designed by 3 year old 'just a tool' that is to be used despite obviously being shitty?
Never understood that argument.
Re: I thought I understood recursion
#10> My background is in OO programming, mostly using C#. C# being the versatile language it is, I have had the perception that whatever you do in other programming languages, you can with a little more code and hassle achieve in C# as well. If need be, I can program C# using a functional paradigm. And, of course I use recursion all the time. I know all there is to know about recursion. IME there are two kinds of progra…
It's not obvious to me why choosing the right tool for the job is better than choosing the right job for the tool.