1083587559907745792, 1166970972882128896, 1208980950744330240, 1210042197027876864
This commit is contained in:
1 parent
ecce37ab9a
commit
ef7201f5bf
7 files changed
+323
No files matched your search
+39
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: "Problems I don't have when writing C and C++ code:"
|
||||
type: archive
|
||||
source: twitter
|
||||
source_url: "https://x.com/rfleury/status/1083587559907745792"
|
||||
author: "Ryan Fleury"
|
||||
handle: rfleury
|
||||
post_id: "1083587559907745792"
|
||||
date: 2019-01-11
|
||||
archived: 2026-08-26
|
||||
draft: false
|
||||
tags:
|
||||
- archive
|
||||
- twitter
|
||||
- rfleury
|
||||
description: "Problems I don't have when writing C and C++ code:"
|
||||
in_reply_to: ""
|
||||
---
|
||||
|
||||
## Source
|
||||
|
||||
- URL: https://x.com/rfleury/status/1083587559907745792
|
||||
- Author: Ryan Fleury (@rfleury)
|
||||
- Posted: 2019-01-11 04:53:01
|
||||
|
||||
## Thread
|
||||
|
||||
**1/** **@rfleury** ^1083587559907745792
|
||||
|
||||
Problems I don't have when writing C and C++ code:
|
||||
* Managing memory
|
||||
* Organization
|
||||
* Readability
|
||||
* Ownership
|
||||
* Verbosity
|
||||
* "Elegance"
|
||||
|
||||
Problems I do have when writing C and C++ code:
|
||||
* Not having extremely basic introspection and code generation capabilities
|
||||
+43
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: "@rfleury For a moment I thought you were revealing your new lisp-like"
|
||||
type: archive
|
||||
source: twitter
|
||||
source_url: "https://x.com/William_Bundy/status/1166972251993866245"
|
||||
author: "William Bundy"
|
||||
handle: William_Bundy
|
||||
post_id: "1166972251993866245"
|
||||
date: 2019-08-29
|
||||
archived: 2026-08-26
|
||||
draft: false
|
||||
tags:
|
||||
- archive
|
||||
- twitter
|
||||
- rfleury
|
||||
description: "@rfleury For a moment I thought you were revealing your new lisp-like"
|
||||
in_reply_to: ""
|
||||
parent_post_id: "1166970982155767808"
|
||||
---
|
||||
|
||||
## Source
|
||||
|
||||
- URL: https://x.com/William_Bundy/status/1166972251993866245
|
||||
- Author: William Bundy (@William_Bundy)
|
||||
- Posted: 2019-08-29 07:14:00
|
||||
|
||||
## Branch
|
||||
|
||||
**1/** **@William_Bundy** ^1166972251993866245
|
||||
|
||||
**@rfleury**
|
||||
|
||||
For a moment I thought you were revealing your new lisp-like
|
||||
|
||||
**2/** **@rfleury** ^1166973237806256130
|
||||
|
||||
**@William_Bundy**
|
||||
|
||||
Ha, nope; just thoughts on non-textual programming. No work being done right now by me (though I might experiment with a special-case environment for The Melodist's scripting language).
|
||||
|
||||
## Related
|
||||
|
||||
- Spine: [[archive/threads/rfleury/2019-08-29-why-do-we-spend-so-much-effort-to-encode]]
|
||||
+37
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: "@rfleury Many people seem skeptical of this idea with regards to alternative ways to render or edit the AST but I think there is a pretty clear path forward there personally..."
|
||||
type: archive
|
||||
source: twitter
|
||||
source_url: "https://x.com/hmn_riscy/status/1167764451724017664"
|
||||
author: "RISCY BUSINESS"
|
||||
handle: hmn_riscy
|
||||
post_id: "1167764451724017664"
|
||||
date: 2019-08-31
|
||||
archived: 2026-08-26
|
||||
draft: false
|
||||
tags:
|
||||
- archive
|
||||
- twitter
|
||||
- rfleury
|
||||
description: "@rfleury Many people seem skeptical of this idea with regards to alternative ways to render or edit the AST but I think there is a pretty clear path forward there personally..."
|
||||
in_reply_to: ""
|
||||
parent_post_id: "1166970982155767808"
|
||||
---
|
||||
|
||||
## Source
|
||||
|
||||
- URL: https://x.com/hmn_riscy/status/1167764451724017664
|
||||
- Author: RISCY BUSINESS (@hmn_riscy)
|
||||
- Posted: 2019-08-31 11:41:55
|
||||
|
||||
## Branch
|
||||
|
||||
**1/** **@hmn_riscy** ^1167764451724017664
|
||||
|
||||
**@rfleury**
|
||||
|
||||
Many people seem skeptical of this idea with regards to alternative ways to render or edit the AST but I think there is a pretty clear path forward there personally...
|
||||
|
||||
## Related
|
||||
|
||||
- Spine: [[archive/threads/rfleury/2019-08-29-why-do-we-spend-so-much-effort-to-encode]]
|
||||
@@ -0,0 +1,60 @@
|
||||
---
|
||||
title: "Why do we spend so much effort to encode programming language semantics into a textual form just so a parser can go through the error-prone process of ripping that same exact information back out? Why not work directly on a program's abstract-syntax tree? (1/8)"
|
||||
type: archive
|
||||
source: twitter
|
||||
source_url: "https://x.com/rfleury/status/1166970972882128896"
|
||||
author: "Ryan Fleury"
|
||||
handle: rfleury
|
||||
post_id: "1166970972882128896"
|
||||
date: 2019-08-29
|
||||
archived: 2026-08-26
|
||||
draft: false
|
||||
tags:
|
||||
- archive
|
||||
- twitter
|
||||
- rfleury
|
||||
description: "Why do we spend so much effort to encode programming language semantics into a textual form just so a parser can go through the error-prone process of ripping that same exact information back out? Why not work directly on a program's abstract-syntax tree? (1/8)"
|
||||
in_reply_to: ""
|
||||
---
|
||||
|
||||
## Source
|
||||
|
||||
- URL: https://x.com/rfleury/status/1166970972882128896
|
||||
- Author: Ryan Fleury (@rfleury)
|
||||
- Posted: 2019-08-29 07:08:55
|
||||
|
||||
## Thread
|
||||
|
||||
**1/** **@rfleury** ^1166970972882128896
|
||||
|
||||
Why do we spend so much effort to encode programming language semantics into a textual form just so a parser can go through the error-prone process of ripping that same exact information back out? Why not work directly on a program's abstract-syntax tree? (1/8)
|
||||
|
||||
**2/** **@rfleury** ^1166970974463377408
|
||||
|
||||
This would speed up builds and tools by preventing a parsing step entirely. It would also allow tools to more easily work within the semantics of the language, both because of the lack of a parsing requirement, and also because of the form of the modifications. (2/8)
|
||||
|
||||
**3/** **@rfleury** ^1166970975834927104
|
||||
|
||||
You wouldn't need to use strings to reference other pieces of the code, you could just *actually* reference them. Say goodbye to needing to fix up identifier usage sites when you change something, or having to ever care about a symbol table when writing a code tool. (3/8)
|
||||
|
||||
**4/** **@rfleury** ^1166970977470705665
|
||||
|
||||
This also has the property of decoupling code representation from code semantics. Zooming out in an editor could produce dynamic code LODs. Visualization of parallelized code becomes as easy as visually seeing two execution streams down two execution paths. (4/8)
|
||||
|
||||
**5/** **@rfleury** ^1166970978670301184
|
||||
|
||||
A debugger could visually show a piece of code writing into visually-represented memory. The memory could also be represented in different forms. Why not hit a button and have it visualized as 3D geometry, or a texture? Writing the wrong result would instantly be knowable. (5/8)
|
||||
|
||||
**6/** **@rfleury** ^1166970979861422082
|
||||
|
||||
Instead, right now, we're stuck looking at static text that: Constantly breaks and does not reflect a valid program without constant modification and maintenance, fundamentally couples representation with semantics, and innately prevents better tooling from easily existing. (6/8)
|
||||
|
||||
**7/** **@rfleury** ^1166970981006508032
|
||||
|
||||
Can you imagine if "find the definition for this type" in a large codebase didn't take *in the order of seconds* to complete, because your editor wouldn't need to search for it? Or, maybe you want to search for every function in the program *without* waiting 10 seconds. (7/8)
|
||||
|
||||
**8/** **@rfleury** ^1166970982155767808
|
||||
|
||||
I argue that this is the natural next step in computing. Artists do not manually write down a set of pixels, vertex data, or musical notes to get the results that they want, as we've decided there can be better tools for that. Why do we think that's untrue for programming? (8/8)
|
||||
|
||||
Branches: [[archive/threads/rfleury/2019-08-29-why-do-we-spend-so-much-effort-to-encode/2019-08-29-William_Bundy-for-a-moment-i-thought-you-were-revealing-your]], [[archive/threads/rfleury/2019-08-29-why-do-we-spend-so-much-effort-to-encode/2019-08-31-hmn_riscy-many-people-seem-skeptical-of-this-idea-with]]
|
||||
+92
@@ -0,0 +1,92 @@
|
||||
---
|
||||
title: "The new 4coder update, beta 4.1.0, has been awesome! I've already had a ton of fun adding custom editor features that both help out quite a bit when programming, or are just fun."
|
||||
type: archive
|
||||
source: twitter
|
||||
source_url: "https://x.com/rfleury/status/1208980950744330240"
|
||||
author: "Ryan Fleury"
|
||||
handle: rfleury
|
||||
post_id: "1208980950744330240"
|
||||
date: 2019-12-23
|
||||
archived: 2026-08-26
|
||||
draft: false
|
||||
tags:
|
||||
- archive
|
||||
- twitter
|
||||
- rfleury
|
||||
description: "The new 4coder update, beta 4.1.0, has been awesome! I've already had a ton of fun adding custom editor features that both help out quite a bit when programming, or are just fun."
|
||||
in_reply_to: ""
|
||||
---
|
||||
|
||||
## Source
|
||||
|
||||
- URL: https://x.com/rfleury/status/1208980950744330240
|
||||
- Author: Ryan Fleury (@rfleury)
|
||||
- Posted: 2019-12-23 05:21:35
|
||||
|
||||
## Thread
|
||||
|
||||
**1/** **@rfleury** ^1208980950744330240
|
||||
|
||||
The new 4coder update, beta 4.1.0, has been awesome! I've already had a ton of fun adding custom editor features that both help out quite a bit when programming, or are just fun. Here's a thread showcasing them:
|
||||
|
||||
#programming
|
||||
|
||||
**2/** **@rfleury** ^1208980963465678848
|
||||
|
||||
Scope ending annotations, brace highlight, and brace lines! If the top of a scope is not visible, an annotation will be displayed at the closing brace to help me understand where I am.
|
||||
|
||||

|
||||
|
||||
**3/** **@rfleury** ^1208980980989456384
|
||||
|
||||
Code peek! I can take a look at type/function/general search results of an identifier instantly, without opening a separate tab or window.
|
||||
|
||||

|
||||
|
||||
**4/** **@rfleury** ^1208980987427741696
|
||||
|
||||
Calculator comments! Any comment starting with '//c' will be parsed as a set of mathematical statements. Variables and functions can be used. Very useful for quick inline calculations that either document some math, or are used as rough calculations in the moment.
|
||||
|
||||

|
||||
|
||||
**5/** **@rfleury** ^1209231171881586688
|
||||
|
||||
Added graphing to calculator comments!
|
||||
|
||||

|
||||
|
||||
**6/** **@rfleury** ^1209281825895411713
|
||||
|
||||
Continuing to improve these.
|
||||
|
||||

|
||||
|
||||
**7/** **@rfleury** ^1209918796879679488
|
||||
|
||||
More 4coder plotting!
|
||||
|
||||

|
||||
|
||||
**8/** **@rfleury** ^1209918986638352387
|
||||
|
||||
Adding the ability to plot data from source code (WIP).
|
||||
|
||||

|
||||
|
||||
**9/** **@rfleury** ^1209944968590086144
|
||||
|
||||
Time as an input...
|
||||
|
||||
<video controls src="https://video.twimg.com/tweet_video/EMqWbsZUcAAgiPC.mp4"></video>
|
||||
|
||||
**10/** **@rfleury** ^1209946577583788032
|
||||
|
||||
...it can be used anywhere.
|
||||
|
||||
<video controls src="https://video.twimg.com/tweet_video/EMqX-YeUUAAtZnl.mp4"></video>
|
||||
|
||||
**11/** **@rfleury** ^1210073680950087680
|
||||
|
||||
Sweeping through bin sizes!
|
||||
|
||||
<video controls src="https://video.twimg.com/tweet_video/EMsLlkpU4AA5IR7.mp4"></video>
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: ""
|
||||
type: archive
|
||||
source: twitter
|
||||
source_url: "https://x.com/rfleury/status/1210042197027876864"
|
||||
author: "Ryan Fleury"
|
||||
handle: rfleury
|
||||
post_id: "1210042197027876864"
|
||||
date: 2019-12-26
|
||||
archived: 2026-08-26
|
||||
draft: false
|
||||
tags:
|
||||
- archive
|
||||
- twitter
|
||||
- rfleury
|
||||
description: ""
|
||||
in_reply_to: ""
|
||||
---
|
||||
|
||||
## Source
|
||||
|
||||
- URL: https://x.com/rfleury/status/1210042197027876864
|
||||
- Author: Ryan Fleury (@rfleury)
|
||||
- Posted: 2019-12-26 03:38:35
|
||||
|
||||
## Thread
|
||||
|
||||
**1/** **@rfleury** ^1210042197027876864
|
||||
|
||||
|
||||
|
||||
<video controls src="https://video.twimg.com/tweet_video/EMru2bJUYAApcdu.mp4"></video>
|
||||
|
||||
**2/** **@rfleury** ^1210072723038191617
|
||||
|
||||
Basic interpolation demo with my 4coder animated plots.
|
||||
|
||||
<video controls src="https://video.twimg.com/tweet_video/EMsKpuBVUAEG87O.mp4"></video>
|
||||
|
||||
**3/** **@rfleury** ^1210275665942941696
|
||||
|
||||
Cleaning up the visuals of plots a bit with better fonts and number labels on axes.
|
||||
|
||||
<video controls src="https://video.twimg.com/tweet_video/EMvDOqMUUAEo7eG.mp4"></video>
|
||||
|
||||
**4/** **@rfleury** ^1210277746552606720
|
||||
|
||||
omg just realized the y-axis is flipped.
|
||||
@@ -11,6 +11,10 @@ tags:
|
||||
|
||||
- [[archive/threads/rfleury/2018-11-12-in-modern-day-software-engineering-culture-there]]
|
||||
- [[archive/threads/rfleury/2018-12-10-a-recent-lesson-ive-learned-about-programming-the]]
|
||||
- [[archive/threads/rfleury/2019-01-11-problems-i-dont-have-when-writing-c-and-c-code]]
|
||||
- [[archive/threads/rfleury/2019-08-29-why-do-we-spend-so-much-effort-to-encode]]
|
||||
- [[archive/threads/rfleury/2019-12-23-the-new-4coder-update-beta-4-1-0-has-been-awesome]]
|
||||
- [[archive/threads/rfleury/2019-12-26-thread]]
|
||||
- [[archive/threads/rfleury/2024-12-18-one-of-the-most-powerful-lessons-i-learned-as-a]]
|
||||
- [[archive/threads/rfleury/2025-04-30-to-the-degree-this-is-true-its-only-in-a]]
|
||||
- [[archive/threads/rfleury/2025-10-10-new-post-multi-core-by-default]]
|
||||
|
||||
Reference in new issue
Block a user