I don’t have a physics background but I’ve always seen “c” as the speed of causality. The light happens to go at that speed in the absence of gravitational disturbances. Gravity and others fields should also move at this maximum speed.
That said, I’m still trying to come to terms with the fact that breaking this speed limit just means that causality would be potentially broken. Isn’t that just something we axiomatically believed based on experience and we just haven’t observed otherwise?
Looks like the intention of the author was to play with that word game in order to get an appealing title, but even for people familiar with the topic it can have the "not logical" meaning first.
+1 to this! Moreover, if you are invested into the Apple ecosystem, seamlessly integrates with iOS and comes with a WatchOS app, so you can see your 2FAs in the Watch. A huge convenience when doing TOTP from the phone.
I don’t disagree with you but I want to point out that it’s interesting how better software, running on an OS, running on a chip architecture, has enabled us to write better OSs and better chip which in turn allows us to write better software that allows us to repeat the cycle.
Aren’t we somehow simulating how life works? Higher abstractions/constructs improve the way the lower constructs work :). Of course, just an oversimplification.
Not an economics expert at all, but what happens if profit per unit is still more significant? Maybe Apple is targeting something like:
Total Profit = Volume * Profit Per Unit
So even though Volume is smaller because units are more expensive, the increased markup increases the total profit and that's the reason why they are getting ~90% of the profits in the industry. This idea makes more sense to me considering guidance for the next quarter won't include volumes.
Is there any reasoning behind only targeting volume that I am unaware of? Genuine question.
Good job on creating a lightweight client. Apollo can be overkill for smaller projects.
You should be careful with the name though because it's named the same as the official reference implementation of the backend: https://github.com/graphql/graphql-js.
I completely agree! I worked with Rails 2+ years and it was really comfortable that everything I needed was at hand at the moment of scaling the application with new features or requirements.
After that, I needed to make some microservices orchestration and NodeJS (using Koa as the HTTP server wrapper) was a better tool to deal with all these asynchronous tasks.
But: Routing? Parsing JSON? Storing files in S3? Dealing with databases? Serve some static assets (e.g. Swagger)? Up to you! And good luck finding the up-to-date and standard library for your needs.
Overall, using workers, doing asynchronous tasks (e.g. starting a thread after hitting an endpoint) and coding orchestration endpoints (e.g. GraphQL) was a enjoyable experience where you have almost full control of what you were doing, but I still miss those days working with Rails where the community was so helpful in finding a friendly path to dealing with some common problems. My impression is that it feels less fragmented overall.
I haven't found myself an ORM as good and expressive as ActiveRecord or Sequel. Overall I think it has to do with all the metaprogramming tools you have available on Ruby. That's something amazing to deal with cookie-cutter problems, but also a problem when you need to do more granular control or get out of the typical CRUD problems.
I'm not completely sure because I'm not familiar with the topic, but maybe it has to do with the fact that even when they sue you with an impossible-to-win lawsuit, they can destroy you with the cash you need to expend to even start defending yourself.
This can also destroy investment rounds for many startups.
I used to think that way, but then you realize that JSX ends up behaving only as syntactic sugar for `React.createElement`.
If you have that clear, JSX is only syntax for the pure JavaScript you end up writing. Diving in the toolchain and ecosystem also helps you note that. Adding Webpack loaders to the mix, and then your application ends up only consisting of JavaScript files, where you abbreviate `React.createElement` with the old HTML tags.