I thought it was very interesting, but maybe also incredibly naive politically ? it's like he's re-discovering alienation under capitalism. A wood-worker could do the same argument, there's the "official" wood-working…
It's already on my bank app since a couple of week, but I haven't tried it yet.
You should really do a Bayesian fit for such predictions and give confidence intervals, it would probably show that the uncertainty is very high in these cases.
That works well to get around patents btw :)
If it taste as good and is cheaper, sure.
I think there's quite a bit of "quiet work" going on that isn't very visible. Personally I've been happily using Julia for work everyday for years. When the language was younger there was "big" updates that were news…
I gave it a try, I asked to do a reddit like forum and it did pretty good but damn I quickly hit the daily limit of the $20 pro account, and it took 10% of the monthly just to do the setup and some basics. I knew LLM…
Also tried it on a small project, it did ok finding issues but completely failed doing rather basic edits, like it lost closing brackets or used wrong syntax and couldn't recover. The CLI was easy to setup and use…
Yeah that was a missed opportunity fore sure, joining forces 8 years ago would probably had yield better results that the current situation.
Funny how the already weak case for not working on Julia instead of creating a new language is becoming even more flimsy : FAQ: > Why not make Julia better? > We think Julia is a great language and it has a wonderful…
>And it's basically not possible to escape that environment until the plane lands Ever heard of closing your eyes ?
I would add: - Good integrated test system (and test culture in the community) - Super good package/environment manager - Great integrated documentation system - Good version control practices in the community - Awesome…
I thought it was very interesting, but maybe also incredibly naive politically ? it's like he's re-discovering alienation under capitalism. A wood-worker could do the same argument, there's the "official" wood-working…
It's already on my bank app since a couple of week, but I haven't tried it yet.
You should really do a Bayesian fit for such predictions and give confidence intervals, it would probably show that the uncertainty is very high in these cases.
That works well to get around patents btw :)
If it taste as good and is cheaper, sure.
I think there's quite a bit of "quiet work" going on that isn't very visible. Personally I've been happily using Julia for work everyday for years. When the language was younger there was "big" updates that were news…
I gave it a try, I asked to do a reddit like forum and it did pretty good but damn I quickly hit the daily limit of the $20 pro account, and it took 10% of the monthly just to do the setup and some basics. I knew LLM…
Also tried it on a small project, it did ok finding issues but completely failed doing rather basic edits, like it lost closing brackets or used wrong syntax and couldn't recover. The CLI was easy to setup and use…
Yeah that was a missed opportunity fore sure, joining forces 8 years ago would probably had yield better results that the current situation.
Funny how the already weak case for not working on Julia instead of creating a new language is becoming even more flimsy : FAQ: > Why not make Julia better? > We think Julia is a great language and it has a wonderful…
>And it's basically not possible to escape that environment until the plane lands Ever heard of closing your eyes ?
I would add: - Good integrated test system (and test culture in the community) - Super good package/environment manager - Great integrated documentation system - Good version control practices in the community - Awesome…