briandilley

What a great BF4 map.

Wow, I never knew that.

Here's a link to the video: https://www.youtube.com/watch?v=MT4Ig2uqjTc

Thanks, i'll check it out.

I like this version of the same question - it's like a mini commitment.

> Like Pinot, Elasticsearch is a JVM-based database, and as such, does not support joins and its query execution runs at a higher memory cost.

What does the JVM have to do with joins?

woah, I haven't seen slashdot in a minute.

painful

I don't even need to read the article to know that a more accurate title would be: 'Undress or fail: Instagrams user patterns strong-arms users into showing skin' or the classic 'Sex Sells'

I wonder how Linus feels about tabs vs. spaces (I didn't read the entire post, so maybe he addressed it?)

with food and water, how else?

I want a voice controlled bidet. Can it clean _more_ than your asshole though? IE: 'Alexa, stimul... wash my beaver.'

why?

Angular

... but why?

I can't tell if this is a good thing, or a bad thing.

that guy was the most annoying interview i have seen in a while.

What about WindowMaker?

does the name... BUG you?

It's a nod at resiliency, clever IMO.

> I find it difficult to setup PostgreSQL without having a single point of failure and introducing downtime for things such as upgrades.

Amazon does this with RDS, and so can you.

This really isn't very tough to achieve with replicas. And for upgrades you just add a new replica with the latest version and promote it to master and replace the remaining nodes one at a time.

- hire into your weaknesses - hire people smarter than you

What about team based offices? Where a team of ~4 or ~5 people share an office?

Apparently search isn't an exact science yet ;)

I thought it was common knowledge that the ancestry part of the 23andMe "project" was croud sourced and not an exact science? The "you are related to XYZ person in our database" stuff was 100% accurate, as that is coded in your genetics. But their ancestry data is based on who is related to who and what they think their ancestry is.

Biome. We no longer say ecosystem, we say "Biome".

unfortunately - this is probably correct. don't fall victim to the sunk cost fallacy, as this is the most expensive way (time) to do so.

I do.

> As the project matures, GUI code and back end code diverges.

This. This is why ASP.NET, ServerFaces, JSP+Taglibs, etc. became a nightmare.

RPC - this isn't anything new.

When I started doing web development in the late 90s for about ~5 years I was the designer, front-end, and backend developer all in one. Then over time things changed to allow for specializations and we now have many different functions, and that's a good thing. RPC has a place, and it's not for web apps, at least most of the time.

I've noticed over the years that JavaScript developers tend to try and put their JavaScript everywhere and I often wonder if it's because they don't want to learn other technologies. Don't get me wrong, I like a little bit of JS too - I even added JavaScript support to an old 2D Game engine using SpiderMonkey (before V8 was a thing) back in the day so that I could make desktop games with JavaScript. I just don't want to do _everything_ with JavaScript. Especially with so many interesting languages and technologies to play with these days.

Are JavaScript developers today the PHP guys of the past?

This is the DAO pattern, welcome to 1999 Ruby.

https://www.baeldung.com/java-dao-pattern

this looks terrible