brianshaler

How long until we can co-locate application services in geosynchronous orbit to cut that latency in half?

Even though I'm someone who doesn't reach for TS by choice (have had to use it for a couple of projects) I would add that even in a small or simple app, if you ever work with abstractions or wrapped values, you'll quickly feel the benefits of having types.

> password entered encrypts and stores that on disc, then each time it wants to talk to us it can decrypt its password.

Is there a reason you don't want to use tokens? Upon authenticating once (admin, manually), the web service would generate a token, which it would store and potentially have to revoke.

With something like OAuth, the token could be more temporary and automatically replaced during each use, to avoid having one secret (whether it be a password or token) that could be leaked and used by multiple clients.

None of my credit cards do at the moment. I've had 1 or 2 in the past but the issuer replaced them with non-contactless cards (I think Chase Slate even claimed removing contactless was for security reasons)

If I see the contactless payment logo I'll usually reach for my phone instead of my credit card because chip readers are agonizingly slow.

Android users: did you know you can add shortcuts to specific cards to your home screen? Pretty neat even though I tend to use my default card for the vast majority of POS purchases.

I'm pretty sure websocket is fifo with delivery guarantees and as far as I'm aware cannot be used in the same manner as UDP. I haven't played around with WebRTC, but that might be an option.

This seems noteworthy:

> Any scenario still requires the user to install the malicious update from a source outside the Google Play store.

Even with paved access and a substantial budget, I'm not sure building permits would be feasible for any future construction. I don't know that they've been singled out by local officials so much as the original designs weren't forward compatible with modern (1980's+) building requirements.

They've done a commendable job of trying to keep up with some modern advancements since the original designs were inked in the 60's. They have fiber optic internet access, some solar panels, and a few ADA-compliant ramps. My concerns would be more about integrity of the foundations. Modern surveying, concrete chemistry, and so on have raised the bar. I think there may have also been problems with routing utility lines with ventilation shafts and not having much of an alternative due to the structures being solid, load-bearing concrete.

As an organization, I don't have very much faith in the leadership doing much more than barely staying afloat. There's a strong bias for seniority over meritocracy, which over the long term frustrates and deflects talented people with good ideas and favors people who just stick around or have don't have better alternatives.

"liberated from the need to work" is an interesting way to say "unemployment"

The kind of world we have created is one where one must create value in order to have food & shelter. Automation simply funnels more and more of the value created into the pockets of fewer and fewer individuals.

The planes on the taxiway have white takeoff/landing lights. It sounds like the second in the queue didn't turn theirs on until just before the incident, but if any of the others had theirs on prior, it could contribute to misidentifying the taxiway. I think it's common to have the lights on while taxiing and turning them off at rest.

Or http://zom.bo if you want infinite possibilities but have a finite amount of time to type.

I'm with you, but it's not necessarily new. HN has always been a blend of STEM and money/hustle.

Not (always) vice versa. In Ho Chi Minh, where Grab operates, I was not able to book using Lyft and had to install/setup Grab.

Below the paid options:

  Free Plan
  For quick demos and other simple tunneling needs.
  * HTTP/TCP tunnels on random URLs/ports
  * 1 online ngrok process
  * 4 tunnels per ngrok process
  * 40 connections / minute

The photo and caption about the spectacular paintings in North Korea remind me of how much I regret going into the country without a good amount of cash. On the tour, we visited several galleries and artist studios stocked full of large and exquisite paintings—most not propaganda—at what I remember being very reasonable prices.

Obviously, they were unable to accept Visa, MasterCard, or American Express.

Yes, because they're pending changes. When they're finished, they can be committed and the branch can be rebased to include them.

You could also test the waters with a `2to3` branch.

If you have uncommitted changes, instead of dropping them in as "last before..." you can git-stash them before branching and git-stash-pop them when you come back.

> questioning whether U.S. consumers will be willing to pay much higher prices for equipment of equal quality

There's also the threat of substantially increased tariffs that could make a panel manufactured by a <$3/hour worker cost as much or more than a panel manufactured by a >$10/hour American worker.

I read the guide and came here looking to see if there was a docker image. I just don't want to blindly pipe-sh on my host machine (would need to review what rustup is doing first). On top of that, 'wait 2 hours' is not something I want to do when I want to kick the tires on a Hello World.

This is a great example of docker-for-dev. Don't bother setting up the specific versions of compilers and then worry about clean-up afterward.

The guide should be 2 lines: docker pull, then docker run.

It seems that is the goal and intent: to increase both the supply and demand of batteries, infrastructure will improve, commoditization will increase, and prices will be driven down.

While it may be a profitable business in itself, Tesla does not seem to be targeting battery sales as its primary revenue source of the future. Instead, their stated and apparent goal is to sell many more electric vehicles once the cost of production reaches an inflection point where an electric drivetrain is cheaper to produce than an internal combustion one.

I upgraded from a $3200 rMBP (mid-2012) to a $1700 XPS13 i7 (9343/2015). The speed and battery life of the XPS13 have seemed on-par with the rMBP to me.

If I was underwhelmed about anything, it was the rMBP feeling slightly slower than the bottom-of-the-line MBP I got in 2010 with upgraded RAM & SSD.

Granted, the hampered rMBP performance was probably mostly due to that specific model being underpowered for the new retina display.

It's surprising how much of a disruption this caused to their launch schedule, but it's great that they got to the bottom of the issue before repeating the process on any further rockets.

The worst kind of bug is the intermittent one that you can't reproduce or see in logs. With only 35-55 milliseconds of metrics leading up to the event and nearly obliterated evidence, it seemed nearly impossible they would be able to nail down the exact cause.

Critics have pointed out risks in SpaceX's method of loading supercooled fuel. Accidentally forming solid oxygen around carbon fibers from a buckling overwrap is an example of this.

There are benefits, but they will need to find and prevent all these possible edge cases exposed by the new method.

If you think about how we often say the time within an hour as "15 past X" and "15 til X," doing the same with days in the month doesn't seem as exotic.

I haven't really dug into open source speech recognition, so I can't speak much to that side of things, except observing that advancements favor deep learning and cloud-based services over efficient on-device detection (aside from very specific "hey siri"/"okay google"/"hey alexa" recognizers). When it's not a library that can be included, but a service that must be maintained, it'll be that much hard for free and open solutions to get adoption.

For face detection & recognition, some of the greatest advancements are getting acqui-hired and locked away (e.g. Facebook acquiring Face.com) there is still progress being made with tools like OpenCV & Dlib. I just worry progress in the open-source space will lag behind and continue to be difficult to work with, as the delta grows between proprietary capabilities and open-source options.

Anyone setting out to do something like this will quickly see how much of a hassle it is to exfiltrate data from relevant services and your own devices. APIs and SDKs cover a lot of use-cases, and that is all great and commendable, but we don't truly own our own devices, data, or the algorithms that make them useful. I think this will continue to hamper our ability to have a truly useful 3rd party (your home in this case) orchestrate your digital life.

A worry about reading about Zuckerberg digging into this area is that anything Facebook does will likely be within their walled garden. There is certainly a glimmer of hope they'll make something on the "open" side, but I wouldn't get my hopes up.

I wonder to what extent having great advances in this area by proprietary cloud services will hamper the advancement and adoption of libre alternatives.

If the Supercharger stations are on private property, it seems like Tesla could legally activate self-driving "Summon" functionality to move fully-charged Teslas to nearby parking spaces. The only real challenge would be safely unplugging the cable without damage to the car, which is relatively trivial compared to the self-driving technology they've already built.

The key difference is the telephony company needs to know who I want to talk to so they can connect me, which web sites I want to load so they can retrieve the data from the server, and where I am so phone calls and data are routed through a nearby tower. People aren't going to be as upset about a company having data that is necessary for their core service to be provided. Does Uber need to know where I sleep in order to catch a ride from my office to a bar for happy hour?

In a way, it's an end of an era. What jQuery did for the industry when it first came out was amazing. Normalizing differing browser APIs, making cumbersome APIs more palatable, providing powerfully expressive query selectors, enabling fairly trivial plugin development, and the nifty monadic chaining.

Some of those issues have been addressed by browsers, making vanilla JS a little less unreasonable. For other bits, rails-ujs provides some niceties that aren't worth carrying all of jQuery to have. These days most developers will want to use le framework du jour, and don't need jQuery for DOM querying and manipulation.

This is an argument that the TouchBar should not be considered a deterrent for vim users since they shouldn't reach up to that row in the first place.

Also, this seems to be a generic complaint about the TouchBar as a feature of MacBooks Pro, which has been discussed at great length in threads about the feature, and not relevant to this post, which is about adding TouchBar support to React Native apps.

When I was on Mac and in the earliest versions of atom, I suffered through the slow startup time and keystroke lag for the ease of customization (JS/coffee, JSON/CSON; vs custom DSL, C, Python or whatever). Altogether, I'm not very opinionated about text editors, so the pros and cons were pretty negligible. Upon switching to Linux, the performance were gone. I don't know if it was because I'd been using too old of a version on Mac or if OS X just has a latency penalty for using web views.