I don't know how many neighborhoods are like mine but we recently had our roads redone and each house in the neighborhood was assessed based on the road frontage that they had. Our neighborhood does not own the street maybe but we have a financial incentive to keep them nice since the residents actually paid for a large part of the construction. An extra 45,000 cars per day would wear the roads much more quickly.
Sure, now. In 5 years who knows? I could definitely see AAPL partnering with visa/mastercard/amex or even directly with banks for direct account access on a program that doesn't require a physical card. Plastic cards will become the new cash (right now cash-only businesses are a little behind the times but they still exist) and phone payments will become the new plastic.
How much does a digital sign really benefit from tracking the most recent releases anyways? Other than the obvious issue of security fixes, it doesn't seem like that is a domain that would really care that much about trying to keep up.
AFAIK they are saying that because it is a DKMS module and Linux is not a derivative work, they are not restricted from using it by the license. By Canonical's interpretation, it would only become an issue if they were to build the support directly into the kernel natively rather than using a standalone zfs.ko file.
Keep in mind IANAL and this is just my limited understanding of the issue.
I'm not familiar with the project but it sounds to me more like they just relicensed it with a free as in freedom license. Not that it is just becoming open source.
He actually addressed that. He said its hard to promise to keep that stuff forever, implying that limiting the promise only to published content was an intentional decision in order to make it feasible to make the promise at all. Notice also that he did mention that they save that stuff right now, despite not promising. Better to promise to save what you can than to not save anything at all. I thought his response was quite adequate.
Likely a site with the influence of twitter would be able to get this taken care of. (directions at another domain on how to clear your cache or even a direct update from browser vendors possibly)
They get away with it by being a well established known player with a long history of trustworthiness and branding. Github enterprise is not a guy I've never heard of just saying "Hey run this closed source binary on your computer." They also offer an amazing product that was revolutionary when it first came out. They weren't copying an already well known good product. There are some open source competitors now, but they had an enormous head start.
Which is why I use the noscript fallback. I'm just saying it's not worth my time to worry overmuch about supporting everybody's use case on a personal blog full of half-completed thoughts. Nobody is trying to automate anything using my site and if they are then I feel bad for them. If javascript is on my site is fine, if not then you can see the markdown files. I'm not worried about anybody else.
Many browser exploits that break out of the sandbox take advantage of javascript. Disabling it prevents entire classes of exploits. Also, a lot of ad networks use javascript as a tracking tool.
It really depends on the use case. My site[0] works in a very similar fashion to cms.js but if you have javascript disabled it forwards you to the raw markdown file using a simple noscript tag. Sure, it breaks cURL but it's just a personal website so who really cares?
I would certainly hope code written today at least _could_ last until python 4. The idea that everything has to be rewritten just because of a language version bump is a flawed thought process IMO.
Please don't do that with drop shadows. The combination of the non-3d image and the 3d drop shadow makes for a really disconcerting distortion effect. Are the corners of the image curled up or not? A simple 2-3 px drop shadow on the right and bottom edges would look much better imo.
It's not really "stealing" but you could theoretically fork it and gain enough market share on your fork that your version becomes what people think of when you say Android.
Well to be fair, you can just use the man pages if you don't have network access. Or you could git clone the repo and print it from the repo. I think his point is that this is a problem that is easy to overengineer and really doesn't need that much work to be done.
I think this is probably both caused by, and in order to take advantage of, personal subconscious bias. Not only do people expect assistants are going to be female, but actually notice when they're male. It's just another small facet of the huge gender inequality problem. Worth noting that you can rename clara if you pay enough and the only competitor that I know of (https://x.ai/) has male and female options.