HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vshymanskyy
ViperIDE
JavaScript2024–2024
vshymanskyy / ViperIDE

ViperIDE

An innovative MicroPython / CircuitPython IDE for Web and Mobile

Developer ToolsCommand LineWeb DevelopmentHardware & EmbeddedMobile & Desktop
Explore on GitHubRead Hacker News discussions
2Distinct people
2Mentions
1Explicit recommenders
594GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An innovative MicroPython / CircuitPython IDE for Web and Mobile

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

This is super cool, and I love the old school tech stack. It makes for a very approachable codebase and a fast user experience. As a reminder given the recent polyfill io…

esprehn used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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, 3:56:07 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 3-hour interval2 dated mentions

Observed mentions: 2024-06-30 12:24:39 UTC to 2024-07-02 15:14:18 UTC.

012024-06-30 12:00:00 UTC to 2024-06-30 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 30, 12:002024-06-30 15:00:00 UTC to 2024-06-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-30 18:00:00 UTC to 2024-06-30 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-30 21:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 00:00:00 UTC to 2024-07-01 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 03:00:00 UTC to 2024-07-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 06:00:00 UTC to 2024-07-01 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 09:00:00 UTC to 2024-07-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 12:00:00 UTC to 2024-07-01 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 1, 12:002024-07-01 15:00:00 UTC to 2024-07-01 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 18:00:00 UTC to 2024-07-01 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 21:00:00 UTC to 2024-07-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-02 00:00:00 UTC to 2024-07-02 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-02 03:00:00 UTC to 2024-07-02 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-02 06:00:00 UTC to 2024-07-02 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-02 09:00:00 UTC to 2024-07-02 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-02 12:00:00 UTC to 2024-07-02 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-02 15:00:00 UTC to 2024-07-02 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 2, 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
Jun 30, 12:002024-06-30 12:00:00 UTC2024-06-30 15:00:00 UTC110
Jun 30, 15:002024-06-30 15:00:00 UTC2024-06-30 18:00:00 UTC000
Jun 30, 18:002024-06-30 18:00:00 UTC2024-06-30 21:00:00 UTC000
Jun 30, 21:002024-06-30 21:00:00 UTC2024-07-01 00:00:00 UTC000
Jul 1, 00:002024-07-01 00:00:00 UTC2024-07-01 03:00:00 UTC000
Jul 1, 03:002024-07-01 03:00:00 UTC2024-07-01 06:00:00 UTC000
Jul 1, 06:002024-07-01 06:00:00 UTC2024-07-01 09:00:00 UTC000
Jul 1, 09:002024-07-01 09:00:00 UTC2024-07-01 12:00:00 UTC000
Jul 1, 12:002024-07-01 12:00:00 UTC2024-07-01 15:00:00 UTC000
Jul 1, 15:002024-07-01 15:00:00 UTC2024-07-01 18:00:00 UTC000
Jul 1, 18:002024-07-01 18:00:00 UTC2024-07-01 21:00:00 UTC000
Jul 1, 21:002024-07-01 21:00:00 UTC2024-07-02 00:00:00 UTC000
Jul 2, 00:002024-07-02 00:00:00 UTC2024-07-02 03:00:00 UTC000
Jul 2, 03:002024-07-02 03:00:00 UTC2024-07-02 06:00:00 UTC000
Jul 2, 06:002024-07-02 06:00:00 UTC2024-07-02 09:00:00 UTC000
Jul 2, 09:002024-07-02 09:00:00 UTC2024-07-02 12:00:00 UTC000
Jul 2, 12:002024-07-02 12:00:00 UTC2024-07-02 15:00:00 UTC000
Jul 2, 15:002024-07-02 15:00:00 UTC2024-07-02 18:00:00 UTC101

What Hacker News says

2 sources
esprehn·Jul 2, 2024Recommendation phrase
This is super cool, and I love the old school tech stack. It makes for a very approachable codebase and a fast user experience. As a reminder given the recent polyfill io attack, don't use public CDN hosted JS without also setting SRI attributes [1]. It's a marginal perf benefit because the cache is partitioned by top level domains now and it opens you up to attacks from the CDN owners. https://github.com/vshymanskyy/ViperIDE/issues/14 As a bonus set CSP headers and a nonce when you can too, but definitely set SRI on any 3p scripts. [1]: https://developer.mozilla.org/en-US/docs/Web/Security/Subres...
In Show HN: ViperIDE – MicroPython IDE for web and mobile

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.