What Are You Working On? May 2015 - Developers

[QUOTE=sarge997;47775255][B]Oh man I'm lovin this..[/B] [I] Sound warning.[/I] [vid]http://a.pomf.se/cttvze.mp4[/vid][/QUOTE] Very nice. That's also giving me some major gmod winter survival vibes.

[QUOTE=Xystus234;47775941]So I finished a month and 1/2 long overhaul of the AI at my job today. I ended up rewriting the AI from a simple system that used range and small algorithms to determine what to use when attacking, to creating an AI system that utilized a state-machine tree combined with a little invention of mine where when entering combat or deciding an idle state, the AI builds a list of states that it could engage in, each with a labeled weight system of values that are modified based on the capacity and the environment that the NPC is in. In other words, I wrote an AI that [I]literally weighs out[/I] situations depending of certain things. For example, if an AI has a ranged attack, it will weigh out to more likely cast a spell then attack melee. If it's health is low, it has more of a chance of retreating. I even got it so that NPC's mock the player when they run away from the fight. I can't post what project I'm working on or how long till it's out, because I'm still under an NDA, and we're still technically in pre-alpha. But once I do, I'll definitely post screenshots.[/QUOTE] Are you Harold Finch :v:

[QUOTE=sarge997;47775255][B]Oh man I'm lovin this..[/B] [I] Sound warning.[/I] [vid]http://a.pomf.se/cttvze.mp4[vid][/QUOTE] What's the technique you use to keep the mist particles from obviously clipping with the world? It's very good looking.

[QUOTE=nomad1;47777609]Are you Harold Finch :v:[/QUOTE] Oh please, he must be Nathan Ingram. Harold would have posted screenshots.

Size DOES Matter won best Nordic Handheld Game at Nordic Game Awards. Among the Sleep won Best Artistic Achievement. I'm happy to be a member of both. [IMG]http://i.imgur.com/zdbng4I.png[/IMG] [I]Me and my bro thanking satan, the norse gods and the people behind jägermeister[/I]

What do you mean there weren't tarmac roads in medieval times? [t]http://i.imgur.com/NelZE1B.png[/t]

[QUOTE=_RJ_;47776779]Very nice. That's also giving me some major gmod winter survival vibes.[/QUOTE] Ohhhh damn man... You nailed it.. Didn't think anyone would guess what I'm going for so quick. Bravo.

I'm currently working on a save system using Protobuf and I just realized that if I release the .proto files, people can very easily make save editors and what not. That's pretty cool.

[QUOTE=andrewmcwatters;47774851]if someone could just make relational dbs as easy to use as document stores then you'd really have something big on your hands a mongo killer[/QUOTE] There is a mongokiller. It's Couchbase. It's not as easy to use, but its the same shit. Except mongo performance goes down the shitter when requested data sample is bigger than operative memory. Guess COuchbase is more for enterprize so it doesn't get as much PR. I only found out about it because I had to do research about it at worj.

Article about the innards of Mongo and the HN comments [url]https://news.ycombinator.com/item?id=9417773[/url]

I decided to give SFML a try. Building and linking it statically took way longer than it should have (do not link against the x64 libraries while creating a x86 application!), but in the end I managed to make it work. So far I've created a simple application with tiles being drawn and having a world matrix which I use to navigate through the scene with. [vid]http://www.broxzier.com/files/ShareX/2015-05-22_15-18-57.mp4[/vid] I'm quite surprised by how easy SFML is to use.

[QUOTE=andrewmcwatters;47774851]if someone could just make relational dbs as easy to use as document stores then you'd really have something big on your hands a mongo killer[/QUOTE] it already exists and it's called postgresql. you can even use it like a document store through the json data type and functions.

[QUOTE=SteveUK;47778865]it already exists and it's called postgresql. you can even use it like a document store through the json data type and functions.[/QUOTE] PostgreSQL is great but it's not as easy to use as something like MongoDB. I haven't used it before but [url=https://github.com/torodb/torodb]ToroDB[/url] could be the answer to that, it's a document store built on PostgreSQL that's compatible with MongoDB's client protocol.

[QUOTE=Rohans;47779128]PostgreSQL is great but it's not as easy to use as something like MongoDB. I haven't used it before but [url=https://github.com/torodb/torodb]ToroDB[/url] could be the answer to that, it's a document store built on PostgreSQL that's compatible with MongoDB's client protocol.[/QUOTE] Are Node hipsters really so afraid of SQL they'll have something sit in the middle?

[QUOTE=SteveUK;47778865]it already exists and it's called postgresql. you can even use it like a document store through the json data type and functions.[/QUOTE] postgresql on its own is equivalent to mysql in usage imo. i don't see how that's revolutionary. i don't know of any libs in any language ecosystem that competes with mongodb's js api or mongojs for instance in terms of usability. don't get me wrong, i love mysql, but as far as i and many other people are concerned, postgresql isn't much of a difference in comparison.

How did I even? [T]http://i.imgur.com/sMIj2FF.jpg[/T]

[QUOTE=SteveUK;47779242]Are Node hipsters really so afraid of SQL they'll have something sit in the middle?[/QUOTE] you seem to be of the crowd that dismisses schemaless design for some sort of database purity mindset, likened to people who care about normal forms in databases with less than a million records a lot of people don't care about that [code]db.users.insert({ username: 'andrewmcwatters', games: [ 'Vertex Adventure', 'The Spooky Cave' ] }, callback); [/code] This is a relational insert, for people who care. Is that important? Yes, it actually is for medium to large sized projects. You could even argue it for small projects. But I guarantee you can't show me something as easy to use in the relational world, because you have to set up schemas to begin with, which is more work. Even if you could make it painless, it's not going to be as quick as doing lazy document CRUD work. [editline]22nd May 2015[/editline] This is why MongoDB is popular for the wrong reasons. [editline]22nd May 2015[/editline] It's not about being a "hipster", it's about doing less work. Is there a technical debt you will end up paying? Sure. Is there a technical debt people incur using jQuery, hell yes there is, but jQuery doesn't have 34k+ stars on GitHub because it's the most performant, correct piece of software to use for the DOM.

[QUOTE=Rocket;47775109]More like [url=https://github.com/cpancake/ROHONGODB.git]ROHONGODB[/url].[/QUOTE] [url=https://olegdb.org/]OlegDB[/url] is what all the cool kids use these days.

[QUOTE=andrewmcwatters;47779514]postgresql on its own is equivalent to mysql in usage imo. i don't see how that's revolutionary. i don't know of any libs in any language ecosystem that competes with mongodb's js api or mongojs for instance in terms of usability. don't get me wrong, i love mysql, but as far as i and many other people are concerned, postgresql isn't much of a difference in comparison.[/QUOTE] Not really, Postgres runs circles around MySQL. PostgreSQL [b]on its own[/b] can store JSON blobs which can be queried out of the box, with this you get the best of both worlds. But whatever, Mongo has an easy to use library for Node so that makes everything else invalid right.

[I]Yes. It does.[/I] Why go as far as to underestimate ecosystems? It actually does invalidate it. Because you have feature X or Y doesn't mean you immediately have both benefits. I can't suddenly write equivalent code and have it be relational. I want to use SQL and still be able to do something as simple as what I posted above. You don't get both. You get one or the other, that's the nature of the tech. Just because I can do doc stores in Postgres doesn't mean I also magically get relational benefits out of it, it just means you've taught an old dog a new trick. It's not inherently new technology. Postgres attempting to be more than a relational database but not actually provide any of its benefits makes it worse than just outright using MongoDB or any other document database with a client that is easy to use. If I have to write more code, it's already lost.

my data may never be written to disk but at least the code to insert records is nice.

I think it's kind of silly to prefer the shitshow that is mongodb because it's "easier to write to" i used mongodb for one project and oh my god what a mistake that was

i think it's kind of silly that people are saying one is better than the other. just use what's easier and more useful for what you're doing. no need to take sides.

[QUOTE=Quark:;47780120]i think it's kind of silly that people are saying one is better than the other. just use what's easier and more useful for what you're doing. no need to take sides.[/QUOTE] The attitude of "nothing is better than anything else" annoys me though. Using that logic, [b]some people[/b] might still be storing passwords in text files on an FTP server!

[QUOTE=SteveUK;47779993]my data may never be written to disk but at least the code to insert records is nice.[/QUOTE] lol, [url=http://docs.mongodb.org/manual/reference/write-concern/#j-option]changing write concern is one line of code[/url] writing schemas takes up more than that. i'm not advocating that relational dbs are bad, they're what should be used in a majority of cases, but you can't argue ease of use, it's futile. [QUOTE=geel9;47780001]I think it's kind of silly to prefer the shitshow that is mongodb because it's "easier to write to" i used mongodb for one project and oh my god what a mistake that was[/QUOTE] guess you didn't rtm, what a mistake that was

i'm not saying that nothing is better than anything else, that's obviously not true. i'm saying that it's silly to say one is better than the other overall for everyone which is sort of the undertone that seems to be implied behind those kinds of posts. trying to influence what people use is kind of silly. let em choose for themselves.

So many logical fallacies in this thread it's not even funny. You know what'd be great? If people thought "Hey, can this exact argument be used in favor of something I disagree with?". Because if the answer is yes, then you should probably refrain from posting it.

[QUOTE=andrewmcwatters;47780177]lol, [url=http://docs.mongodb.org/manual/reference/write-concern/#j-option]changing write concern is one line of code[/url] writing schemas takes up more than that. i'm not advocating that relational dbs are bad, they're what should be used in a majority of cases, but you can't argue ease of use, it's futile. [/QUOTE] You shouldn't have to change a basic configuration option that, left unchecked, fucks shit up. [QUOTE=andrewmcwatters;47780177] guess you didn't rtm, what a mistake that was[/QUOTE] this is a stupid thing to say.

how is that stupid, you literally did not read the docs when do you ever use a db and not first figure out if it's ACID compliant, what it's write behavior is, etc?? [editline]22nd May 2015[/editline] could you imagine working in an enterprise environment and someone proposes a database change for a small project, but they literally could not tell you if it supported transactions or not and they were a dba? you'd be a joke [editline]22nd May 2015[/editline] i'm playing devil's advocate here keep in mind i don't think it's right to use doc stores for relational data, but you can't make a compelling argument for using relational databases over document stores if someone is lazy already, and to use relational dbs because of [I]reliability[/I] that can be set with [I]one line of code[/I]

[QUOTE=andrewmcwatters;47780273]how is that stupid, you literally did not read the docs when do you ever use a db and not first figure out if it's ACID compliant, what it's write behavior is, etc?? [editline]22nd May 2015[/editline] could you imagine working in an enterprise environment and someone proposes a database change for a small project, but they literally could not tell you if it supported transactions or not and they were a dba? you'd be a joke [editline]22nd May 2015[/editline] i'm playing devil's advocate here keep in mind i don't think it's right to use doc stores for relational data, but you can't make a compelling argument for using relational databases over document stores if someone is lazy already, and to use relational dbs because of [I]reliability[/I] that can be set with [I]one line of code[/I][/QUOTE] what of the trash that was this post has anything to do with my situation?