HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mileszs
wicked_pdf
Ruby2015–2021
mileszs / wicked_pdf

wicked_pdf

PDF generator (from HTML) plugin for Ruby on Rails

2Distinct people
2Mentions
0Explicit recommenders
3.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

PDF generator (from HTML) plugin for Ruby on Rails

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 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 year2 dated mentions

Observed mentions: 2015-01-07 02:49:52 UTC to 2021-01-04 10:23:25 UTC.

012015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

2 sources
Thanks for sharing - it takes a lot to share these sort of personal experiences. I've definitely been there, too. Aside from all the good and valid comments about reducing scope and shipping an MVP, I'd like to raise another point which may be controversial (or even wrong), but still worth raising: Would it have been different if you had used Rails? A few of the problems you mention (rich text editing, validation, and to some extend, pdf exports) are very easily solved in Rails. Take rich text editing: It's literally a couple minutes to use ActionText. Or validations / forms, there's really not much work to do. PDF exports are also not too hard via wicked_pdf [1] if you're okay with fixing some formatting quirks later on. I've seen both worlds by writing tons of JS / React code myself, and at that time (2016-2018) those problems were almo
Read the rest
st an order of magnitude more time-costly to implement in SPAs. I remember react-router.. not great memories. Of course, all the points reducing MVP scope still hold, but.. if you could have had all those features (nearly) for free, would you be at another stage now? Who knows. [1] https://github.com/mileszs/wicked_pdf
In 20 months, 2K hours, 200K € lost. A story about resilience and sunk cost fallacy
Read the rest
ver4j https://github.com/sensu/sensu-community-plugins/blob/master/handlers/notification… https://github.com/schneems/wicked/wiki/Testing-Wicked-with-RSpec https://github.com/schneems/wicked https://github.com/satyr/coco https://github.com/satyr https://github.com/sampsyo/beets/issues/546 https://github.com/rust-lang/cargo https://github.com/rniemeyer/knockout-delegatedEvents https://github.com/rniemeyer/knockout-amd-helpers https://github.com/qbit/node-pushover https://github.com/openSUSE/wicked/issues/432 https://github.com/openSUSE/wicked https://github.com/Nuku/Flexible-Survival/blob/master/Stripes/Candy https://github.com/Netflix/Lipstick https://github.com/nemomobile/lipstick https://github.com/mrmrs/colors https://github.com/mirage https://github.com/mileszs/wicked_pdf/issues/78 https://github.com/LubosD/darling https://github.com/laprice/pushover https://github.com/kryap/php-pushover https://github.com/krisselden/broccoli-sane-watcher https://github.com/Knockout-Contrib/Knockout-Validation https://github.com/knockout/knockout https://github.com/knockout https://github.com/kirang20/wgxp-java-rosa https://github.com/jreese/znc-push/blob/master/doc/pushover.md https://github.com/jnwatts/pushover.sh https://github.com/jfinkels/flask-restless/ https://github.com/jasonlewis/resource-watcher https://github.com/huxi/lilith https://github.com/hannorein/rebound https://github.com/gregghz/Watcher https://github.com/feuerbach/tasty https://github.com/facebook/rebound-js https://github.com/facebook/rebound https://github.com/erniebrodeur/pushover https://github.com/entertailion/Fling/blob/master/README.md https://github.com/enkydu/raspi_runner https://github.com/dyaa/Laravel-pushover https://github.com/danesparza/Pushover.NET https://github.com/crazed https://github.com/callmenick/css-loaders-spinners-2/tree/master/js https://github.com/callmenick/css-loaders-spinners-2 https://github.com/allure-framework/allure-core https://github.com/abrt/satyr Thanks for reaching out to us! We have received your legal request. We receive many such complaints each day; your message is in our queue, and we'll get to it as quickly as our workload permits. Due to the large volume of requests that we experience, please note that we will only be able to provide you with a response if we determine your request may be a valid and actionable legal complaint, and we may respond with questions or requests for clarification. For more information on Google's Terms of Service, please visit http://www.google.com/accounts/TOS Regards, The Google Team
In DMCA Copyright Complaint to Google

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.