Re:Stop Writing Dead Programs (Transcript)
by kibwen on Tuesday October 18, 2022 @08:22PM
(#33255874)
It's also just the wrong place in the stack to add these features. It's not a language concern, it's a platform concern. If I'm running a program in a web browser, it doesn't matter what language it's written in, I can pause the program and interactively explore it via the browser console. We should have the same thing for native apps on operating systems in general, and they should be native to the OS (provided by the OS vendor themselves) and not require any modification to the program (or any special programming language) in order to use.
[ Parent
| on HN ]
Re:Stop Writing Dead Programs (Transcript)
by mwcampbell on Tuesday October 18, 2022 @09:06PM
(#33256164)
To what extent can native-code debuggers, like lldb, fill this need?
Re:Stop Writing Dead Programs (Transcript)
by jmartin2683 on Tuesday October 18, 2022 @09:23PM
(#33256285)
I agree this would be very cool. I can’t count the number of times I wish I had runtime interactive debugging in a repl along the lines of pry in Ruby in just about every language that doesn’t have it.
That said, gdb etc are pretty awesome too if it’s an option
Re:Stop Writing Dead Programs (Transcript)
by none_to_remain on Tuesday October 18, 2022 @09:30PM
(#33256323)
This pretty much means debugging a running process' assembly code
You can already do this but it is a difficult way to play
Re:Stop Writing Dead Programs (Transcript)
by pjmlp on Wednesday October 19, 2022 @04:06AM
(#33259075)
History has proven it only works on language platforms, and as Dan Ingals asserts, the OS shouldn't be there.
Anyway a modern OS where this is partially there, is Android.
Re:Stop Writing Dead Programs (Transcript)
by kibwen on Wednesday October 19, 2022 @10:08AM
(#33262418)
History has proven the exact opposite, as the failure of Smalltalk and the ascendancy of the web browser demonstrate. And as I assert, Dan Ingals is incorrect.
Re:Stop Writing Dead Programs (Transcript)
by pjmlp on Wednesday October 19, 2022 @10:47AM
(#33263019)
Last time I looked into it, the Web browser is a OS agnostic platform and JavaScript influence in tooling traces back to Smalltalk via SELF influence.
There are even two Smalltalk like development experiences Web browser based, Amber Smalltalk and Lively Kernel, the latter from Dan Ingals.
The OS should be an implementation detail of language runtimes, as proven by serveless computing and cloud native development, who cares if those runtimes run on top of an OS, bare metal or a type-1 hypervisor.