For about a year back in 2003-2004, I only had dial-up internet, no TV, and no social media (because it didn't exist yet). It was the most productive and creative time of my life. Then I got broadband, and I never reached those highs again. ¯\_(ツ)_/¯
I once was the victim of an empty box scam when I purchased an expensive item off Amazon a few years ago (luckily I got a refund), and since then I've used Amazon much less, and only for inexpensive things. Maybe enough people have reduced their spending such that Amazon has been forced to take notice.
> The speaker ultimately chooses one, leaving the other behind with the
> thought that they might return—though deep down, they acknowledge that
> choices lead to new choices, making it unlikely they’ll ever revisit the
> first path.
Not unlike TODO comments! An interesting analogy for life in general.
Luckily, Pepsi products are much cheaper in my area; 2L bottles regularly go on sale for 3/$5, or even 4/$5. Coke seems to be the super premium brand around here for some reason.
I've noticed it mostly at the supermarket. E.g., Coca Cola products are much more expensive than they were at the beginning of the year, and they're never on sale anymore. Certain meats and vegetables are noticeably more expensive too. Aside from that, I luckily haven't been affected too much (yet), as my energy and fuel consumption is relatively low. I'll be surprised if my HOA fee doesn't get raised again next year, though.
I’m in a senior role working for an SF company, and my permanent address is in the Bay Area. Although I haven’t relocated per se, I work from the EU for months at a time because my partner lives there. It’s occasionally inconvenient for me because meetings occur when it’s evening / nighttime in Europe —- sometimes quite late —- but fortunately I don’t have too many such meetings, and I’m a night owl anyway. For coding tasks, sometimes it can actually work out better because I can do my day’s tasks before anyone in the US is awake, then submit my PRs, attend my standups, and sign off. Sometimes it works out worse because if I’m waiting on a code review or need help during the daytime in Europe, it won’t come till nighttime. And of course there are the random times when someone in the US legitimately needs to chat with me near bedtime etc. I do believe that being so remote so often means that I wouldn’t be a good fit for roles that require more leadership, because the time zone difference makes it hard to maintain a very high level of responsive communication and availability, particularly when it comes to meetings and chat. However, I’ve more or less accepted it for now as a reasonable trade-off of being a bit of a digital nomad.
I think the analogy is that software engineering used to be like carpentry and woodworking, but now it's more like assembling Ikea furniture. Sure, the final result is the same from a purely practical point of view, but if you learned and loved the former, then it definitely feels like something has been lost in the latter.
I think you might be overlooking the fact that bias comes in different forms against different groups. E.g., a hypothetical racist might be comfortable around Asians because he thinks they're subservient and weak, whereas he might be uncomfortable around black people because he thinks they're angry and violent. If this hypothetical racist ran a company, it's plausible he'd hire Asians, but not hire black people at all.
Heh, when I was a kid I used to draw a lot, and I remember being bothered that I didn't know how to draw a bike, so back then I explicitly memorized the shapes (parallelogram in the back, and another line for the front wheels). Wonder if that's common for doodlers.
LibSass maintainer here -- it's really great to see another project pick it up, and although we're aware that we still have a fair bit of catching up to do, things like this give us all the more incentive!
Ah, that's because Travis is running all of the "to-do" tests as well. Reorganizing the tests and making Travis happy is ... well, it's on the to-do list.
We do want to support the indented syntax eventually (and I believe it should be possible with a relatively simple pre-processing step), but it's still a low priority compared to reaching feature parity with the canonical implementation.
We did a lot of development during the summer (including a rewrite that was long overdue), so there were a few segfaults back then. The library should be pretty stable now though -- we've embedded it into our SDK and build system, and it's been working fine.
As for the parser -- that started out as an experiment of sorts. I wanted to do something like parser combinators (but for scanning), and I decided to templatize the whole thing so that all of the scanning code would be generated at compile-time. If I were to redo it, I'd probably use expression templates (which I didn't know about at the time).
Yes, playing catch-up with Ruby Sass has been difficult (the sophistication and subtlety of some of Sass's features are impressive), but we're hoping to make some big leaps by the end of the year!
On huge projects, Ruby Sass can be quite slow, taking several seconds or even minutes to compile. If you have an interactive, iterative workflow where you're constantly refreshing the styles, having a faster Sass compiler can be a godsend.
I once wrote a toy video-player program, and I was able to implement robust, interactive playback controls fairly cleanly by structuring it as a state machine.
Actually, I'm the primary developer of the library (I work with hcatlin). Large Sass projects can take a long time to compile (more than several seconds), so the performance increase should not be dismissed. Also, providing a C/C++ library makes it easier to embed Sass in other languages and platforms.