Never read an article inside the App Store. That's a first.
Me neither, and thanks to Apple’s idiotic thought of 1 country = 1 language I’m not even allowed to read it my the language of choice. Thanks Apple!
BBEdit: Where Respect Is Due
111–120 of 177 posts
Re: BBEdit: Where Respect Is Due
#112Earlier quoted context omitted.
> That’s hard to do and I would guess that their ability to distinguish between what users ask for and what they need is a big part of the software’s longevity. True, but it's also necessary. As Henry Ford (supposedly) famously said "If I had asked people what they wanted, they would have said faster horses."
I've always thought this anecdote about Henry Ford is misleading, if not utterly false. In most cases giving people what you think is best for them and not what they ask for, results in a completely failure. Only a small percentage of cases actually leads to a groundbreaking new technology. But our memory is biased: we only tell success stories and forget the failures...
Re: BBEdit: Where Respect Is Due
#113Earlier quoted context omitted.
I've no reason to doubt your experience at all, I'm really just idly curious. Was that on Windows though? 2004-2005 I think it was all but gone from the Mac, and people had moved to Project Builder (later Xcode), but maybe you were still working on some older project. AFAIK the current CodeWarrior is based on Eclipse, if they're still updating it.
I think it was, yes, and specifically for some embedded toolchain that required it. It would regularly lock up, crash, and lose my work. Though it’s quite possible the toolchain was at least partially the problem, and I wish I could remember which one it was. I might go digging through my old backups, I’m curious myself now
Again, in spite of my current experience I don't doubt for a second that you had a lot of issues. Software was just a lot worse back then, and having now dipped my toes in the frameworks and languages used in the circa 2000 period, I'm not really surprised why. There's 0 references to automated testing in any of the programming books or documentation I've looked at, and as far as I can tell absolutely no support for it. Version control is extremely rudimentary. I didn't programme professionally until early last decade, and some of what I can infer to be have been normal is just baffling for me.
Re: BBEdit: Where Respect Is Due
#114Earlier quoted context omitted.
I'm somehat worried about the incidental harm caused by people relying on GPT's word chain hallucinations as facts for something critical. Most laypersons don't understand that GPT is not a factual search engine. I'm increasingly seeing people who should know better also forget this now and then.
the problem is that the quality of data on the web is such you can't really trust what you get from google either, so you need to go back to the pre-google days of using specialized search engines, or accept that some of what you get back is likely polluted and you don't have the resources to verify everything.
with gpt, you got nothing but the same convincing tone.
Re: BBEdit: Where Respect Is Due
#115Re: BBEdit: Where Respect Is Due
#116Ohh, BBEdit. I've long since moved on from the Mac platform, but I still have really fond memories of it and wish more text editors could match it (SublimeText is pretty good too). I remember when BBEdit came out. It was revolutionary at the time. It was a fun challenge to find "large" files to test it on, and for a while nobody was sure how it did the magic it did. It shipped with a really clean UI and it gave me my…
Re: BBEdit: Where Respect Is Due
#117What is the analogue of BBEdit on Windows? On Linux I guess it’s things like EMacs, and Vim?
I liked Programmer's Notepad but I don't think it had the same power as BBEdit.
Re: BBEdit: Where Respect Is Due
#118 > BBEdit 14
>
> It doesn’t suck.®
Dang, I love it. The feature list looks good enough to back the claim. It almost sounds like an editor for Linux. And I'm also curious if there are any Linux alternatives?Re: BBEdit: Where Respect Is Due
#119Earlier quoted context omitted.
The Henry Ford quote is based on the premise that most people lack the technical knowledge and problem understanding needed to develop visionary solutions, and would just try to give you what they think is best for you (a faster horse, a cleaner car, a fancy new dependency, etc).
The Henry Ford quote is both dumb and extremely misapplied. It basically tells you that a successful, category-defining mass market product, does not look like what you'd get if you imagined asking a bunch of friends a quick question and took their imagined ad-hoc answers at face value. I say imagined, because any actual horse owner would tell Ford they don't want a faster horse - they want a horse that's stronger, e…
Re: BBEdit: Where Respect Is Due
#120I haven't used BBEdit regularly since I discovered Vim (and now Neovim) 10+ years ago, allowing my license to lapse. But I couldn't resist the 30th anniversary sale to purchase the latest version for $30. The UI hasn't changed much, which is both good and not so good. Neovim will continue to be my daily driver but I'm glad to support a small, local (to where I live) developer who's been making great Mac software for…
I'm curious to understand how proprietary software can act as an insurance policy against open source software. I can understand how the reverse would be true.