That’s because it makes sense when dynamically creating HTML. HTML is not a programming language, it’s simply markup - so if you want to generate some block of HTML in a loop and later access that block of HTML in JS (e.g. to interact with the UI separate from creating it in the first place), it’s a completely reasonable thing to do.

Just wanted to give props to this super informative comment. Thanks for the write up and relevant links!

TS is “better” but often I feel like just configuring typescript takes up a significant amount of the time you save by using it.

deleted by creator

Those look like small cards. But why not just inspect the page and grab the CSS if you’re so focused in re-creating them? Why try to find and shoehorn a component from a UI library to look exactly like that when your browser will tell you exactly how it looks the way it does?

Out of all the modern browsers, it’s always Safari that I end up needing to write compatibility code for. I’m sure the app works fine on Firefox, they just haven’t tested it.

What exactly are you trying to do with the height?

What bike do you use and would you recommend it? I’ve been looking for an e-bike recently since I work so close to home, but I haven’t found any that seem reputable and a good value. I’m definitely looking for one that’s easily repairable and not paired to a specific brand’s software or proprietary parts.

Granted, I’ve only been passively looking (I.e. when I see an ad or doing a quick google search sometimes), but from what I can tell most of the advertised bikes are just the same handful of models with a different logo slapped on it and dubious claims about its performance.

The Odin Project is an excellent resource. I’d recommend working your way through both the “paths” they have - take both the Ruby and JavaScript paths. To land a job you’ll want a thorough understanding of the back end and while Ruby doesn’t have as high of a demand anymore, I do think it’s important to build skills in more than one language to be a compelling candidate. If you don’t want to take the Ruby course, I’d recommend learning how to build a back end in C#/Java to make yourself more well rounded.

They also recently released a React course - I haven’t checked that out yet, but it’s a highly marketable skill and the rest of their curriculum is great so I’d imagine that is too.

In any case, they do a great job in teaching you how to “think like a developer” instead of just how to follow a tutorial- which should give you a good foundation for building your own portfolio. TOP played a huge role in landing my first job - but you do need to hold yourself accountable to studying every day if you want to succeed through self-studying.

I only use packages that are from a reputable source and/or have a huge amount of downloads. It’s not a perfect system, but I’ve never had a problem so far.

If the downloads are low and I’ve never heard of the author, either a) I don’t need it and can build a solution myself or b) it’s a niche package that’s small enough that I can audit it by skimming the GitHub repo.

The normal common sense rules still apply - check for typos and any attempts to look like they’re a package or author that they’re not

It depends what you’re using them for, but it’s pretty common to use the original icons of other services/companies if you’re using them on your website rather than a stylized version.

In my experience, anyways, that’s more common than using a stylized version of a 3rd party logo - and that’s not to mention potential legal issues with using an altered version of a 3rd party’s icon.

Out of curiosity, why?

https://join-lemmy.org/docs/contributors/02-local-development.html#frontend-development

That should get you running locally. If you’re familiar with React, you should feel right at home. In either case, the Inferno docs should help you out a lot.

You’re correct that it’s transpiled into minified JS, but the source is in human-friendly TypeScript. The transpilation is handled automatically for you by Yarn.

I’m super excited to see what the final release looks like for Blazor web apps. Clearly there’s a lot of hard work going into unifying server/WASM rendering and I’m ready to get my hands on it.

Any production project, especially with that sort of rigor, should be sticking to the LTS releases. IMO there is no project that should be on 7 with no plans to upgrade to 8 after it’s released.

If a version upgrade is out of scope, then it should’ve been built on 6 to begin with.