milesokeefe

What theater lets you bring in outside food/drink? I've never heard of the practice, outside of theaters that let you bring your own growler for them to fill.

Ubiquitous 5g could allow for constant data egress.

Cruel to the insurance company?

Public Utility District, for those wondering.

https://en.wikipedia.org/wiki/Public_utility_district

*her

I know that the sportiness and novelty of a car drives up the insurance price but it doesn't seem to as much as I thought, my friend recently got a new WRX and pays very very little in insurance for it considering he's a 22 year old male.

But yeah it being a beater makes sense, I just got quotes for a 1981 Honda Civic in Seattle and some are even less than $700/year.

You pay $700/year for insurance as a 25 year old?

I wouldn't call his interpretation "first grade". The author has a bit of experience in this domain:

https://en.wikipedia.org/wiki/Brad_Feld

source: https://github.com/tunabrain/gpu-fluid

Shame that the y axis on the first 3 charts isn't labeled. I assume it's milliseconds, kilobites, milliseconds.

Yep, still a major issue. This was run at 0.15 kelvin (-273c/-459.4f) and they'd like to get it colder:

In these experiments, the electron temperature accounts for 10% of the reduction in our visibility, and spin relaxation accounts for the remaining 5-10%. In our experiment we readout the qubits sequentially, reading the left qubit first. Relaxation of the right qubit during the readout of the left qubit is what leads to the asymmetry of the expected visibilities. Relaxation contributions to the readout fidelity can be mitigated by using a faster readout technique such as RF reflectometry or by incorporating a cold amplifier into the readout circuit (9, 10). Further improvements can be made by reducing the electron temperature or using cavity-based measurement approaches (11).

People may be taking your comment as general knee-jerk electron hate but it really is something to consider.

If you're sending requests that can return very long json responses, Insomnia can lock up and force you to restart it.

Paw is a pretty good native alternative but it's macOS only, doesn't have a free tier beyond a short trial period, and has some UI quirks that made me ultimately go back to Insomnia despite the electron borne downsides.

If Insomnia could offload the request response parsing/formatting to a WebAssembly module it would be perfect.

Also every time you add/remove a file or make similar breaking changes.

But he did sign a form 'releasing' the money to them.

It's certainly not acceptable, I just think it hasn't been a priority for Apple since it's a relatively niche usecase.

It could also be a security/privacy decision to leave it broken but safe until they can implement camera access through WebViews securely.

The closest to any official reason I could find is a dev letting us know that mum's the word:

>I asked about this internally and the answer is that, right now, WebRTC is only supported in Safari. No WKWebView, not even SFSafariViewController.

https://forums.developer.apple.com/thread/88052#266901

Have you used an iPhone X? The notch actually makes a lot of sense once you've used the gestures associated with it, same with how it integrates into apps. I'll agree that they've made a lot of mistakes in their product lines recently but the iPhone X was not one of them.

Well, sparing software. I've had intermittent phantom screen input using the latest betas on the X, making it infuriatingly unusable at times.

How many people are using the camera in pinned web apps? What's the app you use? I'd imagine most camera-related functions are already best served by native apps.

Interesting, seems to only trigger when the search term contains the substring 'bugzilla' exactly:

http://advancedsearch2.virginmedia.com/main?FailedURI=bugzil...

Might be worth trying the Groovy plugin that was needed prior to ES integrating it:

https://github.com/elastic/elasticsearch-lang-groovy

Can you not use a separate index for each mapping type and just combine the indexes by aliasing them all to one "virtual" index? I think that would effectively be the same but I may be forgetting something.

Abbyy has had that ability for a longer period of time so it may be more accurate, but this is something tesseract supports[1]. In fact I'd say most OCR systems support it with varying degrees of accuracy.

[1]:https://github.com/tesseract-ocr/tesseract/wiki/FAQ#how-do-i...

Moving isn't an option for many people.

Immediate access to the vehicle and monetary returns from renting it out when not using it.

Not exactly, WebAssembly has no direct DOM access so if you want have your front end run in WebASM you’ll still need JavaScript to make anything work.

Personally I think that’s a good thing, I don’t want front ends to get any more obfuscated than they have gotten.

Those aren’t mutually exclusive, both are good things and deserve appreciation.

What’s the worst case scenario here? I can only imagine the devs just getting some spammy notifications and having to unsubscribe.

I suspected so, I just got a queen mattress from them two days ago, I've really enjoyed it so far.

If Tesla does buy them hopefully that would lead to a turnaround on the B1's safety aspects - for instance there are no airbags.

Mind sharing what the company/bed was?

Clickable:

https://bubble.is/