From: Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Heime <heimeborgia@protonmail.com>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Websites with drupal and php
Date: Mon, 30 Dec 2024 14:10:18 +0000 [thread overview]
Message-ID: <haRdCekxzJVqAL411lpn_TefO8kDCCgEvWBdehYbWbO6ZEQZWi7bqBzcPzycC7z-uuzzlZABpK_wbHlrEG0Ey_TIXqRbfWaC8ZljyY-4gik=@protonmail.com> (raw)
In-Reply-To: <7dkcJbw_PS8hnV_T9CylHCNv_3dW7F4Rv4-9Guer0KDJwvfue0jLA-2zrlqlTDuPcmy-_YjlPkeYFyBLRv8U5k7v5HeSivH4Ee0x3my96iw=@protonmail.com>
Sent with Proton Mail secure email.
On Saturday, December 21st, 2024 at 8:58 AM, Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> Have got a work assignment for a website where they are currently
> using wordpress. Been thinking about drupal with php. What is the
> Gnu Project current advice for good websites?
Have been scrutinising things some more and got to some conclusions on different
backend languages.
For Scalability and Security: Java or Kotlin (especially with Spring Boot).
For Modern Development Practices: Kotlin (interoperability with Java while being more modern).
For Rapid Prototyping and Flexibility: Python (Django or Flask).
For Legacy System Compatibility: PHP (especially with CMS needs) or Perl (for existing Perl-based systems).
For Performance-Critical Systems: Rust (although rare for full backend systems).
Has anyone got experience in Kotlin?
prev parent reply other threads:[~2024-12-30 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 20:58 Websites with drupal and php Heime via Users list for the GNU Emacs text editor
2024-12-27 10:46 ` Jean Louis
2024-12-28 12:25 ` Heime via Users list for the GNU Emacs text editor
2024-12-30 14:10 ` Heime via Users list for the GNU Emacs text editor [this message]
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='haRdCekxzJVqAL411lpn_TefO8kDCCgEvWBdehYbWbO6ZEQZWi7bqBzcPzycC7z-uuzzlZABpK_wbHlrEG0Ey_TIXqRbfWaC8ZljyY-4gik=@protonmail.com' \
--to=help-gnu-emacs@gnu.org \
--cc=heimeborgia@protonmail.com \
/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.