{"channel":"cities","content":"the tool of the day is Replit.\r\n\r\n----\r\n\r\nIn what may be a good business decision, but is slightly annoying to the consumer, one must pay the $25 (monthly) up-front before using Replit.\r\n\r\n----\r\n\r\nReplit uses Claude; so one cannot expect it to be particularly better or worse than other tools that also use Claude.\r\n\r\nOne advantage is that the \"billing\" system is very transparent.  It was 5c per \"change\" for the initial changes I made. (<blue> if you aren't paying for it, in the long run it doesn't exist)\r\n\r\nOne disadvantage is that there is a very low limit for the maximum \"context\" one can pass into queries.  It was, generally, << three files >>.  This is rarely enough.\r\n\r\n----\r\n\r\nIt also creates Git changes in a way that almost requires a development repository, and \"flattening\" before pushing to main (<xantham> \"main\" used to be called \"master\", but the language police decided they should change it.)\r\n\r\n----\r\n\r\nThe UX changes it made were a clear case of \"one step forward, one step back\".  Which ... can be helpful.  But, the constraints of Replit make it less helpful.\r\n\r\n<red> <<< At least for a new user, Replit seems to have the philosophy of \"you can't write code\".  If you don't like what it does, tell it to do the fixing. >>>\r\n<orange> <<< Well, actually, maybe there is a terminal available.  And a file editor. >>>","created_at":"2025-05-27T15:10:46.757115","id":563,"llm_annotations":{},"parent_id":503,"processed_content":"<p>the tool of the day is Replit.\r</p>\n<hr class=\"section-break\" />\n<p>In what may be a good business decision, but is slightly annoying to the consumer, one must pay the $25 (monthly) up-front before using Replit.\r</p>\n<hr class=\"section-break\" />\n<p>Replit uses Claude; so one cannot expect it to be particularly better or worse than other tools that also use Claude.\r</p>\n<p>One advantage is that the \"billing\" system is very transparent.  It was 5c per \"change\" for the initial changes I made. <span class=\"colorblock color-blue\"><span class=\"sigil\">\u2728</span><span class=\"colortext-content\"> if you aren't paying for it, in the long run it doesn't exist</span></span>\r</p>\n<p>One disadvantage is that there is a very low limit for the maximum \"context\" one can pass into queries.  It was, generally, <span class=\"literal-text\">three files</span>.  This is rarely enough.\r</p>\n<hr class=\"section-break\" />\n<p>It also creates Git changes in a way that almost requires a development repository, and \"flattening\" before pushing to main <span class=\"colorblock color-xantham\"><span class=\"sigil\">\ud83d\udd25</span><span class=\"colortext-content\"> \"main\" used to be called \"master\", but the language police decided they should change it.</span></span>\r</p>\n<hr class=\"section-break\" />\n<p>The UX changes it made were a clear case of \"one step forward, one step back\".  Which ... can be helpful.  But, the constraints of Replit make it less helpful.\r</p>\n<div class=\"mlq color-red\"><button type=\"button\" class=\"mlq-collapse\" aria-label=\"Toggle visibility\"><span class=\"mlq-collapse-icon\">\ud83d\udca1</span></button><div class=\"mlq-content\"><p> At least for a new user, Replit seems to have the philosophy of \"you can't write code\".  If you don't like what it does, tell it to do the fixing. </p></div></div>\n<div class=\"mlq color-orange\"><button type=\"button\" class=\"mlq-collapse\" aria-label=\"Toggle visibility\"><span class=\"mlq-collapse-icon\">\u2694\ufe0f</span></button><div class=\"mlq-content\"><p> Well, actually, maybe there is a terminal available.  And a file editor. </p></div></div>","quotes":[],"subject":"watertown (part 3)"}