3,307 karma · joined January 4, 2018
However, I say part of the problem is that windows updates are pushed out in a big blob instead the update being pushed in a more granular fashion. This ends up in with sometimes an update containing files or setting for something you removed.
There is no reason it has be like this, but that is how updates work on windows, and I don't think Microsoft is going to change that any time soon. I am imagine in theory it would be possible for a community to break down each update into smaller discrete chunks. However, the community would have to be a decent size and dedicated enough to keep up with the rate MS rolls out updates.
Also there some things like Edge and Cortana that current day windows is not very happy with if you nuke it from the system.
Rust does not have a defined standard yet, but I suspect it also would be quite large.
It can be made to function more like C with #![no_std]. However that is an even less than batteries included experience than C.
However, most countries can dig up rocks out of the ground with radioactive isotopes that can act as a neutron source. However, this has legitimate uses as well from research to medical imagining. Also any power generating reactor is gonna want to use those neutrons to make Tritium otherwise it would quickly run out fuel so not something you just want use on something unrelated to running the fusion reactor.
Still even if it's just the beam we are at an energy positive which is still great news because it mean the fundamentals are working.
Still other issues though, the biggest in my opinion are an effective way to produce Tritium and energy extraction.
The concept makes dealing with some the topics in this post much more logical and easier in my opinion.
Taking the authors example of a TCP network stack you often can't do though since OS won't let you have that low level of access by default without using or writing some custom driver since the OS ends up trying to isolate usee-space completely.
Kinda makes me wish more research has been done on things like exo-kernels where the OS is mainly concerned with security and not the abstraction. All the abstraction runs in user space on such a kernel and you can choose what level is suitable for what your doing. https://en.wikipedia.org/wiki/Exokernel
And once one shingle pops loose suddenly it's much easier for the wind to get under the other shingles near by and the failure can cascade like dominoes in a hurricane situation. Going from a simple repair to replacement of a section or to a whole roof replacement.
Also an other aspect is double checking the shingles are properly placed otherwise the seal strip won't adhere in the correct spot on the shingle below making it easier for the adhesive to come loose and again same problem.
The thing is if you have seen how fast most roofing companies put a roof on a house do you think they are going to do this right?
Also sadly if the roof fails during a hurricane it just means more work for them in the future which means more money paid by insurance. So their incentives are not there. Like there are some roofing companies that will go door to door after a major storm looking for houses basically that have storm damage and get the homeowner to file claim. Looking for things like an out of production shingle so instead of a repair insurance has to buy a whole new roof since replacement shingles don't exist. It's really scummy. The sad thing is this scummy behavior had lead to insurance companies way more likely to deny claims that are valid. I remember seeing a video of roofer with an insurance adjuster acting like what the roofer said was not true or not comment or document it. It was kinda insane and sad at the same time.
Last note: Although shingles without a hurricane rating in my opinion should not be installed in places like Florida.
While this is a different than warning you about errors it still is an important aspect of compiler.
Having used both compilers quite a bit they each have their own strengths. Although I will add clangs code generation as gotten a lot better over the years that it does not generate crazy bad machine code as often anymore, but I still see it happen.
However, I think most human drivers would slow down and/or stop in such situation. The self driving car however in this paper would just keep driving...
In the case of Apple it's pretty hard to justify the court costs for a 1000 dollar device. So Apple rarely has to prove that the Jail break was the cause of the failure. They technically can't deny warranty claim if a modification was not the cause of the failure. However, Apple operates basically by default for almost all failures if Jail Broken you get no warranty which is technically not legal.
They can only deny a warranty if the modification caused the damage. However, they can claim it did and deny you even if it's not true.
Leaving you basically only two options payup or pay lawyers and court fees ect.. to sue them.
Consider, how much just a single lawyer cost per hour I don't think it would be worth it a lot of the times unless the entire car was basically destroyed or something very expensive has failed to have enough value to justify it. Otherwise the repair is gonna be a lot times in a similar ballpark cost wise (for most cars) as a law suite.
-Edit- Moreover if the case is not decided quickly or settled it could also end up costing a lot more.
This statement very much resonates with me. It's honestly one of the things I like about C. Although it's not perfectly like this for me all the time. For example string manipulation is not great.
An other aspect I like about C is there is not a plethora ways of doing the same thing which I have found always made it more readable than rust and C++.
These days they have diverged even further. So I find funny to see C/C++ on job listings like it's one thing. While you can write code in a very C like manner in C++. That is not how typical C++ is often written these days.
I suggest just read the first paragraph of wikipedia: https://en.wikipedia.org/wiki/Price_gouging
Particularly these sentences:
* "In precise legal usage, it is the name of a crime that applies in some jurisdictions of the United States during civil emergencies. In less precise usage, it can refer either to prices obtained by practices inconsistent with a competitive free market or to windfall profits."
* "The term is not in widespread use in mainstream economic theory, but it is sometimes used to refer to practices of a coercive monopoly that raises prices above the market rate that would otherwise prevail in a competitive environment."
The term gouging does not always refer to the criminal/civil (depends on jurisdiction) act of price gouging. There is a reason I said "gouged or overpay" and not just gouged because the term does have a few connotations and the overpay clarifies more of what I am getting at.
As to your second point if the company is still making money in these countries with less purchasing power at lower prices why not just use that price then? Those people would not be locked out of purchasing it then. Also not everyone in a wealthy country is wealthy or has lots of extra money. High pricing in such countries also locks those people out. This argument is basically saying someone should just pay more because they are likely to have more money, and not pay the actually value of the product or goods.
You are combining multiple things in this example such as utility, opportunity cost, economic value to person ect... The same item or product weather priced at $1 or $1,000,000 dollars on average is probably gonna to produce similar amount of utility from person to person. However, with this extreme of the example I made above there are going to be huge difference in particularly opportunity cost. The utility in your case the enjoyment derived from the game of course is going to be same regardless whatever else someone paid for the same game as well.
Now companies generally often want to charge as much as they can for a good. Ideally, for every person a company sells their goods too they would charge economic value for that particular person instead of something like market value to maximize profit. Now in a competitive market a company is unlikely to be able charge whatever they want and still remain in business, but in less competitive markets this not necessarily the case. Even if people can afford the goods at these inflated prices in less competitive markets. Exact dollar amounts aside, higher prices are going to lead higher opportunity costs for people which is not a good thing.
This is just side note you since mentioned value in your example. What is the true nature of value has been argued quite a bit throughout history. What value is partially depends on what one believes is the correct theory of value. I tend believe all items have some intrinsic value as well as a subjective value. Let's take an other example let us say iron and dirt both products of the Earth. I would say the iron would have a slightly higher intrinsic value than just dirt. This is because iron can do lots of things that can provide more numerous types of utility and that boils down to its material properties. Regardless what one feels or thinks of iron it's going to have the same material properties. However, this does not mean dirt has no value as well lets look at the subjective side of value. A farmer for instance is going to value good dirt probably more than welder that fabricates objects from iron and steel. So value between the two is subjective based off the individual. So the value of good dirt is likely to be higher for a farmer than that of a welder. However, this still does not mean dirt has no intrinsic value either based off it's properties. The properties of dirt can be used to grow things, and certain types of dirt such as clay can even be great building materials because it can be vitrified into bricks for example.
Like some companies have ridiculous things like MAP when comes to retailers selling their products.
Just because a lot people are getting gouged and don't realize it does not mean they are not being gouged on price. Ideally other competition would help balance out this information asymmetry. In the ideal sense that a competitors costs to produce the same product/good would be roughly the same or in at least similar ball park that if one company is pricing something insanely high it would stand out. Although there hosts of reasons this does not work out in practice ranging from limited or no competition. Other issues such as that most goods are not identical ect...
That would make interacting with OS slower, and probably even more important are things like .DLLs/.SOs. If the dynamic library or heck even a static library your linking against used message passing imagine all the cases where that would be a bad idea. All that overhead just so you can call a function not written in whatever language you happen to be using. ABI's like we have now are a much better for this reason. Also just because one uses message passing does not mean there are no compatibility issues.
I think the main issue here is if we reference the article linked. "You Can’t Actually Parse A C Header". To know the size of types and therefore figure out memory layout you need to be able to read a C header. With that information you can construct a lot the ABI for a C function. Aside from some OS specific things like stack layout requirements and hardware/OS specific things like what registers are used for certain parameters of a function ect...
The problem here is once compiled this information is not readily accessible without being able to read a C Header. That's why the author here mentions parsing a C header and says most people just end up letting a compiler do that.
If your writing C and ignoring things like INT_MAX or the minimum range requirements specified by the standard or not using sizeof() when your worried the memory size of these base types. Your code is not going to be portable.
C definitely let's you handle and know the domain of your variables.
Although at least a lot of it can be setup with automated tooling. Although the interface seems to also have a lot more overhead than a basic function call. I hardly would call it a better situation.