bryal
> You literally used the word "comical" in the previous post. English is not my language, but if I search for a definition, I get: "comical: arousing or provoking laughter".
One can make an attempt at humour without the whole audience necessarily finding it funny. I was not confused by SubzeroCarnage's wording at all.
You call them out for lacking communication skills and being offensive, but if anything you're the one with lacking English comprehenshion, lashing out because of a misunderstanding on your part.
But I'd also love to be able to do the project without ESP IDF, using `no_std` and smaller specific crates instead. The solution for using ESP IDF in Rust is fairly convenient, but it does require some extra steps and the disk usage is not insignificant. A pure Rust solution would be more elegant.
[1] https://esp-rs.github.io/esp-idf-svc/esp_idf_svc/mqtt/client...
[2] https://git.sr.ht/~jojo/huelia/tree/esp32-c3_and_mqtt/item/p...
To be clear, I don't mean to disparage the author's decision. Programming can be an artistic endeavour, where personal enjoyment trumps most concerns. If programming C is what keeps you motivated, go ahead and use it! Just be aware that this may make your software risky to use and rejected in many real-world situations.
Most of the powers the monarchs in Scandinavia supposedly have can't actually be enforced in reality, so they really don't have as much power as you seem to think.
On the opposite end, is North Korea a democracy just because it says so in their constitution?
Seriously. Opus is close to transparent already at 128kbps.
> 100% agree with this conclusion.
Except the reason that Biden isn't doing as great as he could be is because he's too centrist. He isn't getting enough of the far-left vote because of their apathy towards his agenda, which does not reach far enough by far.
As an example, Florida did not vote for Biden. Not because he's too left, but because he's not left enough. The proof for this is that they also just voted to increase the minimum wage to $15. The democrats wanted a candidate with broader appeal than Bernie, but they only succeeded in alienating the social-conservatives even further.
ML shouldn't be applied where it's not necessary.
[0] http://www.cse.chalmers.se/edu/year/2017/course/DAT350/
[1] https://wiki.portal.chalmers.se/agda/pmwiki.php
[2] https://agda.readthedocs.io/en/latest/tools/emacs-mode.html
You're not going to have as much time available for disciplining and raising your kids properly when you have to spend most waking hours of the day working multiple jobs, just to afford putting food on the table. The "breakdown of family discipline", as you call it, is just another consequence of being poor.
Seriously, there's just no winning for low-income households in the US.
By your logic: 1. Ducks have feathers 2. All birds have feathers 3. Therefore, all birds are ducks
In any case, Haskell didn't get its polymorphism from any OOP language, so the point is moot. ML was first to introduce parametric polymorphism in 1975 — Java/C#/etc with their "generics" came later. Even ad hoc polymorphism with type classes was proposed 7 whole years (1988) before Java was even released (1995). And sure, the paper mentions that OOP has to solve similar issues, but "solving the same problem" ≠ "being the same solution".
Haskell type classes have nothing to do with OOP in the least, and as far as I know, Ocaml is a counterexample rather than an example to your point: they included OOP becsuse it was all the hype at the time of conception, but the OOP features are really quite unpopular today.
As you were completely off with Haskell, I can't exactly trust that you're right about any of the other languages "running back to OOP". If anything it seems to me the languages that started out as multi-paradigm FP/OOP have become more purely FP over time, as OOP has failed to prove its worth.
Aah, alright. I've written a ray tracer that uses an (L)BVH before, so I'm familiar with how it works for ray tracing. What I couldn't figure out was how you'd use an acceleration structure for ray marching. Now that you spelled it out though, I suddenly think I get exactly how it would work.
> ... ray marching has a slightly higher complexity in practice than ray tracing since it takes multiple iterations ...
Great reply, thanks! It made a lot of sense.
> ... there are some amazing tricks you can play with ray marching to reduce the number of rays, and because ray marching often better utilizes a GPU.
Interesting. Now I'm gettin quite interested in exploring ray marching more.
Rust is very nice, but when you've used it for long enough you start noticing the warts. I especially miss Higher Kinded Types from Haskell, and I'm constantly reminded of the lack of Functor and Monad etc. At some point I simply realized that for most applications, the generally lower performance of Haskell and the GC is really not a problem at all. I mean, it's not like it's Python slow—it's just a bit slower than C/Rust. The more advanced type system of Haskell is just so nice, that I feel it's worth it.
Throwing police at the problem is only putting a band-aid on the symptoms, but ignoring the root cause. Violence will only beget more violence in the long run.