Throwaway23459

Maybe he only knew C as you say. I did C++ professionally for a while. Not properly, just updating models in derivatives trading systems. I remember reading 3 Scott Meyer books, the Effective Programming series, at the time, they were a tour de force. Loved that guy. I've lost track of everything since 11 or whenever they introduced move semantics. One day I might go back to it.

> [Paraphrasing] Is Verse supposed to be an easy language for beginners ?

Yes! Well that was the point of my comment. Maybe you have a different interpretation of 'Learnable as a first language' from the article, which is fine, not interested in arguing about that.

Has it got currying? Partially applied functions passed around in folds and traverses are horribly difficult to read for beginners. Example: an Advent of Code solution posted in r/haskell for Day 10 this year, tell me how long it takes you to understand the function cycleStrengths.

   signalStrength cycle x = cycle \* x

   cycleGaps = [19, 40, 40, 40, 40, 40]

   cycleStrengths = foldr a (const []) cycleGaps . (\x -> (1, x))
     where
       a n r (i, xs) = signalStrength m y : r (m, ys)
         where
           m = i + n
           ys@(y : _) = drop n xs

From: https://www.reddit.com/r/haskell/comments/zhjg8m/advent_of_c...

Personally I love this headscratching stuff, but I would not ever dream of subjecting it upon a beginner programmer.

My lecturer in second year, > 20 years ago mind, said we are learning C, because C++ is C with an ugly object oriented graft on top.

> so-called 'lenient' evaluation strategy which is neither strict nor lazy, but somewhere in-between

Sounds like we are still clinging on to laziness in some regard, I wish we could get shod of it entirely. Although laziness makes doing Leetcode problems in Haskell really fun, Idris got it right when they opted for strict evaluation for predictable memory performance.

You appear to be reading more into my post then I intended. The point I was illustrating is that there is no cruft in React.

Try and keep your posts factual.

Most recent papers, in NLP at least, are so sparse on detail that it is impossible to reproduce their models. And then there's the compute cost, as at least one other poster has mentioned.

React and Angular are both blazing fast, and are definitely not pointless. Open create react app, spin up a page with 50000 buttons, compare that to a plain js version, then come back and tell us about the atrocious performance.

Well google use all of their own internal 'frameworks', so you can't really use their web applications to judge the rest of the web.

Does Whisper ever respond with "I don't understand" or does it always try to amble on and give an answer, no matter the confidence of the prediction?

I worked through a popular Introductory Category theory text. Did all the problems and made sure I understood everything in there really. It became clear by the end why some mathematicians like category theory. It lifts some results in certain areas to a higher level of generality.

As for me it helped me with understanding some of what was being discussed on r/haskell. It didn't help one iota getting me a Haskell job though, failed every Haskell code pairing I've done.

> What really bites is when you need to change the type signature of a load-bearing > interface and find yourself spending hours changing every place where the type is > used only to see if your initial stab at something is feasible

Editor/IDE should be able to do this in a few seconds.

> None of these techniques is relevant anymore given that all the hardware has Z buffers

I remember the js13k game jam winner this year used BSPs. Linked below.

https://github.com/SalvatorePreviti/js13k-2022

There's no agreed way to organise a functional codebase. You end up with thousands of functions, can you imagine the mess a big team is capable creating? With some discipline I suppose it could work, but you would need some organising principle and some serious discipline. Object oriented is organised by virtue of the object paradigm.

Laziness principally. In my opinion, laziness is as difficult as managing pointers in C++. Laziness makes memory usage of your program difficult to reason about as it becomes large.

I know! I recently went for a job where when I got to the system architecture rounds they were asking about sharding and setting up a server/db for global level massive scale. I only know what I've done, which is set up EC2/ECS instances that handle small to medium, not massive amounts of load. I don't know this stuff because I've never done it, yet I was expected to come up with a Michelangelo solution.

Seems to have been airbrushed off the site now.

Full stack, been doing this a few decades now. Not really. Every new front end feature just feels like such a chore. You tire quickly of building new CRUD endpoints and pages pretty quickly. You need to write so many mind numbing tests with dynamically typed languages. I really dread writing test after test. I do enjoy hunting down bugs. Performance optimisation can be fun too. But sometimes the bugs are ones that I introduced, so anyone who has worked in this business long enough knows it weighs on you a bit to be the cause of a problem. I tried to get into strongly typed functional programming a bit, but realised after a couple of years doing Haskell that it just swaps one set of problems for another. I've always liked games, currently trying to do a late career change into gaming. I think I just need to believe in the underlying product, then I can put up with the pain. Pay is dreadful though. Getting a new job now is quite time consuming, you need to solve riddles online while someone watches. I think the market is going to become quite illiquid, maybe salaries will go up?

Speeding up the build could be done in other ways, were they using esbuild or something fast previously? Probably not.

The memory usage saving is really not a big deal, load up your favourite news web page and look at the memory it chews up in comparison.

As for the preference implied for python over js, that's fine, but the choice is not binary, typescript is my preference for a React project, for example.

Reduction in LOC is slightly misleading, JSX creates a lot of lines.

It would be interesting to see a proper write up on the data React couldn't handle.