Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
vaughan
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
91.
▲
by
vaughan
4y ago
Spreadsheets are rather peculiar. I don't think anyone would come up with the concept of them today. This "fill formula down/right" feature is so strange. A developer would be like: let's just set a formula for the
92.
▲
by
vaughan
4y ago
Thanks great links. I've been following some of those projects for a while. I haven't dived into the differential dataflow stuff yet. I think a lot of these projects may be handicapped though by trying to work with existing SQL qu
93.
▲
by
vaughan
4y ago
Incremental view maintenance is the general problem and there was recently an extension or feature released to help with this: https://wiki.postgresql.org/wiki/Incremental_View_Maintenanc... The problem is that I think
94.
▲
by
vaughan
4y ago
Makes me think of the current frontend trend of compiled reactive ui frameworks like Svelte. Also the SQLite bytecode engine. https://www.sqlite.org/opcode.html
95.
▲
by
vaughan
4y ago
I've come to believe that relational is the wrong choice for most apps. Most people choose a relational db without even realizing what relational means and what the tradeoffs are. Almost every app dev would prefer that their app reacts
96.
▲
by
vaughan
4y ago
There is way too much local ad-hoc state in modern web apps. (Ad-hoc as opposed to persisted state.) The first example of UI frameworks is always the `counter`, but it's always the least realistic scenario you encounter. Almost every a
97.
▲
by
vaughan
4y ago
The point is not that we should code using visual tools, but that our code should be visualizable. And for debugging, we write textual pretty printers for data structures, but wouldn't it be better to have them graphically visualized.
98.
▲
Programming Should Be Visual
(vjpr.medium.com)
2 points
by
vaughan
4y ago
|
3 comments
99.
▲
by
vaughan
4y ago
I never heard of "smacker", but now I understand where "smackeroos/smackeroonies" comes from in Aus.
100.
▲
by
vaughan
4y ago
I think the problem with talking about understandable code is that we only talk about textual representation. We should break out of the ide and visualize code more. I think then we would see the tangled mess we are creating. And then if we
101.
▲
by
vaughan
4y ago
Turning off SIP means you can’t run iOS apps on macOS. This sucks.
102.
▲
by
vaughan
4y ago
I think this is the future of programming. When we ask ourselves: "how should we structure our code?", the primary goal should be: so that it's easily visualizable and debuggable. Our guiding principles at the moment are all
103.
▲
by
vaughan
4y ago
My biggest pain point with programming is I am constantly rebuilding mental models of software projects. I think its a problem with the way we write software. I think all code we write should be visualizable at different levels of granulari
104.
▲
by
vaughan
4y ago
Gallon drink bottle with a drinking tube.
105.
▲
A Note on Distributed Computing (1994) [pdf]
(scholar.harvard.edu)
88 points
by
vaughan
4y ago
|
42 comments
106.
▲
by
vaughan
4y ago
Original title: A Note on Distributed Computing > A better approach is to accept that there are irreconcilable differences between local and distributed computing, and to be conscious of those differences at all stages of the design and
107.
▲
by
vaughan
4y ago
Thanks for the interesting read. I agree with sentiment of the paper in that it can never be fully transparent. When I say "it should just be a process of identifying hot function calls..." this is admittedly a little contrived -
108.
▲
by
vaughan
4y ago
> Only when this is all done, you think about the communication patterns and discuss how to scale the app. The main thing is that regardless of scaling, the app should always be able to run/debug/test locally in a monolithic
109.
▲
by
vaughan
4y ago
I find it interesting that most discussion forums have essentially the same data model, but just a different UI and moderation. Think: Reddit, HN, Twitter, Discord, TikTok, Insta, Signal/Whatsapp/Telegram/Messenger. I feel li
110.
▲
by
vaughan
4y ago
I cannot understand how everyone avoids the most obvious solution to all of this. Blocking. Instead of bans, Twitter could just add people to their own block list, and then tell new and existing users that they can opt-in to a moderated Twi
111.
▲
by
vaughan
4y ago
Reverse engineering can be a fun adventure.
112.
▲
by
vaughan
4y ago
The query planner can always change how it runs and is a black box. Nodes in the plan thus cannot be cached. This means that for streaming we are usually re-running the entire query, or doing some custom stuff. When a source table changes,
113.
▲
by
vaughan
4y ago
> But don't confuse the visualization with the system. I think this is where people have got it wrong in the past. This tool is an example of something in the right direction: https://www.ilograph.com/ It's jus
114.
▲
by
vaughan
4y ago
> all of the extra information that comes with being visual I think the key is to not make everything visual. You want to be able to view your system as you would draw it on a whiteboard. I believe it could be done using a restricted syn
115.
▲
by
vaughan
4y ago
Thanks for the link. Enso looks very cool. The traceability aspect is nice. I'd never want to use a visual interface to "code" though like they show in their intro video. They have the two-way sync to code-diagram which is co
116.
▲
by
vaughan
4y ago
People don't have enough time to step back from their tools and think about what the ideal thing would look like. I'm convinced this entire space should be visual. We always visualize data pipelines in our minds and on whiteboards
117.
▲
by
vaughan
4y ago
So cool!
118.
▲
by
vaughan
4y ago
person->eat(bread)
119.
▲
by
vaughan
4y ago
> We should be able to build entire web and cloud infrastructures by wiring components together visually 100%. I think this is the next wave of development. Back to the future. > Not monkey about with YAML and JSON. The key difference
120.
▲
by
vaughan
4y ago
Git is a good example because most tools will have a command-palette that prints out the git commands they are running to retrieve data to render. Otherwise they are using libgit2. It's interesting to think about the difference between
More ›