I'm from the only remaining US state without a mandatory seat belt law, New Hampshire. As far as I can tell, we pair off equally with our neighbor to the west, Vermont, in road fatalities[1]. The two states are very similar in geography and population distribution, neither having much in the way of public transportation or large cities.
Regardless of the law, people are wearing seat belts at roughly the same rates. This is to say, at least in my corner of the world--seat belts save lives, but seat belt laws don't. People oppose these laws on philosophical grounds; the role of the state, acceptable levels of police discretion, etc.. Policy is messy, but at minimum must accommodate the values of those it represents.
I want to believe, I really do. Intel can't offer a compelling reason to upgrade my 5 year old 3930k--there's no question that the desktop market has stagnated in the face of a weakened AMD. Can anyone enlighten me as to what video encoding and 3d benchmarks might omit that a more well-rounded passmark score would not?
Archos Jukebox was pretty great--had SPDIF IO and an accessible 2.5" hard drive (upgradable). Wasn't pretty, but in terms of functionality, it was amazing for its time. Rockbox firmware was icing on the cake.
CentOS is in a tricky position with regard to ALPN/http2 support--there's absolutely nothing on the horizon. A continuing shift to Ubuntu in the webserver space is almost certain in the mid-term.
Software updates in general are just getting sloppy, this isn't limited to Apple. The Windows 10 anniversary update had issues as well. Makes me long for the old MS service pack model.
I think this trivializes the scope of what the BBC developed. Even with well automated processes, you'd still want a human doing light QA given the wide diversity of content. The BBC has been at it for over twenty years building ad hoc minisites[1]--sites so far down the long tail, that if forced to choose, they may be more prone to pull the plug than to maintain.
It's a value argument. You've framed it in terms of stability, life expectancy, rule of law; someone else may frame through a different lens (family, leisure, etc.). You can substitute hunter/gatherer for 1960s or 80s political nostalgia and find a similar argument.
This is exactly what works for me. To add to this strategy, I tend to note (not fix) easy todos and leave them as a warm up for the next day. It can be difficult to start cold on hard problems.
I may be reading between the lines, but it sounds like it's the business side of things that is becoming miserable. If you still enjoy writing software, it might be worth worth exploring opportunities outside of self-employment. Working for a manager comes with its own set of problems, but it can be a whole lot less stressful financially and emotionally.
The Pew study looks at household income. I guess that is one way to look at it, but it never struck me as a reasonable model. When you look at wages, the story is far more concerning. Focusing on wages surfaces the fact that households have broadly gone from one income to two since the 70's. Modeling based on household income understands the depressing of wages as a loss of leisure time. I'm not saying it's wrong, just an odd perspective.
It's good to understand the trade-offs and not blindly be adding binaries and configs, but source control conventions should boil down to what works best for you and your team. For configs, I've found a reasonable solution is to include a base config and override with a repo-ignored, local config containing system/db specific values that do not belong in source control.
My team's been using a project management tool to document dark corners and eccentricities within our systems. It sort of works as a searchable DB of notes, and the more I contribute, the more I get the same "who's ever going to read this" feeling. We've also experimented with wiki. I'm not sure what the solution is to contextualizing knowledge, but it certainly feels like the tools available are in their infancy.
It's clear that secondhand smoke does harm others, but the extent to which it does is a matter of debate. There's non-tobacco funded research that indicates it's not a significant risk unless you live with an in-home smoker for 30 years[1] (lung cancer only, not sure about heart disease). There are studies that paint a far more extreme situation, I'm sure, but I think this puts occasional outdoor exposure into perspective.
The need is for the caffeine--the easiest way to get off the diet soda train is green tea, and to ease off the caffeine from there. Others just don't find water satisfying for other reasons, which I can relate to. I tend to drink a 60/40% mix of seltzer and fruit juice, which after a week or so adapting tastes surprisingly sweet. In any case, there are options beyond water that aren't all bad.
I think developers looking for Unreal performance from Unity 3d will be disappointed. What Unity has over Unreal is C#, great interactive tools (a live stage within a running game), and the ability to publish to just about anything.
Superfish is the tip of the iceberg. Microsoft really needs to get the hardware vendors in line before these preinstalls bring down Windows. Causal users make no distinction between the the crapware getting preloaded and Windows itself.
I'm always annoyed when I see UUIDs in my directory structure, it's the same feeling I get when I see a big mac wrapper littered in my yard, or MSOCache in Windows system root for that matter.
You might think about keeping an eye out for jobs in higher-ed if there are any colleges or universities nearby. At least in the US, higher-ed jobs typically have generous vacation benefits and a better than average work culture. Unfortunately, they pay less than market, but for a lot of people, it's a fair trade. A couple extra weeks of vacation a year isn't the be-all, end-all, but it does go a long way toward moving the needle on a side project. Long-term, maybe figure out how to move near an economic hub--which I realize is easier said than done.
I've two minds about the proposed change. On one hand, anything that can make it more difficult for governments to engage in dragnet surveillance is a public good. Though, I have reservations that the CA model is not what should be endorsed here. At the risk of regurgitating the same arguments that come up every time with https, I'd much prefer the separation of encryption and authentication in the way browsers echo security back to the user. When logging into a site, I want authentication, when I'm browsing as a guest, encryption alone is fine. The way browsers have thrown self-signed certificates under the bus has only helped to enable state surveillance at its current scale.
It could have something to do with CPU throttling, though I'm sure there are other factors at play. Once the temperature crosses the threshold, performance will deteriorate significantly. My guess is the better performing games operating below threshold.
Apparently, smoking related fires are deadly, but rarer than you'd think (causing only 2% of residential fires, though surprisingly 14% of deaths). But point taken with regards to smoking in bed, which is apparently still a thing..
I'll gladly defer to an astrophysicist on matters of the universe, a plumber on piping, or a mechanic on auto repair. I think the problem is the field of social sciences is kind of a wasteland. While I can respect the skills and analysis of someone in the field, it's highly nuanced material with plenty of room for debate. I'm not sure it's a bad thing.
The city I live in ran a campaign a number of years ago handing out $1000 vouchers to upgrade inefficient wood stoves. It can be a air quality issue, but the major issue is one of efficiency. Modern wood stoves are very efficient - where a fireplace may run at 15%, some of the new hearthstones exceed 80%. In any case, as someone from New Hampshire, I find it insulting that anyone would frame burning wood as "recreational."
The misuse of the term seems to date back three centuries, and has been abused for literary effect by many notable authors, including F. Scott Fitzgerald, Mark Twain, Jane Austin and Luisa May Alcott. So it seems perfectly acceptable to use the second definition with a wink, casually letting your audience know you know they know.
The upgrade path used to be pretty liberal, until last year you could skip two releases and still catch an upgrade. I think I've spent about $1800 total over 11 years: Macromedia MX Studio (2002) > CS3 Web Premium (2007) > CS6 (2012). That's a just over $13 a month. Not cheap when time comes to upgrade or lose eligibility, yes, but much cheaper than $50 per month in the long run. It really depends on the user's upgrade cycle.
Was wondering where that went. I used it all the time, but only for the link to the cached version. Good to know it's still available under the green arrow.
Had a similar project based on OData called qwikstant.com, by no means a hit, but still trafficked. It's depressing to have to shutter it.. As I was developing I did notice that the OData DB was always slightly behind and the api forums were a ghost town - guess I should have seen it coming, but I had an itch. Got burned when google shut off services before as well, pretty sure I'm finished with free corporate APIs at this point, experimentation and one-offs aside.
That's a good point, and one I've struggled with a bit. I'd envisioned it being mobile friendly (android only so far) which places serious constraints on available screen real estate. On my tablet, the existing search filters run up against the limits. I'm not sure how far a one size fits all approach goes, and forking the display for desktop might be one way to solve that - but it has it's own set of issues.