2,878 karma · joined June 15, 2016
When working from home, when 5pm hits, the first thing I want to do is get out of the house. I do lots of group activities, hiking, kayaking, cycling, pool, trivia, photography, etc.
When I have to go in to the office, when 5pm hits, all I want to do is go home. Once I'm home, I'm much less likely to leave.
I understand I'm a sample size of one. And even though several of my who work from home friends feel the same way, it's obvious I never meet the people who stay at home. But I'm curiious as to whether the people staying at home would go out if they worked in an office. Seems like that'd make most sense if you're hanging out with people you work with, which I don't do much. But I doubt there's a good sample size of people who've switched back and forth.
OpenSCAD supposedly supports Python now (https://pythonscad.org/), but I was not able to get it to work at all. I've fallen back to just OpenSCAD, even though it has limitations, at least I'm familiar with them. I'm mostly just waiting for improvements to anything that'll make it better than OpenSCAD.
You are probably better off searching for old graphics programming books from the 90s. The code they have likely won't work, the the algorithms should be what you're looking for, and shouldn't be hard to adapt.
Really not sure what you're trying to get at there, obviously any element that displays will have a width and height. Maybe you meant a user specified width/height, but the entire point of my post is an inline-block is an inline element with a specifiable width and height. And we've always had the IMG tag, which is also an inline element with a specifiable width and height. The obvious and intuitive choice would have been to not put artificial limits on inline elements.
Just one example most people already know. If I set a height or width on an inline element, it's ignored. So, obviously there is a limitation in the renderer that can't do it. But wait, make it inline-block and suddenly it works! So why the f*k didn't it just honor the width and height to begin with? It's quite literally a rule for the sake of having a rule.
I don't doubt there is some deep dark reason for why it is the way it is, like optimizations, or backwards compatability, but it doesn't matter to the end user. It's an implementation detail they shouldn't have to bother with.
I tried using Build123d, a Python library that lets you use all of the features of Python. And it's supposed to allow specifically things like box1.width, but it's always 0. Lots of other issues/bugs too, and severely lacking in ddocumentation.Maybe it'll get there some day.
But "Every check and balance is working" is clearly wrong.
Starlink launches reduce costs by launching a bunch of satellites with similar orbits on the same vehicle, replacing one or a few satellites is going to cost a lot more per satellite. So just disrupting the network is a lot cheaper than fixing it.
Thought the cheapest is still probably paying an existing employee to break some stuff.