The C/C++ toolchain has been working to add guards and guides to their sharp tools. Things like the various sanitizers in the llvm toolset have already meant that a lot of bugs that would have been released are instead fixed beforehand. You also have things like OpenBSD's implementation of malloc which also helps in the software feedback loop in finding logic errors that allow for things like use after free errors. C still requires attention, but there are a lot of places where it's harder to cut yourself.
I think as a counterexample, one could look to projects like FreeBSD, which have had a long-running development branch and branches for release for a very long time. Breaking changes happen in -CURRENT, but within a stable branch -- 10.x, 11.x, etc, you even get things like ABI compatibility, so a module written for kernel 10.1 will work for kernel 10.2.
The example projects show more a lack of development discipline than a problem with the big break model. A version number change from 1.8.7 to 1.9.0 doesn't suggest big changes that one should be cautious of, causing problems. Linux Kernel 2.5 had the problem of a lack of developers willing to write more inclusive tests and a lack of a pre-determined roadmap. Python had the problem of a lack of a transition version where deprecation warnings were on by default. Successful breaks can be made when they are declared in advance so people can have reasonable feedback. The projects in question show communication problems, not problems with the idea.
Things like the parentheses in print was why the 2.7 branch was created -- allow the old to exist and make available some of the new features. Probably the biggest mistake there was not to make deprecation warnings on by default, to accentuate that it was a transitionary release. Then again, it's the same problem PHP has, with not wanting to warn that the old way of doing things is going away for various reasons.
There was MS-DOS, and also Digital Research, later Novell, then Caldera, etc DOS which tended to have features that wouldn't be around until a version or two of MS DOS later. There were also nasty power plays involving the two -- early betas of Windows 3.1 would refuse to run on DR-DOS.
It has a lot of uses here and there. A ton of companies use it as the OS for their hardware diagnostic packages, or for things like firmware updates. It claims very little of the hardware for its own, so it makes it a lot easier to do things like low level format a hard drive without having to worry about some other driver/process messing with things.
That's a single 35 mile tunnel, in a comparably geographically stable area. The high speed rail project would need essentially two of those, each of which would need to cross the San Andreas fault. Additionally, a substantial amount of the remaining amount of track would need to be newly laid, because the existing rail infrastructure in the area is already near capacity, and the freight companies are hostile to any sort of improvements to passenger infrastructure. Yes, some of the issue is political, but it is an immensely challenging engineering problem to work through.
One of the problems is that the corridor in question is underserved in passenger rail right now. The only way to get between the two cities right now involves taking a train and a bus or two, because the rail company that owns the trackage between LA and Bakersfield doesn't want passenger trains running on it, and the rail company that owns the track between Ventura and San Jose would love to see passenger trains on that section of track halted as well. With such a hostile environment, it's difficult to build the interconnections that are needed for a modern rail system. Opening the Tehachapi Loop to passenger rail would be an alternative to a full passenger buildout, but you're never going to see BNSF agree to it.
There are also a lot of rather substantial engineering issues that have to be overcome in California that the train in China didn't have to consider. For example, the high speed train in California also has to cross notoriously rugged mountain ranges. The Diablo Range has a smattering of two-lane roads winding through it because it's so difficult to build through the gnarled hills. In the south, the Sierra Pelona and Tehachapi ranges almost caused California to be split in two separate before some rather remarkable feats in roadbuilding connected the two halves of the state. As such, there is an immense amount of planning, engineering studies, etc that need to take place before construction can start.
Additionally, there's a huge political element. A vocal minority of people have done everything they can to try to keep the project from taking off for various reasons. As such, there have been a rather insane amount of lawsuits filed which divert money to lawyers and time that would better be served by actually putting shovels in the ground. There are people who want it to fail for the sake of failing, because they want to bang their "government doesn't work drum" to the detriment of the taxpayers who are stuck paying for lawyers to fight their silliness.
One of the things I'm seeing there that strikes me is the lack of criticism of using contractors in this kind of work. I'm curious as to how many off the cuff conversations about the programs weren't brought up in hearings because he was a contractor, and thus not afforded as many of the rights under whistleblower statutes that employees are afforded. His chain of command is so meandering and circuitous that it would discourage damn near anyone from reporting if the toilet was backed up, let alone real problems.
Totally. I'm writing an app myself using UWP, albeit in C#. I was addressing the wanting it to be a webapp part, not the UWP or written in javascript parts, which is a totally different issue.
Which is why standardization is just as important, if not moreso, than openness in making sure things stay secure. Such an attack is made a lot more difficult if you have a second toolchain you can use to verify things, and even moreso if you have a third.
Yes, that is a huge amount of space if you concentrate it, but think about all the idle space out there -- the many many acres of rooftops of a city, for example, or the acreage of interstate highways. There are a number of places where solar can be placed where it can be ubiquitous, but at the same time, invisible. Nuclear needs a significant amount of dedicated space, whereas solar can coexist with a significant amount of uses.
To be honest, I don't want a webapp. Webapps may have a good thirty second use case, but adter that, i want something thatnis with all my other programs that I can pin to a menu/quick launch bar, that runs in a different process space so that a bug in a different program doesn't take down your program, etc. I want the same UI/UX as a native app, and that's something tat webapps still fail terribly at.
The Ubiquiti APs really are the key here. My household had the same problem with the various makes, models, etc until we switched there. For wifi, we use a mini-itx box running pfsense and it works fantastically. If you want reliability, you need to not use consumer gear, period, because it's all crap.
I don't have this problem, blank pages don't take "seconds" to load, even on my little atom-based tablet. The big question I have for people noticing this behavior is how many add-ons do they have. How many times is your "blank page" parsed by an enormous amount of code written in a language not known for its performance?
I talk about the same thing when inner city drug problems are brought up to. The article isn't about the greater problem of the war on drugs, it's about the problem as it pertains to a very poor part of West Virginia. If you aren't going to fix the underlying problems, then bringing down the exploiters isn't going to do a damn thing, because more will just take their place.
Opioid addiction is a symptom, not the disease. The disease is a generation of people who are left behind, who don't have the mobility to go where the jobs are, who can't go back to school because there are no schools in the area. The disease is the minimum wage job at dollar general which keeps their employees at 28.5 hours to keep from having to provide all the social and economic obligations of maintaining a full time employee. The disease is a lack of psychologists who can treat the underlying despair and hopelessness caused by living in a dying county. The disease is a lack of physical therapists that can teach exercises to help keep the pain away. The disease is a complete lack of infrastructure that entraps people in these small towns. The disease is an employment system that ensure that a drug conviction from ten years ago precludes them from having any sort of decent job. The disease is stigma and stagnation. We won't stop this epidemic until we fix the broken system that let it happen in the first place, and that's going to take a lot more help and a lot more money than just blaming the doctors and drug companies.
My mother had a job like this 30 years ago. She worked data entry as a keypunch operator. However, it was a full time job, above minimum wage, provided insurance and vacation time. Mechanical Turk relies on the race to the bottom, the fact that some people need any job to keep from being on the street. Of course companies love the gig economy, it keeps them from having to think of their workers as people.
This is how these sort of attacks have always worked. Get something that's just close enough so that it passes the glance attack. If someone doesn't notice anything in the first few seconds, you've done half your work right there.
They may need compiled to a specific architecture, but the actual driver code itself is pretty device-independent. Unless you're doing something like implementing your own bus instead of using something like PCI, aside from weird corner cases, the code at that level doesn't care.
What about the attempts to alter political discourse in Hong Kong, such as the Umbrella Revolution. How about their reaction to 零八宪章 (Charter 08)? Are those things we can criticize China on?
They are used in bad ways right now. Search for Tiananmen Square not via a vpn or other tool. Let me know when your internet comes back. Let me know what you want to search for afterwards, I'll let you know when my internet connection comes back up.
I feel it's more complicated than that. The problem seems to be more that psychiatric medication is being prescribed without therapy being prescribed as well. I don't feel I could be able to discuss the things I do in therapy without the psychiatric medications I'm on helping with the healing process -- blocking adrenal response due to social anxiety is one example. While I try to gain the confidence needed to socialize at all, having a medication to help me not run and hide is definitely a good thing.
Regarding your last statement, sometimes you do fix a CPU with a butane torch. There are techs that use butane solder irons so they don't have to worry about cords getting in the way while repairing bad solder joints. Sometimes there really is a mechanical problem, and not just a logic error.
A lot of medications have different effects based on dosage. For example, DXM, the active ingredient in most cough medicines is a deleriant at very high doses, and people take it recreationally (robotripping). Does this mean we should ban Robitussin? Another example is that cocaine in small doses is used as a numbing agent. Medications can and do have different effects given the dosage.
I'd compare them more to orthotics than running shoes. Some people only need them temporarily until their legs get better, some people need them for the rest of their lives. You still need a doctor, but they help with day to day activities.
Or it could be that medication keeps people from hiding from their problems. I know people who have stopped going to therapy and thus, according to stats, are "cured", however, they still have all the problems they had before. Conversely, because you need to see a doctor regularly while on psychiatric medications, it makes it a lot harder for one to hide from their situation. Over prescribed meds are definitely an issue, but there is more at play than just that.
Edit:
One of the data points describes the amount of people taking antipsychotics. The article fails to tell how a lot of psych meds, like antipsychotics, have off-label used. For example, seroquel is a sleep medication in low doses. That would count as taking an antipsychotic even though the dosage is a tenth of that needed for an antipsychotic effect. This article fails to describe how psychiatric medications really are complicated.
That is even worse, because now you have to look at two numbers to see if something's breaking or not. If you change the API, you bump the major. If you don't want to bump the major, then either figure out a way to do it with the original API, such as a different number of arguments, or put that module in a package that can be installed seperately. Given your original example, you may have package Foo 1.0 which includes subpackage Bar, but you have subpackage Bar 2.0 which people can install separately if they need to. Bumping the major tells people straight out that things have changed. Two majors means that people have to keep track of two numbers for that -- can you tell at a glance if 54.32.593.3 is compatible with 54.33.594.4, for example.
Totally different. That is a web-based chat app. MS is selling a large monitor which has chat, whiteboarding, etc, which doesn't depend on a third-party server to run. If that company goes under a year from now, you have to find another app, retrain everyone to use it, etc. Plus, it doesn't have any hardware, so you still need to set up cameras, microphones, fuss with them if things don't work right, etc. That's what MS is selling, something that's plug and play.