Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sgbeal
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
52 ms
·
631.
▲
by
sgbeal
4y ago
Anecdote: i backed pine64's first-ever Kickstarter and got two of their A+ boards (i think they were called). They claimed high performance and full HD video. In the end i couldn't get a single Android game, no matter how primitiv
632.
▲
by
sgbeal
4y ago
It's unfortunate that the article doesn't _link_ to the numerous related projects it mentions.
633.
▲
by
sgbeal
4y ago
> The sqlite library is tiny. Often smaller than some JSON parsers! Stripped of all comments, the current "amalgamation" build of sqlite (which is the one most projects use) has 178k lines and 4.7MB of code. If your JSON parser
634.
▲
by
sgbeal
4y ago
> The SQLite site runs on SQLite and it has considerable traffic. The forum and source code trees run on sqlite (via the Fossil SCM, authored by sqlite's Richard Hipp). The main sqlite site is static HTML with a tiny sprinking of JS
635.
▲
by
sgbeal
4y ago
FWIW, i just almost wet my pants laughing that that :).
636.
▲
by
sgbeal
4y ago
> I just want names, possibly mail forwarding, not hosting etc. Another alternative is NearlyFreeSpeech.net. i'm using them simply for DNS with great results and fantastic prices. IIRC, if you _just_ use them for DNS it costs 1c pe
637.
▲
by
sgbeal
4y ago
> Ads, trackers and internal tools that somehow I have to contribute my data to, and their accompanying libraries EASILY make up 70% of all JS. Citation needed. Literally 100% of the JS code i've written over the past 24 years has b
638.
▲
by
sgbeal
4y ago
> So if someone new on the team accidentally commits "node_modules" Then the 120k+ files in node_modules is in there forever, far outliving that team member's career as a software developer. If the user has not yet synced
639.
▲
by
sgbeal
4y ago
> Why do you mean "modify"? As in rewriting history (commits before HEAD)? Fossil flat-out does not support, with the exception of "shunning" (forcibly removing content), the modification of any history. It supports t
640.
▲
by
sgbeal
4y ago
> So if somebody accidentally commits customer data to the monorepo First, you use that as a "teaching opportunity" to educate that someone about why doing so is Bad for Business. Secondly, you "shun" the artifact(s)
641.
▲
by
sgbeal
4y ago
> I amend commits in Git quite often before pushing. Fossil supports amending checkins at any time after committing, as often as you like - change the checkin commit, re-attribute to a different user, change the timestamp, or similar. Wh
642.
▲
by
sgbeal
4y ago
> But every time I have to wrestle with un-fucking git's state I find myself considering my life choices and how I got there :( cough Fossil cough
643.
▲
by
sgbeal
4y ago
> Which cat meme was deemed appropriate for the final approval of the change? FWIW, that wins my internet for today and i'll aim to make that a factor in any future code reviews/approvals.
644.
▲
by
sgbeal
4y ago
> A question rarely raised: why is Git considered suitable for small or medium projects? Quite frankly, _it's not_. There's _absolutely nothing_ ideal about git except for its ability to super-scale to that _exceedingly small_
645.
▲
by
sgbeal
4y ago
> I do hope someday git and others employ either a git annex or mercurial-style scheme where if it's a large binary file: 1. no diff is performed, and 2. only the latest version is kept within the history. That will never happen in
646.
▲
by
sgbeal
4y ago
> What does it matter? I do $packagemanager install git and am done. _Freedom_. Fossil is trivial to build on all modern platforms and we (in the fossil project) always recommend that folks use the trunk version, building it for themselv
647.
▲
by
sgbeal
4y ago
> How is large file support? Fossil is, because of its sqlite dependency, limited to blobs no larger than 2GB each. Some of its algorithms require keeping two versions of a file in memory at once, so "stupidly huge" blobs are n
648.
▲
by
sgbeal
4y ago
(A long-time fossil dev here...) Re. integrated wiki: when i first saw fossil (Christmas break of 2007) two features made it a killer app for me: wiki and hosting as a CGI. The wiki aspect has long since taken a back seat to the so-called &
649.
▲
by
sgbeal
4y ago
> The problem with that is that SQL as a standard is so patchy and inconsistently implemented that effectively everything has database-specific features. Noting that when it comes to such patchiness, sqlite's developers specifically
650.
▲
by
sgbeal
4y ago
> Attempts at multiple DML logins will not block until successful, but simply fail. sqlite has a "busy handler" mechanism which tells it how to respond to blocks and most apps use the builtin one with which they can tell it &q
651.
▲
by
sgbeal
4y ago
> The article is from 2016. I doubt passwords are still stored in plaintext. Fossil has not stored a plaintext password in many years (2008-ish). Only a one of the small handful of "first-generation" repositories has any chance
652.
▲
by
sgbeal
4y ago
> Ouch. A single round of SHA-1 means you can easily make over a million attempts per second on a single general-purpose processor... That's FUD: you cannot connect to a remote anywhere nearly that fast. Fossil's passwords are
653.
▲
by
sgbeal
4y ago
> The biggest surprise was the web UI didn't seem to provide a way to review changed files in the working directory and perform a commit. Since (IIRC) late 2021, you can view a diff in your browser with: fossil diff -b (use -by for
654.
▲
by
sgbeal
4y ago
> Would the wiki part of fossil be a good static site generator? Not in the general case, no. Fossil-generated wiki/markdown output expect to be browsed within the context of a fossil repository, and will generate links accordingly.
655.
▲
by
sgbeal
4y ago
(A fossil dev here...) "Purge" is really only intended for use with fossil's "bundle" feature, bundles being essentially feature-rich patches which record all of the historical state of the bundle. (Yes, it's l
656.
▲
by
sgbeal
4y ago
> Or perhaps, I suspect, that software developers nowadays just think people expect from software, so they provide it without even reflecting whether it's really necessary at all. For the most part i blame that on the marketing folk
657.
▲
by
sgbeal
4y ago
> You have to be able to architect your application to send all write traffic to a single process ... Counter-point: sqlite's sister project and SCM, the Fossil SCM, is a self-hosting sqlite client application and has been since 200
658.
▲
by
sgbeal
4y ago
> (Unless it reset to the state the database had when you imported it, instead of clearing it? It might work…) There's no way to know what the db's state was when it was imported without literally keeping a second copy of the w
659.
▲
by
sgbeal
4y ago
> If you consider the design space, “resetting the state every time” is exactly how basically every other “fiddle” app works. This app's design space is exposing the sqlite3 shell app via the web, not to emulate every other fiddle e
660.
▲
by
sgbeal
4y ago
> In what use cases would it make sense to transfer the entire db file over the network, then pluck out the relevant rows into JSON, versus just doing that server side and transfer the JSON back? Lots of dbs are small - a few hundred kb,
More ›