154 karma · joined August 26, 2017
This would not protect against stack overflow or similar environmental panics.
In Numba it only recompiles for dimension changes i.e. if shape changes from (7, 10) to (2, 10, 12). However numba does not integrate AD so if you need that, JAX is probably your best bet unless Enzyme matures and you want to look into integratig it with numba.
Edit: I feel like I should point out that I agree that RTFM is an incredibly offensive term, but some form of answer like: “it is covered in the documentation” actually conveys one important bit of information: The answer can actually be found in the documentation.
Personal anecdote: I read one of Ray Kurzweils books in school back then, completely misunderstood how neural networks worked and ended up making a markov model chatbot with single word states.
Frankly in my reading of your question you come across as very arrogant, where you use the guise of a “serious question” to show off your knowledge cryptography.
> For most software projects, there should be a way to buy a commercial support license.
> For many, such a license should be required for use in any org which is over X employees.
I interpret this to mean that: You impose in the license of the software that if you are an organization over X employees, you are not entitled to use and distribute the software under that license instead you must hold the commercial license or you must in addition to the normal license hold the commercial support license.
In the first case(where the normal license grant does not apply to sufficiently sized orgs) I believe you impose a restriction of use on the software in a specific field of endeavor in contradiction with section 6. in the OSD.
In my view it is clear that if you require an additional commercial support license for some users but not everybody you violate section 7. as the rights to the program is restricted for some parties (orgs with over X employees only has those rights if they also acquire a commercial support license):
“7. Distribution of License
The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.“
Now it might very well be that you had another mechanism in mind for imposing your requirement of “Orgs over X employees must hold a commercial support license”. In that case it might very well be a different mechanism in the definition that conflicts with your mechanism, but I cannot see how you can achieve your aim of imposing a requirement on usage of the software for some users without contradicting the spirit of the open source definition which says that you must grant the same rights to all users of your software.
I cannot find in your link [2] what you mean by the phrase: “In practice, there are many "Open Source" licenses that allow paid licensing [2]”. Usually when people speak of paid support licensing for open source (or free software) that is an OPTIONAL support license or a separate commercial license(see the QT license options) that you acquire the software under, and it does not conflict with either free software or open source software. My opposition is only your stipulation that the commercial license be required for some users of the software, and it is this requirement part that I claim conflicts with the Open Source Definition. Note that it is perfectly valid to charge people to obtain your open source software from you, but you are not allowed to impose restrictions on their ability to redistribute that software (including source) to others for free, hence this is probably not the solution you are looking for?
*you as in the driver, I am aware that the parent poster is not necessarily driving a loud vehicle.
> As far as I can tell, the L in "FLOSS" is typically "libre," not "Liberal." I feel like the author is vastly and misleadingly inflating his relevance in this post.
I worked as a model quant for a year a couple of years ago in a bank in the team responsible for developing and implementing the derivatives pricing models. Everything was written in (a lot of) C++, but I suspected and still suspect that you could get the same performance by leveraging one of the off-the-shelf deep learning libraries with a lot less code. Maybe you would have to write a few central components in C++ and assembly to get the exact same performance. I am glad to see someone actually following through on that idea.
I am not passing a judgment on whether decentralized currencies are good, but I do not understand why central banks would move in that direction.
* At least the Fed seems to be: https://www.bloomberg.com/opinion/articles/2019-03-08/the-fe...
While I understand the technical differences, I cannot see why from a policy perspective the government or the central bank would be interested in a cryptocurrency like solution? Rather with the current system and Know Your Customer regulation for the banking system, they have tighter control with money transfers since they are all ultimately between bank accounts tied to named entities. I think it is more likely that we abolish physical cash than migrate to a more decentralised currency.