HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
winglang
wing
TypeScript2022–2023
winglang / wing

wing

A programming language for the cloud ☁️ A unified programming model, combining infrastructure and runtime code into one language ⚡

6Distinct people
9Mentions
0Explicit recommenders
5.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A programming language for the cloud ☁️ A unified programming model, combining infrastructure and runtime code into one language ⚡

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 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 month9 dated mentions

Observed mentions: 2022-12-19 14:11:38 UTC to 2023-12-06 19:17:59 UTC.

01232022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 20222023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 20232023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsDec 2023

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
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC000
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC000
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC110
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC303
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC101
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC000
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC000
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC101
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC211

What Hacker News says

9 sources
> Why a whole language rather than a library that could just as well abstract the cloudy infrastructure and expose its data structures as "first class citizens" ? "Very cool, but what here cannot be done by a library or compiler extension? In existing languages, where there is no way to distinguish between multiple execution phases, it is impossible to naturally represent this idea that an object has methods that can only be executed from within a specific execution phase (or within certain scopes of the program). You are welcome to read more about it here (including code samples that show the same app built in Wing vs. other solutions)." https://github.com/winglang/wing#very-cool-but-what-here-can...
In Show HN: Winglang – A new cloud-oriented programming language
In my opinion, AWS can be challenging for developers who are not familiar with cloud. The main issue is that it's not very user-friendly to fully utilize all the features of AWS through the Management Console alone. Here are some specific challenges: 1. Constantly switching between different components can cause frequent context switches, making it harder to work efficiently. 2. AWS offers a wide range of capabilities, and developers may struggle with figuring out how to effectively combine them in real-world scenarios. 3. There are many concepts and security restrictions within AWS, such as IAM, which adds complexity to the learning curve. To make the most of what AWS has to offer, developers need to invest time in studying extensive documentation and even learn Infrastructure as Code. Unfortunately, this can slow down the implementation
Read the rest
of innovative ideas. Fortunately, there are a few new tools that can help address these problems. For instance: - Plutolang: https://github.com/pluto-lang/pluto - Winglang: https://github.com/winglang/wing - Nitric: https://github.com/nitrictech/nitric
In Ask HN: Is the AWS console developers friendly?
In this insightful article, Elad Ben-Israel, the mind behind the CDK, shares his love for the cloud, but also his frustrations with the complexity of building cloud applications. The challenges he identifies include: 1. Focus on non-functional mechanics: The need to understand and manage cloud platform mechanics instead of focusing on building valuable features for users. 2. Lack of independence: Developers often need to rely on others to handle parts of the deployment process or to resolve issues, interrupting their work flow. 3. Delayed feedback: The current iteration cycle in cloud development can take minutes or even longer, significantly slowing down the development process and making it harder for developers to stay in their flow state. ## It's not just a rant Elad is not just ranting about cloud development. He proposes a solution
Read the rest
in the form of a programming language for the cloud. This language would treat the entire cloud as its computer. The language compiler will be able to see the complete cloud application, unbound by the limits of individual machines. Such a compiler would be able to handle a significant portion of the application's non-functional aspects, enabling developers to operate at a more abstract level, thus reducing complexity and promoting autonomy. Moreover, it could expedite iteration cycles by allowing to compile applications to quick local simulators during the development process. ## The Winglang Project Elad reveals that he's in the process of developing such an open-source, “cloud-oriented” language, dubbed Winglang (https://github.com/winglang/wing). Wing aims to improve the developer experience of cloud applications by enabling developers to build distributed systems that leverage cloud services as first-class citizens. This is achieved by integrating infrastructure and application code in a secure, unified programming model. Wing programs can be executed locally via a fully-functional simulator or deployed to any cloud provider. ## My Interest in Winglang I, together with a group of dedicated contributors, joined forces with Elad to develop Winglang. While still in Alpha and not yet ready for production use, it's already possible to build some real applications (https://github.com/winglang/research/tree/main/dogfooding). Check out https://github.com/winglang/wing for more details.
In [dead]
This insightful article by Gregor Hohpe covers: * Evolution of programming abstractions. * Challenges of cloud abstractions. * Importance of tools like stack traces for debugging, especially in distributed systems. Gregor emphasizes that effective cloud abstractions are crucial but tricky to get right. He points out that debugging at the abstraction level can be complex and underscores the value of good error messages and observability. The part about the "unhappy path" particularly resonated with me: "The unhappy path is where many abstractions struggle. Software that makes building small systems easy but struggles with real-world development scenarios like debugging or automated testing is an unwelcome version of “demoware” - it demos well, but doesn’t actually work in the real world. And there’s no unlock code. ... I propose the follow
Read the rest
ing test for vendors demoing higher-level development systems: 1. Ask them to enter a typo into one of the fields where the developer is expected to enter some logic. 2. Ask them to leave the room for two minutes while we change a few random elements of their demo configuration. Upon return, they would have to debug and figure out what was changed. Needless to say, no vendor ever picked the challenge." Why it interests me? I'm one of the creators of Winglang (https://github.com/winglang/wing), an open-source programming language for the cloud that allows developers to work at a higher level of abstraction. We set a goal for ourselves to provide good debugging experience that will allow developers to debug cloud applications in the context of the logical structure of the apps. After reading this article I think we can rephrase the goal as being able to easily pass Gregor's vendor test from above :)
In Programming without a stack trace: When abstractions become illusions
This insightful article by Adam Ruka covers: - What's IaC. - First gen. tools: Declarative, Host Provisioning (Chef, Puppet, Ansible). - Second gen. tools: Declarative, Cloud (CloudFormation, Terraform, Azure Resource Manager). - Third gen. tools: Imperative, Cloud (AWS CDK, Pulumi, SST). - The future: Infrastructure from Code (Wing, Eventual, Ampt, Klotho). Why it interests me? I'm one of the creators of Winglang (https://github.com/winglang/wing) that is featured there as one of the future 4th gen. tool, along with Eventual (https://github.com/functionless/eventual), Ampt (https://github.com/getampt) and Klotho (https://github.com/klothoplatform/klotho).
In History and Future of Infrastructure as Code
None of the links to the Github repositories for the language resolve. I checked the link for the compiler [1], the SDK [2], and the VSCode extension [3], and all of them 404. Seems like the repositories are all still private, which is odd, given that the page claims However, it's definitely ready for those brave of hearts who would like to be involved at this early stage, influence our roadmap and join us for the ride. Kind of hard to do that when all the source code is closed. [1]: https://github.com/orgs/winglang/projects/1 [2]: https://github.com/orgs/winglang/projects/3 [3]: https://github.com/winglang/wing
In Wing: A cloud-oriented programming language – request alpha access

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.