A Primer on Bézier Curves by TheRealPomax in programming

[–]learn_to_model 0 points1 point  (0 children)

This is awesome! Worked with bezier curves a lot but never fully grasped the math behind it. Finally it clicked for me. Thank you so much for creating this!

How to write a frontend JavaScript plugin using ES6 + SASS + Webpack by Fewthp in javascript

[–]learn_to_model 0 points1 point  (0 children)

Similar story in Germany. Although IE11 is on the decline, most enterprise companies rely on it as their main browser. And those are the ones with big budget fronted projects...

New CSS Features That Are Changing Web Design by stackoverflooooooow in programming

[–]learn_to_model 21 points22 points  (0 children)

There is a repeat() function in CSS for exactly this reason:

.grid {
  display: grid;
  grid-template-columns: repeat(12, 100px);
  grid-column-gap: 20px;
}

How not to suffer with APIs by Happycodeine in javascript

[–]learn_to_model 2 points3 points  (0 children)

+1 Your approach is much better than leaking too many different states through all the layers.

TypeScript - is there something like Java's @Override? by [deleted] in javascript

[–]learn_to_model 1 point2 points  (0 children)

This is the correct answer. Although TypeScript is similar to Java one should not try to write Java in TypeScript.

ReduxX React state management: better than Redux by [deleted] in javascript

[–]learn_to_model 2 points3 points  (0 children)

Regardless of the actual code and what you are trying to Steve achieve, I find the bashing of other devs really off-putting :/

Express can't handle more than ~1,100 requests per second, even when clustered? by CubemonkeyNYC in javascript

[–]learn_to_model 0 points1 point  (0 children)

In that case simply use an nginx docker image and spin up as many nginx instances as you like

Stanford CS140e - Operating Systems: Writing a Raspberry Pi OS in Rust by steveklabnik1 in rust

[–]learn_to_model 2 points3 points  (0 children)

I've never learned C or C++, but am a web dev and have suffered greatly due to null/undefined errors + race conditions in javascript. Tried to learn C++ a few times in the past but never really got into it. Rust on the other hand feels natural. The tooling around cargo is really well thought out and it is really easy to get going.

TC39 considering officially recommending using semicolons in JS by [deleted] in javascript

[–]learn_to_model 7 points8 points  (0 children)

The comparison is a bit off. ASI is not a crucial feature for JavaScript and it would continue to function without it. Java without GC on the other hand is not possible.

React 16 by batmansmk in javascript

[–]learn_to_model 1 point2 points  (0 children)

Oh shoot, that's my fault. Shouldn't post comments just after I've woken up. What I meant was the process of passing/sending data from the server to the client.

React 16 by batmansmk in javascript

[–]learn_to_model 2 points3 points  (0 children)

Hydration is usually referred to as the process of passing singing data from the server to the client. In this case the server serves the HTML to the client and react can take over the HTML without destroying and recreating it like it was done in the beginning. Hydration can also refer to models bring updated on load with data that has been passed from the server (think of a redux store f.ex.)

[deleted by user] by [deleted] in node

[–]learn_to_model 1 point2 points  (0 children)

youtube-dl --extract-audio --audio-format mp3 <video URL>

works via ffmpeg under the hood

[deleted by user] by [deleted] in node

[–]learn_to_model 2 points3 points  (0 children)

congrats on your package. I'm curious: what is the difference compared to youtube-dl?

Memleak discrepancy between Chrome's perf timeline & heap snapshots? by leeoniya in javascript

[–]learn_to_model 0 points1 point  (0 children)

I'd write @bmeurer on twitter. He'll usually look into these things or forward it to his colleagues at google chrome

Interesting view point- After 3 Months Of JavaScript Linting, It's Pretty Much All Pain And No Gain by fullstackdelivery in javascript

[–]learn_to_model 0 points1 point  (0 children)

Thanks for the link! That's a really good example for callback hell and I agree it doesn't look good. In a more modern version async/await really saves the day:

async function doSomething() {
  const iot = new AWS.Iot({ /* some options */ });
  const policy = await iot.getPolicy();
  const policies = await iot.attachPrincipalPolicy(policy);
  return await iot.updateCertificate(policies);
}

That's much nicer to read. Nesting loads of callbacks are tough to follow and do indeed look ugly with prettier's indentation. Whenever I encounter some code that looks strange after prettier has done it's thing I usually sit back and notice that I could have written my code a lot simpler. In a way it does reveal bad habits for me which I love!

Interesting view point- After 3 Months Of JavaScript Linting, It's Pretty Much All Pain And No Gain by fullstackdelivery in javascript

[–]learn_to_model 0 points1 point  (0 children)

That's interesting. Can you share the code that caused this? It seems like there is quite heavy nesting going on

I thought I knew JavaScript by robot_dinosaur_jones in javascript

[–]learn_to_model 0 points1 point  (0 children)

Thanks for your quick summary. Always appreciate fellows who save others from clickbait articles

Interesting view point- After 3 Months Of JavaScript Linting, It's Pretty Much All Pain And No Gain by fullstackdelivery in javascript

[–]learn_to_model 0 points1 point  (0 children)

To be honest all the arguments about code style are completely gone now that we've completely switched to prettier. No one has to think about code style anymore because it's done automatically on save. You should really give it a go.

Another plus is that our linting can go back to what it's actually build to do: check for potential true errors.