110 karma · joined September 23, 2020
Same for imperative languages with "parameter list" style. In python, with
def f(a, b): return c, d
def g(k, l): return m, n
you can't do
f(g(1,2))
but have to use
f(*g(1,2))
what is analogical to uncurry, but operate on value rather than function.
TBH I can't name a language where such f(g(1,2)) would work.
Another possible consensus would be that copyright don't exist, and anyone can copy proprietary or copyleft work and improve it. Nobody would be harmed in such situation, original author still have its copy. I would have no problem with such state - but it must be same for everyone, not just FOSS.
In the other thread you argued that AI output is not copyrighted.
Do you think I can take proprietary code and lauder through AI to get a non-copyrighted copy of it, then modify to my needs? How can I obtain the proprietary code legally in the first place?
MIT asks for credit. GPL asks or credit and GPL'ing of things built atop. Unlicense is a free gift, but it is a minority.
AI reproduces code while removing credit and copyleft from it and this is the problem.
- often you use decimal fraction on output and input anyway
- it's slower, even slower with bigint
- no square root, sin, and so on with rationals
head {display:block; background:Canvas; color:CanvasText;}
meta[content] {display:block; padding-bottom:1em;}
meta[content]::after{content:attr(content); display:block;}Also DFA has no looping as in "doing infinite computation steps over finite input".
"One can be 4x more performant when led by empowering rather than bureaucratic boss" is plausible. "Unskilled, slacking person will achieve nearly as much as skilled one in same team" is questionable.
Double Commander is an acceptable substitute of Krusader on non-Unices.
C23 is about to
- add keywords that was valid identifiers before
- remove K&R parameter syntax
- change semantics of the most popular function argument list declaration
- forbid representations other than 2's complement
Opera did that when version went up from 9 to 10. Too many websites looked at first digit of version rather that doing feature discovery back then.
Useragent string of Opera 12 is "Opera/9.80 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/12.18".
It works and is better than placing password in clipboard and than "xdotool type $pass". Likely worse than proper integration with password consumer.
To illustrate, let's look at summaries of top popular projects (by number of commits, because that's what Apache shows on stats page):
> Camel is an Open Source integration framework that empowers you to quickly and easily integrate various systems consuming or producing data.
> Apache Flink® — Stateful Computations over Data Streams [here image of taking events and DB as inputs of process]
> Airflow is a platform created by the community to programmatically author, schedule and monitor workflows.
??? Why would i need them?
> Apache Spark™ is a unified analytics engine for large-scale data processing. > spark.read.json("logs.json").where("age > 21").select("name.first").show()
> Lucene Core is a Java library providing powerful indexing and search features, as well as spellchecking, hit highlighting and advanced analysis/tokenization capabilities.
These tell or show what they do. Good.
For some, it is execution environment for Web Apps, where backend-frontend split and communication over network is accidental, basically internal for App. Either run in latest version of one-three of top browsers or go away. Logic and security checks can be implemented in frontend in order to save server's electricity, because it will be run in browser anyway.
For some, it is Protocol which is implemented by User Agents to fetch resources exposed by Servers and display it to them. User Agent can be unmodified or heavily customized top browser, lynx, dillo, curl, telnet, specialized tools[1]. JS should be optional nearly always. It is them who is controlling what his computer is executing. From this thinking goes aversion to 30-seconds loading sites, lack of Progressive enhancement[2] going to the point of requiring JS to load blog post, emphasis on server-side validation.
From this difference come many misunderstanding and sometimes conflicts.
[1] https://weboob.org [2] https://en.wikipedia.org/wiki/Progressive_enhancement