HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
thewhitetulip
Tasks
Go2015–2017
thewhitetulip / Tasks

Tasks

A simplistic todo list manager written in Go

2Distinct people
18Mentions
0Explicit recommenders
561GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A simplistic todo list manager written in Go

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:28:18 AM 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 month18 dated mentions

Observed mentions: 2015-11-15 16:39:10 UTC to 2017-03-20 07:43:36 UTC.

012342015-11-01 00:00:00 UTC to 2015-12-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsNov 20152015-12-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2016-02-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2016-02-01 00:00:00 UTC to 2016-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-01 00:00:00 UTC to 2016-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-01 00:00:00 UTC to 2016-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-01 00:00:00 UTC to 2016-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-01 00:00:00 UTC to 2016-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-01 00:00:00 UTC to 2016-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 20162016-08-01 00:00:00 UTC to 2016-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-09-01 00:00:00 UTC to 2016-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-10-01 00:00:00 UTC to 2016-11-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2016-11-01 00:00:00 UTC to 2016-12-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2016-12-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-01-01 00:00:00 UTC to 2017-02-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-02-01 00:00:00 UTC to 2017-03-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-03-01 00:00:00 UTC to 2017-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 2017

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
Nov 20152015-11-01 00:00:00 UTC2015-12-01 00:00:00 UTC110
Dec 20152015-12-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
Jan 20162016-01-01 00:00:00 UTC2016-02-01 00:00:00 UTC211
Feb 20162016-02-01 00:00:00 UTC2016-03-01 00:00:00 UTC000
Mar 20162016-03-01 00:00:00 UTC2016-04-01 00:00:00 UTC000
Apr 20162016-04-01 00:00:00 UTC2016-05-01 00:00:00 UTC000
May 20162016-05-01 00:00:00 UTC2016-06-01 00:00:00 UTC000
Jun 20162016-06-01 00:00:00 UTC2016-07-01 00:00:00 UTC000
Jul 20162016-07-01 00:00:00 UTC2016-08-01 00:00:00 UTC000
Aug 20162016-08-01 00:00:00 UTC2016-09-01 00:00:00 UTC101
Sep 20162016-09-01 00:00:00 UTC2016-10-01 00:00:00 UTC101
Oct 20162016-10-01 00:00:00 UTC2016-11-01 00:00:00 UTC202
Nov 20162016-11-01 00:00:00 UTC2016-12-01 00:00:00 UTC404
Dec 20162016-12-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
Jan 20172017-01-01 00:00:00 UTC2017-02-01 00:00:00 UTC202
Feb 20172017-02-01 00:00:00 UTC2017-03-01 00:00:00 UTC202
Mar 20172017-03-01 00:00:00 UTC2017-04-01 00:00:00 UTC101

What Hacker News says

2 sources
> with minimal understanding of what they're really doing In my opinion, this is very dangerous. It is always better to understand the inner workings and then write an app, otherwise you just feel you have accomplished something when, in reality, it was just the framework you used and you didn't learn. I am saying this out of experience, when I used to use Django, I didn't understand the difference between GET vs POST. Still, I built a small note taking app, I didn't understand how cookies worked and until I wrote this: https://github.com/thewhitetulip/Tasks, I didn't know that the cookie details were read and sent to the sever in each request. Frameworks are powerful in cases when you want new comers to get started quickly, but in my opinion that has to be after the new comers are familiar with webdev, so they know what the underlying te
Read the rest
ch are and how they work. Plus, frameworks need to be chosen with care, because you are basically bound to the framework you choose. Personally, I like to write apps without a framework by using various toolkits, I never felt the necessity to use any framework, because they don't provide me with any distinct feature which I can't replicate with little additional code using the stdlib and supporting toolkits like gorilla. From my experience building the Tasks application, I wrote an introductory e-book which teaches building apps with example, so no more magic! I didn't find a resource which taught how to write web apps using an example, thus wrote one. https://github.com/thewhitetulip/web-dev-golang-anti-textboo... and on multiple requests, recorded a screencast: https://www.youtube.com/playlist?list=PL41psiCma00wgiTKkAZwJ...
In Buffalo – MVC Web Framework for Go

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.