The article makes a convincing argument that Haskell compilation is too slow for the fast code generation of AI. But python?
I have yet to experience a RHEL major version change that did not blow up all my tiny simplistic python scripts. I see the following options for using python:
* run inside the container it was developed in
* build your own python interpreter and environment and libraries and never use python pieces from the OS (i.e., act like a container without using one)
* keep different versions of the code for different OS versions and use AI to rewrite all the code for the new OS version
Start to consider third party dependencies, and none of those feels tractable without an AI assist.
I've dabbled in C device driver code and kernel version differences were my only problem, not C. My perl scripts never break. My bash scripts rarely break. My dabbling in erlang didn't suffer from language version differences. My little elisp hasn't broken. Only python has inflicted this level of version pain. I have a colleague who says java has the same version pain as python, and from what I've seen from Jenkins maintenance he may be right, but I don't have colleagues who want to read java code, so I haven't written my own.
As an ancient one (graduated college 1981), my use of AI is very conservative: look things up. Generate code I can read and understand in less than 30 minutes. This is working well for me, because when the AI botches the answer, I know quickly. It either works or fails fast: there's no importable function by that name, that keyword isn't in the language, that only works in a different version of the OS. I never ask it to do something I couldn't do myself in 10x the time (spent fixing typos or missing punctuation). If I ask it to do something I don't know how to do, I create tests - usually informal - to ensure that I understand what the code is doing. If the syntax is unfamiliar, I make it explain what it's doing, and then I informally test that explanation (usually toy examples at the command line). You must learn to do these things regardless of where the answers come from - the Internet, a journal, a book, a colleague. Otherwise >>when<< it fails, you will not be able to reason about the causes for the failure and how to find a correction.
I've seen copyright notices that explicitly forbid use for AI training. Would this "transformation" argument still hold in such cases?
For example:
No Generative AI Training Use
For avoidance of doubt, Author reserves the rights, and grants no rights to, reproduce and/or otherwise use the Work in any manner for purposes of training artificial intelligence or machine learning technologies to generate text, text to speech, voice, or audio including without limitation, technologies that are capable of generating works in the same style or genre as the Work, unless individual or entity obtains Author’s specific and express permission to do so. Nor does any individual or entity have the right to sublicense others to reproduce and/or otherwise use the Work in any manner for the purposes of training artificial intelligence or machine learning technologies to generate text, text to speech, voice, or audio without Author’s specific and express permission.
What is being licensed by the End User License Agreement (EULA) is the copyright on the code and its artefacts (executable bytes, etc.) - you can't have an EULA without having the copyright to license.
The first amendment protects from U.S. government censorship (with exceptions for national security and commission of otherwise illegal acts, such as child molestation, fraud, or yelling fire in a crowded theater). The suppression here is a civil matter in which the author signed a contract not to "disparage" and would suffer civil penalties (monetary, other negotiated constraints) for violating the contract.
I dealt with physical paper tape on only three or four occasions in the early 1980's, each time terrified of a jam or tear. It seems in this case it's a read-once operation, which is plausible. Read-many, not so much. Punch cards are orders of magnitude more reliable.
This year, the first $15,000,000 of an estate is exempt from federal taxes, so unless it is on top of a different $14,000,001 in estate net assets, the estate tax (a tax on the estate) on that $1,000,000 house is $0. [0]
Some U.S. states have an additional inheritance tax (payable by the inheritors). Those rules vary. [1]
Explain to me how qualified immunity is better than any ill it is supposed to address? And how is it that if you sue the government and win, then the judgement doesn't automatically award reasonable legal fees?
The left hand scale is presumably dollars per ounce of silver. The right hand side is "margin requirement ($)". I can think of two interpretations of that, neither of which make sense to me. The first interpretation is that one recently needs a $25000 margin per $90 ounce of silver instrument - obviously absurd. The other interpretation is that once you have a $25000 margin you can buy unlimited silver instruments, which is only barely less absurd. How does reality work?
My 2007 Corolla odometer has been at 299999 since 2019. I've replaced the transmission once, but the rest is original, aside from expected maintenance - tires, brakes, fans, etc. - and an added stereo.
If your colleagues just don't feel the benefit of the extra .lit file, is there a way to pull their changes to the derived files into your own .lit files and to keep the .lit files in a parallel version control repo or branch?
Nope. The current system may be misdirecting 95% of labor, but until we have sufficiently modeled all of nature to provide perfect health and brought world peace, there is work to do.
And not only that, but most >>changes<< to software shouldn't happen, especially if it's user facing. Half my dread in visiting support web sites is that they've completely rearranged yet again, and the same thing I've wanted five times requires a fifth 30 minutes figuring out where they put it.
I'm a python newby, so please correct the following: The first function looks quadratic in time and linear in stack space, while the second function looks linear in time and constant in stack space. Memoizing would convert the first function to linear in time and linear in space (on the heap instead of the stack). For python, wouldn't I always use the second definition? For Haskell, I would use the [1..] syntax which the compiler would turn into constant space linear time machine code.
I do a lot of ansible which needs to run on multiple versions, and their yaml typing are not consistent - whenever I have a variable in a logic statement, I nearly always need to apply the "| bool" filter.
That style is not restricted to Asian speakers. Reading (a translation of) Gabriel Garcia Marquez's "One Hundred Years of Solitude" with its deep recursive layers of introducing a topic and then giving the backstory thereof - the firing squad from the first paragraph gets explained a hundred or so pages later - I immediately recognized my wife's normal pattern of discourse. I then congratulated her on having a Nobel prize winning speaking style :-)
I have yet to experience a RHEL major version change that did not blow up all my tiny simplistic python scripts. I see the following options for using python: * run inside the container it was developed in * build your own python interpreter and environment and libraries and never use python pieces from the OS (i.e., act like a container without using one) * keep different versions of the code for different OS versions and use AI to rewrite all the code for the new OS version
Start to consider third party dependencies, and none of those feels tractable without an AI assist.
I've dabbled in C device driver code and kernel version differences were my only problem, not C. My perl scripts never break. My bash scripts rarely break. My dabbling in erlang didn't suffer from language version differences. My little elisp hasn't broken. Only python has inflicted this level of version pain. I have a colleague who says java has the same version pain as python, and from what I've seen from Jenkins maintenance he may be right, but I don't have colleagues who want to read java code, so I haven't written my own.