:screm:​ almost *every* time I open VS Code it updates an extension and then wants to be reloaded 🙃

@owenblacker @theresnotime I wonder why it's so bad at live-updating.

#Emacs has been doing that just fine for basically as long as it has existed.

@lispi314
Emacs added online repository of packages and package manager way later than ~198x, in late 200x I think.
@owenblacker @theresnotime

@nesc @owenblacker @theresnotime That's correct, but live updating of major parts of the #Lisp environment long predate the addition of the package repository.

@lispi314 @nesc @owenblacker @theresnotime

thats how IDEs worked in those days smalltalk was written in smalltalk so mod your code and it just restarts the module.

dunno if the restart thing is due to the trend to C code & compilers.

@dekkzz76 @nesc @owenblacker @theresnotime The part that's weird is that with static languages that's just normal and expected.

But VSCode is largely a Javascript codebase, or effectively it's written in a dynamic language (which is what allows both #Lisp and #Smalltalk environments the features they provide) yet ignoring those capacities.

Follow

@lispi314 people are used to thinking in statically-typed workflows. Working in dynamic systems is apparently not easy. Many of the -ers, e.g. @k9ox , have said it was too easy to make a mess. Even in , it is possible to irrecoverably mess up; it happens in the background too, I have never seen my Emacs run longer than a few months.
@dekkzz76 @nesc @owenblacker @theresnotime

@tetrislife @k9ox @dekkzz76 @nesc @owenblacker @theresnotime You can actually do dynamic languages with static typing, but yes people are used to limiting their thinking to static languages' capabilities.

I haven't really tried such long-lived sessions (kernel updates & not bothering to setup live-patching limiting the opportunity), but even if you just read-desktop & save-desktop at the start & end of your workday, you largely don't need to restart #Emacs to update packages.

@lispi314 @tetrislife @k9ox @nesc @owenblacker @theresnotime

Ruby 3.0 now does static typing following on from typescript's sucess

@tetrislife @lispi314 @k9ox @nesc @owenblacker @theresnotime

Yes i know from ruby what pitfalls dynamic typing can get you into, but good coders tens to minimise getting bitten. them,

@dekkzz76 It's more that in most dynamic systems, you can overwrite stuff you really shouldn't touch and very much break your live environment.

You've got the power, but using it responsibly is up to you.

@lispi314

not a problem for me, i was brouught up on that & when 128K RAM was a lot.

@dekkzz76 Yeah, so doing fun stuff like modifying calling conventions in a live system. Bad idea. You can do it though. :3

@lispi314

then we get to modern languages allowing duck typing & metaprogramming ;) more worms....

@dekkzz76 Yeah, you could add duck-typing to CL via metaprogramming features.

I wouldn't recommend doing so. The strong types are a feature.

@dekkzz76 I recall some project adding dependent types to it though, which is pretty cool.

@lispi314 @dekkzz76

let agree = String::from("with everyone here I guess. But my timeline is full of this Convo so I thought I'd join in")

Sign in to participate in the conversation
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.