jalons

Licensing.

Recommended alternatives?

Yes, if the python interpreter the poetry environment utilizes is in your $PATH.

Exception handling and (unit|py)test are worth the headaches.

I tend to agree with you that pyenv|pipenv|etc shouldn't be used for actual production usage.

This of course leads to other issues to solve, now that your development environment doesn't actually mirror production.

It was a tongue in cheek joke that conda is complex enough to be it's own OS.

You've also got to include the pyenv shim instantiation. So now you've got something like

0 0 * * * /path/to/bash/script/to/init/pyenv && /my/path/to/poetry run /my/path/to/python.py -arg1

This helps highlights the main issue I have with python today, and that's running python apps.

Having to ship a compiler to a host|container to build python with pyenv, needing all kinds of development headers like libffi for poetry. The hoopla around poetry init (or pipenv's equivalent) to get a deterministic result of the environment and all packages. Or you use requirements files, and don't get deterministic results.

Or you use effectively an entire operating system on top of your OS to use a conda derivative.

And we still haven't executed a lick of python.

Then there's the rigmarole around getting one of these environments to play nice with cron, having to manipulate your PATH so you can manipulate your PATH further to make the call.

It's really gotten me started questioning assumptions on what language "quick wins" should be written in.

No. The only thing ZeroMQ and RabbitMQ have in common are the letters M and Q.

RabbitMQ is a messaging system. ZeroMQ is sockets on steroids.

My experiences line up with yours. It was terrible then, it's not any better now.

> I know this is becoming repetitive, but seriously still no optional touchbar? I mean for gods sake, why?

Because apple pay with the touch bar is more important revenue stream than the vocal minority of users (who I'm a member of) who hate the touchbar.

There's always the BSDs.

Hashicorp Vault hits most (all?) of these points

HFT also still pays top dollar for competent FPGA developers. I'd wager they're willing to pay more than the listed industries too, especially if you factor in profit sharing and bonus structures.

This one is new, so they haven't learned all the corner cases that make VoIP more difficult than anticipated.

Those are also (usually) loss leaders for the super markets. Not that that makes this acceptable, of course.

This doesn't address the issue, as that still leaves the vulnerable git binary on your system. It just takes one call to /usr/bin/git instead of /usr/local/bin/git to fall victim.

Saltstack is moving away from ZeroMQ. https://docs.saltstack.com/en/latest/topics/releases/2015.8....

I've seen those issues as well. I it Duet more as a second display more on my win8.1 laptop, and have very strange 'disconnects' - the iPad screen just randomly goes berserk and technicolor, and I have to quit the app and restart to get it picked up. This usually happens around the same times iTunes tells me there's an update, so guessing it's related.

Which utility are you using to treat it as a second screen? I've had modest luck with duet.

It's shocking the amount of people that don't grasp this. "It works in my home, why isn't it the same in the office." Is it misinformation? Have people become so used to things "just working" in home they don't think of the technical differences between a couple devices and a couple hundred devices?

Tools. Compatibility. Resembles systems already in place (i.e., back when BSD failed to get SMP support "soon" there wasn't an option if your workspace was CPU bound). Numbers (it's popular in HPC/HFT because it's popular).

We're not consuming/using the built in network stacks anyway, we're using the OS as a content delivery system. Get us something we can get to the cores on, we're going to pin our applications directly to those cores keeping the kernel relegated to scheduling tasks on whichever NUMA core is further away from the PCIe bus running into the CPU. We'll have the CPU's we're using pegged in a constant spinlock anyway which would make the scheduler think really, really hard about running tasks there. We don't use realtime kernels as it's better for us to pay the price on the occasional spike outlier than to raise the baseline latency up.

Due to my own unfamiliarity, I don't know what BSD's equivalent to isolcpus is. I don't know how to taskset on a BSD. I don't know if the infinibad/ethernet controller's firmware/bypass software works. I don't know how BSD's scheduler works (not that we usually care, but there are times when one can't avoid work needing to be scheduled, things like rpc calls to shut down an app, ssh if you can spare the clock cycles for key verification, etc).

Would dtrace come in handy? Most definitely. Is that enough for us to abandon what we know works? Not yet.

A safety deposit box with the password to the master database?

Sometimes low tech works.

It's a reference back to John Draper's work on the blue box. You could trick AT&T pay phones into thinking you had deposited money by playing tones which were reproducible on toys that came out of Captain Crunch boxes.

It's arbitrary who owns it, it just has to be owned. On a very superficial level, it's supply and demand. Increase supply without increasing demand causes price to fall.

This appears to be a lot like the Cube. Some thought it was ahead of its time then. Looks to me like Apple is giving it another try.

Your balance is irrelevant - your available credit line is debt, as at any moment you can be liable for up to that amount.

Am I missing something, or did they say they didn't want to scale mongo horizontally via sharding, then comment that they're doing so with riak, but faulting mongodb for requiring it?