-
Hey Guest. Check out your NeoGAF Wrapped 2025 results here!
Any angular peeps on GAF?
- Thread starter cormack12
- Start date
Rentahamster
Rodent Whores
I'm more of the curvy type.
Captain Zyrain
Member
girl, please
BlackOlivesMatter
Banned
Bitch I ain't no rhombus
I used to be quadrilateral, now I warp like a smile.
I used to be quadrilateral, now I warp like a smile.
pr0cs
Member
Taking an Angular course right now, just finished the chapter related to template and reactive forms.
What's your question?
Fushitsusha
Banned
Very astute.
Fushitsusha
Banned
In all seriousness, I will help you OP.
Last edited:
MiyazakiHatesKojima
Banned
Papa
doing his absolute best to try and act like this isn't his alt
brap
,
CyberPanda
, come check this shit out 
diffusionx
Gold Member
Yea I preordered a Cybertruck
MiyazakiHatesKojima
Banned
godhandiscen
There are millions of whiny 5-year olds on Earth, and I AM THEIR KING.
React is more in vogue, which seems to be the only thing that matters when it comes to front end frameworks. Why Angular?
cormack12
Gold Member
At the moment I just want to create a form by looping over a json array rather than adding each formcontrol manually.
So let's say I have a json file with six top level arrays. All I want to do is loop over that json as a service and add a form control for each item. So for future I can just update the json and the form will just dynamically update.
I just really like it. I can try react as I havent looked at it but for single page applications it looks really sleek.
I'm basically building a web app using php, mysql and jquery to get a proof of concept up quickly but I'd prefer to medium term or in parallel move to a framework.
H
hariseldon
Unconfirmed Member
Angular chap here - just bookmarking this so i can respond properly when I'm at a computer instead of a phone.
godhandiscen
There are millions of whiny 5-year olds on Earth, and I AM THEIR KING.
If you like it, that's all that matters. However, to juniors I wouldn't recommend it. Not even Google is fully behind Angular, they just released Flutter not so long ago. I recommend React because it has the largest momentum and a path for code portability to native apps.
H
hariseldon
Unconfirmed Member
Personally I'm happy with Angular - I'd say it's misleading to say Google isn't behind it, they're constantly updating and improving it. Both are bloody good frameworks, but for my needs I've chosen Angular to sit in front of a spring microservices back-end (also built by me) and I'm happy with the results.
Rather than typing up a big tutorial myself I see no point in reinventing the wheel so here's one I found online. looks pretty decent, albeit I hate the way medium formats code.
Elektro Demon
Banned
I reading OP's post and the responses and I still don't get what this thread's about.
Lanrutcon
Member
That's because it's Angular, not angular.
Stiflers Mom
Banned
We had some Angular stuff at work.
It felt needlessly obtuse and bloated to me.
It felt needlessly obtuse and bloated to me.
pr0cs
Member
I still think you need an intermediate class that handles the translation from json object to typescript object. If your array was always of a fixed size (6 as you say) there might be ways to simplify that translation but if the array is dynamic and the objects not native Java objects then you still need something to translate the json into something you can use in typescript.
Reactive forms can be dynamic but they still rely on you defining them in typescript.
That being said, I suspect with some creativity it should be relatively straightforward to write a service that would do the translation and add a Subject to listen to inside your form to be notified when there are new translated objects to respond to.
I like angular too, I've been a pure Java dev for the last 26 years so my opinion likely doesn't mean shit but I thus far haven't found it overly complicated.
Web dev in general (from the perspective of a native/Java developer) has always been clunky since so much of the gory details is hidden from you. But compared to some other tech I've screwed with angular is pretty good. Based on the contents of this page it sounds like I need to read up on flutter too. Though to be honest Angular and React are the two most requested skills for careers in my area.
Last edited:
godhandiscen
There are millions of whiny 5-year olds on Earth, and I AM THEIR KING.
Like I said, all that matters is that you like it since it is your own project. I am a systems architect now, so I don't touch any UI much anymore, but I can write good JavaScript any day, and I can tell you that the prominent JS UI frameworks are just unnecessary complications unless you are developing a huge app supported by a large team. Ask yourself this question, do you want to learn something or build something? If you want to build something, you mentioned that you already know JQuery, so just roll with it. Angular won't bring anything special.
Also, it is not misleading to say Google isn't fully behind it. Google has been trying to move away from JavaScript for years now with Dart, and Flutter is their latest champion in promoting Dart adoption. Now, don't take this as "JavaScript is dying soon" or Google doesn't like JavaScript. There is no single technical leadership at Google, but there is clearly a strong group of their staff engineers that wants a different language and framework for the UI; that's all I meant to say.
Last edited:
Katsura
Member
Are you learning it for a specific project? Because those frameworks have a tendency to be very flavour of the month in my experience. There is always a newer and trendier one just around the corner
At any rate, i can't help you with Angular specifics. I try to stick to the basics on the rare occasion where i do any web dev work. I did have to use React at one point and that was a pain
If you're just in it for the learning experience, my advice would be to stick to pure JS and JQuery and then learn a framework once it's required
At any rate, i can't help you with Angular specifics. I try to stick to the basics on the rare occasion where i do any web dev work. I did have to use React at one point and that was a pain
If you're just in it for the learning experience, my advice would be to stick to pure JS and JQuery and then learn a framework once it's required
H
hariseldon
Unconfirmed Member
I run a small team, building software used by massive multinationals. Our software stack is chosen with great care (by me). I architect the system but I'm something of an all-rounder, being solid in design, database architecture, system architecture, UX, etc. Honestly JQuery is fine if you're making an old-fashioned site that's not doing too much but if you want a single-page application (for those not in the know this means something like gmail where you load a single page and all of the components just pop in without having to wait for stuff to load as you navigate around the page) it's much much easier to build it in a framework built for that purpose. React and Angular are both excellent for that job, and thankfully use Typescript instead of javascript, because Typescript is bloody brilliant if you're a fan of strongly-typed languages (I'm a Java guy so that's me) - javascript gets so messy where Typescript saves a lot of hassle.
I chose Angular because it gets the job done well. I've had to borrow a couple of app developers and a uni graduate as I was shortstaffed and they managed to make the jump from Android/iOS to Angular+Spring easily, illustrating its ease of use, and showing the benefits of using something widely supported with a good solid base of users posting on stack overflow etc. That matters. I had to maintain and enhance an old system running on Struts 2 (Java framework) and the lack of material online was horrific. Never again.
Angular isn't some flavour of the month, it's fairly mature and in wide usage. Further, learn Angular and you'll pick up React and others pretty quickly. It's true that front end frameworks come and go pretty quickly but I'd have confidence in Angular and React as solid choices, especially as they use Typescript which is wonderful. Yes it's good to have a solid grounding in JS (I do - I was working with it in the pre-jQuery days when one had to get stuff working in ie6 with no dev tools) but the lads have coped well despite not having that grounding - it does help them that I'm around and can fill in the gaps for what they're missing.
Constant Flux
Member
I feel confused and scared. Someone hold me.
Katsura
Member
All valid points and admittedly i'm biased against over reliance on frameworks and libraries but that's neither here nor there when it comes to this thread. I will leave the Angular advice to you
H
hariseldon
Unconfirmed Member
I agree that over-reliance on frameworks and libs is a thing - a lot of young programmers just know the framework without knowing what lies beneath, and of course libs are a pain because they lead to dependency hell (and Angular can suffer from this - updates can get stuck due to requirements on typescript versions for different libs). I remember in my PHP days in the early days we had no frameworks and it was great, though I did end up building one from which all our sites were built [it meant I could do in a week what others could do in a month]. Later on though Drupal and Wordpress took over everything and it was hell - I found CodeIgniter acceptable as it at least got out of the way while providing some nice DB abstraction to make guarding against SQL injection a bit easier and so on, but the heavy bastards dominated everything. I moved to Java and everything there is built on frameworks, and in this case rightly so. Spring makes development so much quicker and rips out a lot of boilerplate vs DIY - and things like Lombok add an extra layer of usability on top. I could build it all out myself but I'd be reinventing the wheel and I have deadlines to hit to meet the needs of the businesses I serve. Can't be precious when money's at stake.
I have encouraged my team to build from scratch using as few libs as possible, and I'm aware that if support for Angular goes down the shitter I've got a problem. That said, I simply wouldn't be able to get a project the size of what I'm building done with the size and skill level of team I have without them, and I have enough confidence that Angular is used widely enough in the industry that support is unlikely to die in the lifetime of the project, and if it does I expect migration to be feasible.