We have quite a FoC relevant edition of Papers We Love Education this month: we’ll be discussing “Hedy: A Gradual Language for Programming Education” with Professor Felienne Hermans! Thursday 26th at 6pm CET, all the info here: https://github.com/papers-we-love/edu/discussions/11 For those not familiar with Hedy: https://www.hedycode.com/

The code engine in Henosia can now interact with Chrome's own debugger, including any local variables used at the breakpoint. It's an internal tool for now to debug the code engine. Might be useful for hybrid designers though 😁 Details in this twitter post.

I've implemented Effect handlers in my language https://vimeo.com/794219638 This is now the whole feature set I wanted to version 2 of my language. Now all that's left is to actually use it

Hi friends! I'm new to this slack, but I've been dabbling in this space off and on for a while. I've completed a draft of a blog post about type inference in my projectional language / structured editor, and I'd love to get your feedback! "Type inference that sticks". thanks! 🙂

Heya, small demo showing sync between nodysseus instances. While this is on a desktop, it also works between two different devices so long as they are online at the same time

Hi everyone I did a talk at the Peckham Digital festival yesterday! It's about spatial programming! I come in at 42:59 :) https://www.youtube.com/live/L2U_Sd1qMJ4?feature=share&t=2579

I've now published my post about type inference + projectional editing 🙂 thanks for the feedback! https://jaredforsyth.com/posts/type-inference-that-sticks/ (HN)

With @Patrick Dubroy we have been working for some months on a digital-first book "for JavaScript programmers who want to learn the nuts and bolts of WebAssembly. You'll go from hand crafting bytecodes to building a real compiler for a simple programming language." 🐦 Announcement Tweet On top of writing a book we are exploring what's possible if we create content ignoring the constraints of "printing dead words". Follow WasmGroundUp for updates, or sign up at https://wasmfromthegroundup.com.

Nice, sounds really interesting! Sign me up as a beta user right now

Hey all, finally released a pretty cool (well I think so) demo of the rules language DSL we built for fighting spam/abuse/fraud/all-the-bad-stuff at Smyte (acquired by Twitter). It's heavily SQL-based but includes a lot of features for working with very large teams, deploying new rules in seconds, and tracing which rules caused an action to occur. Demo: https://websqrl.vercel.app/twitter Docs: https://sqrl-lang.github.io/sqrl/ Motivation: https://sqrl-lang.github.io/sqrl/motivation.html Would welcome any comments/questions. Just glad to finally get this out the door 🥳

cross-sharing from #devlog-together

Outables: Outlines + Data Tables - Row & column pagination - Customizable number of rows and columns per page - Pin & Hide columns - Expand a row to see all fields - Ctrl + Click to jump 10 pages - Ctrl + Alt + Click to jump to first/last page

hello everyone please enjoy my new video that I've been working on for a while now. it's about a few different topics that might be relevant to you such as programming, creative coding, life, art, intelligence, definitions and dead fish

Hey everyone! Really excited about this new feature we shipped today at Subset, which allows you to jump between your different files kind of like Notion. I’ve noticed that I have a ton of little trackers and calculators that I eventually forget about, but every time I come across it again, it reminds me of a task I need to do. Ultimately, it makes individual files and spreadsheets less ephemeral. Here’s what it looks like. Next up we probably need some grouping or favoriting system. Let me know if you have any thoughts 🙂

Future of Coding • Episode 62 Fred Brooks • No Silver Bullet 𒂶 https://futureofcoding.org/episodes/062 Jimmy and I have each read this paper a handful of times, and each time our impressions have flip-flopped between “hate it so much” and “damn that’s good”. There really are two sides to this one. Two reads, both fair, both worth discussing: one of them within “the frame”, and one of them outside “the frame”. So given that larger-than-normal surface for discursive traversal, it’s no surprise that this episode is, just, like, intimidatingly long. This one is so, so long, friends. See these withered muscles and pale skin? That’s how much time I spent in Ableton Live this month. I just want to see my family. No matter how you feel about Brooks, our thorough deconstruction down to the nuts and bolts of this seminal classic will leave you holding a ziplock bag full of cool air and wondering to yourself, “Wait, this is philosophy? And this is the future we were promised? Well, I guess I’d better go program a computer now before it’s too late and I never exist.” For the next episode, we’re reading a fish wearing a bathrobe. Sorry, it’s late and I’m sick, and I have to write something, you know?

Made a code notebook for datalog queries. https://vimeo.com/798469951 As there is no plain text (or parser) does this count as another structural editor

Prototyping an interactive WebAssembly spec interpreter for https://wasmfromthegroundup.com/

A four-minute demo of Leibniz, my Digital Scientific Notation: https://diode.zone/w/1RUVjM5xj54gZjHXobSNUe

Inspired by re-reading Naur’s “Programming as Theory Building” I decided to make myself a text editor to solve all my problems… tl;dr I wrote a blog post and some bash instead 😂

Hello everyone! 👋 I am thrilled to share the progress made with Flyde with this community of like-minded individuals. Flyde is an open-source, flow-based, and visual programming toolkit that prioritizes exceptional UX/DX and seamless integration with existing code. The toolkit features a VSCode extension, visual debugging, full TypeScript support, a rich standard library, and is designed to work in tandem with existing codebases. In essence, Flyde is similar to NodeRED, but geared towards web development. This is the first time I am sharing Flyde with a broader community, and I believe feedback from such a talented, inquisitive, and passionate group of people would be invaluable to the project. Check out the interactive playground here - https://www.flyde.dev/playground/! I look forward to hearing your thoughts and feedback! Additionally, a star on GitHub would be greatly appreciated! 😊

Sorry if this has been asked before, I couldn’t find it in the history with search, but how’d folks feel about threading the URLs to their personal sites? I’d love to follow more folks over RSS.

May be of interest to Future of Coding folks as a way to get feedback or share your work. VL/HCC 2023 (IEEE Symposium on Visual Languages and Human-Centric Computing) is currently soliciting papers (abstracts due April 21, papers due April 28). -------------------------- VL/HCC 2023: IEEE Symposium on Visual Languages and Human-Centric Computing https://conf.researchr.org/home/vlhcc-2023 The IEEE Symposium on Visual Languages and Human-Centric Computing is the premier international forum for research on this topic. Established in 1984, the mission of the conference is to support the design, theory, application, and evaluation of computing technologies and languages for programming, modeling, and communicating, which are easier to learn, use, and understand by people. The 2023 symposium is scheduled to take place October 2-6 in Washington, DC, USA. VL/HCC 2023 is 100% Sponsored by IEEE Computer Society Technical Committee on Multimedia Computing (TCMC). ***Call for Research Papers*** IMPORTANT DATES - Abstracts only: April 21, 2023 - Submission deadline: April 28, 2023 - Rebuttal phase: June 5 - 9, 2023 - Notification: June 23, 2023 - Camera-ready: July 14, 2023 SCOPE AND TOPICS We solicit original, unpublished research papers on computing technologies for modeling, programming, communicating, and reasoning, which are easier to learn, use or understand by humans than the current state-of-the-art. Papers should focus on efforts to design, formalize, implement, or evaluate those technologies and languages. This includes technologies intended for general audiences (e.g., professional or novice programmers, or the public) or domain-specific audiences (e.g., people working in business administration, production environments, healthcare, urban design or scientific domains). Empirical papers that validate current proposed solutions with rigorous scientific means (i.e., empirical studies, controlled experiments, rigorous case studies, etc.) are also welcome. Areas of interest include, but are not limited to: - Visual languages: Novel visual languages, Design, evaluation, and theory of visual languages and applications, Development of systems for manipulating and interacting with diagrammatic representations - Human aspects and psychology of software development and language design, such as supporting inclusion and diversity in programming - End-user development: End-user development, adaptation and programming, Creation and evaluation of technologies and infrastructures for end-user development - Crowdsourcing design and development work - Representations: Novel representations and user interfaces for expressing computation, Software, algorithm and data visualization - Modeling: Model-driven development, Domain-specific languages, including modeling languages, Visual modeling of human behavior and socio-technical systems - Thinking more deeply about code: Computational thinking and Computer Science education, Debugging and program understanding, Explainable ML/AI If you are not sure if your paper is a good fit for VL/HCC, feel free to email the PC Co-chairs (see “Contact” below). We welcome those new to the VL/HCC community to submit! SPECIAL EMPHASIS FOR 2023: Low-Code / No-Code Development This year’s special topic is “Low-Code / No-Code Development”. This development paradigm enables the creation and deployment of fully functional applications using visual abstractions and interfaces and requiring little or no procedural code. This way, users are empowered to create software applications for constrained domains, even if they lack a programming background. This year, we especially welcome papers at VL/HCC that design, build, or evaluate any aspects of low-code and no-code solutions. PAPER SUBMISSIONS We invite two kinds of papers: - full-length research papers, up to 8 pages - plus unlimited additional pages containing only references and/or acknowledgements - short research papers, up to 4 pages - plus unlimited additional pages containing only references and/or acknowledgements Papers must be submitted using the IEEE two-column conference paper format. Be sure to use the current IEEE conference paper format (which was updated in 2019), and to select the “US letter” template: http://www.ieee.org/conferences_events/conferences/publishing/templates.html Papers should be submitted via the EasyChair system (https://easychair.org/conferences/?conf=vlhcc2023). To facilitate the assigning of papers to reviewers, we require paper abstracts to be submitted via EasyChair at least 1 week prior to the paper submission deadline (see Important Dates below). The abstract must be kept up to date such that it matches exactly the abstract in the submitted paper. The abstract must be no longer than 250 words. All accepted papers, whether full or short, should be complete, self-contained, archival contributions. Contributions from full papers are more extensive than those from short papers. Note that some full paper submissions may be accepted as short papers if reviewers deem contributions to be comparable in size to a short paper. Work-in-progress, which has not yet yielded an archival contribution, should be submitted to the Posters/Showpieces category. All submissions will be reviewed by members of the Program Committee in a double-blind review process. Authors will then receive the reviews for their submissions and will be able to answer them in a rebuttal phase. Only after this step the PC will make a final decision about the acceptance of the submissions. Submissions and reviews for the technical program are managed with EasyChair. At least one author of each accepted paper is required to register for VL/HCC 2023 and present the paper at the conference. There will be a virtual presentation option in case of travel restrictions. IEEE reserves the right to exclude a paper from distribution after the conference, including IEEE Xplore Digital Library, if the paper is not presented by the author at the conference. The proceedings of IEEE VL/HCC are published in digital form by the IEEE Computer Science Society and archived in the IEEE Digital Library with an official ISBN number. Accepted papers will be available to conference attendees via the IEEE Open Preview program in the IEEE Xplore Digital Library (http://ieeexplore.ieee.org/). DOUBLE-BLIND REVIEWING We follow a double-blind reviewing process. Both authors and reviewers are expected to make every effort to honor the double-blind reviewing process. In case of questions, please contact the Program Chairs. Authors should ensure that the submission can be evaluated without it being obvious who wrote the paper. This means leaving author names off the paper and using terms like “previous research” rather than “our previous research” when describing background. However, do not hide previous work – papers must still reference all relevant research using full (non-anonymized) citations, including the author’s own prior work, so that reviewers can evaluate novelty. Please reference your own prior work in the third-person just like you would do for any other related work (e.g., avoid “As described in our previous work [10], … ” and instead write something like “As described by [10], …“). It is also important that authors specify all conflicts of interest with potential reviewers during the submission phase. Reviewers should not undertake any investigation that might lead to the revealing of authors’ identity. If identities are inadvertently revealed, please contact the Program Chairs. The Program Chairs will check all submissions for obvious signs of lack of anonymity and may ask authors to make changes and resubmit the paper within three days of the submission deadline. Only changes to resolve anonymity issues will be permitted. EVALUATION AND JUSTIFICATION Papers are expected to support their claims with appropriate evidence. For example, a paper that claims to improve programmer productivity is expected to demonstrate improved productivity; a paper that claims to be easier to use should demonstrate increased ease of use. However, not all claims necessarily need to be supported with empirical evidence or studies with people. For example, a paper that claims to make something feasible that was clearly infeasible might substantiate its claim through the existence of a functioning prototype. Moreover, there are many alternatives to empirical evidence that may be appropriate for justifying claims, including analytical methods, formal arguments or case studies. Given this criterion, we encourage potential authors to think carefully about what claims their submission makes and what evidence would adequately support these claims. In addition, we expect short papers to have less comprehensive evaluation than long papers. CONTACT PC Co-Chairs: - Philip Guo (University of California San Diego, United States) - Esther Guerra (Universidad Autónoma de Madrid, Spain) - Contact email: vlhcc2023@googlegroups.com

Wrote something recently on the idea of using LLMs as part of in-the-loop software assistants: https://nickarner.com/notes/llm-powered-assistants-for-complex-interfaces-february-26-2023/

Here's a little gif of the new scenario editor in the version 1.4 of Blawx I released today. It allows the user to make fully-, partially-, or un-ground statements that are true, false, or unknown , answers the query with natural language explanations that set out the assumptions being used for unknowns, and then recommends additional fact statements that would be relevant to finding additional conclusions that are not based on assumptions. It's aimed at encoding statutes and regulations in such a way as to allow those encodings to be made, or at least validated, by lawyers and other non-programmers. Feedback welcome. https://github.com/Lexpedite/blawx. The new release is up at dev.blawx.com now.

I just integrated the newly announced ChatGPT API into GlooData, here's a video showing how to use it to schedule slack messages with interesting facts about home appliances.

Hey folks, I have been hanging around Future-of-Code-like communities for a few years, trying to figure out what I want my focus to be. I’ve finally figured it out, and I made a demo video to share with y’all about what I’m working on. It’s a web and mobile app for tracking your personal information, including allowing end users to configure buttons and actions to customize their workflow. It’s not groundbreaking research, but it does enable end users to create interactive software anywhere they are. I’ve been able to replace at least four apps I previously used with “boards” I’ve configured in this app. I plan to open-source it and set up a free open-registration server soon. Here’s the demo if anyone would like to take a look!

We've just published our first academic paper about Clerk, in case anyone's interested: https://twitter.com/jackrusher/status/1635434839968194561?s=20

Today we released our Slack bot for anyone working with companies or communities with active link sharing and discussions. (Also available as a discord bot!) The bots give you a searchable archive of all links, videos, events, pdfs that people post in your Slack channel. (Search coming this or latest early next week!) Bit like the archive here at the Future of Coding Slack. Also it's GPT supported to give you summaries of articles and youtube videos, so you can much more easily see if things are worth watching/reading. Here is more info, and here instructions on how to give it a try.

I’ve been playing around with hand tracking, inspired by Bret Victor’s Future of Interaction Design article from ages back, and it’s come together in this little toy I made, combining fluid simulation: Magic Hands 🙌 (blog post) Very much a starting point, but quite keen to see what else can be done with hand tracking in the browser - also keen to hear more examples of hand tracking work 🙂