#whitespace — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #whitespace, aggregated by home.social.
-
Breaks between meeting sessions should be longer than zero minutes. How long should they be? The answer depends on several factors…
https://www.conferencesthatwork.com/index.php/event-design/2012/05/give-me-a-break
-
Note for Python detractors...
If you post a public diatribe against Python - which is your right, go ahead and express yourself - but your centerpiece is "Python is slow!", you're marking yourself out as (a) not knowing Python very well, and (b) hating it because you don't understand it.
It's the more modern cousin to "Python sucks because I can't (not) indent to my taste! Significant whitespace, yuck!". It makes it very difficult to take any of the rest of your complaint seriously.
(Significant whitespace has been shown to result in less opportunity for confusion when reading code, and you spend a lot more time reading code than you do writing it.)
And while Python may be slower for some tasks compared to some other languages, it's (a) not outrageously slow, and (b) a case of use the right tool for the job. I can't trim my lawn quickly at all with my pinking shears, but that doesn't mean pinking shears are "slow".
So please, write your analysis - but make it deeper than "argh it sux i hate it i hate it" if you want anyone to actually consider your argument.
#python #rant #diatribe #whitespace #argument #LanguageWars #RightToolForTheRightJob
-
中英文之間的空白與 CSS 的 text-autospace
#auto #autospace #browser #chinese #cjk #css #english #support #text #whitespace
-
中英文之間的空白與 CSS 的 text-autospace
#auto #autospace #browser #chinese #cjk #css #english #support #text #whitespace
-
Whitespace in filenames is a major category error IMO.
OTOH, filenames themselves (and filesystems as presently incarnated) are also grossly insufficient for many needs. It's interesting to note, for example, that on Android (and possibly iOS), databases (usually sqlite) have emerged as the de-facto default persistent data storage mechanism, even for content which would normally be held on a filesystem.
I've long been looking at questions such as what a document-oriented filesysem (#docFS) or the World Wide Web as fileystem accessible (#webFS) might look like.
For documents, I've generally arrived at a naming standard which uses underbars (_) to separate elements, hyphens (-) for standard whitespace, and double dashes (--) to indicate punctuated / multiple element (e.g., multiple authors, or a subtitle following a colon or dash). Permitted characters are otherwise 7-bit ASCII alphanumeric ([A-Za-z0-9], with dot as a file extension only, and possibly parentheses.
So:
Author-One--Author-Two_Title--Subtitle_YYYY.filetypeThat might have a publisher or journal title added (additional underbar-delimited element after the title(s). Additional contributors (e.g., editors, translator) might be mentioned. And it's possible some identifier (ISBN, OCLC, DOI, LoC call number) might be added, though those are supplemental.
The idea isn't to fully and completely or precisely represent all aspects of a document or work, but to usefully do so. So yes, that means that foreign charactersets aren't presented, that full author lists aren't included (for scientific paper these can number in the tens to hundreds), etc. But enough to find the work reasonably within a corpus through a directory listing.
Yeah, I'm familiar with Calibre, Zotero etc., and should really get more familiar with them. But they're clunky enough and not sufficiently universally available (e.g., on Android, where most of my documents live these days, via an e-book reader) that I'm not optimistic they're really a solution.
(Hoisted from a limited share.)
#DocumentManagement #Whitespace #OnTheNamingOfCats #OnTheNamingOfFiles #Whatever #SameThing #RockyHorror #MacavitysNotHere #Bombalurina #Effanineffable #OldPossum #TSEliot #DOS #PaulOtlet #Mundaneum
