2 ms·

> More like breaking changes That certainly has not been my experience with the language since 1.0 > weird issues with basic transitive dependencies breaking

> More like breaking changes That certainly has not been my experience with the language since 1.0 > weird issues with basic transitive dependencies breaking after a minor version bump to the language. Not sure what exactly this is referring to, but I suspect it was some bugs that happened when some stdlib packages were taken out of the sysimage and started being treated more like regular packages which are pre-installed. For a couple minor versions, if you instantiated an manifest from a previous version that used some stdlibs, it could error out. That was indeed unfortunate and IMO should not have been released as such, but it's since been fixed. I will point out though that officially, you are not supposed to use the same manifest across versions. > didn't even know you could do web dev in Julia. I don't want to know what that looks like. There's actually some rather cool stuff happening in that space, but yeah it's early days.

lalalanananana 29d ago
Yea this wasn't user error which is the common gaslight trope from the Julia community. Yes some of these instances post dated 1.0 . Yes the average person is sick of being told there's nothing wrong with the technology when there's been a serious track record of it being a disaster. For companies an expensive one. It's really not early days. The language is about 15 years old. That excuse gets really tired. It's crazy to me how every person posting positively about Julia has the same tactics. They don't change year after year. They try to draw people in only to find it's a Trainwreck or a waste of time. I just hope my comments save a start up a few million dollars or a curious hobbyist 5 months of their free time.
- eigenspace 29d ago
  Not trying to gaslight you. Especially if you were hitting that issue with the stdlibs, as I said, I don't think we should have allowed a release to go out with that problem. It was treated as bug though and fixed (though it also took longer than hoped). The manifest thing is a good example of a hard situation. You have a file format that's not designed to be portable across versions, but the usage pattern around it heavily encourages that, so of course it gets used across versions and bad stuff happens. I'm sure theres also some other examples like this one can pull up. Of course there's cases where we should be doing better. I'm just also saying that this isn't the only experience out there, and the negative experience you're reporting isn't my experience. > It's really not early days. The language is about 15 years old. That excuse gets really tired. Please don't twist my words. I was responding to what you said about webdev, and I said there was some interesting things happening in that space, but still early days. I was explicitly referring to the webdev ecosystem being immature, not the language.

lalalanananana 29d ago

Yea this wasn't user error which is the common gaslight trope from the Julia community. Yes some of these instances post dated 1.0 . Yes the average person is sick of being told there's nothing wrong with the technology when there's been a serious track record of it being a disaster. For companies an expensive one. It's really not early days. The language is about 15 years old. That excuse gets really tired. It's crazy to me how every person posting positively about Julia has the same tactics. They don't change year after year. They try to draw people in only to find it's a Trainwreck or a waste of time. I just hope my comments save a start up a few million dollars or a curious hobbyist 5 months of their free time.

eigenspace 29d ago
Not trying to gaslight you. Especially if you were hitting that issue with the stdlibs, as I said, I don't think we should have allowed a release to go out with that problem. It was treated as bug though and fixed (though it also took longer than hoped). The manifest thing is a good example of a hard situation. You have a file format that's not designed to be portable across versions, but the usage pattern around it heavily encourages that, so of course it gets used across versions and bad stuff happens. I'm sure theres also some other examples like this one can pull up. Of course there's cases where we should be doing better. I'm just also saying that this isn't the only experience out there, and the negative experience you're reporting isn't my experience. > It's really not early days. The language is about 15 years old. That excuse gets really tired. Please don't twist my words. I was responding to what you said about webdev, and I said there was some interesting things happening in that space, but still early days. I was explicitly referring to the webdev ecosystem being immature, not the language.