From: Stefan Kangas <stefankangas@gmail.com>
To: "Daniel Mendler" <mail@daniel-mendler.de>,
"Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
Cc: "Ergus via Emacs development discussions." <emacs-devel@gnu.org>,
Yuan Fu <casouri@gmail.com>,
Theodor Thornhill <theo@thornhill.no>, Dmitry <dmitry@gutov.dev>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Philip Kaludercic <philipk@posteo.net>
Subject: Re: [PATCH] New major-mode: bicep-ts-mode
Date: Sun, 7 Jan 2024 12:26:19 -0800 [thread overview]
Message-ID: <CADwFkm=rh5dHJnaAvogZerrrL8Qx5VjPVKV3Cky2XJzn=Uh7ew@mail.gmail.com> (raw)
In-Reply-To: <87jzoldnpm.fsf@daniel-mendler.de>
Daniel Mendler via "Emacs development discussions."
<emacs-devel@gnu.org> writes:
> Jostein Kjønigsen <jostein@secure.kjonigsen.net> writes:
>> Currently if one works with Microsoft-oriented solutions (C#, .NET, TypeScript,
>> Azure, etc) one often also has to work with Bicep. Bicep is a programming
>> language used to describe Infrastructure-as-Code used for deploying services in
>> Microsoft Azure cloud.
>>
>> Unfortunately the only editor currently available with useful Bicep-support is
>> Microsoft VSCode. Working with Bicep in Emacs currently is not really feasible.
>>
>> The Bicep language itself is a type-safe language with an associated open-source
>> toolchain, which in turn gets compiled to JSON-formatted Azure Resource
>> Manager (ARM) templates, which can actually provision resources in Azure.
>>
>> With appropriate editor-support, working with Bicep is superior to working with
>> the untyped JSON for ARM template purposes. As such, adding support for Bicep
>> to Emacs, would mean most Azure-developers can still stay 100% within Emacs
>> to do their job :)
>
> Stefan Kangas <stefankangas@gmail.com> writes:
>> Daniel Mendler via "Emacs development discussions." writes:
>>> Also, recently there has also been a
>>> discussion to add a `bicep-ts-mode' to Emacs core, with the argument
>>> being that VSCode supports it. Makes sense, it is a Microsoft product to
>>> help using Microsoft products. The description of Bicep on Github
>>> (https://github.com/Azure/bicep) is "Bicep is a declarative language for
>>> describing and deploying Azure resources". Does Bicep really need to be
>>> part of Emacs core? Couldn't it be added to ELPA instead?
>>
>> I think we should be sympathetic to arguments such as the above, yes,
>> but why not ask this question in the Bicep thread instead? :-)
>
> Agree, the question if `bicep-ts-mode' should be added to ELPA instead
> of core should be discussed in the Bicep thread.
[Copying in Stefan and Philip.]
The basic question is: Would bicep-mode might make more sense in GNU
ELPA or in Emacs itself?
I don't know anything about Bicep or what it does specifically, but I'm
starting to lean towards GNU ELPA, myself. The basic reason is that
adding Bicep to core could be seen as promoting Azure, given that it
seems to only be useful for using that service specifically.
next prev parent reply other threads:[~2024-01-07 20:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 14:32 [PATCH] New major-mode: bicep-ts-mode Jostein Kjønigsen
2023-12-22 10:42 ` Stefan Kangas
2023-12-22 11:55 ` Jostein Kjønigsen
2023-12-24 14:32 ` Stefan Kangas
2024-01-02 7:52 ` Jostein Kjønigsen
2024-01-03 7:16 ` Yuan Fu
2024-01-04 4:52 ` Stefan Kangas
2024-01-05 19:10 ` Jostein Kjønigsen
2024-01-07 18:04 ` Daniel Mendler via Emacs development discussions.
2024-01-07 20:26 ` Stefan Kangas [this message]
2024-01-07 23:25 ` Stefan Monnier
2024-01-08 11:30 ` Jostein Kjønigsen
2024-01-08 19:23 ` Stefan Kangas
2024-01-09 0:33 ` Stefan Monnier
2024-01-09 19:12 ` Jostein Kjønigsen
2024-01-09 19:16 ` Stefan Kangas
2024-01-14 4:43 ` Stefan Monnier
2024-01-15 9:56 ` Jostein Kjønigsen
2024-01-15 17:35 ` Philip Kaludercic
2024-01-15 19:20 ` Stefan Monnier
2024-01-09 19:24 ` Philip Kaludercic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=rh5dHJnaAvogZerrrL8Qx5VjPVKV3Cky2XJzn=Uh7ew@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=casouri@gmail.com \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
--cc=jostein@secure.kjonigsen.net \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=theo@thornhill.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.