@eldereko

> he plugins are still very few compared to other mature editors. also, it’s not quite as configurable as Sublime

AFAIU, it doesn’t have a plugin runtime, which is fairly glaring to me (but maybe not for devs these days).

This is what triggered my “is it hype” thought, as I’ve seen people say it does but it’s in rust or something.

And I feel like many fail to realise how hard it is to build a new editor with everything we take for granted these days.

Fediverse & typst similarly.

@programming

I get that peeps are coming from VSCode and I support competition with MS’s EEE of software dev.

But, like, bloat and corporate capture were always the trade offs with VSCode … you all knew that right?

@hrefna @tschenkel @astrojuanlu @programming

Yea … it seems that things like this are part of Julia’s problem …

that for many the “two language problem” is actually the “two language solution” that’s working just fine and as intended, or as you say, well enough to make an ecosystem jump seem too costly.

@FizzyOrange

Yea I remember reading about some deeper issues with the language (Dan Luu was quite dark on it I think) and that more or less turned me off. At the time I would have had to have been amongst some dedicated users urging me on to consider adoption.

@festus

In general, how much more performant would you say Rust is or can be than Julia? Any good resources on this?

What’s interesting about this take is that it targets the whole “two language” thing and implies that it might be a fool’s errand.

@mvirts

Problem with that logic is that python was essentially “reborn” at some point 2010-2012.

That’s when scipy, pandas and notebooks all came together, and with early pandas putting python on the map more than some (cough - Guido - cough) are willing to admit.

Of course the maturity of the ecosystem by then is part of it … but also pushing through the python 3 situation wasn’t trivial and likely speaks to the momentum the science stack brought to the ecosystem.

@tschenkel @astrojuanlu @programming

I understood … I was reaching for some shorthand (500 char limits FTW!)

There’s probably a good amount of work that exists somewhere between your needs and “could be a spreadsheet”, where caring about performance isn’t an issue or hasn’t surfaced yet, either practically or culturally (where the boundaries of what research *can* be done “tomorrow” are of importance)

BTW, cheers for all the info!!

@tschenkel @astrojuanlu @programming

I’d suppose part of the problem might be that there’s a somewhat hidden 3rd category of user that “feels” whatever added complexity there is in a two-language lang like julialang and has no real need for performant “product” code.

And that lack of adoption amongst this cohort and your first enforces lang separation.

I may be off base with whether there’s a usability trade off, but I’d bet there’s at least the perception of one.

@astrojuanlu @programming

> Maybe nobody (save for the Julia developers) ever cared about the “two language problem”

Yea, it’s what prompted my post. I saw in a rust forum push back on the two language thing but from the lower level side (where they were arguing about introducing lazier memory management facilities on the basis that you should just use swift/Python etc).

And re MATLAB … absolutely! This is not a diss against Julia at all.