HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
electric-sheep-uc
black-sheep
C2019–2019
electric-sheep-uc / black-sheep

black-sheep

Open source humanoid robot platform for the RoboCup competition created by Electric Sheep

2Distinct people
3Mentions
0Explicit recommenders
7GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open source humanoid robot platform for the RoboCup competition created by Electric Sheep

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 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 hour3 dated mentions

Observed mentions: 2019-08-06 07:15:51 UTC to 2019-08-06 15:46:13 UTC.

012019-08-06 07:00:00 UTC to 2019-08-06 08:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 6, 07:002019-08-06 08:00:00 UTC to 2019-08-06 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-06 09:00:00 UTC to 2019-08-06 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-06 10:00:00 UTC to 2019-08-06 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-06 11:00:00 UTC to 2019-08-06 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 6, 11:002019-08-06 12:00:00 UTC to 2019-08-06 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-06 13:00:00 UTC to 2019-08-06 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-06 14:00:00 UTC to 2019-08-06 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-08-06 15:00:00 UTC to 2019-08-06 16:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 6, 15:00

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
Aug 6, 07:002019-08-06 07:00:00 UTC2019-08-06 08:00:00 UTC101
Aug 6, 08:002019-08-06 08:00:00 UTC2019-08-06 09:00:00 UTC000
Aug 6, 09:002019-08-06 09:00:00 UTC2019-08-06 10:00:00 UTC000
Aug 6, 10:002019-08-06 10:00:00 UTC2019-08-06 11:00:00 UTC000
Aug 6, 11:002019-08-06 11:00:00 UTC2019-08-06 12:00:00 UTC000
Aug 6, 12:002019-08-06 12:00:00 UTC2019-08-06 13:00:00 UTC000
Aug 6, 13:002019-08-06 13:00:00 UTC2019-08-06 14:00:00 UTC000
Aug 6, 14:002019-08-06 14:00:00 UTC2019-08-06 15:00:00 UTC101
Aug 6, 15:002019-08-06 15:00:00 UTC2019-08-06 16:00:00 UTC101

What Hacker News says

1 sources
> Please see here: https://github.com/electric-sheep-uc/black-sheep/blob/0735de... Creating and destroying threads in a tight loop (and blocking on their destruction, thereby reducing the point of having many) seems like a bad idea. Conceptually you have only maximum of two threads in any given part of this snippet, the one running the loop and the current instance of visThread. My guess is also that the loop thread spends most of its time waiting for the recently created threads to die. Why not have visThread only get created once and process a queue of events? Anyway without additional evidence you potentially flagged a bug in the c++ standard library rather than pthread_create.
In The Linux kernel's inability to gracefully handle low memory pressure

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.