iamed2

Sounds like https://github.com/JuliaArrays/AxisArrays.jl/ ;)

Canada Post provides this service. My building has a parcel rack and they just put a numbered key in your mailbox when you have a parcel. No need for codes or phones.

For those who may not know, Canada's national postal service is the largest parcel carrier in Canada.

I can't imagine a language more suited for implementing this than Julia. Custom N-d array types are easy to create and are composable with the rest of the linear algebra ecosystem. Multiple index and index iteration strategies are supported. It's easy to implement optimized code for common operations, falling back to reasonably-efficient generic implementations. There are strong metaprogramming facilities in case custom unrolling behaviour is necessary at compile time.

If someone was interested in exploring an implementation I would strongly suggest giving Julia a try.

I think the downvotes are probably because the article didn't actually talk about Julia that way. And Julia definitely expresses a target audience and target problem domain. As a member of the Julia community, I don't see people jumping on board because of "fanboyism". People come because they have a problem that Julia is suited to solve and they have been disappointed with the alternatives.

This is the exact sort of book I've been looking for for a long time. I work with quite a few physicists and engineers who make extensive use of linear algebra I don't fully understand (my university courses only went up to chapter 6.1's content), so I've been looking for some way to get up to speed.

I wonder whether it would have been more natural if it was written as "quick, brown fox" as would be customary English. Usually when adjectives don't have commas between them it's because the last adjective is coupled to the noun.

This incident was resolved: http://globalnews.ca/news/3309437/skipthedishes-says-sorry-t...

The last paragraph says:

> The bigger task is to redesign power markets to reflect the new need for flexible supply and demand. They should adjust prices more frequently, to reflect the fluctuations of the weather. At times of extreme scarcity, a high fixed price could kick in to prevent blackouts. Markets should reward those willing to use less electricity to balance the grid, just as they reward those who generate more of it. Bills could be structured to be higher or lower depending how strongly a customer wanted guaranteed power all the time—a bit like an insurance policy.

Most electricity in the US is distributed across wholesale electricity markets with nodal pricing, which have all of these mechanisms where distributors/utilities are the customers. The author appears to suggest moving pricing out to end users, which is possible even just on the utilities side, without having to restructure power markets. Restructuring power markets to take into account individual end user behaviour rather than aggregate demand would be a gargantuan effort--right now the California Independent System Operator's (CAISO) optimization process takes into account a few thousand nodal prices, and there are tens of millions of households in California. Having utilities introduce demand response and smart metering to approximate their costs would be a much simpler implementation.

It is possible (after clearing many hurdles) to participate in the electricity markets in order to identify inefficiencies around renewables and incentivize their use by providing better price signals to planning markets, but this is very challenging and most utilities and power trading groups/companies are not interested in that angle. It is, however, one of the things we're doing at Invenia ( https://invenia.ca/).

More specifically, it's designed to support as much as possible of MATLAB's syntax to provide an open-source alternative to MATLAB.

I think that was the aim; I think the composer was trying to illustrate the ship using music. I can see how one might find that confusing, but I enjoyed it.

We use ML to model complex interactions in electrical grids in order to make decisions that improve grid efficiency, which has been (at least in the short term) more effective than using an optimizer and trying to iterate on problem specification to get better results.

Generally speaking, I think if you know your data relationships you don't need ML. If you don't, it can be especially useful.

I think people compare them because they were both designed as alternatives to C++ (or at least with that in mind). What people might miss is that they were solving two very different problems: Rust aims to be as fast (or faster) while guaranteeing memory safety, while Go aims to be easy to understand and get productive as quickly as possible.

There's a big Amazon event (AWS re:Invent) and they are announcing an extraordinary number of new tools. Think an Apple or Google event but one where they announce a new product every 15 minutes. People with many different kinds of jobs are excited for different reasons. It's double-Christmas for people who work extensively with AWS.

"Ordinary people, too, have long been using like as an appendage to indicate similarity with a trace of hesitation. The “slow-like” kind of usage is a continuation of this, and Saul Bellow has thoroughly un- Beatnik characters in his novels of the 1950s use like in a way we would expect a decade or two later. “That’s the right clue and may do me some good. Something very big. Truth, like,” says Tommy Wilhelm in 1956’s Seize the Day,"

My grandfather uses "like" often, but only in this way (he grew up in Depression-era semi-rural Canada). I've always found that interesting since I rarely see that usage mentioned.

Anyone else have older relatives who use "like" this way?

Looks like they were planning to Jepsen test later this year [0]. But it looks like they're preparing to run it themselves [1]?

[0]: https://www.arangodb.com/2016/05/getting-closer-arangodb-3-0...

[1]: https://github.com/arangodb/jepsen/commit/2b79809df73ca6c755...

This was the link I successfully used to install.

What puts MATLAB ahead of Julia, in your opinion?

It's quite nice, and works for user-defined collections as well: https://www.youtube.com/watch?v=4XorFlvQEiI

See davidacoder's post at the top; it does that now, essentially.

Constructing a narrative around the usage of donations has been something scientific/medical charities have struggled with in comparison with foreign aid charities like World Vision. This article is a smart move for them.

So pay him to do a Cassandra re-test

Shashi Gowda presented on APL implemented in Julia at JuliaCon today: https://gist.github.com/shashi/9ad9de91d1aa12f006c4

I think this may fill a void in the "teaching language" space. It doesn't require lots of boilerplate but retains some key teachable moments (type system, pointers, stack vs heap, interfaces, etc.). I think a language with this sort of brevity and breadth of features would do well as a replacement for the Java/Python/C/C++ hodgepodge that currently exists at many universities.

Yes, there are packages that can read and write HDF5 (including specific support for .mat) [0] and NetCDF [1] formats.

[0]: https://github.com/timholy/HDF5.jl [1]: https://github.com/meggart/NetCDF.jl

The fully integrated experience you mention would do a lot for the Julia community in terms of gaining users tied to the GUI elements of MATLAB and VS for other languages. Integrated debugging and inspection in particular is a long-requested feature that has yet to see much attention.

Integrating with Pkg as Julia Studio does would be another important feature, as well as providing some sort of integrated plotting/graphics widget (a backend canvas along with plot navigation and image export, ideally supporting more than one of Julia's plotting backends).

I would certainly contribute to an alpha- or beta-testing effort :)

This seems the only way to satisfy everyone. There are clearly those who strongly prefer some degree of open office space, and some who strongly prefer private space. However, few of the articles I've read give open+optional private offices as an option.

Currently, some at my company use unused meeting rooms as quiet space but generally prefer an open environment, with headphones on or off. A growing number prefer a casual, social environment like couches and tables rather than desks.

A strong influencing factor is the amount of collaborative work. Those who are working alone on projects tend to be solitary, while those who make many collaborative decisions want to be closer to others. This may reduce the need for formal meetings, which allocate blocks of time for a whole group that may not be necessary or efficient.