sgbeal

47 ms·

691.
by sgbeal 5y ago
> ... the possibility of recursion was implemented only recently, etc). Noting that "recently" was August 2014 (version 3.8.6), according to https://sqlite.org/oldnews.html . The "missing" right/f
692.
by sgbeal 5y ago
FWIW, i've never once started with sqlite and then later "upgrade" to another db. i once actually used sqlite to implement locking for a mysql db because mysql's locking requires (or required, back then) that the calling
693.
by sgbeal 5y ago
> One activity question for HN: why do you think Dropbox continues to exist today while copycats like Barracuda Copy have failed? FWIW, i've been using Dropbox since practically the day they went online, and have been a subscriber f
694.
by sgbeal 5y ago
> Perl is very much an unreadable code soup. It has been said that perl is the only language which looks the same both before and after RSA encryption.
695.
by sgbeal 5y ago
FWIW: when i met drh for the first time in September 2011 i asked him, "what's the D in your name for, if i may ask?" His answer was, "only my mother gets to call me that." PS: He goes by Richard.
696.
by sgbeal 5y ago
> Fossil has had this feature for a long time (A long-time fossil contributor here.) Fossil has no such feature. Fossil sync synchronizes the remote and local saved state (checked-in/saved state only ). It does not do anything wi
697.
by sgbeal 5y ago
> Why does it matter if he can or cannot capture the majority of that market? Amen to that. FWIW... i've actively contributed to fossil since 2008 and can say with some authority that we (the "regulars" on the project) hav
698.
by sgbeal 5y ago
> long long long time ago Fossil destroyed code for Zed Shaw 1) No, it didn't. Please read the part of the thread after Zed's initial panic attack. 2) To the best of our[1] knowledge, fossil itself has never caused a single byt
699.
by sgbeal 5y ago
> The wiki lacks category ... Just FYI: we recently improved the internals to be able to add propagating tags to wiki pages[1], so it will eventually be possible to use those to categorize/group your wiki pages. What's missing
700.
by sgbeal 6y ago
> The ties are interesting and deep. Brad! You're alive! In case you hadn't heard: libfossil was recently revived, has been brought up to date with regards to SHA3 hashes, and got both "update" and "revert"
701.
by sgbeal 6y ago
> Someone else perhaps had a similar idea, so were writing libfossil; however, they seem to consider the protocol implementation a lower priority, That's me ( https://fossil.wanderinghorse.net/r/libfossil ). The
702.
by sgbeal 6y ago
> What's the text editor? If anything could get me off Emacs, it'd come from the Hippoverse. It's a basic tk-based app, IIRC. i peaked at it once when he posted a link to it, but that was 7+ years ago and i don't reca
703.
by sgbeal 6y ago
> Drop-shadows, rounded corners, borders, colouring, fades. All extra work, all a pain to look at. i have it on exceedingly good authority (as the one who implemented it) that the look and feel was about 90% personal preference and 10% f
704.
by sgbeal 6y ago
> How is the security with Fossil? I'm always leery of hosting (niche) web facing services written in C. Fossil's been available for nearly 14 years now and we've had to make only a single security-relevant release in that
705.
by sgbeal 6y ago
> I avoid it because of complete lack of commit amendment tools. That's downright wrong: https://fossil-scm.org/home/help/amend
706.
by sgbeal 6y ago
> Does anyone use Fossil? Almost literally every day since Christmas break of 2007. > I like all it offers for the relatively low resource usage. And setting it up to run over CGI (e.g. over a $5/month shared hoster) takes about
707.
by sgbeal 6y ago
> It isn't clear what makes bundling a chat program into your SCM beneficial. ... you can just use regular URLs in any old chat app. You just answered your own question: trying to get any given group of people to use the same 3rd-pa
708.
by sgbeal 6y ago
> mdel, ltime, mtime. Why do people insist on oft unreadable short column names? You forgot to mention vfile.chnged. i've been contributing to fossil since 2008 and that missing "a" still, to this day, agitates me ;).
709.
by sgbeal 6y ago
> I'd rather he'd announce his MTA & MUA so we can reinstate the fossil mailing list. It's demonstrably become impossible to manage spam in such an environment without the resources of mega-corps, whereas fossil aims t
710.
by sgbeal 6y ago
> If I could be so unproductive... It goes much further than that... When one views a fossil-hosted forum post from the main fossil site or sqlite's site, they are looking at... - A forum post rendered by software Richard wrote. - P
711.
by sgbeal 6y ago
> I feel that's a bit short-sighted, ... You can certainly do it, but you'll run quickly into issues and be buried in feature requests (Disclaimer: i wrote 99%+ of the fossil chat front-end code.) FWIW... When Richard (our Alph
712.
by sgbeal 6y ago
Another option is running is behind Apache as a CGI, and let Apache handle the HTTPS part. My repos (fossil.wanderinghorse.net) all run as CGIs on a $7/month shared hoster, and have been since 2008, without issues.
713.
by sgbeal 6y ago
> Sounds lightweight! Its public API is literally a single function. You give it pikchr code and it returns a string which contains either an SVG or a description of an error it ran across. (You, the user, can determine which it is by th
714.
by sgbeal 6y ago
FWIW, pikchr is not intended to be used to create "marketing materials," but solely for dry/boring technical diagrams (not that that's a bad thing - i'm all for dry/boring diagrams). It certainly excels at simp
715.
by sgbeal 11y ago
"Mistakes" was indeed a poor choice of words, but the principle is the same: fossil does not allow the public record (mistake or otherwise) to change, with the one exception of the "nuclear option" (shunning, which forci
716.
by sgbeal 11y ago
i don't know which business you work for, but i have it on good authority (from an unspecified sqlite core developer) that getting software into commercial airplanes requires 100% auditability of the source history. i _assume_ that&#x2
717.
by sgbeal 11y ago
Why do you feel that you _have_ to be able to correct history? The past is immutable. Fossil treats it as such. git does not, no matter what configuration you're running - i can always create a fork, modify the history in my fork, and
718.
by sgbeal 11y ago
i've been on the fossil dev team since 2008, and i have seen many people claim that it "could" be compromised/modified post facto, and yet... nobody has been able to do it. Fossil's core data model does not just _as
719.
by sgbeal 11y ago
> What is the value in having history be static? auditability, for one. Certain business processes, e.g. those sending people and machines into space, require 100% immutable auditability.
720.
by sgbeal 11y ago
> Ehm, That's not a fair assessment. Git is as much immutable as fossil. HA! HAHA! HAHAHA!!!! For any reasonable definition of "immutable," git is most certainly NOT immutable.

More ›