andmarios

Is there really a need for 24 hour doctor visits most of the time?

No. Doctors can have mostly normal 8-hour workdays, 5 times per week. Nurses administer drugs and monitor the patients. If a problem arise, they can call the doctor in charge of the patient or bring the doctor doing the night —or weekend— shift.

Not necessarily. After calibration your monitor displays as accurately as it can sRGB (or any other profile you calibrated for). It still may miss or shift parts of sRGB though.

Thus your software has to know what your display is capable of. It can use this information to show you which parts of the photograph you edit are not shown accurately.

Very sad to see so many negative comments. It seems a good product. As the owner of an emlid navio2 rasp pi hut I have to say that I am impressed with their work. Top hardware quality and great documentation. In the first hour of use, I used their C libraries and Python examples to manage to access some of the module's sensors via go. I hadn't even ever do C bindings with go before that.

This board seems to target people who want to create products with it. I wouldn't place a rasp pi in an end product and certainly wouldn't come near an orange pi even for a prototype.

There aren't any mathematical tricks, rather how the real world (generator) translates to math.

The generator at the power company has 3 stators that are on equal distance between each other on a circle. As the rotor rotates, it induces AC voltage at each of them.

Because the rotor rotates at a stable speed, the AC voltage follows a sine function.

Because the stators are placed 2/3pi apart, their sine waves have a phase difference of 2/3pi.

Because 2/3pi+2/3pi+2/3pi=2pi, if you add them all together then you get 0 (sin[2pi]=0) and this is your neutral wire.

Quite honestly I learned that very late in the university which is a pity. Once you see how the real world translates to math, many things (like euler's formula which is of utmost importance for engineers) fall in place.

Imho the main race will be against the car's DRM.

This is certainly true, the difficult part is to find a middle point between vigilance and sufficient progress rate.

Sometimes though, you can work in parallel. A consumer-grade CPU may for example be used in a airtight setup when increased security is needed.

There are more questions that arise from this. For example if Intel were more vigilant and this lead to a 10x reduction in technological progress (CPU power has increased exponentially), how many lives would have been affected or even lost because cutting edge research that relies on super computers would happen 40 years from now?

If by making CPUs more secure, self-driving moves 30 years into the future, how many lives will this affect?

There is an old joke, about Bill Gates saying that if the automotive industry could move as fast as the computer industry, we would had $100 cars that do 1000 miles to the gallon and the GM chief answering that whilst these cars would exist, they would crash twice a day.

Good thing with Hurricane Electric's service is that they also provide slave DNS capability.

So you can run your own DNS master server and rely on HE for availability when your server is down or even give preference to the slave DNS, so your users can get the results quick.

QDirStat —it's original code, by the same author— is actually part of KDE. Just open Konqueror, visit a directory and select View -> View Mode -> File Size View.

We already use high voltage for power transmission. Step up transformers at the power plant bring the voltage up to 230kV for transmission and step down transformers within the city bring the voltage down to normal.

My guess for the frequency, is that it is a harder conversion to perform with acceptable loss. Compatibility reasons doesn't allow for just bumping it up. Also let's not forget that AC frequency actually comes from the revolutions per second the power generator does, so there may be some other physical limiting factors here.

Last, some underground high power transmission lines are actually emerged into oil, to keep them cool.

Modern sales are driven by marketing: making you feel good about yourself by purchasing a certain good.

If your brand is actively associated with a controversial practice, then your sales will fall. There will be people that won't want to be seen carrying an iPhone.

It would seem to me that having activists occupy your stores doesn't work very well toward maximizing your profits.

Just tested. Ssh has indeed better performance, at around 870Mbit/sec.

But the gap in my -anecdotal- testing is much smaller than OP's and maybe predictable due to the differences (as OP described) on how OpenVPN and ssh work.

There should be some catch in the setup. Maybe the CPUs he used are old and don't support hardware AES acceleration?

I just run iperf3 over OpenVPN / UDP with AES-256-GCM between two servers in the same DC (but different rooms, through their public network, 1gE links) and got an average of 750MBits/sec. I don't have any special setting.

Using go's websocket library would also be viable.

For the receiving end, go can use http handlers for websockets. So when a message from any websocket is received the handler will be spawn and process it (just as any http request). Preferably dispatch it to a big central channel.

Keeping separate channels for each websocket seems overkill to me. Go has maps. Create a map with all the websocket connections and maybe smaller maps for each chat room, then set n workers to listen to the central channel and dispatch messages directly to each room member.

There is Amazfit Pace on the low spectrum of price and Garmin on the higher end. All with transflective screens and battery that varies from 4 to 10 days, depending if you want to receive notifications on your watch (and how many, Slack for example is pretty heavy due to the number of notifications).

I own a Pace and I am pretty happy with it. Not a complete smartwatch but has all the important features for me: always on screen, stylish, acceptable battery, activity tracking and notifications.

The LG V30 teardown is pretty impressive too. I watched it first, a couple weeks ago, so the iPhoneX teardown didn't do much for me. If I had watched them in a different order, maybe I'd find the iPhone one more impressive.

Though most impressive ever for me was a Panasonic cassette player (walkman style) in the 90's. The thing was barely larger than a cassette itself. My young mind was blown out.

Integration tests are very important and in many cases mandatory. I'd argue though unit tests with good coverage are more important. The latter helps you make sure your application has the correct output. Nothing worst than having a piece of software you think is working and silently introducing errors. The former (integration tests) makes sure your application starts and probably works in some scenarios.

With docker and containers, integration testing is easier than ever.

I've written a very simple integration testing tool (a quick hack to be honest) that executes commands, checks their exit code, the output through regexp, etc and produces a nice html report.

https://github.com/landoop/coyote

Originally written for testing some configuration tools and scripts, we quickly found a use for it for our Kafka connector collection (Stream Reactor). Our connector integration tests are at github as well:

https://github.com/Landoop/kafka-connectors-tests

Obviously unit tests make sure that the connectors work as expected. Integration tests catch simpler errors that can be showstoppers. For example an internally renamed configuration option that didn't trickle down to the configuration parser, class shadowing issues between the connectors, unexpected errors in logs that the developers should check out etc. As the tests are written by people who don't do development, they also expose problems in the documentation. In some cases they provide us an easy way to quickly run locally a connector and catch some issues manually, like extensive CPU usage or way too much logging (e.g a function with a log statement was inside a loop that run hundreds or thousands of times per second).

It gives us confidence in what we ship with every release.

If the data are stored in a Russian VPS, you ask the Russian authorities to get them for you.

Asking Google to get them, is akin to asking a hacker hack foreign servers. Would you like the reverse? A Russian company delivering data from US based servers just because a Russian court asked for them?

Thanks, although I personally will keep it. When I was maintaining web servers as a living I used to add a custom header here and there, so I see no harm in the practice.

Not being able to use the release binaries (even from github) for commercial purposes is a bummer but if this is the price to pay for having caddy available as open source, then it is fair.

What I am afraid of, is that this friction to start with caddy (because $50 per month is way too much for most use cases) will affect its user base and as a consequence the participation in development. Of course mholt and the team behind caddy are the people who love it the most and care about its future the most, so I trust they will keep pushing forward.

For people who find it difficult to build caddy from source, here is an example, provided you have Go installed and configured:

  go get github.com/mholt/caddy
  go get github.com/caddyserver/builds
  
  cd "$GOPATH/src/github.com/mholt/caddy/caddy"

  # Enable cors, prometheus plugins.
  cat <<EOF>caddymain/plugins.go
  package caddymain
  
  import (
          _ "github.com/captncraig/cors/caddy"
          _ "github.com/miekg/caddy-prometheus"       
  )
  EOF
  
  go get -u -v -f ... || echo "Updated dependencies"
  go run build.go

Edit: updated with the latest build procedure

Totally agree. The author seems to write about a specific subset of side projects: SaaS with a possibility to commercialize.

At Landoop we submitted our proposal to present our KSQL at the Kafka summit but we were rejected. Ah, if we only knew... :)

The watch is build to function at the desired latitude of the buyer. These aren't mass produced models, so it's feasible. Especially considering the price tag. :)

If you have to access the terminal frequently, a dropdown terminal emulator is the way to go. Press F12, the terminal comes down. Press F11 it goes to full screen. Press F12 again, it retracts. I use yakuake and can't imagine life without it.

Or, maybe, he just want the people living on the other side of his bedroom wall to be some stable neighbors and not seeing someone new every three days.

As a side point about Termux, Android 7 finally stopped hijacking the control+space combination, so you can use emacs efficiently.

Termux is really useful, giving you an almost complete linux environment in Android phones and tablets. You can install it via Google Play, no need for root or any modification to your device. Add an external keyboard and you can work on the go.

Ah, as usual, why solve something with education when you can solve it via forcing anyone who wants to watch porn to give their credit card details to a shady xxx website.

It is common for people who write UIs and APIs to call themselves software engineers, but real engineering is what AUDI and other automakers do for a living.

Demonstrating a “god-awful” UI as evidence that they can't do autonomous driving is silly imo. We talk about people who design cars that can safely travel at 150+ kph. The tiniest bug or design failure can kill their clients in a spectacular way. We trust these guys with our lives.

Autonomous driving isn't about the UI, it is about math, systems, modeling, safety valves, rigorous testing. This is engineering and isn't taught in CS but in ECE classes. It is easier for an engineer to learn git than for a developer to learn differential equations. Airplanes, cars etc are controlled by microprocessors for the couple last decades. Sure, writing a polished website in angular is cool but engineers write the software that runs pacemakers. How can they not understand reliability?

Charging is optional but supported.

Random video of A8 wireless charging: https://www.youtube.com/watch?v=ME8nFtbTH44