kernel

Kernel for z80 calculators

Systems & Infrastructure

Explore on GitHub Read Hacker News discussions

3Distinct people

9Mentions

0Explicit recommenders

300GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Kernel for z80 calculators

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, 2:59:53 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 year9 dated mentions

Observed mentions: 2014-01-20 08:48:57 UTC to 2018-02-02 20:27:01 UTC.

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.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2014	2014-01-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	4	1	3
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	2	0	2
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	0	0	0
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	1	1	0
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	2	0	2

What Hacker News says

2 sources

Sir_Cmpwn·Oct 27, 2015

I worked with a friend of mine to write a documentation generator for assembly code. It lets you write your docs with markdown, and has "[[syscall]]" syntax to link to another syscall from your docs. Example: http://www.knightos.org/documentation/reference/threading.ht... https://github.com/KnightOS/kernel/blob/06aeba5442a073d02338...

In Classeur.io: Re-enjoy writing, with Markdown

Sir_Cmpwn·Jul 25, 2015

I'd be happy to give some more detailed thoughts. I write a lot of assembly myself [1], so hopefully that lends me some credibility. I haven't read much of your TLS implementation, but I'm not a security researcher and I don't think I'm qualified to give an opinion on your particular implementation. However, there are some points to be made here. First of all, almost no one ships their own crypto for a good reason. To trust that something is secure, you need to have lots of people working on it and lots of projects invested in it (something that OpenSSL and such have). "Many eyes makes bugs shallow" is the common phrase, but it holds truer when large companies with highly skilled engineers are putting their secrets and their customer's secrets on the line. Your implementation has the unfortunate problem of being written in assembly. While

Read the rest

I don't think there's anything inherently wrong with assembly, many people don't share the same opinion. People will be reluctant to contribute to it (how do people contribute, anyway?). Also, it is easier to make mistakes in assembly, and I would be surprised if there weren't several mistakes in your TLS implementation and in the rest of the server. This doesn't reflect poorly on you as a developer, but is instead a consequence of choosing assembly. Assembly also inherits a lot of the common security problems C has (like buffer overflows), but makes them harder to identify. I would feel very uncomfortable exposing anything written in assembly to the public net, and doubly so if it used an unproven TLS stack written in the same. Other projects avoid the problem of untested crypto by using tested crypto from an external module like OpenSSL. [1] https://github.com/KnightOS/kernel

In Rwasa – A high-performance web server in x86_64 assembly