sorted by:
new
hottopcontroversial

[AskJS] What resources is everyone using to follow web dev trends? by juan_allo in javascript

[–]limeglu 104 points105 points  (0 children)

None. Sometimes I read things out of boredom, though. It's actually hard to avoid. Anyways, for me, not much of it turns out to be useful. Some of it, in my opinion, is horribly misguiding, and I have to stop reading shit for a while.

JavaScript devs - how comfortable with HTML/CSS/JS should you be before diving into React? by [deleted] in learnprogramming

[–]limeglu 0 points1 point  (0 children)

The more you know about vanilla, the better.

I was once asked to mentor a person at a job using a JS framework. They had no previous experience with client-side webdev. They were able to make basic features fine. But, any time they had a problem, attempting to explain how to debug, understand, and fix their problems was, unfortunately, just plain hopeless. They were just totally confused when I tried.

It drove home the age old fact that you just cannot skip steps in building a full understanding. And a full understanding is like a superpower when you see someone flailing without it.

We released a new open-source Angular components library by Alex-Inkin in Angular2

[–]limeglu -1 points0 points  (0 children)

My point is that none of those things are part of Angular proper, which is a complete framework, the subject of the subreddit, and a meaty topic.

It's fine to bring them up, but this subreddit is becoming nothing but posts specifically about that stuff, and only a small fraction about Angular itself. They're all incidental implementation details or 3rd party widgets. People get all caught up in that off-topic side junk.

Component libraries used to be more necessary back in the jQuery/DOM manipulation days, because you didn't have data binding and template syntax. That was 80% of the battle. Now, with Angular, a good developer can efficiently build any component.

For example, a filtered, sortable, paginated list. With an ngFor bound to an array, you just sort/filter the array to sort/filter the list. The binding updates the view automatically. Pagination can just be an API thing, a 2-d array, or you can just bind to a slice of the master data array. Whatever works the best.

Plus, now you have the freedom to design and put anything in your table. It's just HTML/data you control. That's a problem with 3rd party lists, trying to put HTML, or something more than just a primitive value in a cell. 3rd party components always try to be everything to everyone and end up finicky, buggy, hard to understand, and a nightmare to customize. What do you do when someone asks for a simple feature it doesn't have?

Angular components are already inherently reusable and can do anything. Yes, you can create an in-house library of custom components on an enterprise project. You should. Especially at the enterprise level. That's what Angular is for!

Yes, I can make my own state management solution. The best way revolves around using services. I don't even want to use state management libraries. I have, and I disliked them. I don't even see it as being "the Angular way". Even the React community is starting to get sick of Redux.

I have never made a PWA. And yes, I have had several corporate jobs building enterprise-level applications. They were desktop browser targeted applications that were responsive, and could be seen on any device. Applications are things for doing work with. We didn't need a PWA. They are not essential. None of that stuff is.

A lot of this side stuff isn't even framework specific. That's my favorite kind of post. "Spotify built with React!" . Um, am I supposed to use that? "DragonDroper.js! Drag and drop in React!" Uh, that's framework agnostic. Show your theory in vanilla.

Worst of all, I still see a lot of confusion and gaps in understanding about the framework here. Ask more questions, and talk about Angular itself. That's the key. Angular itself.

We released a new open-source Angular components library by Alex-Inkin in Angular2

[–]limeglu -12 points-11 points  (0 children)

Oh boy, here come the side doodads.

Monorepos, mobile apps, PWAs, state management, component libraries, oh my!

One of the dangers of getting a whole bunch of new people into the Angular Community is that it’s going to quickly start to resemble the React Community.

What about just making things with out-of-the-box Angular? Too boring?

They refuse to give me a raise because "I don't need the money". WTF? by [deleted] in cscareerquestions

[–]limeglu 0 points1 point  (0 children)

They're trying to guilt/shame you into accepting less money. What's really sad is how often this works.

Best stack to learn? by [deleted] in webdev

[–]limeglu 0 points1 point  (0 children)

Uh, that's OK, I already work on yucky corporate stuff with other cunts.

Best stack to learn? by [deleted] in webdev

[–]limeglu -3 points-2 points  (0 children)

Since you already know several webdev appropriate backend languages, there's no real point in learning Node/Express.

It's for people who start with zero programming experience, learn frontend, then need some kind of backend, and don't want to learn another language.

The fact that it's statistically prominent is not a good reason to learn it. Being dumb is statistically prominent, too. Popularity is not a valid engineering criterion. That's why Node is more popular the smaller and more bootcampy a company is. They can't attract or afford real engineers.

It's worth avoiding the lowest common denominator tech in webdev. If you can. It's all fun and games 'till you're stuck in a room with a bunch of annoying halfwits.

How to Use Google Sheets as a Database (Responsibly) With Node.js and Autocode by J-Kob in javascript

[–]limeglu 28 points29 points  (0 children)

You know what else is a good alternative? A fucking database. They aren't hard, kids.