RCrcarmo·Oct 30, 2016
It's not a blog, it's a Wiki (https://github.com/rcarmo/sushy), and the blog just hangs off it. I see no damning in that - you can always either not visit or not click :)
In Elementary OSrcarmo
sushy
Python2014–2026
rcarmo / sushy
sushy
A wiki/blogging engine with a static file back-end
2Distinct people
29Mentions
0Explicit recommenders
105GitHub stars
What to know before exploring
What it is
A wiki/blogging engine with a static file back-end
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 6:01:32 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year29 dated mentions
Observed mentions: 2014-11-29 18:56:09 UTC to 2026-01-05 07:28:42 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
5 sourcesUp until recently, I used a Mac for everything, so everything was on the native services:
* To do lists/Reminders - macOS reminders
* Bookmark lists - Safari bookmarks
* Kanban boards - Trello
* Wikis - http://taoofmac.com (https://github.com/rcarmo/sushy for the engine source)
* Financial tools - Numbers or Excel
* Calendars/Reminders - macOS Calendar
* Files on disk - Dropbox + a NAS
* General notes - Evernote (now OneNote)
* Mindmaps - Mindnode (works great on iOS)
* Photos - NAS
These days I have to use a PC at work (I'm at Microsoft), so a few things changed:
* I left Evernote around 6 months prior to switching jobs because the app was becoming useless and migrated everything across to OneNote (which was free anyway). That gave me:
* To-dos
* Notes
* Blog drafts (I wish it did Markdown, but...)
Read the rest
* Occasional web clipping I want to keep beyond Pocket.
* I started using Pocket more to bookmark stuff I'd want to follow up at home or on the move
* I started using Chrome more (thought about Firefox, realized that Chrome also kept extensions synced the way I like it. Would switch if I could set up a private sync backend)
* I started using OneDrive alongside Dropbox at home (I don't run Dropbox on my work laptop, but some files I might need at work like school schedules and stuff go on OneDrive)
* Trello was replaced for work purposes by Office 365 Groups (works pretty well)
* My NAS now backs up nightly to Azure
* I use Outlook for work calendars, iOS to access everything (Outlook on iOS is pretty good and has its own isolated calendar, which suits me fine)
Mindmaps, reminders and to-dos are always with me on my iPhone (both work and leisure), so no need to sync them. My personal wiki only has public stuff and doubles as my blog, so the copious amount of public references I amass (see http://taoofmac.com/space/infoviz, http://taoofmac.com/space/dev/Python) is still useful regardless.
In general, I don't mix work and personal stuff (OneNote is an exception because it can _access_ different notebooks, but they're on two separate accounts. I generally access my "Shopping" notebook at work to check on to-dos and add stuff, then close it).
The maintainers quoted having a few customers using it, but here's my stuff: http://github.com/rcarmo/sushy
In How to Write a Lisp Interpreter in Python (2010)Both my current[1] and previous[2] blog engines work like this - as long as the post tree is updated by git or Dropbox, they're perfectly happy. Plus I can use whatever markup I want (even Jupyter notebooks).
1: https://github.com/rcarmo/sushy
2: https://github.com/rcarmo/yaki
In Show HN: Publish blog post with a simple Git pushI'm still using Textile. My blog engine (https://github.com/rcarmo/sushy) can cope with ReST, Markdown, Textile, raw HTML and iPython notebooks, and I still turn to Textile for complex tables and other niceties. Out of the 7000-odd pages on my site, most complex pieces are Textile (although most newer items are Markdown).
I find ReST incredibly awkward to use, really, because it's anything but intuitive - both Textile and Markdown are easier to write off the cuff.
More importantly, though, I really wish that Textile, Markdown, ReST, etc., were formally specified as PEG grammars or similar. There's just too much variation, and "standards" or specs defining them tend to be written in ambiguous English rather than something that could be formally validated and easily ported across to new languages (rather than the spaghetti messes of regexps
Read the rest
that most parsers turn out to be when you look at the source).