3,623 karma · joined July 17, 2016
This comment should be featured higher in a discussion. The "stupid" label is thrown rather fast although more often than not the problem lies in how critics fail to understand the problem and, more importantly, the restrictions applied to the decision-making process. Therefore critics base their view on their personal and very over-simplified and under-informed view of the problem, don't understand how an outcome is a valid and reasonable solution, and instead of assuming that they have limited information and understanding... They instead assume they have perfect information and complete insight into a problem and therefore any outcome they didn't approve or understand can only mean stupidity.
Research grants also fit that description quite nicely.
You're assuming that an organization can whip out the best proposal possible at a moment's notice, which is highly unlikely. What you perceive as waste is simply development costs, without which the organization could not come up with the most competitive option possible.
Complaining that having different teams working internally on a product is wasteful is just like complaining that a sports team that hiring backup players and running development league teams is wasteful.
Additinally, the Apple whataboutism is a non-sequitur that adds zero to the discussion.
You mean Google's own Google Play store?
Sounds like Google is in control of that one as well.
Apples and oranges. Smart pointers are wrappers over raw pointers. They extend functionality, but are not the same.
> Except that you generally create them with std::make_shared() and std::make_unique()
Again, apples and oranges. You're confusing factory functions that wrap memory allocation for convenience with actual memory allocation.
At most you could only complain that those factory methods duplicate the role of constructors, which would be silly.
> And then you have the fun of passing those to a function. Do you pass by value (shared_ptr) or by reference (I believe you do not) or pass a naked pointer (when you need to pass a unique_ptr to a function that uses, but does not modify or cache the pointer, if I remember correctly).
There is no duplication in your examples. You are just unaware of how those functionalities are used.
That may be your personal opinion but that contrasts with both the facts and pushes a narrative that doesn't fit reality. For example, I routinely charge unexpected expenses on a credit card although I am more than capable of easily covering them with my savings. I'm sure thay the sheer convenience of charging expenses on a CC drives the decisions of regular CC users, specially as some CC plans charge 0% interests under some conditions.
Arguably, what makes C the perfect example is not necessarily its standard library functions per se but the language's official string data type.
One of the biggest disservice that has been made towards humanity is the fabrication of this notion that evil totalitarian regimes such as Nazi Germany or Communist Russia are exceptional events created by exceptional individuals who are extraoedinarily evil up to a supernatural/cartoonish level. This fabricated sense of exceptionalisn leads people to believe that thesr massive levels of cruelty are impossible to reproduce, thus there is no likelihood that our little world could ever descend into that state of affairs, even when we repeatedly see cases where police forces assassinate citizens with complete impunity.
Serverless costs you money. Running a low-volume db in the same VM you serve the site and the web api costs you zero.
Doesn't the video show a group of gunmen who the camera guy was following around?
Actually, it is. Specs dictate the potential uses of a device, and a more expensive but less capable option simply means users have to pay more to be able to achieve less.
In this case one option appears to be outclassed im every criteria. If these technical aspects weren't relevant then the specs wouldn't have been presented as the device's selling point.
It is obviously a technical shootout. Time and money are a finite commodity and having to spend more on a less capable device that takes more work to get up and running is not a good way to invest our resources.
Edit: why are you downvoting a honest question?
What's the difference? Developers can only leverage existing technology if they are aware they exist, and unfortunately specs such as the "home document for HTTP APIs" draft aren't publicized that often, so developers tend to waste time reinventing the wheel.
> Additionally, this would be more useful it contained (I didn’t see any from my phone) links to example implementations or discussions about the RFC.
Typically specs already include examples. For example, picking up again the "home document for HTTP APIs" draft, section 2 starts off with a clear example of such a document.
HATEOAS is not a standard nora specification. It's a basic part of the REST architecture style.
> "When designing a hypermedia API [per HATEOAS standards], you're really designing for a client that does not, and will never, exist."
I don't believe this is factual or even conceivable. Arguably, OData speficies a standard that designs clients and servers that are full-on REST (per HATEOAS standards) and it does exist and is used in the wild for some years now.
Additionally, there are other standards and specs that do help to implement full-on REST, such as HAL or JSON-LD.
Supervisor: I need to improve my metrics and you only published a paper last year. You owe me 3 papers in the next 6 months.
Me: How am I going to write 3 papers?
Supervisor: You figure it out.
Me: What topic should I write about?
Supervisor: That's your job.
That's also a big fat red herring.
The clients of a service are not employers of the contractor, and just because a contractor decides to invest some of his time to provide a service through ads posted on a job board that connects clients and service providers it does not mean that the job board suddenly becomes an employer.
That's an awfully short-sighted comparison.
There are far more job offers for deploying and managing systems with kubernetes and to develop front-ends with React than there are for developing TCP/IP infrastructure. It's fun to earn a living and enjoy the priviledges of having a high salary, and the odds you get that by studying solved problems that nowadays just work are not that high.
That's a good point. Indeed if the project is already rolling with a message bus then it wouldn't make much sense to increase complexity just to use a specific message exchange pattern.
Your definition makes no sense at all. There is no distinction. Architecture specifies which components comprise the system, their interfaces, their responsibilities, and how components are expected to interact with each other. You pick certain tools because they are expected to handle certain responsibilities, because they implement certain interfaces, and because they support or enable certain types of interactions. There is no distinction.
Honest question: if the goal is to implement the request/response pattern then why should anyone adopt AMQP instead of plain REST/RPC-over-HTTP?