EPTI don't know how it was before but visual studio 2013 community edition is appearantly free
The Big Programming Thread - Page 547
| Forum Index > General Forum |
Thread Rules 1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution. 2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20) 3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible. 4. Use [code] tags to format code blocks. | ||
|
Isualin
Germany1903 Posts
I don't know how it was before but visual studio 2013 community edition is appearantly free | ||
|
WindWolf
Sweden11767 Posts
Even more good stuff from Microsoft regarding Visual Studio. Really liking what MS has been doing recently | ||
|
Manit0u
Poland17843 Posts
Does this mean that the mono project will go down in flames though? | ||
|
ZenithM
France15952 Posts
| ||
|
bangsholt
Denmark138 Posts
On November 13 2014 17:45 Manit0u wrote: Have any of you tried Rust yet? Looks pretty awesome at first glance. Yes, I played around with it, tried to write some command line utilities (cat, echo and so on are often good to get intros to languages) and I disliked it at the time due to their docs being terrible. They were well aware of it, and even ended up hiring a guy to fix it up. Then it also suffers from "new language"-sickness meaning they still do breaking changes - so, I guess it's an OK language, but nothing exceptional. | ||
|
Saumure
France404 Posts
by any chance, does someone have a c++ code to make a minimum spanning tree out of an adjacency matrix? That would be an implementation of prim's algorithm  | ||
|
Blisse
Canada3710 Posts
i think they're slowing merging mono into .Net | ||
|
Nesserev
Belgium2760 Posts
| ||
|
Blisse
Canada3710 Posts
edit: i'm a mobile dev on all 3 platforms so i can help a bit if you have qs | ||
|
xboi209
United States1173 Posts
| ||
|
CatNzHat
United States1599 Posts
On November 14 2014 05:05 Saumure wrote: Hi there, by any chance, does someone have a c++ code to make a minimum spanning tree out of an adjacency matrix? That would be an implementation of prim's algorithm http://www.dailyfreecode.com/code/prims-algorithm-minimum-spanning-tree-1027.aspx http://bit.ly/1xswq8T | ||
|
Khalum
Austria831 Posts
On November 16 2014 08:25 xboi209 wrote: Does anyone have a non-Express edition of Visual Studio? I'd like to get some code compiled If your code builds on the 2013 VS I recommend this: http://www.visualstudio.com/products/visual-studio-community-vs | ||
|
Nesserev
Belgium2760 Posts
| ||
|
Manit0u
Poland17843 Posts
On November 16 2014 08:25 xboi209 wrote: Does anyone have a non-Express edition of Visual Studio? I'd like to get some code compiled http://stackoverflow.com/questions/18286855/how-can-i-compile-and-run-c-sharp-program-without-using-visual-studio | ||
|
r3dox
Germany261 Posts
http://www.codingame.com/games is has different challenges/puzzles to solve with an own program chosing from a large number of available programming languages. all puzzles are game based and have visual representation of the behaviour of your program. there are multiplayer battles as well (your ai vs other peoples ai etc.) check it out guys  | ||
|
FFGenerations
7088 Posts
Both are APIs to connect to large anime databases One is UDP something One is ... RESTful XML? I'm not sure what terminology should be used to describe and compare these two things The question arises because the documentation of the latter seems really simple whereas the former UDP API has a shtiton of documentation. Why might this be? And what google keyword could i use to compare the former and latter systems? Thanks..... Links: UDP API of aniDB website http://wiki.anidb.net/w/UDP_API_Definition other API of anime news network website http://www.animenewsnetwork.com/encyclopedia/api.php 3rd API , of myanimelist website https://bitbucket.org/ratan12/atarashii-api I need to choose which one to use based on factors that I'm trying to come up with which is difficult because I'm technically unsound and reasons such as "this one looks simpler for some reason but im not sure why" Anything to help me google e.g. what is a UDP API compared to that other one , or anything else would be cool edit: someone in AniDB IRC suggested that they might use UDP because their website can't handle the load of the other method (because anime news network is a much larger, commercial website) edit: i'm guessing the other type is HTTP API vs UDP API (from anidb page) would the UDP API be better performance-wise? does it hold open a connection or something to make it faster to make multiple requests? or am i crazy. | ||
|
_fool
Netherlands685 Posts
On November 17 2014 11:42 FFGenerations wrote: Hey guys, I am wondering if someone technical could briefly describe to me the difference between these two things? Both are APIs to connect to large anime databases One is UDP something One is ... RESTful XML? I'm not sure what terminology should be used to describe and compare these two things The question arises because the documentation of the latter seems really simple whereas the former UDP API has a shtiton of documentation. Why might this be? And what google keyword could i use to compare the former and latter systems? Thanks..... Links: UDP API of aniDB website http://wiki.anidb.net/w/UDP_API_Definition other API of anime news network website http://www.animenewsnetwork.com/encyclopedia/api.php 3rd API , of myanimelist website https://bitbucket.org/ratan12/atarashii-api I need to choose which one to use based on factors that I'm trying to come up with which is difficult because I'm technically unsound and reasons such as "this one looks simpler for some reason but im not sure why" Anything to help me google e.g. what is a UDP API compared to that other one , or anything else would be cool edit: someone in AniDB IRC suggested that they might use UDP because their website can't handle the load of the other method (because anime news network is a much larger, commercial website) edit: i'm guessing the other type is HTTP API vs UDP API (from anidb page) would the UDP API be better performance-wise? does it hold open a connection or something to make it faster to make multiple requests? or am i crazy. My guess would be that the UDP protocol is used for streaming data, movies for instance. UDP is a lightweight protocol that does little error checking, streaming data is one the usecases for that (dropping a frame here and there is better then stopping the request). The restful xml sounds more like simple request-response. Getting lists of stuff, or details about an item. Depending on what your goal is, you need the one API or the other. So: what kind of questions will you be asking the API's? What is the payload of the messages that go over UDP, and what's the payload of the xml? Maybe you even need both: one to fetch id's of episodes, and the other to fetch the stream for that id. | ||
|
goody153
44300 Posts
I was specifically tasked to convert 2 websites that was hardcoded into MVC coding style(or architecture or whatever the term i should use) so i did some googling and i ended up finding 3 PHP framework that apparently commonly used and i believe would help me on the task which are CakePHP, Laravel and CodeIgniter. I won't ask which one is the best since they all probably have their own pros and cons. So my question would be which PHP framework between CakePHP, Laravel and CodeIgniter have you guys used or have been using ? or have you switched from one framework to another ? or which framework have you had a wonderful experience or have worked on you? which didn't ? Btw i'm really new to this MVC coding architecture. Thanks in advance. | ||
|
adwodon
United Kingdom592 Posts
On November 17 2014 11:42 FFGenerations wrote: Hey guys, I am wondering if someone technical could briefly describe to me the difference between these two things? Both are APIs to connect to large anime databases One is UDP something One is ... RESTful XML? I'm not sure what terminology should be used to describe and compare these two things The question arises because the documentation of the latter seems really simple whereas the former UDP API has a shtiton of documentation. Why might this be? And what google keyword could i use to compare the former and latter systems? Thanks..... Links: UDP API of aniDB website http://wiki.anidb.net/w/UDP_API_Definition other API of anime news network website http://www.animenewsnetwork.com/encyclopedia/api.php 3rd API , of myanimelist website https://bitbucket.org/ratan12/atarashii-api I need to choose which one to use based on factors that I'm trying to come up with which is difficult because I'm technically unsound and reasons such as "this one looks simpler for some reason but im not sure why" Anything to help me google e.g. what is a UDP API compared to that other one , or anything else would be cool edit: someone in AniDB IRC suggested that they might use UDP because their website can't handle the load of the other method (because anime news network is a much larger, commercial website) edit: i'm guessing the other type is HTTP API vs UDP API (from anidb page) would the UDP API be better performance-wise? does it hold open a connection or something to make it faster to make multiple requests? or am i crazy. That UDP API doesn't make a single lick of sense to me, but I'm not a web guy so I suppose that's why. I've not really read too much into the links you've posted as I don't have time for that but here are some thoughts... UDP is a transport layer protocol, compared to HTTP which is an application layer protocol. Normally you'd use TCP to send HTTP packets and UDP for streaming RTSP packets etc as UDP is a connectionless protocol, meaning no handshakes and you'll just be sitting there twiddling your thumbs hoping for a response which is fine if you just want something to spit frames at you, but not so good if you want to query a database. Why do you care about performance? A UDP request might be 'faster' but at what cost, you have no guarantee of delivery among other things, is a few milliseconds extra going to be a problem for you? (if you aren't streaming audio / video the answer is no performance in this context doesn't matter). Just read this: http://en.wikipedia.org/wiki/User_Datagram_Protocol#Comparison_of_UDP_and_TCP As for a 'RESTful' API, REST is just an architectural thing but it allows you to make simple requests unlike SOAP which is a bit more complicated. Read this: http://rest.elkstein.org/2008/02/what-is-rest.html I'm not sure what you're on about in terms of RESTful XML, REST uses HTTP requests, however if you are querying a database you may well get database information returned to you in XML. So yes ultimately it sounds like you're dealing with UDP vs HTTP, I know shit all about UDP packets and my advise would be to stay away, but I suppose it wouldn't hurt either. | ||
|
BByte
Finland49 Posts
On November 17 2014 21:25 goody153 wrote: I was specifically tasked to convert 2 websites that was hardcoded into MVC coding style(or architecture or whatever the term i should use) so i did some googling and i ended up finding 3 PHP framework that apparently commonly used and i believe would help me on the task which are CakePHP, Laravel and CodeIgniter. I won't ask which one is the best since they all probably have their own pros and cons. So my question would be which PHP framework between CakePHP, Laravel and CodeIgniter have you guys used or have been using ? or have you switched from one framework to another ? or which framework have you had a wonderful experience or have worked on you? which didn't ? I haven't used any of the mentioned frameworks extensively, I use Symfony both at work and for some of my own projects. Based on what impressions I have of the three mentioned, I'd choose Laravel. The best framework really depends on what you actually need to convert those sites. If they are rather simple, you may want to consider using a micro-framework. Even something simple will force you to use a proper MVC model and micro-frameworks can be a lot easier to learn. You certainly don't have to use or learn to use every component even if you pick a heavier option though. When converting an existing site I'd especially consider support for different types of template and configuration files. If the sites are currently hardcoded, it's likely the view / template code is written in raw HTML + PHP. You may want to keep it that way and just separate the business logic. But if you also need to create some new templates a proper template engine can be useful. Mixing different types of templates may not be the cleanest solution, but in can mean a lot less work. Same goes for config files: Maybe you want to keep some of the old PHP or XML files, but want to use YAML for the new files. If the framework can seamlessly support different types of configuration, it's a little easier. | ||
| ||
