Re:Kube Doom, Kill Kubernetes Pods Using Id's Doom
by SahAssar on Monday October 05, 2020 @06:22PM
(#24692711)
That's only true if you don't consider the context that the code lives in. For example coloration in editors could be considered a visualization of additional dimensions of info (syntax, types) and autocompletes are like a branching "time-like" dimension. Besides that code mostly tries to solve problems that can be represented and show visually.
The need exists, how to turn that into a solution with a useable interface that I'd use for multiple hours a day is beyond me though.
For me Bret Victor's talks point to this problem where we treat code as something we only interact with as text but it can be so much more: https://vimeo.com/36579366 https://vimeo.com/64895205
Re:Kube Doom, Kill Kubernetes Pods Using Id's Doom
by b0rsuk on Tuesday October 06, 2020 @03:44AM
(#24695540)
Computers have essentially 1D instructions. They execute instruction after instruction. Making a 2D programming language would cause an extra layer of abstraction between the programmer and instructions. There would be performance and memory use issues.
Re:Kube Doom, Kill Kubernetes Pods Using Id's Doom
by k__ on Tuesday October 06, 2020 @07:31AM
(#24696627)
Yes, maybe 2D for multiple processors?
Re:Kube Doom, Kill Kubernetes Pods Using Id's Doom
by cinquemb on Tuesday October 06, 2020 @05:36AM
(#24696091)
My problem with programming is that I don't even want to look at the screen, type on the keyboard or use a mouse.
Constantly translating my thoughts and ideas manually through my hands and eyes directly is annoying.
So 2D programming isn't really a thing. That's probably why 3D isn't a thing either.