For anyone who is working, people are "giving" them $5 all the time. But they probably don't have people buying them coffee/beer/lunch all the time.
1,562 karma · joined November 23, 2016
For anyone who is working, people are "giving" them $5 all the time. But they probably don't have people buying them coffee/beer/lunch all the time.
A bakery is obviously going to have an interest in politics directly related to operating a bakery and the employment laws affecting it. A bakery might reasonably avoid political stances on something unrelated, such as nuclear power, foreign conflicts, etc.
It's rather analogous to physical products that are shipped with the instructions in 8+ languages or Tesla selling cars with their batteries limited in software.
It's both IMO. The whole market is in a giant bubble due to various fiscal policies and decisions, but the big tech companies have substantive/reasonably solid businesses within the bubble.
An iPhone is clearly a different case. Measuring what options users have is not limited by a geographic region but by what policies and app stores govern the device.
If iPhone had no App store and only had official Apple apps we wouldn't be having this conversation, regardless of how popular iPhones are.
I think Apple is in the wrong, but a critical issue what threshold or criteria must be met for them to be required to offer an open(ish) platform?
*open(ish) meaning allowing alternative app stores or charging industry standard payment processing fees.
I think there's a reasonable argument that users buy iPhones with the expectation of a market in the app store (I can get or buy apps from any company that cares to develop one), so when Apple charges a 30% fee (far above normal payment processing fees) on every transaction made through the app they are abusing a monopoly position.
The App store comission is like Apple charging you 30% anytime you sell one of those goods to someone who lives in an Apple branded house. (To complete the analogy, maybe you're a door to door salesman and Apple charges you a "sidewalk usage fee" or something)
One (Unreal Engine) is a licensing agreement for a tool with no upfront cost; the other is a tax on any sale made to an end user.
Hard to see MS/Github maintaining a browser after Microsoft just adopted Chromium for Edge, but it would be cool to see Firefox given the VS Code treatment. Github had Atom which is where Electron came from, then VS Code is an evolution on top of Electron. Would be nice if Edge was built on Firefox instead of Chromium.
What would "Foxium" offer that Brave, Vivaldi, Edge, Chromium, or Chrome don't already offer?
I don't think your speculation is unfounded though.
But I also agree, browsers and web apps aren't exactly lightweight either. Maybe WASM adoption can help on this front?
Granted the parent was anecdotal with their own experiences too, you could at least address the points. E.g. to the point of achieving 100-200Mb daemons, you might reference what RAM footprint you typically expect/experience from a similar program running in JDK 14-16. Rather than just:
> You'd be wrong, because JDK 14 will most likely give you substantially better performance than Go
If a battery or metals (or self-driving) engineer comes up with a material break through and starts a company they could easily eclipse Levandowski's earnings.
Making views async won't do much to make an individual request faster (besides keeping it from being blocked by other slower requests).
One difference for Elixir/Erlang (which GP mentioned) is that the BEAM VM can interrupt any function by default. (There's a few exceptions when you deal with native code and other things)
I don't mind soft-locked features too much since it can be cheaper for the manufacturer to just install it on everything than to build two separate models; plus it can be nice as a consumer to still have those additional features available if you change your mind later.
I also doubt they would make the same complaint if JetBrains or someone else wrote the same proprietary extension for VS Code.
Neither the first case nor the second would make any of those editors any less open source.
The stronger or less guessable a password is, the more likely it is to be written down or recorded somewhere where it could be compromised.
Or are you arguing purely in the sense of SMS and Email based 2FA?
Consider also that sometimes complexity/engineering really is warranted; either by the domain or by the tooling.
In other words, avoiding complexity-domain mismatch isn't just a "these days" problem, it's a constant consideration in software development.