292 Matching Annotations
  1. Sep 2026
    1. Thank you for the additional clarification and for the considerable expenditure of explanatory effort represented by the preceding response. Before proceeding further with the underlying technical question, it may be useful to establish a more explicit shared understanding concerning the relationship between the quantity of information supplied, the extent to which that information is necessary for the immediate decision being made, and the finite amount of maintainer attention available for converting the supplied information into an actionable conclusion. For the avoidance of doubt, the concern being raised here is not that factual accuracy, reproducibility, technical precision, correction of earlier assertions, or sufficient evidentiary support are undesirable. Each of those properties is useful and may, under the appropriate circumstances, be necessary. The difficulty arises when the information required to establish the relevant fact is accompanied by additional explanation whose presence, although potentially interesting and perhaps even technically correct, does not materially alter the fact itself, the confidence with which that fact can be evaluated, or the action that follows from accepting it. Every response imposes what might be described as a comprehension obligation upon its recipients. That obligation consists not merely of reading the words presented, but also of determining which statements constitute factual claims, which function as evidence, which are qualifications, which are conjectures, which supersede earlier statements, which merely restate conclusions already established elsewhere, and which are included primarily to explain the circumstances under which some other statement came to be made. The cost of satisfying this obligation tends to increase with the length, density, and structural complexity of the response, even where the amount of information capable of changing the maintainer’s eventual decision remains constant. This consideration is particularly significant in the context of open-source maintenance, where the time required to read, classify, verify, and contextualize one response cannot simultaneously be used to reproduce another issue, review a pull request, investigate a regression, prepare a release, answer another contributor, evaluate a dependency update, improve documentation, or perform any of the numerous other activities competing for the same limited pool of attention. Consequently, verbosity is not entirely without cost merely because the information is supplied voluntarily, constructively, and with the intention of preventing misunderstanding. Its cost is transferred to each recipient who must determine which portions are operationally necessary and which portions can be disregarded without compromising the validity of the resulting conclusion. We would therefore ask that future responses be prepared according to something approximating a principle of minimum sufficient communication, by which a response contains the smallest collection of independently useful facts required to answer the question currently being asked or to establish the behavior currently under discussion. Information should not be included solely because it is adjacent to the subject, because it records the path by which a conclusion was reached, because it anticipates questions that have not yet been asked, because it exhaustively delineates the boundaries of claims whose ordinary interpretation is already sufficiently narrow, or because omitting it might leave some peripheral aspect of the subject less than comprehensively characterized. The use of the word “smallest” in this context should not be interpreted as a request for artificial abbreviation, unexplained assertions, incomplete reproduction instructions, or the omission of facts required to distinguish the reported behavior from another superficially similar behavior. It means, instead, that each sentence should justify the attention required to process it by contributing something without which a maintainer would be materially less able to verify the report or determine the appropriate next action. Where the removal of a sentence would leave the actionable meaning unchanged, that sentence should generally be presumed removable. Where several paragraphs can be replaced by a single concrete observation without sacrificing reproducibility, the concrete observation should be preferred. Where a mechanism can be demonstrated through a minimal configuration change and an immediately observable result, that demonstration should ordinarily take precedence over a comprehensive narrative describing the mechanism’s provenance, implications, surrounding implementation details, and hypothetical manifestations in configurations not yet tested. Qualifications should similarly be restricted to those that alter the reasonable interpretation of the principal claim. It is generally unnecessary to enumerate every proposition that is not being asserted, every environment that has not been tested, every alternative explanation that was considered and rejected, every inference that a sufficiently careful reader might otherwise draw, or every reason the author has for believing that an untested configuration may behave similarly. Where uncertainty is relevant, it is usually sufficient to identify the precise boundary of verification rather than narrating the broader epistemological status of all related propositions. One potentially useful standard for deciding whether information warrants inclusion is to ask whether the behavior that actually occurs, the smallest reliable procedure that causes it to occur, and any qualification without which those statements would become materially misleading remain understandable and reproducible after the information is removed. If they do, the removed material was probably not necessary for the immediate response. Background already available elsewhere in the issue, detailed explanations of standard language or bundler behavior, speculative generalizations beyond the verified reproducer, extended discussion of why an earlier reproducer was inadequate, descriptions of investigative paths that did not produce the final result, and multiple reformulations of the same conclusion at successively different levels of abstraction should normally be retained by the author unless and until a maintainer requests them. This request is not intended as a judgment concerning the effort, competence, thoroughness, or good faith involved in preparing the response. It concerns the format in which the result of that effort is presented. A technically correct response may nevertheless be disproportionately expensive to consume, in much the same way that a comprehensive diagnostic log may contain the relevant error while simultaneously making that error more difficult to locate. The objective is not to minimize the amount of investigation performed by the reporter, but to minimize the portion of that investigation which every subsequent reader must reconstruct before reaching the actionable result. We recognize that determining what is essential requires judgment and that contributors cannot invariably know in advance which detail a maintainer will consider relevant. In such circumstances, the preferred strategy is progressive disclosure, under which the shortest adequately supported factual answer is provided initially and further supporting detail is supplied only when a maintainer identifies a concrete need for it. It is substantially easier for a maintainer to request one missing fact than it is for multiple maintainers to independently identify and disregard several pages of facts that do not affect the decision being made. The appropriate optimization target is therefore not maximum completeness at the time of the first response, but minimum aggregate effort across all participants required to reach a sufficiently supported conclusion. A concise response that results in one targeted follow-up question may satisfy that target more effectively than an exhaustive response which attempts to preempt every conceivable follow-up but requires substantially greater processing time from every reader, including readers for whom most of the anticipated questions would never have arisen. Facts directly necessary to establish the reported behavior should be included. Evidence directly necessary to verify those facts should be included only to the extent that verification would otherwise be impractical or ambiguous. Context that may be interesting but does not change the facts, their verification, or the resulting action should be omitted unless specifically requested. Where several formulations communicate materially identical information, the shortest formulation should be selected. Where a direct statement is available, it should take precedence over a narrative account of how the statement was discovered. Where one verified claim is sufficient, it should not be surrounded by multiple hypothetical extensions. Where the answer to a question can be expressed as a concrete condition and an observable consequence, the response should ordinarily contain that condition and consequence without attempting to supply a general theory of every adjacent failure mode. It is also important to clarify that this does not mean providing a concise summary followed by the same extended explanation that the summary was intended to replace. The continued presence of the explanation preserves most of the reading, classification, and triage cost. A summary is not a substitute for removing unnecessary material when the unnecessary material remains directly beneath it. Supporting details can remain available to the author and can be supplied in a subsequent response if a maintainer determines that the initial facts are insufficient. Nor is it generally necessary to surround relevant facts with introductory courtesies, repeated apologies, rhetorical transitions, anticipatory defenses, summaries of prior misunderstandings, explanations of why the current answer differs from a previous answer, assurances about claims that are not being made, or concluding restatements of conclusions already expressed. Courtesy is appreciated, but its communicative footprint need not substantially exceed that of the technical substance. A correction is most useful when it makes the corrected claim immediately identifiable and permits the obsolete claim to be discarded without requiring the reader to reconstruct the entire history of the correction. Applied to the present exchange, the information that appears most capable of affecting maintainer action is that disabling HMR removes the React refresh preamble, that the resulting client bootstrap no longer causes the relevant environment initialization to occur before createClientRpc is evaluated, and that server-function construction consequently encounters a ReferenceError because process is unavailable. The precise import-order mechanics, the contrast with the initial theory concerning a relative URL, the implications for other plugins whose preambles may differ, the explanation of why the originally linked example does not exhibit the behavior under its default configuration, and the broader characterization of the problem as a dependency on an incidental ordering guarantee may become relevant during implementation, but they need not all be transmitted before maintainers have had an opportunity to evaluate the narrower verified condition and its immediate consequence. In consideration of the asymmetry between the effort required for an author to preserve additional material and the cumulative effort required for every recipient to inspect and classify that material, and with due regard for the limited and nonrenewable character of volunteer maintainer attention as it relates to the substantially renewable supply of potentially relevant contextual exposition, future participation would be most effective if each response were reduced, before submission, to only those empirically established statements whose omission would prevent reproduction, materially distort the reported behavior, or leave the specific question under consideration unanswered, with all supplementary narrative, speculative extension, duplicative reformulation, historical reconstruction, rhetorical cushioning, and otherwise nonessential elaboration withheld pending an explicit indication that its disclosure is required.

      and the finite amount of maintainer attention available for converting the supplied information into an actionable conclusion.

      We recognize that determining what is essential requires judgment and that contributors cannot invariably know in advance which detail a maintainer will consider relevant. In such circumstances, the preferred strategy is progressive disclosure, under which the shortest adequately supported factual answer is provided initially and further supporting detail is supplied only when a maintainer identifies a concrete need for it

      with due regard for the limited and nonrenewable character of volunteer maintainer attention as it relates to the substantially renewable supply of potentially relevant contextual...

  2. Jun 2026
  3. Dec 2025
    1. There were dedicated spaces for married red pill men, but almost all of them were miserable in their marriages (And of course they were. A happily married man who’s getting laid five times a week has no need for TRP!)

      lol

  4. Nov 2025
  5. May 2025
  6. Apr 2025
  7. Mar 2025
    1. The solution is to not do this. When working with fenced code blocks, do not indent them. This isn’t an issue that can really be worked around, even if the parser did make assumptions about what you meant. Because code blocks are designed to respect whitespace, any fix would simply result in a different but equally frustrating failure. Don’t indent code blocks.
  8. Nov 2024
  9. Oct 2024
    1. I’d love to see more lists of self-evident phenomena we can’t explain; not “how do we reduce scores on the Modern Racism Scale by 10%” but “people do this weird thing…WHY.”
  10. Sep 2024
  11. Aug 2024
  12. Jun 2024
  13. May 2024
  14. Apr 2024
  15. Feb 2024
  16. Nov 2023
  17. Sep 2023
    1. Back in the day, the de facto standard for sending binaries across electronic mail was uuencode. It still exists, but has numerous usability problems; if at all possible, you should send MIME attachments instead, unless you specifically strive to be able to communicate with the late 1980s.
  18. Aug 2023
    1. However, one crucial question remains that has not yet been settled, and it is not a technical, but a social or political question: with everybody locked-in, who is to act in which way to ensure the redirection of funds from the legacy system to the replacement solution, i.e. an open scholarly infrastructure?
  19. Jul 2023
  20. Jun 2023
  21. Apr 2023
    1. “Trying to squeeze a few more drops of freedom from the rotting carcass of the industrial era is not going to help us abolish human nature.” (Sometimes, reading this book, one wishes for a conversation between Harrington and Ted Kaczynski.)

      I actually LOLed at this

    1. --ignore-unmerged When restoring files on the working tree from the index, do not abort the operation if there are unmerged entries and neither --ours, --theirs, --merge or --conflict is specified. Unmerged paths on the working tree are left alone. Holy smokes! I guess the git-ish fix for the user interface problem here will be to rename the option from --ignore-unmerged to --ignore-unmerged-except-in-cases-where-we-do-not-want-to-allow-that--consult-documentation-then-source-code-then-team-of-gurus-when-you-cannot-figure-it-out---and-wait-while-half-of-them-argue-about-why-it-is-right-as-is-while-the-other-half-advocate-adding-four-more-options-as-the-fix.
  22. Mar 2023
  23. Feb 2023
    1. At some point, somebody has to say “You know, maybe freeing Cthulhu from his watery prison is a bad idea. Maybe we should not do that.”

      Cabin in The Woods Movie Anyone? Who were the Gnostics that got that thing made?

    2. As always when dealing with high-level transhumanists, “all available hardware” should be taken to include “the atoms that used to be part of your body”.

      Ah good old computronium

    3. Every two-bit author and philosopher has to write their own utopia. Most of them are legitimately pretty nice. In fact, it’s a pretty good bet that two utopias that are polar opposites both sound better than our own world.

      Two opposite Utopias sound better than reality. That's quite a funny observation.

    1. It includes some nice HTML sanitizers, which are based on HTML5lib's safelist, so it most likely won't make your codes less secure. (These statements have not been evaluated by Netexperts.)
  24. Jan 2023
    1. Chérizier has denied that his nickname “Babekyou” (or “Barbecue”) came from accusations of his setting people on fire. Instead, he says it was from his mother's having been a fried chicken street vendor.

      This is one of those people that we need to make a movie about

    2. The job of a historian is to figure out what really happened, not to beat his political enemies over the head with tendentious, emotional, juvenile propaganda. Again, though—in 2023, it’s easy to see why someone might get that impression.

      Funn

    1. In an episode of Seinfeld, Elaine’s favorite contraceptive stops being sold, and now for every potential lover she has to weigh in whether he is ‘spongeworthy’. An economics professor at Princeton wrote a paper on this, and it was actually published in Economic Inquiry (Dixit, 2012).

      Does that mean what I think it means?

      I read the paper, yes it does mean what I thought it meant.

    1. Every Bay Area person who has jogged past this plaque with their golden retriever, read it, and thought some happy thought about the Jalquin/Irgin (dollars to donuts that the Jalquin massacreed the Irgin at least more than once, presumably after much wrangling over whose brand sounded more like a birth-control pill), has figured out how to believe in blood-and-soil nationalism.

      Funny

  25. Dec 2022
    1. I'm glad this isn't a lego set because it would cost you an arm, a leg, a nose, a kidney, your children, your siblings, your siblings-in-law, a boat, a lot of money, the London Borough of Haringey, the Eiffel Tower, your 1st cousins, a pool, Poole, a guy named Paul, Long Island, your life savings, nuclear launch codes, another lego set, thirteen domestic cats (Scottish Fold), most of your house, Birmingham, AL, your daily income, everyone who died in the Napoleonic Wars, $30,000,000,000,000,000,000,000,000,000 and £30,000,000,000,000,000,000,000,000,000, Zimbabwe, Lesotho, Angola, Namibia, Ethiopia, Mauritania, Canada, Cuba, Jamaica, The Bahamas, Georgia (country), Georgia (US state), every single person from Bosnia and Herzegovina and your time. Luckily, it doesn't.
  26. Nov 2022
    1. I know this is older but I'm surprised by the "Is redrawing 110K glyphs (with metrics and kerning and combining attributes and hinting) too hard?" I used to do typography. A plain, unoriginal typeface with 255 straightforward latin-# oriented letters is at least a couple days of work; probably a couple weeks; couple months for truly good work. 110K is the equivalent of 400+ faces with much harder metrics and such. 15,000 hours of work or drastically more; so at least 7 or so years. So, kinda hard.
  27. Oct 2022
    1. As a kid, I had cobbled together a version of “me” using parts from different sets, but it never looked exactly right (though I did have two lightsabers and a hoverboard, which is definitely just like the real me).
    1. I'm afraid you missed the joke ;-) While you believe spaces are required on both sides of an em dash, there is no consensus on this point. For example, most (but not all) American authorities say /no/ spaces should be used. That's the joke. In writing a line about "only one way to do it", I used a device (em dash) for which at least two ways to do it (with spaces, without spaces) are commonly used, neither of which is obvious -- and deliberately picked a third way just to rub it in. This will never change ;-)
  28. Sep 2022
    1. When we read EA literature we are struck by the same sense of wonder that the young Freud felt, when he thought he had discovered the cure for depression. It was actually just… cocaine.

      These are not political formulas but they are something

    2. Third: as we’ll see, altruism is like meth. No one is questioning two facts: that you should clean your room, and that meth helps you clean your room. No one ever did their first hit of meth, or even their nth hit, with the goal of becoming a methhead. Nor does everyone who does meth become a methhead. Many people can chip meth!

      [Insert Jordan Peterson Meme Here]

    1.   high school kids vs. high-school kids (school kids on pot, or kids in high school)   one armed bandit vs. one-armed bandit (an armed bandit alone, or a bandit with one arm)   criminal law professors vs. criminal-law professors   small animal veterinarian vs. small-animal veterinarian   old boat dealer vs. old-boat dealer   bad weather report vs. bad-weather report   big business owner vs. big-business owner
  29. Aug 2022
  30. Jul 2022
  31. May 2022
    1. If “slow reading” is so liberating, why has every lit major with a Twitter feed written a thread about how they once loved big Russian novels such as Anna Karenina but now struggle to make it through lifestyle articles in the newspaper?

      Hypocrisy

  32. Apr 2022
  33. Mar 2022
  34. Feb 2022
    1. Since factory_bot_rails automatically loads factory definitions as your application loads, writing a definition like this would cause another Daniel to get added to your database every time you start the server or open a console. I like Daniels and all, but there is a limit.
  35. Jan 2022
  36. Dec 2021
  37. www.kickstarter.com www.kickstarter.com
  38. Nov 2021
  39. Sep 2021
    1. Question: Why a cable for a wireless keyboard? Answer: .noScriptDisplayLongText { display : none; } <style> .noScriptNotDisplayExpander { display : none; } .noScriptDisplayLongText { display : block; } </style> because it is not a wireless keyboard...
  40. Aug 2021
    1. If width: 100% is your friend, then width: 100vw is the kid who only pretends to be your friend, so that he can swim in your pool. (I’ve never had a pool, but I know this kid exists from friends of mine who grew up with pools. Also, I am this kid)
    1. I really hope they keep breaking it. Being the lead on a library for several years, most of the forced refactors were pretty straight forward and in almost every case made our code either more sound or easier to be consumed. Now I work on a runtime that embeds TypeScript and 3.5.1 has broken some code, thought it took me all of about 15 minutes to make the changes to adopt it, and in every case, it broke because we were being a bit loose with the types. While it didn't find any bugs, it made the code more "safe".

      I really hope they keep breaking it.

  41. Jul 2021
  42. Jun 2021
  43. May 2021
    1. In real life I ride a Ninja, the last in a line of many bikes over more than forty-five years. However, within this game I've apparently never ridden a sport bike. Or any motorcycle. Or a bicycle. Or watched people ride. Or walked upright. I'm playing with a Thrustmaster joystick, but frankly I might as well be controlling the bike with a Ouija board. If I can not hit a wall, it's a personal victory. Personal victories do not occur often. Instead of the feeling that I'm controlling an exquisitely balanced, steep fork angle sport bike, or even a full dress Harley with an enormously fat passenger and two flat tires, I feel like I'm controlling a rocket-powered lawnmower with several missing tires. Perhaps towing a couple trailers connected with springs. Dying fish don't flop around like me. In forty minutes I've not come close to anything resembling control, much less fun, and I've hit my limit on time I'm willing to throw at it. Wasted money for me; time to acknowledge my mistake, uninstall and get on with my life.
    1. Using unfinished software to build an app that will be seen by millions of people is a risk, and in general I don't recommend it. But it has enabled us to develop the app much faster, and has made the framework itself much stronger than it otherwise would be.
    1. Anyway it's difficult to write too much about the game because it crashes on launch. Broken games don't get thumbs up. I have a dream that one day I'll play an indie game where they bothered testing it. Either way, don't buy broken games. Impossible to recommend.
  44. Apr 2021
    1. Sustainable DistributionGavin uses an electric scooter to transport the games to the drop off points. He would use his electric bike but he is nervous of someone nicking it when He is in the post office. Gavin has a plant based diet. The diet reduces his carbon footprint and his emissions, which his wife is very happy about.
    2. Environmentally friendly factoriesGavin uses the Cubiko Games workshop ‘factory’. Yes, it is a bit cold in the winter but, hey, I built it myself. Transporting goods from the ‘factory’ is very economical, it is about 20 metres from the factory to Gavins house via the garden. The worker in the ‘factory’ (Gavin) is committed to looking after the environment and tries his best to use every piece of wood to the best of his ability. The working conditions are great. (Flexi-time, unlimited food and drink breaks). No child labour. (Samuel sometimes ventures into the factory but we don’t put him to work).
    1. Certainly, if for some reason Python doesn't suit you either you can install, let us say, PHP language. Well, I think you realize that the searching of suitable solution can go on for a long time and may be only MS Visual Basic will be lacking in the list of results. So, I believe the time has already approached to put it all aside and come to to the Point.
    1. If you'll sell it in the U.S. for less than 3948098 dollars, I'll pre-order. I've been wanting this game for quite a long time.I've got a copy of Fjords, I guess I should list it on the marketplace for 3948097 dollars.Only if you want to get rid of it for such a ridiculously low price!
    1. Use a Bobcat to smooth a lawn that mirrors a minefield Though a bit pricey to hire, a Bobcat is perhaps the best weapon to deploy on a large, groove-ridden yard (the type resembling a battlefield).
    1. Playing the game reminds me of when Han Solo has to maneuver in an asteroid field and C3PO says "Sir, the possibility of successfully navigating an asteroid field is approximately 3,720 to 1!"
  45. Mar 2021
    1. To the consternation of some users, 3.x employed Unicode variable names such as λ, φ, τ and π for a concise representation of mathematical operations. A downside of this approach was that a SyntaxError would occur if you loaded the non-minified D3 using ISO-8859-1 instead of UTF-8. 3.x also used Unicode string literals, such as the SI-prefix µ for 1e-6. 4.0 uses only ASCII variable names and ASCII string literals (see rollup-plugin-ascii), avoiding encoding problems.
  46. Feb 2021
    1. Apologies: it's hyperbole. The parent site has a bunch of "spend x to get one of y Steam games" deals, which is what I was referring to. it was not meant literally. Just an attempt to build common ground with the poster who was talking about gambling and fomo.I thought they were referencing the larger site, so I wanted to acknowledge that so I didn't come off as dismissive of their concerns.Which turned out to be entirely separate concerns! Obviating the reason for the comment in the first place.Anyway, sorry for the short novel. But that's the danger of pithy one-liners: assumed context for the poster can be entirely lost in translation.Thanks for coming to my public apology press release?
    1. {'good': ['API objects', 'structured data', 'data sources', 'filtering and operations'],'improvement areas for v2': ['AWS deployment images too small', 'not setting up the data sources in aws that it talked up','not enough numpy','no deep learning yo','drop or shorten up the kitchen analogy, we get what distributed computing is'],'realization: "out of the box functionality won't be much help for real life... have to get weird w delayed objects"}
    1. The blog A Life Of Productivity uses double opt-ins to make sure that people signing up for the email newsletter really want to read it. If a site visitor was somehow subscribed by accident, the subscription won’t go through unless they click the verification button sent to their email address.<img class="aligncenter size-full wp-image-32479" src="https://www.convinceandconvert.com/wp-content/uploads/2016/05/A-Life-of-Productivity.jpg" alt="A Life of Productivity" width="724" height="549" />
    1. This is not a game.It's just a thing.It's nothing to do with cash.Luckily, it's free.Don't pay a dime in this.it's not a game.It's just... more.It's just more.Not in a good way.Nor in a bad way.Sometimes more is just more.This is more. More snore.Is it a good snooze?You decide.I recommend you decide for yourself.After you give it a try.It's free.A free what though?This is not a game.
    1. So what’s the point in a post like this? Is it just me pointing and saying “ha, you’re a sucker!”.No, not at all. (Well, it was to start with, but then I realised I’m a sucker too, so I changed my tune.)
    2. I have a Content Security Policy!Oh, do you now.And did somebody tell you that this would prevent malicious code from sending data off to some dastardly domain? I hate to be the bearer of bad news, but the following four lines of code will glide right through even the strictest content security policy.
    1. Who cares if the game is old? Old games are also loved, you cant hate on a game thats older than you. I'm saying this to those 10 year olds who disliked the game just for being ''old'' I hate how people are nowadays.

      agree

  47. Jan 2021
    1. Please don't thank me! ;-) If this answer did help, just click the little grey ☑ at the left of this text right now turning it into beautiful green. If you do not like the answer, click on the little grey down-arrow below the number, and if you really like the answer, click on the little grey ☑ and the little up-arrow... If you have any further questions, just ask another one! ;-)

      How would you even describe this comment?

      "just doing my job"? but he is (I assume) answering to be nice not because it's his job

      "I won't take it personally"? vote my answer up or down, whichever you please

      impartial, dispassionate, and objective, perhaps? "just the facts, ma'am"


      Separately, what is the "Please don't thank me!" for? Is it that politeness? False modesty? Genuine modesty? Or is it rude? Why not allow someone to thank you??

    1. Great, I can use vw to scale text so it doesn't look puny on a desktop! Perfect... Oh. Huh, now the text is too small to read when viewed on a phone. Okay, well I can just use "max(x,y)" to make sure it doesn't get shrunk beyond a minimum size. Perfect... Oh. Hmm. Looks like "max" isn't supported properly by Chrome. Okay, well guess I'll just use "px" again.
    1. “So, what do you do then?” “Oh, I’m the LocalStorage” he replied, shuffling uncomfortably. “I provide a scripting interface for text storage maintained across pages and browser sessions.”
  48. Dec 2020
    1. For some interpretations of this dengerous oxygen deprivation, you can stop now. Support has been added to both babl and GEGL to handle CMYK images - which can be be used and tested on the commandline - and used in the experimental alternative GUIs for GEGL that are in git. If someone hooks this code up to GIMP I will be diverting some more of my already thinly stretched attention back to the CMYK code in babl and GEGL to make it fast as well. :)
  49. Nov 2020
  50. developer.mozilla.org developer.mozilla.org
    1. as a man who likes to go to bed early, at 10 p.m. on the night of 11 September 2001, President George W. Bush was complaining that he needed to get to sleep.

      jeez. i have something in common which george w.bush.

  51. Oct 2020