Not hating the player nor the game. Point was that it's hard to adopt something that one can't be confident will be maintained and supported a year from now.
> For those who use debuggers regularly, would you be willing to share how you learned to use them or any tips and resources that helped you?
I use debuggers a lot. I learnt the most when I implemented my own toy debugger. Everything made a lot more sense afterwards. It also made me realize that debuggers give you only a limited view of what is really going on in a CPU. If you want to truly understand how a program is executed on a CPU you'll need to learn a lot more about CPUs and likely about the specific CPU you work with.
That's a cool idea and I think a fair argument. I learned a lot from watching Ben Eater on YouTube, he manages to explain (and demonstrate!) how CPUs and many other components work really well.
Out of curiosity, what language did you write your toy debugger in?
Not a fair comparison IMO. Jax is low level library used to make ML frameworks while pytorch is a full blow ML framework.
In terms of is it worth using it - that depends on what you're doing. If you just want to start with ML training probably not. If you have something already and you want to take it to next level (e.g. influence how training and inference work) than it's a good choice. You might be interested in looking into flax or haiku instead of using vanilla Jax. These are closer to pytorch.
Nice effort. Would love to see more open source work from tech companies in this space. I remember working on a healthcare product (which involved HL7) years ago and it was a pain. The lack of documentation and any supporting tooling was "mind blowing".
I wonder if all the banks in the world consume more energy vs Bitcoin network? What if we didn't have these big institutions that employ hundreds of thousands of people to basically increment and decrement a counter in a computer. Imagine all costs that we wouldn't have to incur (e.g transport to work, operating buildings, etc). Today's banks seem very archaic.
The banks are also serving several orders of magnitude more people than the bitcoin network. The energy usage per transation isn't even close to being comparable.
Even with all of the inefficiencies of modern banking, by comparison cryptocurrency is like lighting oil wells on fire.
Purpose of any modern bank is to make money for its shareholders. It does so by taking money on one side and lending it on the other. Lending is inherently a risky business and that risk must be managed. It's unfortunate that in this process people who deposit money can lose it. Essentially, those people take risk of losing money for <1%.
There is also another aspect to banks which is to provide ability to exchange money. That part of banking doesn't generate a lot of revenue compared to loans so it receives a lot less attention.
Not sure if this is due to Google "being unhealthy" or overall economy contracting. If the drop / stagnation is due to economy contracting these results are still very good.
I think about these frameworks as products. They are meant to solve specific problem for specific audience. I also think we need to start differentiating between different classes of developers. I think a good analogy is car mechanic vs mechanical engineer. when a car is made there will be a lot of need for mechanical engineering. Once it's on the road and needs to be fixed is when car mechanic comes into play. You need to decide whether you want to be mechanical engineering or a mechanic - skillet is very different.
