scientuslatens

joined 3 years ago
[–] scientuslatens@infosec.pub 0 points 3 days ago* (last edited 3 days ago)

Back with some pictures:

Detail of the new type of hinge. The hinge is one piece now Detail of the new type of hinge. The hinge is one piece now

The way they fold/stack for storage The way they fold/stack for storage

[–] scientuslatens@infosec.pub 0 points 3 days ago

I had my Q30s last me ~ 4 years (I even preordered them) until my headband came apart. I tried putty epoxy to fix them but there just wasn’t enough places for it to grab on to. I got replacement pads for them after about 3 years too. My battery was still good, so they would have lasted some more time before I gave up on them.

I got the space ones in November. The ear cups swivel to pack down and that seems to fix the weak spot I got on the Q30s, so I’m happy about that.

Just one note really, the Space Ones have a carrying bag, but if you have the Q30 case, they will fit in there.

So far so good!

[–] scientuslatens@infosec.pub 2 points 3 months ago

Is this the chatbot equivalent of “you spelled the word so wrong, even autocorrect can’t help you”?

[–] scientuslatens@infosec.pub 4 points 6 months ago

Delonghi parts are easy to get a hold of too, so get the part if you can

[–] scientuslatens@infosec.pub 0 points 8 months ago (1 children)

That seem reasonable. Don’t add more to learn before you know you need it. Is there an http server that is built in to Rust?

[–] scientuslatens@infosec.pub 0 points 8 months ago (9 children)

The backend you are working on can also help narrow down what front end you may want to try. I am a “full-stack” .NET (i.e. I do backend but I’m stubborn enough to touch and make choices on our front end vs other members on my team). Naturally, our apps are ASP.NET MVC/Razor pages, and I’ve dragged a few things over to Blazor for some of our new apps. One could still add vanilla JS / Browser APIs on top of this and cover most needs. Bootstrap consider what you need to keep you app mobile-friendly (usually described as “responsive”), and can be used with just data- attributes.

My opinion is the front end should be quick and should also be light on business logic. Then you are just making http requests for data retrieval or requesting the server to do something. Then you can break out your backend methods/services to handle your data persistence > business logic > shaping the results for what your front end needs

Sorry that got long TL;DR see what front end usually seems paired with your backend and start there. For example, try .NET/ASP.NET Core