Sorry for not answering your question, but asking how to not let something do your work for you not be so exhausting is like listening to a billionaire complain that they have to instruct their maids and chefs too often.
Personally I think ubiquitous software is even more important to have Easter eggs, because they're the most widely distributed, and we want as much joy as we could possibly have, before you know.
No, proper easter eggs don't introduce security issues, they're benign almost by definition. I think what made them disappear was the introduction of all the suit-wearing people who decide what the programmers are supposed to program, with no room for autonomous work within that.
Proper code doesn't either, and yet there they are! The point is they added another attack surface, however small, and another code path that should be tested.
When people started to care about 100% test coverage, they started to disappear.
> The point is they added another attack surface, however small, and another code path that should be tested.
I dunno, "attack surface" to me means "facilitate opening/vulnerability somehow" and none of the easter egg code I've seen has done that. You have any concrete examples where a easter egg made possible a security vulnerability that wouldn't be possible otherwise?
But yes, another code path created by easter eggs that wasn't tested I've seen countless of times, but never been an issue, but maybe our easter eggs always been too small in scope for that.
Or they were removed for other reasons than security.
In Star Trek: 25th Anniversary, we had a hidden animation of Captain Kirk's toupee jumping off his head and running out of the room. It was caught before release and they made us take it out since no one wanted to piss off William Shatner.
It should make you wonder instead about the appropriateness of testing over man(1) output, I suppose unless you're actually generating the format for use as man(1) input, in which case congratulations on your functional tests doing their job!
What are you talking about, there is actually too much unicode awareness in C++. Unicode is not the same thing as utf-8. And, frankly, no language does it right, I'm not even sure "right" exists with Unicode
c++20's u8strings took a giant steaming dump on a number of existing projects, to the point that compiler flags had to be introduced to disable the feature just so c++20 would work with existing codebases. Granted that's utf-8 (not the same thing as unicode, as mentioned) but it's there.
Jira’s problem is that it’s effectively free-form, and there are no enforcements in place. You can have three teams - one using kanban with relative estimates, another using springs with story points, and a third using waterfall with time estimates - all in the same project, with the same workflows, and conflicting requirements. You have 3 different release fields, 2 are required, the third one is the one that your team are generating reports from.
Jira (hasn’t been JIRA for a long time) is great when you have proper Jira governance in place, with admins who say “no, you can’t have a new custom field, use this one with a new context”, configure good workflow transitions with validators and conditions, design appropriate create, view and edit screens (instead of using the same one for three separate operations), etc. The problem is always crappy administration, not Jira. Jira can be fantastic when properly managed.
Why is rust allowed to reorder fields? If I know that fields are going to be generally accessed together, this prevents me from ordering them so they fit in cache lines.
You can choose in Rust to explain the representation you want for your data type. Unlike C or C++ that's not a non-portable vendor extension it's just part of the language, look at the repr documentation: https://doc.rust-lang.org/nomicon/other-reprs.html
So if you want "what C does" you can just repr(C) and that's what you get. For most people that's not a good trade unless they're doing FFI with a language that shares this representational choice.
Rusts tradeoff is awful. People organize struct members in the logical ways in which they will be accessed. Rust just decides to do things different so they can say they do things different and "better" than the old C. The featured article is an extreme case but other normal cases would have the same issue. Packing structs should be the exception.
Ignoring the ambiguity of the word "refuse", that often means "turn into trash", it's also completely redundant with "reduce". To the point that it doesn't add anything new.
I hadn't heard the "rot" one, but I imagine it's referring to composting. We have a county-run composting site (https://www.princegeorgescountymd.gov/departments-offices/en...), and apparently when done right it produces a whole lot less methane than letting organics get buried and decompose in landfills.
There is overlap but I can see some distinction. Refuse might be simply not in first place buying some product group say a smartwatch. Where as reduce would be buying one but updating it less often. One could argue that refusing entire products is easier than reducing use.
How confusing. There's no appreciable difference between "refuse" and "reduce". "Rot" is only applicable to organic waste, which is rarely considered part of "recycling" since the other Rs don't really apply.
Consumers have the option to "refuse" products from irresponsible or predatory vendors: ones which brick or obsolete devices.
Vendors should at a minimum open source APIs for abandoned hardware and allow unlocking it. "Refuse" to buy from those that don't. Ask for legislation forcing it.
I have a wonderful old ipad mini that's useless. I'd love to jailbreak it and put my OS on there but Apple wants a new sale instead.
Bio degradable packaging is not really suitable for composting yourself. Most of it takes a really long time to break down naturally or requires high composting temperatures that can be hard to achieve in a home compost pile. This is true even for basic stuff like cardboard and paper. You also need a lot of "green"[1] (high nitrogen) composting material to balance out cellulose from packaging.
The net result is that this is still an industrial process. Though probably less energy-intensive than recycling.
Source: we have a compost pile and it's not all sunshine and roses.
A lot of "biodegradable" will use a literal interpretation, in that it it degrades in nature. 500 years you say? But it still degrades...
Home compostable is really the only one that makes sense. Even industrial composting requires a high heat environment as the catalyst, so if something contaminates the batch and goes into general refuse then it will never break down.
At its core antitrust cases are about monopolies and how companies use anti-competitive conduct to maintain their monopoly.
Github isn't the only source control software in the market. Unless they're doing something obvious and nefarious, its doubtful the justice department will step in when you can simply choose one of many others like Bitbucket, Sourcetree, Gitlab, SVN, CVS, Fossil, DARCS, or Bazaar.
There's just too much competition in the market right now for the govt to do anything.
Minimal changes have occurred to the concept of “antitrust” since its inception as a form of societal justice against corporations, at least per my understanding.
I doubt policymakers in the early 1900s could have predicted the impact of technology and globalization on the corporate landscape, especially vis a vis “vertical integration”.
Personally, I think vertical integration is a pretty big blind spot in laws and policies that are meant to ensure that consumers are not negatively impacted by anticompetitive corporate practices. Sure, “competition” may exist, but the market activity often shifts meaningfully in a direction that is harmful consumers once the biggest players swallow another piece of the supply chain (or product concept), and not just their competitors.
There was a change in the enforcement of antitrust law in the 1970s. Consumer welfare, which came to mean lower prices, is the standard. Effectively normal competition is fine and takes egregious behavior to be violation. It even assumes that big companies are more efficient which makes up for lack of competition.
The other change is reluctance to break up companies. AT&T break up was big deal. Microsoft survived being broken up in its antitrust trial. Tech companies can only be broken up vertically, but maybe the forced competition would be enough.
Not really. It's a network effect, like Facebook. Value scales quadratically with the number of users, because nobody wants to "have to check two apps".
We should buy out monopolies like the Chinese government does. If you corner the market, then you get a little payout and a "You beat capitalism! Play again?" prize. Other companies can still compete but the customers will get a nice state-funded high-quality option forever.
The more stable/secure a monopoly is in its position the less incentive it has to deliver high quality services.
If a company can build a monopoly (or oligopoly) in multiple markets, it can then use these monopolies to build stability for them all. For example, Google uses ads on the Google Search homepage to build a browser near-monopoly and uses Chrome to push people to use Google Search homepage. Both markets have to be attacked simultaneously by competitors to have a fighting chance.
It does? Do you know git is a dvcs? And therefore you're able to continue working without an internet connection or a service provider being up? It delays the code review process but doesn't break it.
I get it that you want it to be 100% up, but let's be serious your FLOSS projects probably break more stuff than GitHub being down does.
Not sure how having downtime is an anti-competition issue. I'm also not sure how you think you can take things away from people? Do you think someone just gave them GitHub and then take it away? Who are you expecting to take it away? Also, does your system have 100% uptime?
Companies used to be forced to sell parts of their business when antitrust was involved. The issue isn't the downtime, they should never have been allowed to own this in the first place.
There was just a recent case with Google to decide if they would have to sell Chrome. Of course the Judge ruled no. Nowadays you can have a monopoly in 20 adjacent industries and the courts will say it's fine.
You've been banging on about this for a while, I think this is my third time responding to one of your accounts. There is no antitrust issue, how are they messing with other competitors? You never back up your reasoning. How many accounts do you have active since I bet all the downvotes are from you?
I've had two accounts. I changed because I don't like the history (maybe one other person has the same opinion I did?). Anyways it's pretty obvious why this is an issue. Microsoft has a historical issue with being brutal to competition. There is no oversight as to what they do with the private data on GitHub. It's absolutely an antitrust issue. Do you need more reasoning?
Didn't you just privately tell me it was 4 accounts? Maybe that was someone else hating on Windows 95. But you need an active reason not what they did 20 years ago.
What someone saying to me privately via other channels that it was them when I asked them. It was some dude at Google so maybe complain to Google but I don't think this site has rules about what you do off the site. I don't think you understand rules and laws and stuff to be fair. And I'm pretty sure it was you because it's weird if someone was pretending to be you.
Perl was written to write more complicated bash scripts. It's so seamless to call and handle shell commands and the first class regexes make it terse in a way that's appropriate for this use case.
reply