Legion

I'm not the person that insulted the plugin, but I had a less than positive reaction to it too. I would say that this is putting into the template what belongs as JavaScript.

In pretty much every case, where the README shows the "before transformation" and "after transformation" comparison, the "after" part is what you should be writing to begin with. This feels like adding an extra layer of abstraction just for the purpose of not learning to do some simple things in JavaScript itself.

I would be pretty annoyed if I started working on an existing React project and it had that sprinkled across all the components.

Sure, but this isn't a story of people who were making a concerted effort to avoid facial recognition, which the title's wording implies for a little bit of sensationalism.

OR, as was my point, the title as written suggests they were actively engaged in efforts to evade facial recognition, which is a completely different story.

> This, people, is exactly what prejudice is.

You're reaching.

More like "stumbled into" than "figured out".

MoltenVK implements the Vulkan API on Metal: https://arstechnica.com/gadgets/2018/02/vulkan-is-coming-to-...

And as stated in that article, work is also being made to implement Vulkan on DirectX, allowing Vulkan apps to be distributed through the Windows Store (which requires DirectX).

Nintendo Switch supports Vulkan. I expect we'll see Vulkan support quite strongly in the next generation of consoles (besides maybe Microsoft's)

I miss this era of the Internet. It represents a period of time where average people used the open Web to publish, rather than post on a corporation's platform.

Obviously there's been plenty of development since then that I would not give back, but people favoring publishing their own sites rather than posting on social media is not incompatible with those developments. That part didn't need to be lost.

I look forward to this being a benchmark for testing CPU advancement in the years to come.

"It gets 2 frames per hour in Branchless DOOM!"

Some of the good material that would have been turned into movies in the past gets turned into television/streaming shows now. Game of Thrones occupies the kind of cultural space that something like Star Wars did during the original trilogy.

It's not that that material doesn't exist, it's simply that it no longer is the sole domain of the movie format.

Logo is great and all, but we're not talking about beginning programming for kids, we're talking about CS degrees.

At some point between Logo and bachelor's degree, you run face-first into that complexity, which is the "wall" the commenter atop this thread was referring to.

> I would say that this basically screams "badly taught programming". Missing semicolon does not take down work, it just needs to be put back in and ide should help you.

The point is that the incidental complexity is there, and that it's something that has to be dealt with, to even begin to get to the fundamental part of the problem.

That you have to be using the right IDE (and learn how to use it, and learn to recognize it's attempts at helping you with the problem) does not refute the point, it's a perfect illustration of it.

CS isn't harder. CS has high incidental complexity, the crap you have to deal with just to be able to work on the problem within a real world environment.

The part I find interesting is the 100% success rate between bottled and tap, which is something bottled water drinkers insist is true (being able to taste the difference, that is), but are often told is just in their heads.

I hope their efforts involve an overhaul of Curse, because Curse's UI is the #1 reason I use Discord.

Atlassian's cloud-hosted JIRA performed so poorly with even an empty account and empty projects that I thought something had to be wrong the two times we tried using it.

I imagine it's a problem you can throw resources at when hosting it yourself, but I could not get over how poor the experience was.

On Wave 3, "justify-content: space-between" appears to position incorrectly on Firefox 44 on OS X: http://i.imgur.com/nx6hROH.png

On Chrome, it positions the turrets on the edges as expected.

EDIT: Looks like evunveot noticed the same in Linux and linked to the Firefox bug.

> The author's proposed method is basically the same as how php's composer does it

Composer merely cloned Ruby's Bundler and its Gemfile/Gemfile.lock in that regard. Which is a good thing. It's beyond puzzling that Python has spawned multiple dependency managers, none of which have replicated the same golden path.

These sorts of projects always want me to fill in a list of repos to "watch". We've got an organization full of repos, with new ones coming on and old ones being archived all the time.

I want to just say "watch this organization", and anything that gets assigned to me in that org, I get notified for. I don't want to have to manage a notifier every time new repos get added or archived.

I can't stand articles with pagination that lack a "single page" view, defeating convenient read-it-later offline saving.

It should also be pointed out that this book was the basis for the show Homicide: Life on the Street, which Simon consulted on and later produced. That's what got Simon into television and eventually writing The Wire. (That said, Simon felt the show did not closely enough reflect the book, which is probably what fed into the creation of The Wire. Still, for a network TV drama, Homicide was pretty outstanding.)

> and about elaborate .vimrc's that take you so far away from 'standard' that you're crippled without them. Stick to a fairly basic standard install and a .vimrc of 50 lines, tops.

I think this is terrible advice. While it is true that one should avoid getting lost down the plugin rabbit hole, for many of us, the whole point of Vim is that it is a configurable, composable editor.

As for being "cripped" without my vimrc, well, moving tiny text files around is pretty much a solved problem at this point. And as a developer, I'd prefer to optimize my 99.9% of the time environment, and not worry about the .1% of the time I'm away from it.

I do, however, recommend that your vimrc is something you should build up over time, understanding what you are putting into it, rather than grabbing some big off-the-shelf framework and using it without understanding what is going on.

At my company, we switched from Sendgrid to Mandrill when we ran into some deliverability problems with Sendgrid that we could not identify a cause for, but which magically disappeared once Mandrill was doing the sending.

> This is an "all your eggs in one basket" issue.

And that's an incredibly valid concern, but at the same time, when you look at the other baskets and they're falling apart and have holes in the bottom, it's easy to see why people put those eggs where they do.

In my opinion, the lockout-shortened 2012-13 NHL season (started in January, 48 game regular season) was the best thing ever.

Particularly in a country where NFL football reigns supreme, the NHL starting an 82 game season in October is just a loser. Starting the compressed season in January, with the NFL regular season over, made so much more sense.

This is absolutely true for real-world coding. However, for the purposes of an exercise, I think the fact that 15 was chosen was not an accident, but is part of the exercise. Does the coder recognize the relationship between the multiples, and recognize the ability to optimize by removing an extraneous comparison?

It's kind of a trivial test for that sort of recognition, but anything as small as FizzBuzz is going to be rather trivial.

Twitter's experience was also on pre-1.9 Ruby, ie. before YARV.

Ruby itself has made major jumps forward in performance since then. Much of Ruby's reputation for slowness was earned on an interpreter that no longer exists. It's still not the fastest dog on the track, but it is a ton better than those earlier days.

This is exactly what shadowbanning is for. You can see what Terry posts by opting in to do so.

Neovim seriously has me so excited that I could scream like a little girl.

On a list of software projects I wish existed, a modernized Vim would be numbers 1 through 10. I enjoy core Vim, but the pain of Vim's limits when adding in new functionality with plugins (like pauses running Syntactic checks, or the hiccups and lack of smoothness of every autocompletion plugin ever) are a downer.

TDD is a means to an end, not an end in itself. I think some TDDers lose sight of that fact.

The end is well-tested code. Developers often lack the discipline to write tests after writing what appears to be working code. The point of TDD is to force that discipline by making it part of the process of writing the code in the first place.

It's a good technique that many use to great effect, but it is just that, a technique, not a goal in itself.

What matters is that, when you're checking in new code and pushing it upstream, that code has tests along with it. Whether you wrote the tests right before the check-in, or as part of a TDD cycle, is immaterial to everyone else.

EDIT: By browsing to the Github repo, I found the link to the One Big HTML page: http://www.greghendershott.com/fear-of-macros/all.html

Original post: I wish there was a single-page version of this that I could Pocket. Or an epub that I could put on my reading devices.

I don't tend to read multi-page things like this at my desk, not in this era of high-resolution lightweight portable screens.

I don't have words for how obnoxious the little flying "Quote" box that appears when highlighting text is.