|
| 1 | +<!DOCTYPE html> |
| 2 | + |
| 3 | +<html lang="en"> |
| 4 | + <head> |
| 5 | + <meta charset="UTF-8" /> |
| 6 | + <meta name="viewport" content="width=device-width, initial-scale=1.0" /> |
| 7 | + <title>WriterSharp - Devlogs</title> |
| 8 | + <link rel="stylesheet" href="../css/styles.css" /> |
| 9 | + <link rel="icon" type="image/x-icon" href="../assets/favicon.ico"> |
| 10 | + </head> |
| 11 | + <body> |
| 12 | + <header> |
| 13 | + <div class="title">WriterSharp - Devlogs</div> |
| 14 | + <nav> |
| 15 | + <a href="../index.html"><i class="nf nf-fa-home"></i></a> |
| 16 | + <a href="#"><i class="nf nf-fa-download"></i></a> |
| 17 | + <a href="#"><i class="nf nf-md-puzzle"></i></a> |
| 18 | + <a href="index.html"><i class="nf nf-fa-book"></i></a> |
| 19 | + <a href="../about.html"><i class="nf nf-md-information"></i></a> |
| 20 | + <button id="mode-toggle"><i class="nf nf-md-theme_light_dark"></i></button> |
| 21 | + </nav> |
| 22 | + </header> |
| 23 | + |
| 24 | + <main> |
| 25 | + <section class="hero alt-bg4"> |
| 26 | + <h1 class="huge-title">Devlog 2</h1> |
| 27 | + <p><i class="nf nf-fa-book"></i> AI Integration: yay or nay?</p> |
| 28 | + <p><i class="nf nf-fa-clock"></i> 22/07/2025</p> |
| 29 | + <p class="devlog-tag"><i class="nf nf-fa-tag"></i> Future</p> |
| 30 | + <p class="devlog-tag"><i class="nf nf-fa-tag"></i> Community</p> |
| 31 | + <p> |
| 32 | + <a href="devlog1.html"><i class="nf nf-fa-arrow_left"></i> Previous Devlog</a> |
| 33 | + <a href="index.html"><i class="nf nf-fa-home"></i> Go Back</a> |
| 34 | + <!-- no next button --> |
| 35 | + </p> |
| 36 | + </section> |
| 37 | + |
| 38 | + <section> |
| 39 | + <div class="text-container"> |
| 40 | + <blockquote> |
| 41 | + <div class="quote">AI is 90% marketing and 10% reality.</div> |
| 42 | + <p class="small-text">- Linus Torvalds (Adapted)</p> |
| 43 | + </blockquote> |
| 44 | + |
| 45 | + <p>Two devlogs in one week?! That's pretty exceptional, huh?</p> |
| 46 | + <p>Well, it's been a <em>different</em> week - not bad, but one where I've been busy with other projects of mine. WriterSharp's been quiet, but I'm still finding time to update it whenever possible.</p> |
| 47 | + |
| 48 | + <hr /> |
| 49 | + |
| 50 | + <h2>AI Integration - Should WriterSharp join the party?</h2> |
| 51 | + <p>From the very start, I've been trying to make WriterSharp <strong>non-opinionated</strong>, meaning it does not boss you around or force a workflow <em>(the only exception to this rule is the plugin API, which does, understandably, enforce some rules)</em>. It lets you do what you want, when you want.</p> |
| 52 | + <p>Lately, AI-first code editors with built-in AI agents are all the rage. Which begs the question: <strong>should WriterSharp join the hype and have a bundled <em>native</em> AI agent?</strong></p> |
| 53 | + <p>My answer? Nah. WriterSharp's strength is staying out of the way - not following trends just because someone on X says they're good. So it <strong>won't</strong> come with built-in AI of any sorts. If, however, you <em>really really</em> want AI support in WriterSharp, you could always create a plugin to add said feature.</p> |
| 54 | + |
| 55 | + <h2>"Supporting open-source is good." - Nuff said.</h2> |
| 56 | + <p>WriterSharp isn't a big team project - hell, it's not even a small team project - it's me, solo, grinding some coding sessions. If you want to support my work and keep WriterSharp alive, I'd really appreciate it - you can support me at <strong><a href="https://buymeacoffee.com/mf366">Buy Me A Coffee</a></strong>.</p> |
| 57 | + <p>If you wish to go further, join my <strong>membership tiers</strong>! Monthly or yearly support unlocks premium devlogs, tech demos, behind-the-scenes peeks and much more.</p> |
| 58 | + |
| 59 | + <h2>Discord Community</h2> |
| 60 | + <p>Ah, Discord... Right now, WriterSharp does not have its own Discord server and honestly, it'll <em>probably</em> never have one. Instead, when <a href="https://oceanapocalypsestudios.github.io/">OceanApocalypseStudios</a>'s Discord Server goes public, there'll be a dedicated spot to chat about my projects, WriterSharp included. Nothing fancy, just a chill place to hang out and share ideas.</p> |
| 61 | + |
| 62 | + <h2>WriterClassic</h2> |
| 63 | + <p>Meet <strong><a href="https://github.com/MF366-Coding/WriterClassic">WriterClassic</a></strong>: WriterSharp's predecessor. It wasn't built with C#, but rather with good ol' <a href="https://python.org/">Python</a> and <code>tkinter</code>.</p> |
| 64 | + <p>WriterClassic had its fair share of quirks - some features were quite unique for a text editor. Its focus was mostly <strong>text editing</strong>, not code. And its plugin API? Let's just say it had its... rough edges.</p> |
| 65 | + <p>That being said, WriterClassic holds a special place in my heart and I've learned a ton from its flaws. Those lessons are the backbone of WriterSharp's design, helping make it truly <em>sharp</em>.</p> |
| 66 | + |
| 67 | + <hr /> |
| 68 | + |
| 69 | + <p>That's it for now! Thank you so much for stopping by and taking your time to read this devlog. If you liked it, consider sharing it around - it would help immensely with letting WriterSharp reach more people.</p> |
| 70 | + <p>In the meanwhile, see you on GitHub... or in the next devlog!</p> |
| 71 | + </div> |
| 72 | + </section> |
| 73 | + </main> |
| 74 | + |
| 75 | + <footer> |
| 76 | + <p id="footer-copyright"> |
| 77 | + Copyright <i class="nf nf-fa-copyright"></i> 2025 MF366 |
| 78 | + </p> |
| 79 | + </footer> |
| 80 | + |
| 81 | + <script src="../js/dark-mode.js"></script> |
| 82 | + <script src="../js/scroll-animation.js"></script> |
| 83 | + </body> |
| 84 | +</html> |
0 commit comments