Good Morning Everyone,
Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework: * flask for most * pyramid for some of the biggest (bodhi, FAS3) * Django (askbot, Hyperkitty) * TurboGears2 (fedora-packages) * aiohttp (python3, async app: mdapi)
While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all.
However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly.
So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why?
Thanks for your inputs, Pierre
On Apr 21, 2016 5:18 AM, "Pierre-Yves Chibon" pingou@pingoured.fr wrote:
However, as I see us starting to look at JS for some of our apps
(fedora-hubs,
wartaa...), I wonder if we could start the discussion early about the
different
framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to
look at
the recommended one instead of picking one up semi-randomly.
Just to clarify, some apps are starting to use nodeJS for backend development?
(Unfortunately I have no suggestions or experience to offer, just a curious inquiry)
On Thu, Apr 21, 2016 at 07:22:42AM -0400, Miguel M. wrote:
On Apr 21, 2016 5:18 AM, "Pierre-Yves Chibon" pingou@pingoured.fr wrote:
However, as I see us starting to look at JS for some of our apps
(fedora-hubs,
wartaa...), I wonder if we could start the discussion early about the
different
framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to
look at
the recommended one instead of picking one up semi-randomly.
Just to clarify, some apps are starting to use nodeJS for backend development?
I do not think we're there yet, but I hear more and more interest in frontend framework such as angularjs or reactjs.
So I guess I should have specified front-end JS framework.
Pierre
Hi,
On Thu, Apr 21, 2016 at 2:46 PM, Pierre-Yves Chibon pingou@pingoured.fr wrote:
Good Morning Everyone,
Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework:
- flask for most
- pyramid for some of the biggest (bodhi, FAS3)
- Django (askbot, Hyperkitty)
- TurboGears2 (fedora-packages)
- aiohttp (python3, async app: mdapi)
While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all.
Although there are a number of pros for the above approach, I'd like to highlight a few downsides too: - UI and backend development are tightly coupled - HTML responses from backend are not that reusable - Not ready for multi platforms
However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly.
So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why?
After doing quite a lot of reading on ReactJS vs Angular2, and based on instinct, I prefer React because: - lean and thin, less react specific jargon, mostly javascript - initially it might have a bit of more learning curve, but once you get the hang of it, it becomes easier. Unlike Angular2, which is easy to start, but the learning curve, gets steeper and steeper as you progress - React shows errors at compile time itself, rather than on runtime like Angular2 - React is lightweight and has a simple API. You don't need to read react's source code to understand what's happening
On the other hand: - Angular2 is a richer framework, easy for new developers to get started with - I love how nativescript allows you to write native apps for mobile platforms using Angular2, allowing 80% code reuse
You can find some useful reads at [1], [2].
[1]: https://www.airpair.com/angularjs/posts/angular-vs-react-the-tie-breaker [2]: https://medium.freecodecamp.com/angular-2-versus-react-there-will-be-blood-6...
Thanks, rtnpro
On Thu, Apr 21, 2016 at 08:17:50PM +0530, Ratnadeep Debnath wrote:
Hi,
On Thu, Apr 21, 2016 at 2:46 PM, Pierre-Yves Chibon pingou@pingoured.fr wrote:
Good Morning Everyone,
Our infrastructure is mostly a python store, meaning almost all our apps are written in python and most using wsgi. However in python we are using a number of framework:
- flask for most
- pyramid for some of the biggest (bodhi, FAS3)
- Django (askbot, Hyperkitty)
- TurboGears2 (fedora-packages)
- aiohttp (python3, async app: mdapi)
While this makes sometime things difficult, these are fairly standard framework and most of our developers are able to help on all.
Although there are a number of pros for the above approach, I'd like to highlight a few downsides too:
- UI and backend development are tightly coupled
- HTML responses from backend are not that reusable
- Not ready for multi platforms
However, as I see us starting to look at JS for some of our apps (fedora-hubs, wartaa...), I wonder if we could start the discussion early about the different framework and eventually see if we can unify around one. This would also allow those of us not familiar with any JS framework to look at the recommended one instead of picking one up semi-randomly.
So has anyone experience with one or more JS framework? Do you have one that would you recommend? Why?
After doing quite a lot of reading on ReactJS vs Angular2, and based on instinct, I prefer React because:
- lean and thin, less react specific jargon, mostly javascript
- initially it might have a bit of more learning curve, but once you
get the hang of it, it becomes easier. Unlike Angular2, which is easy to start, but the learning curve, gets steeper and steeper as you progress
- React shows errors at compile time itself, rather than on runtime
like Angular2
- React is lightweight and has a simple API. You don't need to read
react's source code to understand what's happening
On the other hand:
- Angular2 is a richer framework, easy for new developers to get started with
- I love how nativescript allows you to write native apps for mobile
platforms using Angular2, allowing 80% code reuse
You can find some useful reads at [1], [2].
We should also give some thought to the framework(s) that:
(1) have robust upstream communities themselves, with active development where appropriate, and
(2) have massive uptake in the overall developer realm beyond just our current contributors;
...and balance that against perceived technical excellence, purity, etc. This way we can grow or maintain our ability to on-ramp new contributors to projects we work on.
Hi, I have experience with a decent amount of these frameworks and wanted to throw my opinion into here.
I have written a blog post [0] comparing a few of the most popular JS frameworks and ones that I have used in the past. Hopefully this can lead to some more discussion about what is best for our infrastructure. In the React vs Angular2 debate I tend to agree with rtnpro for reasons that I go into in the post.
Best, Eric
Really nice rundown, Eric, thanks for that.
I've worked closely with some really great frontend dev teams in the last couple of years and I vote for React. The reason for this is that it seems for be preferred for efficient one way databinding which is a lot of the context for infrastructure applications (monitoring, viewing information, etc.) though it can still do the interactivity we'd need. Angular2 is causing my current team quite a lot of grief, though they are solid pros, and like Angular in general. I think it's probably overblown for what we want in this context.
We really should standardize an appy kind of stack. There's another thread talking about setting up dev boxes for infrastructure with docker or vagrant, and the ideal onramp I think would be to just pull down a scaffold (or generate one) into such a box for the premium infrastructure development experience. :)
Thanks for your reply.
The reason for this is that it seems for be preferred for efficient one way databinding which is a lot of the context for infrastructure applications
This I think is the biggest reason that I like React for us. There currently are not a lot of use cases for two-way binding or keeping track of state in our applications. With React we can apply it to our needs now and add that level of interactivity later on without having the initial overhead Angular brings.
Choosing React can also mean no PhantomJS hacks to keep SEO which I have found to be a pain with Angular in the past.
On Fri, Jun 10, 2016 at 3:25 AM, Eric Barbour ebarbour@redhat.com wrote:
Choosing React can also mean no PhantomJS hacks to keep SEO which I have found to be a pain with Angular in the past.
+1
It seems that Angular 5, which release was announced in November, 2017, is going to have a pretty impressive advantage if compare to Angular 4. Okay, but everyone knows that React.js is one of the main competitor libraries of Angular. So in this article https://artjoker.net/blog/angular-5-vs-reactjs-what-to-choose-in-2018/, you can see the question of what Angular and React are differing with and decide which one is better to choose for client's project.
Hi,
Let me start by introducing myself, I am a full stack developer with near to a decade experience in web development. For past 5 years or so I have been dealing with JavaScript and related libraries and frameworks. Based on my experience I would recommend ReactJS as well for frontend development. If there is a requirement to have a single codebase for frontend and backend where frontend is to use ReactJS and backend is to be implemented using NodeJS, I would recommend taking a look at NextJs (https://nextjs.org/) as well.
PS: I am more than eager to contribute to Fedora web.
Hm, is this some favorite SPAM thread?
Vít
Dne 11. 05. 22 v 13:19 Alex Maddyson napsal(a):
Hi, I can recommend you to read this great article about engineers, I think that it will be interesting for those who are in this industry. https://engre.co/blogs/articles/what-is-a-propulsion-engineer/ _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Wed, May 11, 2022 at 02:08:55PM +0200, Vít Ondruch wrote:
Hm, is this some favorite SPAM thread?
Yeah, it must have some search engine mojo for JS Frameworks.
I hope any future spammers realize that we will unsubscribe them, block them from resubscribing and remove their posts from the archives, so really they aren't going to gain anything from it at all. ;(
kevin
infrastructure@lists.fedoraproject.org