HNHacker News
TopNewBestAskShowJobs

kingdomcome50

297 karma · joined December 11, 2015

submissionscomments
kingdomcome50··on Things I learned while developing a billing system
What about just mapping it? That is, simply choose the smallest increment necessary for your system and _enumerate_ every value within a window as your source of truth. There is less than a million hours in 100 years. Is this system going to be around in a hundred years? Probably not.

It might make some of the math/algorithms a bit painful but I think you could guarantee correctness with the above approach.

kingdomcome50··on Tesla's “full self driving” beta is potentially dangerous
I see this sentiment often. But is this comparison fair? For example, what does the distribution of risk look like in each cohort (AI vs human drivers)?

Presumably the risk of an accident is relatively evenly distributed between all AI drivers (they are using the same AI after all). But is the risk of a car accident evenly distributed between all people? Not even close. It’s perfectly possible to simultaneously reduce the overall risk for everyone while at the same time increasing the risk for a given individual by an order of magnitude.

Would you be willing to assume a greater risk of accidental death _personally_ to decrease overall risk of death? Not a question I imagine reaches broad consensus...

And what about the soft problems? Like responsibility. A self-driving car runs off the road and kills your daughter. Now what? Tesla is certainly not going to accept responsibility. So... you just “chalk it up” as bad luck? At least the current paradigm has the _ability_ to offer closure after a tragedy.

Reducing “self-driving cars” to a single metric is not only mathematically dubious, it’s ethically abhorrent and just plain stupid. I expect better.

kingdomcome50··on Monolith First (2015)
The problem with creating a dichotomy between "monolith" and "microservices" is that... well... it doesn't make any sense. You describe your "microservices" and I'll explain how it's really just a monolith.

"So let me get this straight, you have a Billing package and an Ordering package. How are these organized again?"

-> "We have a distributed system."

"So you you compile them together and deploy them horizontally across many machines? Like a distributed monolith?"

-> "No we use microservices. The two packages are compiled and deployed separately so there is no code dependencies between them."

"Okay. So if I understand this right, you develop each package separately but they both access the same database?"

-> "No no no no! Microservices are not just about code dependency management, they are also about data ownership. Each package is developed and deployed separately and also manages it own database."

"Ah, so you have two monoliths?"

-> "..."

You see the problem is that the above terms are too broad to describe anything meaningful about a system. And usually "monolith" is used to described the dependencies between code whereas "microservices" is used to describe dependencies about data. It turns out there is a lot of overlap.

Design and implement your systems according to your use-case and stop worrying about how to label them.

kingdomcome50··on I followed my dreams to get demoted to software developer
> When you make a decision as a manager or a director, the impact of that decision has a multiplicative force.

The above resonates as an exercise in tautology to me. If the job of a manager is defined as a position in which a person's decisions will have a multiplicative force... well... then of course their decisions will have a multiplicative force! Though I'm not sure the above is even remotely true for the vast majority of management-type positions, save those at the highest-level. And even if it is... then it of course a fact that the value derived from an individual in such a position is therefore not related to the "multiplicative force", rather, the decisions themselves.

I'd wager most managers come from two camps (the first two below):

1. Those that are ex individual contributors who have accumulated enough seniority and experience to best-understand not "what to build", but rather, "how to build it best". And are therefore given the authority, responsibility, and pay-check to do so.

2. And those who are not really managers at all, and whose job would be more accurately named "coordinators". This seems to be the role you are hitting on at end. You know, the guy who asks the engineers "how can I unblock you today?" and whose explicit role is to have the authority to act on the answer. Notably, not synthesizing the answer in the first place.

3. The third camp is of course the ones to which you seem to be alluding in your comment. The high-level, c-suite, "director of strategy"-type roles. And you are exactly right about them. Clearly the person deciding which widget needs to be built is in a position of tremendous responsibility when the value they can add (and remove) is extremely consequential (assuming the resources required to do so are equally consequential). There aren't many roles like this in a company.

It's the second group of "managers", I think, that the OP is confused about. They don't actually make that many decisions, and the ones that they do make are rarely different from the one their most competent reports wouldn't also make. Sure these "managers" sit in meetings and talk about the larger context of the code, the product vision, etc., but only insofar as that its useful to have someone who can distill and relay this information back to the engineers building the product. Because as an engineer it is, of course, nearly impossible to build a truly great product if you don't understand its larger context. It is this group of managers where the tautology is glaring. It is their job to carry-out the work necessary to multiply force. The work isn't all that creative, doesn't require much judgment, and rarely requires much expertise. The value isn't in multiplying force, it's in just showing up...

To clarify, I'm not suggesting managers don't have value, and certainly don't believe there doesn't exist a spectrum between those in the position. Some people multiply force more than others. They know to ask "how can I unblock you today?". They know that Jim doesn't like to be bothered before 11AM. That Susan is more productive if she has a tight feedback loop. Or that Ron isn't as good as Pam at test coverage. They know how to find and exploit people strengths while also minimizing their weaknesses. This is valuable.

Even so I'd wager most of the time a manager's pay is calibrated such that they make more than those whom they manage regardless of the value these people (the people being managed) contribute and without any sort of rigorous appraisal of how much value they bring or how much force they multiply. How could you? The skills illustrated above can't easily be captured in a pay band...

kingdomcome50··on ‘Smallest reptile on earth’ discovered in Madagascar
Here's to hoping its some kind of newt. It would basically name itself!
kingdomcome50··on What Is React: A Visual Introduction for Beginners
You should have included the very next sentence in my quote.

There is a difference between using React and "SPA-izing" everything in sight. React is a library. It doesn't mandate an SPA as its use-case, and, frankly, I've had great success sprinkling React[0] into single pages that need that extra sparkle. Once you move beyond filtering a list or showing/hiding things, the pros quickly start to outweigh the cons.

Could some of those pages be made a bit more efficient or have a smaller download? Probably. But nobody notices and I am able to iterate on them quickly because they follow the same general structure as the bigger applications I've built.

To be clear, I'm not suggesting everyone use React for simple pages but criticizing the tool is a non-sequitur. You are kind of making my point above that all of this "modern JS is ruining the internet" criticism is being levied towards the wrong thing. Like you said, blame the bootcamps for churning out developers that know nothing else about how to develop a web page. Then blame industry for not training them the basics of their craft.

[0] Or preact (https://preactjs.com/). Which is way smaller (3kb)! At this size, it's crazy to use anything else. How big is jQuery again? 20 times that size?

kingdomcome50··on What Is React: A Visual Introduction for Beginners
I agree that the cargo cult is real and abuse of the "SPA" paradigm has never been higher! But that is orthogonal to the tool.

React does make front-end web dev not suck. It may not always be the right tool for end-users, but as a developer? C'mon. It's never been so ergonomic (and plain simple) to build a complex UI.

I googled stimulusjs[0] and you know what? From a development perspective it looks like it sucks compared to React. I'd rather just write vanilla JS than that hot garbage. Is the bundle smaller? Didn't bother to look, probably. Is it faster? Didn't bother to look, hopefully.

I get it! "Our job is to deliver value to the customer blah blah...". Engineering has costs as well. From training to velocity to, yeah I'll say it, developer happiness, you can't just ignore these costs. Working in a shitty, homegrown codebase using these niche libraries is a recipe for turnover.

On the other hand, if you are just whipping a some simple pages here and there that probably don't need to be looked at ever again... go for it! Your future self will cringe a little bit when you open up the source to change something simple years down the line (I know I have!), but at least those interactions are fleeting.

[0] I apologize for my crassness if you are somehow involved in the project.

kingdomcome50··on What Is React: A Visual Introduction for Beginners
I'm curious about this. I have been using the same webpack.config.js file (save modifying paths) for nearly 3 years. I kid you not, yesterday, I finally decided to upgrade to the latest version of webpack because I am about to embark on a new project[0] for the next 6-8 months. It took me roughly 20 minutes to modify the file according to the latest configuration conventions and have everything up and running exactly the same. I find it unfathomable that maintaining a short config file is "too hard".

I decided to try my hand at using CRA for the first (and last) time to build a small app at work because it had recently hit the scene, and appeared to be fast-becoming the idiomatic way of engaging with the library and ecosystem. I don't even remember why at this point anymore, but I had some issue that required me (as in the docs at the time said so) to eject the app. My jaw literally dropped after I saw what the project had become. It was... thousands of LoC. And spread across so many files!

Clearly we have different definitions of "too hard", but, to me, the task of understanding all of that was "too hard". I am simply not wired in a way such that I can use a tool without understanding how it works (obviously within reason). I have to imagine that when you say you "didn't want to maintain a webpack configuration" that you mustn't really understand what that entails, and are using the output from an ejected CRA as a proxy for what that configuration must look like. I assure you, it's rather simple. I've spent 20 minutes in the last 3 years doing so.

[0] I would estimate the kinds of apps that I build are far more complex than the vast majority of use-cases (think fantasy sports draft/league management software).

kingdomcome50··on What Is React: A Visual Introduction for Beginners
I see this sentiment often, that React is too complex, and I just don't understand that criticism. Is there some bloat? I'm sure. But the problems that React solves aren't trivial either.

The signature of a React application (and each component thereof) is simply `f(state) => HTML`. That isn't hard to understand, and the complexity behind the scenes is the complexity necessary to distill and optimize an application to the above. And to your point about JSX, yes, I do want that. I find it silly to write HTML using some other DSL. I have yet to find one that is anywhere near as transparent or ergonomic. How could there be?

I suppose I can agree profiling for the cause of undesired cycles could be easier, but, frankly, I rarely need to do so because I can simply reason about why a function/component is being invoked. The "flow" of a React application is well-defined (and rather simple). To your last point about structuring your code, you are probably right. Things have come quite far since jQuery in many respects, and I am sure that, if I were to try my had at it again, I would find it to be much more sane than 5-6 years ago. I just don't see why anyone would subject themselves to that though...

Kudos on your project! It looks great, and I'm sure provides the faculties important to you and your platform. I would be careful though. Given enough time and energy you may find, in the end, you have simply reinvented React!

kingdomcome50··on What Is React: A Visual Introduction for Beginners
Sorry, the impetus of my comment above was that CRA is introducing FAR MORE configuration/dependency/complexity than maintaining a webpack.config.js file!

The build process of a modern React application has a certain amount of necessary complexity. Hiding it behind a "low-effort" build tool like CRA doesn't change the above and, frankly, is really a disservice to anyone who wants to understand the tools they are working with.

Go ahead, eject a CRA sometime. See how "low-effort" it really is...

kingdomcome50··on What Is React: A Visual Introduction for Beginners
I'm rather convinced at this point that all of these people chanting "Can we just go back to traditional approaches!" have never built a web app of reasonable complexity, never used something like React, or have some sort of combination of FOMO and/or comfort in their long-held approach.

I don't have experience with all of these technologies but have been using React since its inception, and let me tell you, there is no amount of (reasonable) money that would make me want to go back to the times when jQuery the big new thing. It was awful! Procedurally manipulating the DOM! I mean, c'mon guys. Talk about a mess... Where are all of the FP evangelists when you need them?

And I know someone out there is bound to downvote me and respond with something like, "B b b but that one site where it downloaded 300kB of JS for a landing page! It's such a bad user experience!". Sure. That's precisely what I'm talking about /s.

The reality is that libraries like React are so popular because they make front-end web development not suck. You can actually reason about the behavior of your UI without first committing to memory a whole of bunch of procedural, ad-hoc `let el = document.getElementById('i-hate-myself')` nonsense.

I get it. It makes web pages a bit slower, and sometimes (maybe more often than that) get abused. That isn't fun for anyone. But level the critique at the idiots downloading a MB of JS to power a single dropdown, not the tool managing that dropdown's state.

kingdomcome50··on What Is React: A Visual Introduction for Beginners
Have you ever ejected a CRA? Your problems are just beginning once you've opened that can of worms. I used CRA exactly up until the point when I ejected it the first time. Never again. The sheer amount of code behind CRA is... remarkable.

Now I have a package/webpack/tsconfig files that I just re-use (and update as needed) between projects. I've never encountered a problem I couldn't solve. Sure now I need to manage the configuration of each project, but, I kid you not, my webpack.config.js file is 100 LoC total. This includes everything most projects probably need: Dev server setup and proxying, JS minification, JS bundling/code splitting, and SCSS/CSS transformation and purging.

I'm sure other projects have other needs, but it's really not that hard to understand these technologies.

And don't give me this "But all of that code is there to help you!" lecture. I've been deploying reasonably complex React apps since its inception, and have yet to encounter the kinds of edge cases to which the above sentiment is likely referring. Hey, maybe I'm just lucky...

kingdomcome50··on What Is React: A Visual Introduction for Beginners
Have you ever ejected a CRA? If you think your problems are about to be solved after doing the above... I have a bridge to sell you.
kingdomcome50··on F# is gaining independence from .NET
Does this solve the problem though? I'll be honest, I'm not very familiar with Haskell (and frankly only casually use FP in general), but I don't see how the pattern in your link alleviates my concern.

The problem (truly the problem) is about _where_ one defines behavior. It's the expression problem (EP) at its core. A FP approach separates data and behavior in a way that makes adding new behaviors to the same data types easy and OOP combines them in a way to make adding new data types to the same behaviors easy. It's literally the difference between:

    let model' = update model msg
and:

    let model' = model.update msg
Like I said, I don't know Haskell very well (and had a hard time grokking the link), but any purely functional language will suffer from the former over the latter. The side of the EP a language falls on is simply as a matter of the data types/type system available.
kingdomcome50··on F# is gaining independence from .NET
> In order to write that you have to pin a reference to the state

Forgive my ignorance, but why is that the case? Isn't `state` being passed into the loop?

Mutability is orthogonal to the question of where one defines a unit of behavior. Maybe an immutable object is not possible to achieve in F#, but one could certainly imagine the concept of an immutable type with methods. My question is more about the modes of organization: Large unions vs discrete modules and how they affect how one's ability to change a program over time.

If you say that the architecture was chosen out of a purest sense of FP, then fair enough. I can understand why someone would go that route. Just had to know.

kingdomcome50··on F# is gaining independence from .NET
I understand what you are saying. I'm not sure how your points are at odds with the OOP counterpart I describe though. The essence of your response seems to be "because we want to use a pure FP paradigm" to which _I_ would add "despite a clear downside to which F# has the capacity to avoid".

If the framework only expects every `Model` to contain 2 methods (`view`, `update`) and never any more (which is the case), I see no reason at all to adopt the Elm architecture. The interface for `update/view/model` is well-defined and un-changing. It's clearly sitting on the wrong side of the expression problem.

The program loop could work exactly the same no? Just re-organize:

    let (model',cmd') = program.update msg state
to:

    let (model', cmd') = state.update msg // I'm not sure where/how program fits in
My question is truly as simple as trying to figure out the advantage of the chosen semantics (in F# - I don't know Elm). It can't possibly just be "because we want to stay on the Functional programming realm" can it? Immutability can be achieved in any paradigm. Forgive me if I am coming off overly controversial - I don't mean to be.

https://guide.elm-lang.org/webapps/structure.html - Even here in the "MVC" section the documentation _recommends_ you organize your project according to type (containing the `view` and `update` functions). This is very-much akin to my critique. If you reach the point in your project above you have essentially regressed back to OOP (in FP clothes).

kingdomcome50··on F# is gaining independence from .NET
Okay. I don't want to go too far off topic here but the OP is about F# so I'm certain many enthusiasts will be here, and I have been waiting for this moment to get an answer to a very specific question regarding Elmish:

What is the point of the Elm architecture?

I cannot figure out why the `model`, `view`, `update` architecture is preferable to its OOP counterpart. That is, simply defining an interface for each of the above where `IView` and `IUpdate` each contain a single method with the appropriate parameters. That is objectively[0] cleaner!

The current recommendation is to create these ungodly unions for handling the view/update logic. It feels ridiculous and really starts to gum up your modules with implementation logic that is _entirely_ unrelated.

FP and OOP each provide different (opposite) faculties when dealing with the expression problem. FP says[1], "I want to optimize for adding new _behavior_ to the same pieces of data" (one can add functions that operate on the same data without needing to recompile). OOP says[2], "I want to optimize for adding new _data_ with the same kinds of behavior" (one can add classes encapsulating different data that have the same operations without needing to recompile). How does the above square with an architecture built around a set of _single_ functions that operate on different (changing) pieces of data?

The Elm architecture seems to have chosen the exact wrong paradigm (and its associated semantics) for optimizing change! You aren't adding behavior as you build out your application in this architecture. You are adding _data_! The "behavior" is defined exactly one time (in the signatures of the `view` and `update` functions) and doesn't change. I must be missing something... is this really just so we can say "the complier will let us know if we forgot to handle a case"? That seems like a pretty hefty trade-off if you ask me. F# has this beautiful multi-paradigm capability and, in this case, it's been woefully ignored.

[0] Okay fine maybe not objectively, but it certainly seems preferable to modularize this logic.

[1][2] I get it. They don't actually say anything, but the general approach to the EP remains true for most cases.

kingdomcome50··on Why I still Lisp
> I have never had a static type checker (regardless of how sophisticated it is) help me prevent anything more than an obvious error (which should be caught in testing anyway).

"I have never worked in a non-trivial system that changed over time."

FTFY

kingdomcome50··on Parler drops offline after Amazon pulls support
You are connecting unrelated dots. While it could be argued that the "cloud provider" space is an oligopoly (though I would not argue that), simply deciding to not serve a specific business, even as group, is not an antitrust issue. No business has a "right to service".

Antitrust is more concerned with anti-competitive behaviors: pricing-fixing, group boycotts[0], buying a competitor with the express purpose of removing competition, etc. Amazon and Parler are not in the same market - they are not competing for anything. Antitrust is not going to be a fruitful legal avenue.

If Amazon were somehow influencing Parler's ability to "do it themselves" (e.g. preventing a seller from providing them with boxes), then yes, there may be some legal standing.

[0] Look this one up. It's not what you are thinking.

kingdomcome50··on Parler drops offline after Amazon pulls support
So it's not possible. So what? What is your point? We are back to square one. What conclusion are you trying to draw from the fact you can't set up 500 servers in 24 hours?

Are you trying to say it's unfair? I just don't see it that way. If Amazon violated the terms of their agreement then fine, let it be litigated. But if Parler can't get back up quick enough in the mean time that's on them. That's how business works. I know. I conduct it. It's not personal.

kingdomcome50··on India’s “plantain man” has traveled widely to collect unusual banana varieties
I wouldn't be so hasty to call a lack of variety a result of efficiency. Sure that may be one factor, but it isn't trivial to ship such perishables like fruits and vegetables half way around the globe in a way that consumers are willing to pay for quality that shows up. There are some products that just can't be transported in a way that maintains the level of quality a consumer would be willing to pay for.
kingdomcome50··on Parler drops offline after Amazon pulls support
Sure. Does AWS owe them the amount of time it should take to reorganize? Why? It's business. I just don't get your point.

I certainly wouldn't choose to continue serving a client if I thought doing so was costing me money.

kingdomcome50··on Parler drops offline after Amazon pulls support
No. I can't figure out how that is relevant though.

Or let me put it like this: What is the appropriate number of machines and amount of time? And why?

If you want to draw a line, support it please!

kingdomcome50··on Parler drops offline after Amazon pulls support
What am I supposed to say?

Amazon doesn't really come off as the "good guy" by admitting they have weighed the current political climate against their profits. Especially given whose about to be in charge. They made a business decision and wrapped up in some good 'ol PR spin/legalese. It happens all the time. About everything. It's still their right to refuse service.

kingdomcome50··on Parler drops offline after Amazon pulls support
> If you don't like it, build your own competitor

That is fundamental axiom of free-market capitalism. How do you think it is supposed to work? I'm trying to imagine a system where competition doesn't exist... oh wait. It's called "Communism".

> People shouldn't be able to put you out of business because they have more power and don't like you.

You must be young. "I have a bridge to sell you". In 15 years you'll better-understand how the world works and your idealism now will feel rather foolish in retrospect. I'll leave it at that.

> some of which are monopolists

I think this is actually what you are meaning to argue against. Just poorly. There is nothing wrong with a company deciding that the profit they derive from selling me widgets eclipses the losses they realize elsewhere, and to therefore end the relationship. This literally happens constantly. I could give you an example last month where we had to end a relationship with a client because they are a competitor to a bigger (more profitable) client who didn't like us serving both. It happens. I promise.

What it seems like you are actually railing against is anti-competitive behavior which is protected against in antitrust law. Monopolies are not against the law so long as they don't engage in certain market-making behaviors[0]. That is, behaviors that make "building your own competitor" impossible (i.e. undermining the fundamental axiom of FMC). This isn't a case of anti-competitive behavior. This is the market deciding that the financial/political cost of associating their business with an entity is greater than the profits they gain. It's business. Parler, in this moment, simply doesn't have a sustainable business model. The best thing they could do is to turn the narrative, lean in, and applaud AWS for exercising its freedom. But they are young too...

And for what it's worth I wasn't "poking holes" in your analogy. I was tearing it down entirely. It doesn't hold at all - even a little bit. To believe otherwise is to misunderstand the very foundations on which the civil rights movement was based, and some respects, liberal democracy altogether.

[0] Amazon is currently in court fighting the government in this respect. So is Facebook.

kingdomcome50··on Parler drops offline after Amazon pulls support
I can't say for sure, but I think the point is to highlight some hypocrisy of the "free speech" argument.

That is, if you claim censoring ISIS speech is okay but not Parler speech, then you must also be claiming that there is a line somewhere between the two that is being crossed. You are therefore acknowledging a limit to free speech. But that isn't the point yet.

The point is that you (not necessary you) are drawing a line at all. It's that there is a line. And if there exists a limit to free speech, it means someone has to decide where that limit is placed. We are almost to the point.

And if someone gets to decide where the limit to free speech is placed, who gets to make that decision and why? Clearly you have put that line between ISIS and Parler according to your own belief system (or maybe not, you haven't explicitly denoted anything). But the point is that there exists a reason to limit free speech. I promise the point is coming.

If there exists reasons to limit free speech then we have a problem. You see, you and I may agree ISIS should be de-platformed, but other people may believe other things and therefore have other reasons. The point is that there is no such thing as "free speech". That everyone has their reasons. And that the people shouting "free speech" often mean "free speech within the thresholds that I am comfortable". That nobody actually, truly, deep-down believes in "free speech".

The point is that "free speech" is a myth.

So quit wasting your time calling out Amazon for infringing on something that doesn't exist (again, not necessarily you).

kingdomcome50··on Parler drops offline after Amazon pulls support
A religion is similar to politics only in that they are both beliefs. Your argument is essentially that any belief could/should be protected. I don't think you mean that, so I urge you to try to come up with a more coherent formulation.

I would start by exploring the differences between what it means to hold a religious belief vs a political one. Maybe start by comparing how each of the above has changed, or the associations thereof with their respective ideals over, say, the last 1000 years. Maybe then proceed to identify from where a religious belief manifests vs a political belief. Finally, you could look towards the kinds of answers of which each respective belief offers explanatory power (i.e. What kinds of questions does religion answer vs politics?). We could probably even take this a step further and look at the history of each as well no? Political leanings have existed at least as long as religious beliefs. At one time these were likely the same! So what is it about the history of politics and religion that has lead us to the the kinds of separation we have reached today?

I have confidence you can come up with many kinds of differences. Good luck!

kingdomcome50··on U.S. Capitol Locked Down Amid Escalating Protests
Humanity has yet to find a greater way to seek objective truth than the scientific method.

This discussion started as an exploration of the claim that [all] religion is based on misinformation. And I can see, upon reading that word, how someone could interpret "misinformation" to connote a negativity towards religion. I personally do not see it that way, rather, as an accurate and objective description of the phenomenon. This is because believing in religion requires faith, and to "have faith" means [look at discussion above].

In other words religion is a paradigm based on information that cannot be proved true (not just that it hasn't been proved true). I would classify the above as misinformation -- information that cannot be believed (i.e. rationalized). Choosing to believe anyway is each individual's prerogative, but I don't think it changes how we should talk about it.

I don't mean this as a critique to living a life of faith. Though I personally cannot "have faith" (I cannot believe a person walked on water), it doesn't mean I don't believe in God or the values that many religions profess. It just means that "God" means something different to me. It probably means something different to everyone. As you say, "It's personal".

kingdomcome50··on Parler drops offline after Amazon pulls support
Sure we can move the goalposts. No, we did not mine for our own minerals. What is your point? If our company was unable to secure hardware it would have ceased to exist. A shame for the company, its employees, and clients, but that's business.

> The analogy is: if she didn't like being denied because of her race, she should have started her own busline.

Right. The above is not summarizing the reason why our society has a problem with the events that occurred. The problem is why Rose Parks was denied service. It has nothing to do with her ability to start her own bus line. Does that make sense? Again, the analogy is completely missing the point.

> So tell me what law Parler broke?

I have no idea nor the inclination to investigate. They don't need to break a law for another business to cut ties. This happens all. the. time. Your problem seems to be a case of "this instance is different than the rest". If you have a problem with antitrust behavior, argue that. You aren't going anywhere with this line of logic.

kingdomcome50··on Parler drops offline after Amazon pulls support
I've seen this sentiment before, and I can't figure out the logic.

I used to work for a company that didn't make 300K a quarter and we managed our own boxes. Yes our scale and problem domain was about an order of magnitude smaller, but it wasn't trivially small (optimization was still a relevant problem for us). What did people do 15 years ago before all of these could platforms did all the work for you? Do that. It's really not that hard!

The analogy above is ridiculous. The problem isn't that Rosa Parks couldn't start her own bus line (though at the time this was probably not feasible for more reasons than just money). The problem is that she was denied service because of her race. You cannot change your race by "doing it yourself".

If SpaceX denies me the opportunity to fly their shuttle do I have to build my own spacecraft to get to space? Yes... I do. I'm sure we could come up with all sorts of other fun examples!

← PreviousPage 3 of 8Next →