Js Puns

I want to express my gratitude to the administration of this community for its creation and for its contribution to its growth.

Thanks to this community, I've discovered many companies I didn't know before and now it's even harder to choose a laptop than before... 😅

And yes, as soon as I choose and buy a laptop, I will definitely leave my feedback here.

---

Some proposals

• Creating a chat for this community.

Subreddit is good, but having a chat to discuss the latest news, or FAQ (which is better to buy/not to buy and more) seems to me a more convenient option.

But not Discord. I don't know about the others, and I don't like it. Even the Telegram chat will be a more convenient option, IMO. Also, a good and free (as freedom) alternative is Element.io.

I created two chat rooms that are connected by a bridge. So you can choose anyone:

Telegram: https://t.me/AMDLaptops

Matrix/Element: https://matrix.to/#/!ZYgEQsJsPUnAbkkEVr:matrix.org

( /u/dank4tao, /u/csp4me and u/SolarBear28 - please contact me so I can give you admin permissions)

---

I would like to ask the community to give its opinion on creating chat for this community.

Do you have any suggestions or comments?

Sorry for a non-tech post or question, but I just HAVE to express (JS pun) my thanks to the creators of this absolute gem who hopefully read this.

I inherited a mess today. A set of front-end application forms creating records in a backend, intended to act as a SPA, be mobile friendly and make AJAX calls to update the new records periodically. Simple stuff, basic CRUD deal to collect customer details. The client had the code already there, the project is about to launch and they've just had a bunch of change requests come through.

Like an idiot I say "No worries! Gimme a couple of hours! Close of business at the latest!" without looking at the codebase first. The PM was stressing, so I thought I'd try to pull out a quick win. Look like a hero etc.

What a mess. It's actually doing a bunch of record validations (duplicate prevention, checking the data against business requirements & logic), creating a few different related records & has several hundred fields. All done using a mass of jQuery spaghetti code individually hooking into the id of each and every field, as well as mapping data back into various fields from the AJAX calls. No 2-way binding or anything, just global vars pointing to objects. Yikes! And the changes I'd need to make meant it'd be nearly back to square one - I could salvage the HTML & CSS, but the Javascript was getting tossed.

Now I've been a React guy for a while. And I love it. I loved Angular too - but I just found React much nicer to work with. But I also know that starting a project, cutting the HTML up into JSX components, setting up Redux etc would take too long. And as for Angular - sure I can drop Angular 1 straight in & add my ng directives - but then there's a bunch of other gotchas to deal with. And I haven't coded much Angular in a year or 2, I'll be rusty as hell. There's enough happening I'd be more comfortable with a couple of days at least using either framework.

But just yesterday I finally got around to checking out Vue. Not far - just the intro page examples. Looks nice I thought. Like the best aspects of Angular & React in one.

So I decided to roll the dice and just go for broke with Vue. I mean, if it failed I'm already screwed and it'll be a sleepless night tonight smashing it out using something else. And it looked like I could just drop it in there, add some directives (much like Angular) and it'd just work.

And it payed off! Using nothing but the guide on the site it's all done. The p

I'd be super interested to hear opinions from people who have dabbled in both React and Vue.js. React is so popular and demanded that I can't imagine it being anything less than amazing, but at the same time I feel like everything is so much more complex and cumbersome than in Vue.js. I'm obviously still learning but I can't help but think "Doing that would be so much faster, cleaner and easier in Vue.js". Anyone else feel the same way? I can't help but wonder if maybe I'm biased.

For example, setting and then mutating state:

Vue.js:

data(){
    return {
        items: ["1", "2", "3", "4"],
        users: ["user1", "user2"]
    }
}

React:

const [items, setItems] = useState(["1", "2", "3", "4"]);
const [users, setUsers] = useState(["user1", "user2"]);

I also find it weird how if I wanted to push a new element to the React state, I'd need to copy the old state, push the element in that copy and then setItems to the new array. In Vue.js this is done by simply doing this:

this.items.push(newItem)

Or iterating over an array and rendering elements:

Vue.js:

<div v-for="item in items" >{{ item }}</div> 

React

{items.map(item => {
    return <div>{item}</div>
})}

Edit - Wow, I didn't expect this to reach top of webdev! I read every single comment and I really appreciate all the thoughtful, informative and kind comments! Thank you for the 2 cute rewards too!

Hello everyone,

I just got hired by a Fortune 100 company as a Fullstack dev with React, and I thought it was a good time to share my experience and advice I have for others who might be applying.

My Background/Accomplishments

I have been working as a React dev for the past 4 years with small no name startups. I currently live in San Francisco.

I have written several React tutorials for Freecodecamp.com that have a modest amount of popularity with combined 300,000+ page views.

I have created 3 React Udemy courses with 85,000+ students.

I have many open source projects on github with a modest amount of stars/forks.

I reached top 3% overall ranking on stackoverflow.com in 2019

I hold a technical Master’s in Data Science but no Comp Sci Degree.

Some advice

-Take as many interviews as possible. It is a skill like anything else and can be developed and honed. The better you are at interviewing the better will be your results.

-You will never feel 100% prepared and the interviewers will for sure ask you questions you dont know. Just try your best and be truthful if you dont know.

- Most technical screens involve building something related to the core app of the company. For example for an analytics company I had to build a bar chart in HTML and CSS.

- Know Javascript in dept. I got several questions that went deep into javascript closures and functions.

- Promises. Know promises in great detail. I got a question on how to build promises from scratch in javascript.

What to do if entry level or new industry hire

I unfortunately have bad news if you are in this category. There are way too many people going after these positions with not many companies offering them.

I signed up to entry level job sites like Jumpstart and Handshake and what I saw is not very encouraging.

I saw that there were usually about 4000-5000 applicants for a new grad/entry level dev position.

In comparison for some of the sr/mid-level roles I applied to there were 30-50 applications. Sometimes I was the only applicant.

I read some forum posts that there were entry level people that hadnt found a job after 1 year of looking.

Try to do anything you can to get work experience on your resume. Work for free for a startup or do some freelance work with actual clients.

Side projects don’t really mean anything, you have to build apps that have actual business value in a team of stakeholders.

The process

I mainly applied online thr

I bought Brad Traversy's React Front To Back course on Udemy a couple years ago because it was on sale but never even started it. Now I am about to start a new job that requires working a lot with React, so I was wondering if it's still worth going through this React course from 2017-2018 or if I'm better off finding something more up-to-date.

Obviously, I should go with a more recent course all else equal. However, two things to note are that this React course has 11.5 hours of content and, for those that aren't familiar with him, Brad Traversy is a god-tier educator. This in mind, I would really prefer to stick with the Brad Traversy course, but will direct my attention towards something else if you React experts tell me it's not practical.

Edit: Brad has two React courses, one from I believe 2017 (which is what I originally owned) and one from 2019. I just purchased the new course, which covers React 16.8+. Would love some thoughts on this one as well

I've been using core-js with Babel for years in fairly large-scale projects where the bloat it produces has been somewhat disguised by the fact bundles are pretty big regardless. The pros of everything just working for a target environment outweigh any cons, and I think this is where core-js really shines.

However, I've recently started building some minimal NPM packages and it's been an eye-opener for me. So much so that I'm questioning whether core-js is fundamentally broken or if I'm just not fully understanding its purpose or how to leverage it properly.

Assume I'm targeting IE11 specifically and take the following example:

function trimmer(value) {
    return value.trim();
}

There is nothing fancy here; String.prototype.trim() has been supported since IE10.

Running this through Babel with core-js enabled appends require("core-js/modules/es.string.trim.js"); which then creates a chain reaction of dependency bloat. In fact if you use @rollup/plugin-commonjs to include these files in the bundle you end up with nearly 600 lines of code. Let that sink in. That's a 60000% increase for something that didn't even need polyfilling.

Even if a polyfill was required, why the bloat? There's a one-liner on MDN which probably covers 99.9% of cases.

Perhaps this is a bug, so let's move on to another example:

const test = {
    ...{
        foo: 'bar'
    }
};

Spread in object literals is not supported in IE11. That's fine.

If you forego core-js and simply use preset-env then a small block of helper code is injected to polyfill Object.assign(). The same is true when using TSC and compiling to <= ES5. You can take either of these outputs and run them in IE11 with no issues.

If you enable core-js the compiled output grows to over 1300 lines of code.

I'm clearly missing something as there is no way this is even remotely acceptable.

I'm wondering if anyone out there is/was in a similar position to me or can offer some advice.

The opinion I'm leaning toward at the moment is that core-js is great for large-scale projects where the overhead is mostly negated, and you have the peace of mind knowing that everything will just work. For smaller projects, if you're targeting a legacy environment then be conscious of the code you're writing (e.g. use a traditional for loop rather than for...of if it means avoiding 10

I have an idea for a webapp, and I’d like to learn how to create it. It’s just a pet-project and not serious. Usually I just mess around with CSS and HTML so I’m wayyy behind the times when it comes to modern website design.

My husband is a software engineer and told me that it would be best to use vuejs—but it physically pains him to do front-end stuff so I know he won’t be helping me learn lmao.

What do ya’ll think?

Hi,

I am a frontend developer, I have been working professionally as such for about 3 years, as I am starting to get pretty comfortable with frontend, I want to start developing some skills in backend, and as it is still javascript, I guess node.js is the best choice.

I have created MERN stack app previously for university, but that was a bit less than 3 years ago. Right now, I want to learn more in depth.

Can anyone suggest where to start? I will be starting node.js course on udemy by Maximilian Schwarzmüller, but want to know what people are using from node.js frameworks to what databases, to what tools? Where you host your node.js applications?

I know this is a lot of different thing in one post, but I want this to be discussion about what people use, why, why they don't use alternatives and so on, which would help a lot for me starting with node.js

Thanks!

--

I will update this thread with more questions as those will come up.

Does anyone Develop websites with just HTML / CSS / JS anymore? or is all just frameworks? I'm new to dev and just started learning JS but I feel like everything I see people are using only frameworks. I know you have to learn the basics first but once you're passed that is it frameworks from there on out? Also all the cool websites I see people make were usually made with react or similar.

Hey guys, do you have any recommended resources or courses to blockchain and dApps development using Solidity + Node.js? Where to start? I'd appreciate every help!

It’s the end of AWS Lambda support for Node.js v10. AWS Lambda support for Node.js 10 is due to end in August 2021. It’s time to switch! In this article, we’re discussing and comparing the differences of working with Node.js 10 and Node.js 14 + AWS Lambda, the impacts, and benefits of this change: https://dashbird.io/blog/aws-lambda-nodejs-10-vs-14/

I’m looking for a ORM which is similar to Laravel Eloquent. I must say Laravel Eloquent makes it piece of cake to work with relational data. I tried knex, bookshelf, sequelize but none match to the level of Laravel eloquent.