frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Palantir's secret weapon isn't AI – it's Ontology. An open-source deep dive

https://github.com/Leading-AI-IO/palantir-ontology-strategy
57•leading-AI•2h ago•34 comments

How I use Claude Code: Separation of planning and execution

https://boristane.com/blog/how-i-use-claude-code/
223•vinhnx•4h ago•140 comments

Japanese Woodblock Print Search

https://ukiyo-e.org/
23•curmudgeon22•1h ago•3 comments

Show HN: Llama 3.1 70B on a single RTX 3090 via NVMe-to-GPU bypassing the CPU

https://github.com/xaskasdf/ntransformer
144•xaskasdf•7h ago•33 comments

A Botnet Accidentally Destroyed I2P

https://www.sambent.com/a-botnet-accidentally-destroyed-i2p-the-full-story/
45•Cider9986•3h ago•16 comments

Evidence of the bouba-kiki effect in naïve baby chicks

https://www.science.org/doi/10.1126/science.adq7188
96•suddenlybananas•6h ago•25 comments

How far back in time can you understand English?

https://www.deadlanguagesociety.com/p/how-far-back-in-time-understand-english
414•spzb•3d ago•237 comments

Two Bits Are Better Than One: making bloom filters 2x more accurate

https://floedb.ai/blog/two-bits-are-better-than-one-making-bloom-filters-2x-more-accurate
31•matheusalmeida•4d ago•2 comments

Scientists discover recent tectonic activity on the moon

https://phys.org/news/2026-02-scientists-tectonic-moon.html
23•bookmtn•4d ago•1 comments

Parse, Don't Validate and Type-Driven Design in Rust

https://www.harudagondi.space/blog/parse-dont-validate-and-type-driven-design-in-rust/
145•todsacerdoti•8h ago•39 comments

zclaw: personal AI assistant in under 888 KB, running on an ESP32

https://github.com/tnm/zclaw
127•tosh•15h ago•69 comments

CXMT has been offering DDR4 chips at about half the prevailing market rate

https://www.koreaherald.com/article/10679206
173•phront•14h ago•154 comments

Claws are now a new layer on top of LLM agents

https://twitter.com/karpathy/status/2024987174077432126
232•Cyphase•1d ago•672 comments

People Loved the Dot-Com Boom. The A.I. Boom, Not So Much

https://www.nytimes.com/2026/02/21/technology/ai-boom-backlash.html
25•1vuio0pswjnm7•1h ago•16 comments

Forward propagation of errors through time

https://nicolaszucchet.github.io/Forward-propagation-errors-through-time/
16•iNic•2d ago•0 comments

Toyota Mirai hydrogen car depreciation: 65% value loss in a year

https://carbuzz.com/toyota-mirai-massive-depreciation-one-year/
117•iancmceachern•10h ago•270 comments

EDuke32 – Duke Nukem 3D (Open-Source)

https://www.eduke32.com/
164•reconnecting•8h ago•61 comments

Gamedate – A site to revive dead multiplayer games

https://gamedate.org/
8•msuniverse2026•1d ago•0 comments

Canvas_ity: A tiny, single-header <canvas>-like 2D rasterizer for C++

https://github.com/a-e-k/canvas_ity
71•PaulHoule•9h ago•24 comments

Inputlag.science – Repository of knowledge about input lag in gaming

https://inputlag.science
75•akyuu•8h ago•12 comments

Acme Weather

https://acmeweather.com/blog/introducing-acme-weather
221•cryptoz•21h ago•130 comments

I verified my LinkedIn identity. Here's what I handed over

https://thelocalstack.eu/posts/linkedin-identity-verification-privacy/
1200•ColinWright•21h ago•422 comments

Finding forall-exists Hyperbugs using Symbolic Execution

https://dl.acm.org/doi/full/10.1145/3689761
24•todsacerdoti•5d ago•1 comments

What not to write on your security clearance form (1988)

https://milk.com/wall-o-shame/security_clearance.html
410•wizardforhire•11h ago•182 comments

Be wary of Bluesky

https://kevinak.se/blog/be-wary-of-bluesky
271•kevinak•1d ago•181 comments

Personal Statement of a CIA Analyst

https://antipolygraph.org/statements/statement-038.shtml
194•grubbs•10h ago•116 comments

Permacomputing

https://wiki.xxiivv.com/site/permacomputing.html
115•tosh•4d ago•28 comments

Uncovering insiders and alpha on Polymarket with AI

https://twitter.com/peterjliu/status/2024901585806225723
137•somerandomness•1d ago•129 comments

A16z partner says that the theory that we’ll vibe code everything is wrong

https://www.aol.com/articles/a16z-partner-says-theory-well-050150534.html
101•paulpauper•1d ago•158 comments

Keep Android Open

https://f-droid.org/2026/02/20/twif.html
2015•LorenDB•1d ago•694 comments
Open in hackernews

Show HN: ProcASM – A general purpose, visual programming lanugage

https://procasm.temware.site
11•Temdog007•9mo ago
I've been working as a software engineer since 2016. I've always had side projects that I would work on outside of my job. At first, it was just web games. But in 2021, I took an interest in programming languages and started making my own. When I got laid off from my job in late 2023 (budget cuts according to my employer), I decided to focus on becoming an independent developer and being able to monetize my own software.

Since I was working on programming languages, my plan was to make a commercial grade programming language. Monetizing it would be difficult since there are so many free and open source programming languages out there. The only way I could think to stand out was to make something that hasn't been made before. General purpose programming languages DO exist; Visual programming languages DO exist. As far as I know, general purpose, visual programming languages DO NOT exist. So, that is what I decided to create.

I wrote a blog on my website <https://temware.site/html/blogs/procasm_justification.html> talking about how ProcASM works and some justifications on why developers and companies would consider using it. There is documentation <https://procasm.temware.site/documentation.html> describing ProcASM's concepts in more detail. And, there is a manual <https://procasm.temware.site/manual.html> that describes how to use application itself.

I have examples on the website <https://procasm.temware.site/procedure_view.html> showcasing how procedures are displayed in ProcASM. The images on that page are procedures, created in ProcASM, that were exported to SVG files from ProcASM.

You can try out ProcASM for free in your browser here: <https://procasm.temware.site/demo.html>

If you just want to see examples in ProcASM, use the links below to load projects in the demo.

Sample Project: <https://procasm.temware.site/demo.html?sampleProject=https%3...> Execute the Procedures: *Fibonacci*, *Test: Fizz Buzz*, and *Guess Number* to get an idea on how ProcASM works.

Network Project: <https://procasm.temware.site/demo.html?sampleProject=https%3...> This project contains examples of TCP clients and servers. If your using the browser version, you can load the project and view the procedures. However, you cannot execute any of the procedures in this project since they rely on native dynamic libraries which can't be executed in the browser. If you are using the desktop version, you can execute the procedures: Test TCP Client, Test TCP Server, and Test HTTP Server. This page <https://procasm.temware.site/getting_started.html?show=netwo...> can help you with compiling a dynamic library on you machine.

Support Forum Project: <https://procasm.temware.site/demo.html?sampleProject=https%3...> To ensure that ProcASM was suitable for software development, I decided to create something non-trivial with it; the back-end for the support forum <https://forum-procasm.temware.site>. The project was transpiled to C code using ProcASM (available only for the desktop versions). Then, that C code was compiled on a FreeBSD machine to generate an executable. That executable is running on a FreeBSD server. The *Server* procedure is the *main* procedure for the application. The dynamic library is not available. So, you can only view the procedures in this project.

Comments

nizarmah•9mo ago
I just saw the Hello World example on the website, and the video.

It seems like your program is really capable, but I'm finding the UI extremely overwhelming.

I find myself comparing this to MIT's Scratch, and I know your tool is much more capable, but the user experience makes Scratch so intuitive.

Everything reads like a short sentence, and I can just dive in without understanding what I'm doing.

Any chance this can turn into something like "building legos"?

Blocks can be built exactly like Scratch. And, then, maybe you can map their input/output streams as a way to connect blocks (ideally inferred on the run).

And people can re-use blocks that others have built.

I know this is supposed to be a programming language, not a toy. But, selfishly, I want the UX to feel like it's a toy, so simple to discover it on my own. I can imagine prototyping stuff with it, especially if there's a library of stuff that I can use or contribute to while doing so...

Temdog007•9mo ago
Thanks for the feedback.

I was wondering if the UI might give users some trouble. I had decided to write my own GUI library for this application instead of using an existing one. But now, I think retooling the GUI with an existing GUI library is in order.

> Any chance this can turn into something like "building legos"?

I'm not sure what you mean by "building legos"? Right now, users can create and reuse procedures. Sub-procedures, on the other hand, are tied to a specific procedure. I think this tool can work fine as is for prototyping.

But without a better UI, users may be choosing not use the app at all. So, I'll focus on a UI redesign.

nizarmah•9mo ago
The legos was referring to user experience, sorry about the vagueness.

I'd love to try this again with a simpler UI. If there's a place I can follow for updates, LMK.

mdaniel•9mo ago
> Personal Subscriptions are per-user. So, this subscription is valid for one user

So if it's $100 per year and it's a programming language, at 366 days I can't even use what I already wrote? I'd advocate for the JetBrains licensing model: it remains licensed to the user indefinitely but just with no updates. Otherwise for a programming language that's extortion not a licensing fee

Temdog007•9mo ago
> it remains licensed to the user indefinitely but just with no updates

That is how the purchasing model currently works. Once you have downloaded the executable, you are free to use it forever even after your subscription ends.

But, I can see where there might be confusion. So, I'll be sure to re-word that page and make it more clear.