AvgCakeSlice

joined 1 year ago
[–] AvgCakeSlice 2 points 1 year ago

It’s mostly preference. Vue and Svelte are easier to work with, IMO. React is perfectly fine and there is a larger community around it as it is more widely adopted by large companies, but there’s also a lot of crap so it can be hard as a novice to discern what is good and what isn’t.

[–] AvgCakeSlice 6 points 1 year ago* (last edited 1 year ago)

For your first printer I would recommend getting something you can build from scratch if you have the time. You’ll learn about all the different parts of a printer so you have an idea of what to do when something goes wrong. Prusas are great in that aspect as they have wonderful documentation and assembly instructions and it’s easy to buy replacement parts if you need it, plus they’re pretty low-maintenance once built. In your price range I think the MK4 kit would be a good option, just keep in mind that assembly can take upwards of 10 hours depending on how fast you go.

However, if you want to buy something and just forget about it, one of Bambu Lab printers would probably be a better option. Their parts are more proprietary and you won’t get the same learning experience, but its dead simple to setup and use. (Not to mention incredibly fast).

Either way, you’ll be getting a solid printer that should last you for a while, so have fun and be sure to post here if you have any more questions!

[–] AvgCakeSlice 1 points 1 year ago (2 children)

Well, both, but if you’re just talking about the frontend, then yeah I’d use a frontend framework like React (though personally I’d rather use Vue or Svelte if I had the choice)

[–] AvgCakeSlice 4 points 1 year ago (1 children)

As a dad that loves the show, I’m in!

[–] AvgCakeSlice 7 points 1 year ago

Same for me. The day Apollo died was the day I quit. I’m starting to warm up to Lemmy more and more over time as it scratches that same itch.

[–] AvgCakeSlice 1 points 1 year ago (1 children)

That’s a great looking board! How do the default keycaps feel? Your picture makes them look nicer than I originally thought.

[–] AvgCakeSlice 4 points 1 year ago

A Christian Carol. I know Christian movies are low-hanging fruit, but the awful CGI, terrible writing, horrible camerawork, and nonsensical story really just make it truly awful.

[–] AvgCakeSlice 2 points 1 year ago (3 children)

Does AppleTV have a Jellyfin app yet? We’ve got a few around the house and I’d love to switch to Jellyfin from Plex.

[–] AvgCakeSlice 1 points 1 year ago* (last edited 1 year ago)

Started with an Ender 3 V2, which I tried modding with BLtouch because I hated the lack of auto bed leveling. Eventually I just got so frustrated that I got a Prusa i3 MK3S+ and I love it to death. It was just a quantum leap over the Ender and well worth the price bump. I’ve lately been selling prints for profit and have been eyeing the Bambulab X1 Carbon for its speed and the AMS.

[–] AvgCakeSlice 1 points 1 year ago (4 children)

No, not necessarily. React usually calls the backend through HTTP requests in order to fetch data. The backend code is written as an API, not a full-blown web application, that handles those requests, validates the request, permissions, business logic, etc, and then returns a response. The backend code is the gatekeeper between the client and any databases or external API’s in your application.

Traditionally you would use REST API’s, although there are more modern ways of communicating with a backend like with graphQL. But if you’re just starting I would learn how to write a REST API using PHP, Python, Ruby, C#, etc and go from there. REST API’s are pretty straightforward. Essentially your server just exposes a bunch of “endpoints” which are URL’s that represent a resource (for example https://mycoolwebsite.io/api/users) and making certain calls to those endpoints prompts the server to perform some action (for example, an HTTP GET request to api/users/123 gives you the information of the user with the ID ‘123’) the server typically serializes the response data to JSON, so that the client can then receive the response from the server and do something with it. When writing your backend, you are responsible for defining these endpoints in your code and writing the logic that executes whenever a given endpoint is called. For example, when creating a new user (with an HTTP POST request to api/users), you may want to send an email to the newly-created user for them to validate their email address. You would do this by calling some external email service like SendGrid, Mailchimp, etc. and sending a validation email to the address that the user sent in the request body. After that you would create a new user record in the database and initialize the “is_account_verified” field of that user to false. In another endpoint (api/users/{id}/verify-email) you would then check if the verification email has expired or not, then change the verified flag in the DB if it is a valid link.

view more: next ›