cls59

I wish gawk had a native strptime function. Always seems like an odd omission given strftime is included.

One of the first things I grep for in dmesg ;)

AWS is a 8,000 pound gorilla. This means throwing massive amounts of promotional credit at new accounts is often the only viable way to get them into the funnel.

Also: https://sourceware.org/bugzilla/show_bug.cgi?id=10354

Here's a good counter example:

https://www.hec.usace.army.mil/software/hec-ras/downloads.as...

Back when I did work on hydraulic modeling, HEC-RAS was the gold standard for open channel flow. It is only available as a pre-compiled Windows executable.

I had a ton of parameterized simulations to run and would have loved to have gotten my hands on the source code in order to run it on EC2 Linux spot instances and to mechanize the parameter inputs by cutting the GUI input forms out.

It is quite a bit more than structural engineering. 17 broad categories (at this date) with several sub-disciplines:

https://ncees.org/engineering/pe/

What if the deployment model of my "small project" is on-prem operation by end users? How do I evaluate the usefulness of Datomic without forcing those users into a license purchase or going through the up-front cost of buying a license that allows redistribution?

Still going to give it a few more months. Might even wait until 10.14 :)

I'm running an older version because I prefer to let other folks grind the rough edges off of the APFS filesystem before taking the plunge myself.

But also, the folks at medium made that assumption long after RFC 2606 had established a "right answer" for which tld to use when testing.

Same in San Jose.

Because Fortran was purpose-built for manipulating array-based data while C++ is a general-purpose programming language. That means Fortran is optimized for this problem domain starting at the _grammar of the language_ while C++ can provide at best access to a locally optimized set of libraries. Those libraries might be quite good, but the comparative experience is still like trying to drive a Phillips-head screw using a flat-head screwdriver.

Landlords are restricted from breaking lease agreements by Tenants Rights laws. There may not be an equivalent set of laws or regulations that restrict airlines from breaking their contract of carriage with a passenger.

That still ignores the existence of a huge usability problem. The investment of time may pay off in the long run, but IRC is large enough investment (and ongoing maintenance, ZNC doesn't just take care of its self forever) that people will take a route of less resistance when presented.

This all reminds of a few years ago when folks were banging on about how we needed to use Gitorious instead of GitHub for Open Source hosting. Gitorious is dead now and it wasn't until GitLab came along and recognized the usability problem that we got a viable Open Source alternative.

I don't think it's a generational thing either. I know how to use IRC and how to connect with it. The problem is the difference in the amount of energy demanded by the set-up process. Connecting to Slack is extremely simple and I don't have to fiddle with the settings in order to get a decent experience.

Compared to IRC, I have to:

  - Figure out how to configure my client.
  - Figure out how to interact with the user account and moderation bots on Freenode or $other_server.
  - Figure out how to set up something like ZNC in order to federate the client on my phone with the client on my laptop so I don't miss messages.
  - ...

It's an epic yak shave that sucks massive amounts of time and energy a from the thing I joined the community to do: improve a piece of software that isn't IRC.

I don't get it either. Given the status of Uber drivers as independent contractors, I'm not convinced it's Uber's place to call an action like a strike. Such a decision should come from the drivers. On the taxi side it sounds like there were unions who clearly have the representation to make this sort of decision.

The Cement CLI framework for python looks similar: http://builtoncement.com/

Also: https://www.destroyallsoftware.com/talks/the-birth-and-death...

How about a re-write of coreutils in Rust?

https://github.com/uutils/coreutils

Could just be the difference between storing arrays in memory using row-major order vs. column-major order. Not sure which ordering JavaScript uses, but R is definitely column-major.

No kidding. If a team of Doctors, Lawyers or Professional Engineers (Civil, Mechanical, etc.) had been involved in a ethics disaster of similar scale, those people would be in danger of loosing the ability to continue practicing at a professional level.

For server-side frameworks. Agent-side development is moving to C++. Plugins for Puppet are still written in Ruby.

How so? The DigitalOcean provider for Vagrant works great: https://github.com/smdahlen/vagrant-digitalocean

The issue with that is that a LaTeX template is turing-complete. Doing a meaningful import of arbitrary journal styles without re-implementing TeX is a very, very, very hard problem.

I can't take 100,000 lines of my own code, link it against 10 lines of GPLed code, and re-distribute the result under a license of my choice. I have to use a variant of the GPL.

This is the viral aspect that your argument does not address.

In most cases you also loose the ability to specify graphic components declaratively through .append() and .attr(). Instead, you must imperatively specify how to produce the drawing from the data by manipulating the canvas context.

I have use d3 to create composite graphics that included elements rendered to canvas and it certainly is powerful. But, I still believe that the sweet spot of the library requires being able to work with the DOM and CSS.

You can target canvas with d3, but you loose much of the abstraction that makes d3 powerful. For example, look at all of the low-level canvas rendering code that is used. Not as powerful as visualizations driven by chaining .data().enter().append().attr() which can easily be re-shaped by swapping html tags and CSS attributes.

d3 really is a three-legged stool of HTML, JS and CSS. When targeting <canvas>, you loose both HTML and CSS and thus much of the power.

EDIT: I should clarify that I'm thinking of HTML in an abstract sense that also includes SVG. By hooking into the DOM, d3 gets a free scenegraph that makes it easy to modify the components of the visualization without writing low-level code.

I think Colin Percival put it best in his blog post about Heartbleed:

"The most secure code in the world is code which is never written; the least secure code is code which is written in order to comply with a requirement on page 70 of a 100-page standard, but never gets tested because nobody enables that option."

These things get used all the time --- especially when statistical, economic or engineering analysis is being performed. Also, most users aren't using these features directly, they're using a template created by someone who did know how to use them. Most of what the end user does is punch in this years data and interpret the output.

For a specific example: unless LibreOffice or Google Sheets develops a solid equivalent to the Solver add-in, replacing Excel will be a non-starter in any department that deals with Engineering data.

Right. But enforcing state in the packaging system is only one facet of what configuration management tools are used for. Building a better package manager won't remove the need for configuration management tools. The problems that gave arise to these tools extend far beyond package management and cannot be reduced to package management as a root cause.