Wouldn't the more correct analogy be a text editor without "Klippy?"
too many of them these days: https://kakoune.org/
Readit Newsmackeye commented on Claude Sonnet will ship in Xcode developer.apple.com/docum... · Posted by u/zora_goron
mackeye commented on Zedless: Zed fork focused on privacy and being local-first github.com/zedless-editor... · Posted by u/homebrewer
I have found that whenever it fails for me, it's likely that I was trying to one-shot the solution and I retry by breaking the problem into smaller chunks or doing a planning work with gemini cli first.
smaller chunks works better, but ime, it takes as long as writing it manually that way, unless the chunk is very simple, e.g. essentially api examples. i tend not to use LLMs for planning because thats the most fun part for me :)
mackeye commented on Zedless: Zed fork focused on privacy and being local-first github.com/zedless-editor... · Posted by u/homebrewer
To me, using AI to convert an idea or paper into working code is outsourcing the only enjoyable part of programming to a machine. Do we not appreciate problem solving anymore? Wild times.
i'm an undergrad, so when i need to implement a paper, the idea is that i'm supposed to learn something from implementing it. i feel fortunate in that ai is not yet effective enough to let me be lazy and skip that process, lol
mackeye commented on Zedless: Zed fork focused on privacy and being local-first github.com/zedless-editor... · Posted by u/homebrewer
I think you and I are having very different experiences with these copilot/agents. So I have questions for you, how do you:
- generate new modules/classes in your projects - integrate module A into module B or entire codebase A into codebase B?
- get someones github project up and running on your machine, do you manually fiddle with cmakes and npms?
- convert an idea or plan.md or a paper into working code?
- Fix flakes, fix test<->code discrepancies or increase coverage etc
If you do all this manually, why?
> how do you convert a paper into working code?
this is something i've found LLMs almost useless at. consider https://arxiv.org/abs/2506.11908 --- the paper explains its proposed methodology pretty well, so i figured this would be a good LLM use case. i tried to get a prototype to run with gemini 2.5 pro, but got nowhere even after a couple of hours, so i wrote it by hand; and i write a fair bit of code with LLMs, but it's primarily questions about best practices or simple errors, and i copy/paste from the web interface, which i guess is no longer in vogue. that being said, would cursor excel here at a one-shot (or even a few hours of back-and-forth), elegant prototype?
there are approaches to ensure you always or almost always have syntactic validity, e.g. structured editing or error correcting parsing, though of course it's true that the more permissive the system is the more tortured some of the syntactic 'corrections' must be in extreme cases. the approach we're taking with http://hazel.org (which we approximate but don't fully succeed at yet) is: allow normal-ish typing, always correct the code enough to be ran/typechecked, but insert placeholders/decorations to telegraph the parse structure that we're using in case of errors or incompleteness.
i saw hazel mentioned forever ago in an eecs 203 lecture and it sent me on a multi-year fp/type theory rabbit hole :) thanks for your work on it!
we probably have disjoint ideas of the world's problems. why would that fix the world's problems? besides an appeal to authority via andrew tate...
Deleted Comment
mackeye commented on How I build software quickly evanhahn.com/how-i-build-... · Posted by u/kiyanwang
Tangent, is it a Swift thing to have "* ################################################################## / comment markers ?
It becomes quickly very visually dominant in the source code:
> /
###################################################################################################################################### / // MARK: - PUBLIC BASE CLASS OVERRIDES - / ###################################################################################################################################### */i see lots of python with blocks like
###############################################################################
############################### LIBRARY IMPORTS ###############################
###############################################################################
import sys
from pathlib import Path
mackeye commented on Rules of good writing (2007) dilbertblog.typepad.com/t... · Posted by u/santiviquez
Over 80% of the world's languages are classified as SVO or SOV, actually, and probably over 90% of all first language speakers today speak one of these two. Their overwhelming dominance compared to the other four possibilities have led researchers to conclude there may actually be a cognitive benefit to putting the subject first.
arabic can be VSO or SVO. i'm rather new to the langauge but tend to prefer VSO when writing, even as a native english speaker, which gets me to wonder if theres a correlation somewhere between arabic proficiency, other known languages, and VSO/SVO preference. my preference might come from the relative conciseness of VSO in arabic though; often placing the subject before the verb is a bit redundant given context. i'm sure theres a correlation to programming language typing schema somewhere there :)
mackeye commented on Plwm – An X11 window manager written in Prolog github.com/Seeker04/plwm... · Posted by u/jedeusus
I'm hoping one day someone will write a window-manager service for Wayland that replaces the compositor API with a protocol. To once again enable window managers to be implemented in any language, regardless of it having a Wayland/compositor library.
have a look at river, theyre currently working on something like this!