The critical thing is having unlock and recovery for the model. Without that, it can’t generally be reflashed.
The critical thing is having unlock and recovery for the model. Without that, it can’t generally be reflashed.
I think those should work, but if you’re entirely degoogled, maybe running a container would work?
It’s the stupid name.
If be interested. I’ve only used desktop VLC and only as a backup player since it tends to have its own code for most things instead of using shared components that sometimes it can do things other players fail at. That could be useful on Android as well and if the player’s also good, no who knows.
My guesses are clog (99% of all extrusion problems), heater problem, wrong filament diameter or broken extruder (check for slipping and cracked arm, spring etc).
I don’t know if twerking helps, but it doesn’t hurt to try.
The Ender probably wasn’t. It was a lot of effort, and mostly not the interesting kind, and fairly little reward. Although when it worked, it was really good. In the end. Sometimes. And it’s way too big.
The Kingroon, very much yes. It’s cheap, kind of trashy, but compact. Just prints stuff. Parts detach great. Works just about every time. Quiet out of the box. Just kind of annoying to preheat at the start and end of the session to load and unload filament. Very annoying touchscreen. But those are minor things and I’m not tempted to fix it or upgrade anything. I have actual projects to do. Too many actual projects to do.
Oh, and why? Custom parts that are impossible to buy and a lot of work or impossible to machine or fabricate otherwise. Saves a trip to the local library or hackerspace or wherever things could be printed.
You can pick any. I guess the way is to just pick one based on it’s description or users or package availability or size and then learn to use it. And or try another one when you figure out if it has problems. Sick with the one you like the most. Or write your own.
Mostly only the charger cares. A tool often only has power contacts. Something “smarter” like a camera with battery life gauges in the menu etc will most likely want to talk to the battery.
But if the company thinks the extra cost in manufacture is worth it, they’ll probably choose evil.
Most Unix systems had it in CDE, 1993. Most also had it in whatever came before.
The first platform to implement multiple desktop display as a hardware feature was Amiga 1000, released in 1985.
The first implementation of virtual desktops for Unix was vtwm in 1990.
https://en.wikipedia.org/wiki/Virtual_desktop
It had been the expected default for pretty much an entire decade. Also X often supported a different size viewport and desktop so the view would scroll. Not sure if anyone really liked using that.
Have you tried turning it off and on again?
NeXT is probably the pretty direct ancestor of osx dock. Only Apple turned it from good to bad by moving it to the bottom, where there is no space. And that only got worse as screens became wider, but not taller. And they made it overlap and obscure content and bounce around if you got near it making it extra obnoxious and hard to use.
Other docks existed even before, of course.
You could use some sort of caffeine as a workaround. I do since sleep locks don’t always work.
It’s Nvidia. That’s not going to change.
Nvidia user?
Everyone doesn’t. Just a handful of loud idiots who mostly don’t work with init systems. It is objectively better. There are some things you could criticise, but any blanket statement like that is just category a.
I was just thinking that iptables lasted a good 20 years. Over twice that of ipchains. Was it good enough or did it just have too much inertia?
Nf is probably a welcome improvement in any case.
Newer toolkits all seem to be going immediate mode. Which I kind of hate as an idea personally.
But it was the blackjack and hookers that got us into this in the first place.
No. But you can run some of the init scripts with ‘status’ and they might print something. And telinit can do a few basic things.
https://sfconservancy.org/GiveUpGitHub/