The success of Apple (etc.) are due to choices that developers have made, closing themselves in and then citing anti-trust when they themselves locked the doors and gave away the keys.
218 karma · joined February 10, 2016
The success of Apple (etc.) are due to choices that developers have made, closing themselves in and then citing anti-trust when they themselves locked the doors and gave away the keys.
[0] https://abcnews.go.com/Blotter/toyota-pay-12b-hiding-deadly-...
Clean link to a different playlist with just the lectures: https://www.youtube.com/playlist?list=PLLfhkR8m8wYsgLEqr__PI...
Another thing to consider is that there are so many great alternatives to RH that were online, despite encountering similar load. If the whole stock trading network went down that would be a different conversation, but users of other platforms were able to trade, and thus RH not being able to provide the infrastructure to handle the load is a huge disservice to its customers.
Using game engines may not suffice to your use case, but for a lot of people that's the best way to develop games. This argument is similar to using a systems level language vs a higher level language.
I myself prefer game frameworks over either raw graphics APIs and game engines, since it provides me with my preferred level of control while meeting my particular needs. I can see where you come from, if your goal is to learn and highlight that in your resume, writing and experimenting against the graphics APIs are likely the best bet. But for a lot of people, their main goal differs from yours, which is to... make a game.
Direct messaging and protected tweets are a different story though, but your statement is objectively wrong.
> I mainly brought up Google Docs because it's something that many of us use that breaks us from "living in the terminal". Someone who "lives in the terminal" would want all of Google Doc's functionality, but in a terminal.
People who live in the terminal does not literally mean that they spend 100% of their time on the terminal fyi. I doubt anyone does in this day and age, I was under the impression that that fact was implied.
Not all software is suited for the terminal, that should be obvious. Like you would not want to play a graphically intensive game on the terminal because... graphics.
Since you brought it up, what use-case do you have with piping Google docs exactly?
Now to contrast this with GUIs, even the simplest things would require me to jump through menus, type some stuff, etc. Everything in the command line is precise and repetitive steps are easy to replicate.
Piping is another aspect that the command line enables, which basically feeds to output of one command into another. One common example of this is to look at lines of a log file that contain a certain set of words: `cat log.txt | grep "[ERROR]"`.
But perhaps the strongest selling point of working in the command line is consistency among tools. If you want to be productive as a developer, use of various tools for doing various tasks is common. Using the CLI for all these tools keep everything a few commands away, even interoperability is enabled seamlessly due to piping and consistency.
So yes, there is a fairly steep learning curve, but in my opinion learning how to use CLI tools over GUI is well-worth the hassle.
While I agree with the gist of the article, this is worth pointing out since a lot of people do use Chromium because it is advertised this way, thinking that somehow they are not playing into the Chrome/Google monopoly. For those interested, there is an alternative build without all the google stuff baked in: https://github.com/Eloston/ungoogled-chromium
> * Way too easy to quit the whole browser with Ctrl+Q (Chrome uses Ctrl+Shift+Q)
Saying that it's nitpicky to include this in your list would be huge understatement, it's straight out ridiculous. I have always found Firefox to be more responsive and less resource heavy than Chrome, so I don't know why you had problems with that.
But yes, you are right when you imply that Firefox seems to have prioritization problems, lots of them imo. However, it is understandable to me, making the UI looking prettier is for marketing, not usability. Most of these things you listed are not addressing a lot of users, on the other hand, having a flashier UI would address and (potentially) attract more users. But their management still needs to improve, and as a company, they should have better direction.
I guess you are just one of those people who fail to acknowledge it unless it's your own home slowly getting submerged under water.