|
A lot of the so-called SPA frameworks don't require you to build out a SPA. Angular for example does not necessarily need to be built out as a SPA. I've made applications in it that were different pages and it works great in that role as well.
|
#
¿
Dec 20, 2013 20:16
|
|
|
|
| # ¿ May 4, 2024 09:30 |
|
|
I know a guy. My co-dev on the project I'm on right now loves setting all that stuff up. Which is great for me cause I am quickly bored by it all. For putting bower files somewhere not default you need a .bowerrc file in the root directory. http://bower.io/docs/config/ Summit fucked around with this message at 12:48 on Apr 27, 2015 |
|
#
¿
Apr 27, 2015 12:44
|
|
|
I'm told using webpack with bower is not the ideal solution. Right now we just include all the client side stuff with npm and point webpack at it. Working good so far.
|
|
#
¿
Apr 28, 2015 03:48
|
|
|
Your ng-repeat should be "comment in dishDetailCtrl.dish.comments"
|
|
#
¿
Feb 14, 2016 20:38
|
|
|
Note that I changed your iterator to "comment" (singular). So it's not doubly specified. 
Summit fucked around with this message at 02:22 on Feb 15, 2016 |
|
#
¿
Feb 15, 2016 00:50
|
|
|
Pretty much agree with all of this. Angular 1.5 is much more mature and straightforward and will avoid so many headaches. $scope (especially inherited scope wtf) is the way of madness and overly coupled code.
|
|
#
¿
Feb 20, 2016 01:53
|
|
|
Angular performance is a concern for complex web apps (like a chat room) but for the vast majority of simple web sites it is more than up to the task. In an enterprise where the business people just want a spruced up CRUD site I think it's a great fit.
|
|
#
¿
Jun 25, 2016 16:47
|
|
|
Forgive my React ignorance, just started working in it in my spare time (stories are sparse at work end of year). Does MobX solve these boilerplate problems? Granted a lot of the details are hidden/magic but it's been working great for me thus far without any need for reducers, actions, etc.
|
|
#
¿
Dec 17, 2016 21:55
|
|
|
Nobody should really be saying "Angular 4" much like nobody says "React 15" (current version, since they also do semver). I'll admit Angular team has handled this situation very poorly but the piling on about version numbers is pretty silly.
|
|
#
¿
Apr 1, 2017 20:03
|
|
|
I think most are in agreement that starting something brand new with AngularJS would be a poor decision, because the mindshare has mostly moved on from it and there's a wealth of strong alternatives. But if you're already sitting on an AngularJS code base there's no need to panic about a migration path or switching over soon as it's still a very solid solution to the problem of organizing a dynamic front end and will be supported for quite a while into the future.
|
|
#
¿
Apr 1, 2017 22:43
|
|
|
TheCog posted:As someone who's mostly worked with AngularJS (or angular 1, whatever they're calling it now), what's a natural, less painful framework for me to pick up? I'm kind of curious about Ember, cause I've heard good things, but I'd rather not sink a lot of time in if no one is using it anymore or if there's something much better. Vue
|
|
#
¿
Apr 17, 2017 02:22
|
|
|
I know a lot of C# lifers who swear by Visual Studio. After using it for years and then moving over to JetBrains products I have 0 desire to return.
|
|
#
¿
Apr 26, 2017 01:45
|
|
|
Helicity posted:Keep in mind that a lot of backend devs frown on Node and monoglots (people that prefer to work in a single language for everything). Node without TS is painful, callback-based programming distracts from writing the important parts (business logic), and the "omg event loop is async/fast" crowd is ignoring that there are easier ways to get full asynchronicity and there are dozens of server stacks faster than any variation of node and hundreds of server stacks that are faster than what most people need. It's fair to not like Node, but I hope you can see how you are projecting your own preferences onto the community at large.
|
|
#
¿
Jun 20, 2017 20:50
|
|
|
In my dev circles a lot of my fellow consultants have been getting gigs doing Angular (aka ng2), which surprises me. Wasn't sure if it would catch on with all the drama surrounding AngularJS (aka ng1) but it seems to be gaining a foothold. I assume this is coming from shops who were doing AngularJS before and see Angular as a logical next step for their next projects.
|
|
#
¿
Jun 21, 2017 21:54
|
|
|
Yeah I'm not sold myself. Vue seems like a better version of the same thing. That said, a lot of smaller companies find Google's backing very appealing so I bet that is quite a draw.
|
|
#
¿
Jun 21, 2017 22:14
|
|
|
Yeah once you put the brackets there you need to return something. Implicit return only works sans brackets.
|
|
#
¿
Apr 24, 2019 02:14
|
|
|
dupersaurus posted:The React answer (I think) is that you should be componentizing the styling, so instead of having styled <p>s everywhere, you've got a <StyledParagraph> that reduces down to a <p> with that global style Yup. Site wide css is still good too. Just depends on your needs.
|
|
#
¿
Apr 20, 2020 15:10
|
|
|
Bootstrap 4 has a very nice set of utility classes and there’s no reason not to snipe them into your own css file if you don’t want the components/typography/etc.
|
|
#
¿
Apr 25, 2020 20:41
|
|
|
Re: bootstrap talk One thing I didn’t see mentioned in all that is you can customize bootstrap too. I can see why you might view it as a prototyping tool if you never change any defaults, but if you recompile the SASS you can change colors, spacing, etc etc and end up with something that looks completely unique.
|
|
#
¿
Aug 13, 2020 13:22
|
|
|
I learned everything I know trying to turn my dumb ideas into reality.
|
|
#
¿
Dec 28, 2020 14:34
|
|
|
I disagree wholeheartedly that Bootstrap is hard to work with. Granted I think it’s paramount that you setup your stylesheet build such that you can customize its variables to your needs but that’s been easy to do since version 4.
|
|
#
¿
May 18, 2021 01:36
|
|
|
That comparison was posted in my circles today and what I found immediately off about it was it explicitly ignored NextJS’s server side rendered features then claimed victory. Just felt a bit cherry picked and I left me curious what the comparison would be if they used SSR for both.
|
|
#
¿
Jan 20, 2022 04:45
|
|
|
I was recently shown https://github.com/pmndrs/jotai I haven’t used it enough to form an opinion beyond the docs make it look like the perfect solution to shared states for simpler apps where full blown redux feels like overkill.
|
|
#
¿
Mar 6, 2022 15:21
|
|
|
I’ve never understood the desire to get fanboi about frameworks. They all suck. They are all great. If you use one it makes perfect sense. If you use the other it would make sense too. In some number of years we’ll all have moved on to something else. It’s the way of things.
|
|
#
¿
Jun 8, 2022 18:44
|
|
|
camoseven posted:Found the guy who's still using Backbone and jQuery Not sure how you made that leap. Right now I use React at work. NextJS for personal projects. My point was it’s better to keep an open mind and be able to see the value in any framework. They all have value. They will all also be replaced at some point.
|
|
#
¿
Jun 9, 2022 00:27
|
|
|
Speaking of React ecosystem there’s a state management lib called jotai I’ve been checking out and it’s really drat awesome in its simplicity. It’s basically shared useState, works with all hooks the same way useState does. It isn’t ideal for everything but seems to be perfect for the basic business CRUD apps my job calls for.
|
|
#
¿
Jul 31, 2022 02:25
|
|
|
If you aren’t creating a complex app do yourself a massive favor and look into jotai and zustrand. Absolutely perfect state management for simple apps.
|
|
#
¿
Oct 20, 2022 15:30
|
|
|
Learn React as best you can, put it on your resume as a technical skill, when asked say you’ve done some side projects and would love to get a role working with React professionally. Be honest that you’re green with that specific tech but experienced in frontend generally, and willing to learn something new. So many bad devs learn one lib and then refuse to acknowledge anything else exists, this will be a good explanation to certain other devs who understand that the fundamentals and the ability to learn are more important than rote knowledge.
|
|
#
¿
Oct 30, 2022 22:43
|
|
|
Next kicks rear end. Just ignore the new stuff, your project wont explode if you don’t use beta features right away.
|
|
#
¿
Jan 2, 2023 00:56
|
|
|
|
| # ¿ May 4, 2024 09:30 |
|
|
If something solves your problem and is a widely accepted solution, who cares if you’re not using all of it?
|
|
#
¿
Jan 4, 2023 19:03
|
|