tmsr - Search: lines of code

billymg: ok, so trilema logs uses `word-wrap: break-all` on the entire content column. i used jfw's suggestion of `white-space: pre-wrap` on the code column because it wraps long lines without splitting individual strings

mircea_popescu: there's the argument that very long lines are a symptom of poor writing habits, and if one re-wrote his code such that "fitting code to viewport" is never an issue the code won't thereby suffer (and if this means ditching idiocies like "object oriented" and dead-end wanna-be nonlanguages -- well, it's a public service).

ossabot: Logged on 2019-12-12 09:36:02 dorion_road: http://logs.ossasepia.com/log/trilema/2019-12-12#1955110 << I'm thinking to keep it simple along the lines of : 1) register a key, 2) install a V, 3) maintain a blog where you : a) maintain a code shelf , b) publlish your work plans , c) publish articles for context on your vpatches, 4) maintain an irc connection to converse with people (point out '6 months' reading the log is recommended for

dorion_road: http://logs.ossasepia.com/log/trilema/2019-12-12#1955110 << I'm thinking to keep it simple along the lines of : 1) register a key, 2) install a V, 3) maintain a blog where you : a) maintain a code shelf , b) publlish your work plans , c) publish articles for context on your vpatches, 4) maintain an irc connection to converse with people (point out '6 months' reading the log is recommended for

mircea_popescu: ^ link above should be alf's "only so many lines of code within before madness", but i can't find it.

a111: Logged on 2014-11-05 04:47 asciilifeform: as a student, i was once told by a greybeard: 'you're young, but know that you have X lines of code in you. after that - log cabin.'

lobbes: asciilifeform: sounds good. So far it ate 160k lines of #e archive. However, found a bug in my znc2tmsr code where if line payload was null, my thing did not output a ';' at the end

mircea_popescu: you give out a little bit of yourself each time. and eventually, down the road, after enough dealmaking, you discover there's nothing actually left. this is very much the equivalent of alf's point re "only so many lines of code in one before insanity", except for business people, those who are too dumb to realise it on their own.

a111: Logged on 2019-05-29 23:30 mp_en_viaje: http://btcbase.org/log/2019-05-29#1916138 << this incidentally is as fine a measure of code quality as could ever be hoped for : DLC, "disentangled lines count", the number of lines which can be changed.

mp_en_viaje: meaning in a 160k lines of code, 78 can actually be edited.

mp_en_viaje: http://btcbase.org/log/2019-05-29#1916138 << this incidentally is as fine a measure of code quality as could ever be hoped for : DLC, "disentangled lines count", the number of lines which can be changed. ☝︎☟︎

mp_en_viaje: But if you don’t like <pre> or it looks stupid in your browser no matter what styles you try to apply to it or something similar, you might want to use a <div> instead. A <div> will result in more source - GeSHi will have to insert whitespace markup - but in return you can wrap long lines of code that would otherwise have your browser’s horizontal scrollbar appear. Of course with <div> you can not wrap lines if you please. The highlighter demo

billymg: the patch removes tinymce, most of the importers, and some unused plugins -- overall reduction of about 15% in lines of code and close to 20% in size on disk (since some of the files removed were minified files containing only one line)

mircea_popescu: but the 1900s gold dubloons do NOT work for this. because lines of code, or "eyeballs upon cell cultures" are NOT like barels of fish.

a111: Logged on 2018-11-05 09:56 diana_coman: http://btcbase.org/log/2018-11-04#1869273 - a config file seems the better choice, yes; I'll add it to the list to move the keys to a config file and update the tests to read from config file; that should actually meet asciilifeform's requirements too since the code will not contain the >80cols lines (although the config files will, of course)

diana_coman: http://btcbase.org/log/2018-11-04#1869273 - a config file seems the better choice, yes; I'll add it to the list to move the keys to a config file and update the tests to read from config file; that should actually meet asciilifeform's requirements too since the code will not contain the >80cols lines (although the config files will, of course) ☝︎☟︎

mircea_popescu: 32 is a very simple thing and absolutely easy to lift and package into 52 lines of code in the .adb file + 130 in the .ads file so 182 all in total1, comments and two types of input (string or raw array of octets) included."

Mocky: when stepanoff starts talking about a guy who writes 77k lines of code and earns a raise, should instead get a $77M fine, i started listening more closely

spyked: http://btcbase.org/log/2018-07-22#1837147 <-- gah, sorry for the abstruseness. more explicitly: the bot goes through each line in http://www.loper-os.org/pub/ro_eng_expr.txt and if it finds one for which the query is a substr of the entry, it displays the definition. not very effective, it's intended as a very simple (<100 lines of code) demo for next trilemabot patch. but imho there's room for improving it even without adding google ☝︎

asciilifeform: iirc it was mircea_popescu in an earlier thread who had analogy where 'lines of code are like ammunition issued to cannoneer , to spend with his best effort' or how did it go

a111: Logged on 2018-06-06 12:59 mircea_popescu: spyked, re the other thing, i expect the item can be both massively trimmed and significantly improved still. the discussion was carried in principle ("so manty lines!") not really objectively, "why this exact line for each line". i think it's entirely possible even the final product, as a conceptual ideal, may exceed (reasonable!) expectations of "how long code should be".

mircea_popescu: spyked, re the other thing, i expect the item can be both massively trimmed and significantly improved still. the discussion was carried in principle ("so manty lines!") not really objectively, "why this exact line for each line". i think it's entirely possible even the final product, as a conceptual ideal, may exceed (reasonable!) expectations of "how long code should be". ☟︎

spyked: http://btcbase.org/log/2018-06-05#1820747 <-- I dun disagree at all. as far as the thought experiment goes, I still wonder, though, whether those edges of productivity follow from *all* the lines of mp-wp code and is more than the sum of each, or whether there's a lot of extra crud in there. perhaps overly naively/boyishly at the time, I started my (still ongoing) experiment the other way around ("what is the minimum number of lines to ☝︎

mircea_popescu: to be clear, i'm not for a second disputing that such piles of lines of "code" are a scandal and an outrage before god. but i wish to know what we're to do.

mircea_popescu: spyked, i don't see how this distinction works. what does "eliminate word from vocabulary" even mean, you'll take out some classes/dependencies/whatever out of a pile of lines of code, leaving a them-shaped hole behind.

mircea_popescu: "# Code lines of documents with the same version number are always identical. There may be interim modifications of comment lines. The most recent document of PROVABLEPRIME can be obtained from: http://s13.zetaboards.com/Crypto/topic/7234475/1/" << the barbarity.

phf: there's a couple of places where regex is used. exclude filters files by name, (so --exclude=.*c will skip those files by regex), exclude lines filters lines (obviously is not compatible with v), and there's also a function grabber, it's a little piece of code that ensures that, say, c function headers or certain pattern matching lines are in the hunk context

gabriel_laddel_p: incidentally, my CLIM implementation is 99,676 lines of lisp code, as calculated by sloccount just now

mircea_popescu: asciilifeform 12:22 <@fenn> how many lines of code is OCC? <<< see, he is asking the right question. i knew my patience will be dug back out from the hole by the unfolding of events!

a111: Logged on 2017-07-08 02:35 sina: and you contend the actual final implementation of such a thing will actually be less lines of a code than the existing thing

mircea_popescu: sina does sqlite have unicode support ? if it does, then it will necessarily be less lines of code.

sina: and you contend the actual final implementation of such a thing will actually be less lines of a code than the existing thing ☟︎

sina: I keep taking the debug lines out because it's fucking impossible to follow the logic of the code with them in

a111: Logged on 2017-05-15 15:09 Framedragger: so instead of writing code i now need to write a code editor which can break code lines code-semantically? :/

a111: Logged on 2017-05-15 15:07 asciilifeform: fact. there is not a proggy that will intelligently, cleanly, break lines of code in every known lang

Framedragger: so instead of writing code i now need to write a code editor which can break code lines code-semantically? :/ ☟︎

asciilifeform: fact. there is not a proggy that will intelligently, cleanly, break lines of code in every known lang ☟︎

asciilifeform: i am quite aware that 'software industry' today consists of multiple layers of shit sandwitch, each and every one of which consisted of 'great optimization! all you gotta do is add this 5000 lines of code and 40 layer tree of state that gotta be kept consistent'

mircea_popescu: the continual ejection of lines of code which "Who knows, maybe they're useful"

a111: Logged on 2017-01-07 18:04 mircea_popescu: ah. the way i was thinking this'd work would be : the bot answers to any lines where its name is mentioned ; and i can update its "brain" with a !^ url style command. whereby it replaces its "ai" code with the content of the file.

asciilifeform: 'About 28% of the original Bitcoin v0.1 source code remains in Bitcoin Core v0.12 (although that 28% now represents less than 1.9% of the total source lines), so the possibility existed. ' << lol!!

mircea_popescu: ah. the way i was thinking this'd work would be : the bot answers to any lines where its name is mentioned ; and i can update its "brain" with a !^ url style command. whereby it replaces its "ai" code with the content of the file. ☟︎

diana_coman: and it manages to have some half million lines of code doing the job of maximum 100k by the looks of it

ben_vulpes: it is used to further drive down the cost of human cogs crapping out lines of code

phf: ben_vulpes: connect to these and only these is a trivial change, since the logic all sits within 30 lines of code, but ^

asciilifeform: linked piece is lulzy on account of the idiot 'solution' picked on the victim end, 'That solution comes in the form of the "portable dumper" patch from Daniel Colascione. This patch is not small; it adds over 4,500 lines of code to Emacs and it is not yet complete...'

a111: Logged on 2016-11-19 16:07 pete_dushenski: of lines of code and that many chinese sensors ~will~ fail at some point. and it will be unexpectedly. and catastrophically.

pete_dushenski: of lines of code and that many chinese sensors ~will~ fail at some point. and it will be unexpectedly. and catastrophically. ☟︎

mircea_popescu: asciilifeform i can't, not really. as pissed off as i/anyone can be, "What I currently see as best option is to actually comment out those 2 lines of code. But I have no idea what effect this really has on the RNG. The only effect I see is that the pool might receive less entropy. But on the other hand, I'm not even sure how much entropy some unitialised data has. What do you people think about removing those 2 lines of code?

asciilifeform: i will confess, that i judge any such effort first of all by one metric -- how many lines of jwz c code it EXTIRPATES

asciilifeform: 'What there's need for is people to sit down with a cup of coffee and a (preferably printed) copy of the code and just read it through. This can be done in bits as long as the bits aren't arbitrarily segmented (it's ok to summarize a procedure, it's not ok to summarize between lines 520 and 545). Once we have a few of these completed we're already very far down the road.' << mpoepr

asciilifeform: VE-2016-1828 in May 2016 without doing a security review of the code in question. In only 20 lines of code THREE codepaths existed that allowed UAF. Apple fixed only one of those paths although the other release() methods were clearly right next to it in the code...'

pete_dushenski: http://log.mkj.lt/trilema/20160828/from:60/to:60#60 << because moar is better (tm). more protein in your protein bar, more diamonds on your ring, and on and on ad infinitum. that moar lines of code can't replace a competent cabbie is apparently discussion unbecoming of the 'civilised' set

mircea_popescu: aha. because you're copying me rather than copying the idiots with their "programmer's claw" in doing it. if you wrote 50k lines of code a year you'd have it too.

mircea_popescu: let three lines of A code be ambiguously interpretable to mean 5 different things, so that a million lines of A code become a very clearly useful, controllable item.

a111: Logged on 2016-06-23 09:54 mircea_popescu: ps : why is "common wisdom" in agreement that "no man could possibly hold 1mn lines of code in head" when i actually have 10mn words worth of trilema articles in my head ?

mircea_popescu: ps : why is "common wisdom" in agreement that "no man could possibly hold 1mn lines of code in head" when i actually have 10mn words worth of trilema articles in my head ? ☟︎

phf: reload particularly needs to be fixed, and it's perhaps 5 lines of code, but requires dropping one large context, and lifting another to do it intentionally. as is whatever fixes done to log str result of background radiation noise like effects of my brain, "i suddenly remember relevant bits, and here's the solution, go write it down"

ben_vulpes: "minimalist" means "i made an epic shitton of assumptions and then laid down a zillion lines of code in support of those assumptions"

mircea_popescu: the principal specification of any machine, not JUST computers, not just software stacks, not just lines of code, is to specify what it can never do.

mircea_popescu: he decides he wants to add three lines of code to bitcoin. what HE does, in republican world, is write those lines of code, sign them, add his own sig in the wot and voila.

assbot: IBM has just open-sourced 44,000 lines of blockchain code on GitHub | KnowNaija ... ( http://bit.ly/1QjA67q )

ben_vulpes: removing dead code is good, far better than rewriting the log lines. just split it out so that it can be reviewed seperately from the two thousand five hundred and ninety odd other lines of that patch.

assbot: Logged on 21-01-2016 15:23:26; mircea_popescu: specifically, imagine a future in which every line of code has 100 lines of commentary, much like the talmud (which is a VERY proper comparison)

mod6: <+mircea_popescu> specifically, imagine a future in which every line of code has 100 lines of commentary, much like the talmud (which is a VERY proper comparison) << I never thought of it this way.

mircea_popescu: specifically, imagine a future in which every line of code has 100 lines of commentary, much like the talmud (which is a VERY proper comparison) ☟︎

ben_vulpes: the sample code had some declarative rules, and your complaint was something along the lines of "why'd they get rid of the parens?!"

assbot: Logged on 29-12-2015 17:11:50; punkman: ;;later tell asciilifeform in my current V-tron's conflict detector I check whether two patches modify the same file. I could trivially extend this to detect conflicts at line-of-code level. What would be a good way to apply two patches that modify different lines of the same file?

punkman: ;;later tell asciilifeform in my current V-tron's conflict detector I check whether two patches modify the same file. I could trivially extend this to detect conflicts at line-of-code level. What would be a good way to apply two patches that modify different lines of the same file? ☟︎

assbot: Logged on 11-12-2015 03:44:18; ben_vulpes: http://log.bitcoin-assets.com//?date=08-12-2015#1339102 << listen when you can speak cogently about "the bayesian method" and articulate how "millions upon millions" [of lines of code] betrays your complete lack of understanding on the topic of control systems we can revisit this

ben_vulpes: http://log.bitcoin-assets.com//?date=08-12-2015#1339102 << listen when you can speak cogently about "the bayesian method" and articulate how "millions upon millions" [of lines of code] betrays your complete lack of understanding on the topic of control systems we can revisit this ☝︎☟︎

mod6: it's only 2 more lines of code really. so it's not a bad solution, and this affords me not to have to require perl 5.12 or greater.

mircea_popescu: but see, you wish to link to "lines of code" except these are lower than the minimal granularity ; they only catch meaning after the ast was derived from the whole program

assbot: Logged on 23-10-2015 16:45:38; ascii_field: because i can't link to individual lines of code there.

ascii_field: http://log.bitcoin-assets.com/?date=20-10-2015#1303480 << iirc we did this..? google is for error messages, lines of code, quotes from published documents generically. ☝︎

ascii_field: http://log.bitcoin-assets.com/?date=05-10-2015#1292085 << the mega-application for google is 1) error messages 2) lines of published code. ☝︎

mircea_popescu: if every person on earth wrote just 50 lines of code, which is a very small number of lines of code to write for the progress world etc,

punkman: "estimates that the software needed to run all of Google’s Internet services—from Google Search to Gmail to Google Maps—spans some 2 billion lines of code."

assbot: Logged on 09-09-2015 06:26:09; mircea_popescu: <gabriel_laddel> nano sources: Total Physical Source Lines of Code (SLOC) = 21,577 << win. srsly.

mircea_popescu: <gabriel_laddel> nano sources: Total Physical Source Lines of Code (SLOC) = 21,577 << win. srsly. ☟︎