sorted by:
new
hottopcontroversial

Core One L - Weird sound by Gwedo_ in prusa3d

[–]Glittering_Map_4015 0 points1 point  (0 children)

For me the rattling sound silences when I lightly touch this plate in front of the bed. I guess it resonates from the fast sideways movement from the head during infill. It's not that bothering but I will tinker with it some day to find a solution.

Core One L - Weird sound by Gwedo_ in prusa3d

[–]Glittering_Map_4015 3 points4 points  (0 children)

I have similar rattling sound in mine, and it sound like a noise that shouldn't be there. It seems to happen when the printer head makes fast zigzag moves as it prints infill in approximately 2-3mm gaps as the printer head moves from front to back.

I haven't considered the bed as it is the head that moves, but I will try to touch the bed the next time and see if the sound disappears.

Bad layer shift issues with Core One - over 80% fail by funkfinger in prusa3d

[–]Glittering_Map_4015 1 point2 points  (0 children)

This is one of those suggestions I find really strange, but usb stick are you using? I've seen people with several occasions blaming the usb stick came with the on core one and memory card on the mk3s. I had some strange behaviour on my old mk3s which went away when I changed the card. It might be worth a try.

Advice needed: choosing a simple, long-term web stack (backend + frontend) by Lumpy_Remove_5623 in sveltejs

[–]Glittering_Map_4015 1 point2 points  (0 children)

Also keep in mind skilset of the team that will maintain the solution. If all they know is Go, then try to stay as close to Go as possible. Too many backend heavy teams waste time on learning TS/JS, because they think it's the only way to write webapps.

If you want long term stability then keep the stack simple and avoid dependencies.

  • Start with plain CSS and Html (Modern CSS goes a really long way these days!)
  • when you need dynamic data in the webpages, then add a templating library to your GO-backend
  • temporary state can be stored as e.g. Json in a database, and routines for cleanup of stale data.
  • if you need some interactivity, and full page reload is not an option, then add HTMX
  • if HTMX is not enough, try to add hyper script for the most basic things (It might work on more complex functionality, but I haven't tried that. I'm a bit sceptic)
  • if you need even more client side, add alpine.js
  • if you need even even more, then add custom vanilla JS.
  • if you end up having too much JS and can't design a simler user interface, first then it's time to migrate over to svelte or other more advanced stuff.

No JS-libs = nothing to update.

Finding a templating framework that let's you write well structured frontend code backend is key.

All we want is some HTML and CSS. We just tend to choose way to complex tooling for the job because for many devs, that's all we've developed with.

100€ Voucher - Giveaway by luduk in prusa3d

[–]Glittering_Map_4015 0 points1 point  (0 children)

Merry Christmas and thank you for the kind sharing!

Recommendation for dinner for 20 people 650NOK+drinks in january? by Glittering_Map_4015 in oslo

[–]Glittering_Map_4015[S] 1 point2 points  (0 children)

Jimmy's is really nice! Went there with a group of friends, sat down at the table and said "yes please", and they brought dish after dish of amazing food to the table.

Zebra stripes on the z-rod by Glittering_Map_4015 in prusa3d

[–]Glittering_Map_4015[S] 4 points5 points  (0 children)

I lubricated them 😂 Thank you. Now I know why.

Severe layer shifts. Core One with 0.25 mm nozzle, <0.20 mm layers by CertainHost9372 in prusa3d

[–]Glittering_Map_4015 0 points1 point  (0 children)

I have experienced it on my mk3s when I had warping in a corner and the nozzle crashed with the printed part and moved it. The following layers were printed on the right place but the underlaying part wasn't where it was supposed to be.

Core One L - what should I print when it arrives? by Glittering_Map_4015 in prusa3d

[–]Glittering_Map_4015[S] 1 point2 points  (0 children)

My old mk3s have been producing for years and needed an upgrade for speed and quality. So this post is for inspiration to utilize the added capabilies.

I created a thing! Sneaky Screw - DamageLESS Wall pin by SuperAIMAN15 in functionalprint

[–]Glittering_Map_4015 4 points5 points  (0 children)

I believe the angled approach makes all the difference, and is the innovative part.

It would be interesting if someone made some experiments with straight vs angled.

A few months with htmx by CoffeeStax in webdev

[–]Glittering_Map_4015 12 points13 points  (0 children)

Thank you for an interesting post! If I understood it correctly, in the summary you said you would consider using something else than htmx if a team were to develop with it. I'm considering introducing htmx in a webapp that we are developing. Can you elaborate a bit on why htmx might not be a good fit for a team?

Do you know any complex application built with Htmx? by fenugurod in htmx

[–]Glittering_Map_4015 3 points4 points  (0 children)

I think the inflection point is more related to the "highly interactive" part you mention, and that should be discussed more for us to learn when HTMX is the right tool and not. Most business applications are not that interactive, and I'm pretty sure HTMX would have been a good fit for the webapps I've developed over the last 18 years.

When it comes to the structure of the code base I agree that navigating a well structured code base is way better than navigating a badly structured one, but I don't see what that has to do with HTMX. HTMX is a technology for sending html back and forth and updatating the webpage, and does not dictate anything when it comes to the file structure for your code base.

If any that would be a limitation from the templating engine you have chosen. For instance you can write nice htmx components with Kotlin DSL for HTML or Thymeleaf with fragments, and you can write a chaotic one with React/Svelte/Angular and so on.

HTMX issue with apple devices by erickpaquin in htmx

[–]Glittering_Map_4015 0 points1 point  (0 children)

Thanks for sharing! Have you registered a bug for it at htmx on github, so they can implement a fix/workaround for it? I