On Tuesday, 7 April 2020 at 19:12:49 UTC, Laurent Tréguier wrote:
> I started working on this project to make it more comfortable to write D back in 2017,

Thanks for the time and effort you put into this. DLS has been a great piece of software. Thanks again!

On Tuesday, 7 April 2020 at 19:12:49 UTC, Laurent Tréguier wrote:
>
> So today, I am deprecating DLS, along with its editor extensions.
>

I've used it over a year, and unlike code-d it just works. Thank you for your hard work and good luck!

On Tuesday, 7 April 2020 at 22:20:40 UTC, Laurent Tréguier wrote:
> On Tuesday, 7 April 2020 at 20:03:21 UTC, Aliak wrote:
>> Is what you’re working on shareable information (just out of curiosity)?
>
> It's shareable (it's on Github just like DLS); it's a mobile app, the Android version is in Kotlin, and the iOS version in Swift. I think it's hard to beat native languages for these platforms, as they both have tailored APIs and development environments (and they are backed by giant companies putting lots of resources into them)

Yeah, no doubt, it's always that last 10-20 percent of the way you have to go with the non-native languages on those platforms that gets you. The downside is the manpower required to maintain two platforms.

I've been meaning to give flutter a try though... it seems to be catching steam. Only problem is google is "known" for just dropping things. But who knows, let's see.

And WildFyre looks very interesting! Good luck with your future endeavours!

On Wednesday, 8 April 2020 at 12:47:57 UTC, aliak wrote:
> On Tuesday, 7 April 2020 at 22:20:40 UTC, Laurent Tréguier wrote:
>> On Tuesday, 7 April 2020 at 20:03:21 UTC, Aliak wrote:
>>> Is what you’re working on shareable information (just out of curiosity)?
>>
>> It's shareable (it's on Github just like DLS); it's a mobile app, the Android version is in Kotlin, and the iOS version in Swift. I think it's hard to beat native languages for these platforms, as they both have tailored APIs and development environments (and they are backed by giant companies putting lots of resources into them)
>
> Yeah, no doubt, it's always that last 10-20 percent of the way you have to go with the non-native languages on those platforms that gets you. The downside is the manpower required to maintain two platforms.
>
> I've been meaning to give flutter a try though... it seems to be catching steam. Only problem is google is "known" for just dropping things. But who knows, let's see.
>
> And WildFyre looks very interesting! Good luck with your future endeavours!

Xamarin is a choice too.

On Wednesday, 8 April 2020 at 12:47:57 UTC, aliak wrote:
> Yeah, no doubt, it's always that last 10-20 percent of the way you have to go with the non-native languages on those platforms that gets you. The downside is the manpower required to maintain two platforms.
>
> I've been meaning to give flutter a try though... it seems to be catching steam. Only problem is google is "known" for just dropping things. But who knows, let's see.

That's one of the reasons I'm going native; native tools hopefully aren't going away anytime soon.

> And WildFyre looks very interesting! Good luck with your future endeavours!

Thank you, and thank you to everyone else in this thread. I'll probably still be watching D's evolution from afar, and I wish all the best to this community!

On Thursday, 9 April 2020 at 13:06:42 UTC, Laurent Tréguier wrote:
>
> Thank you, and thank you to everyone else in this thread. I'll probably still be watching D's evolution from afar, and I wish all the best to this community!

Thanks a lot for your work! What do you think about transferring the project to dlang-community? Also, I think it's better to leave the VSCode extension in the marketplace, even if you're not able to continue working on it, people would still like to continue to use it. For example, I recently switched computers and I just found out that the extension was unpublished.

On Thursday, 9 April 2020 at 14:59:41 UTC, Petar Kirov [ZombineDev] wrote:
> Thanks a lot for your work! What do you think about transferring the project to dlang-community? Also, I think it's better to leave the VSCode extension in the marketplace, even if you're not able to continue working on it, people would still like to continue to use it. For example, I recently switched computers and I just found out that the extension was unpublished.

It could be transferred to dlang-community if other members agreed to, but I don't know what this would achieve; I don't see the benefit of adding an archived project there.

The reason I unpublished it is because I don't want to leave an unmaintained extension in the marketplace. However, it's still possible to use it, you simply need to clone the extension repo with git, run `npm install` and `./node_modules/.bin/vsce package`, and then install the resulting VSIX file from VSCode (in the extension panel, there is an option to "install from VSIX")

On Wednesday, 8 April 2020 at 12:47:57 UTC, aliak wrote:
> [..]
>
> I've been meaning to give flutter a try though... it seems to be catching steam. Only problem is google is "known" for just dropping things. But who knows, let's see.
>

Flutter is indeed pretty cool. We've used it last year at work. And we'll likely continue using in the second half of this year.
I don't think Flutter will go away as it's been gaining really high traction (almost 90k stars on GitHub [1]), and in general, it looks like Google is accelerating its investment in the tech and the community [2]. Also, AFAIK, it's the primary app platform for their upcoming Fuchsia OS.

The Dart language, however, is seriously handicapped. It's much better than Go, but that's a pretty low bar. Ever since I've used Flutter, I've been making plans to create a tool that translates Dart code to D, so I could use the Flutter engine and the Flutter framework to write a D app ;)

[1]: https://github.com/flutter/flutter
[2]: https://flutterevents.com/

On Thursday, 9 April 2020 at 15:25:46 UTC, Laurent Tréguier wrote:
> On Thursday, 9 April 2020 at 14:59:41 UTC, Petar Kirov [ZombineDev] wrote:
>> Thanks a lot for your work! What do you think about transferring the project to dlang-community? Also, I think it's better to leave the VSCode extension in the marketplace, even if you're not able to continue working on it, people would still like to continue to use it. For example, I recently switched computers and I just found out that the extension was unpublished.
>
> It could be transferred to dlang-community if other members agreed to, but I don't know what this would achieve; I don't see the benefit of adding an archived project there.

The idea is to move it there, so other motivated members of the community can pick up the torch from where you left it and continue active development.

> The reason I unpublished it is because I don't want to leave an unmaintained extension in the marketplace.

Yes, I understand your intention. I still think it's better to leave it there for now, even if it's completely unmaintained, as removing it immediately causes more friction than the potential problems you're trying to avoid. Later on, we can publish the extension again under the dlang-community publisher and then you won't have to worry that people will complain to you when things break.

> However, it's still possible to use it, you simply need to clone the extension repo with git, run `npm install` and `./node_modules/.bin/vsce package`, and then install the resulting VSIX file from VSCode (in the extension panel, there is an option to "install from VSIX")

Thanks, I'll try this!

On Thursday, 9 April 2020 at 15:49:51 UTC, Petar Kirov [ZombineDev] wrote:
> The idea is to move it there, so other motivated members of the community can pick up the torch from where you left it and continue active development.

I doubt anyone will pick it up, but if someone wanted to, I would happily move it.

> Yes, I understand your intention. I still think it's better to leave it there for now, even if it's completely unmaintained, as removing it immediately causes more friction than the potential problems you're trying to avoid. Later on, we can publish the extension again under the dlang-community publisher and then you won't have to worry that people will complain to you when things break.

That's understandable, it's not broken just yet. I'll republish it for now.