![]() It has consistently met our needs, scaling with us, getting better with time as continually pour into and expand our capabilities.The answer to this question depends on exactly what you want to learn. No strong types to protect us from ourselves, but we've rarely found that to be an issue.Īs such we decided to commit resources to our Node APIs and push it out as the core brain of our new system. There were tradeoffs we considered, latency was (acceptably) higher on requests to our Node APIs. For us this was owed to the community coupled with the extremely dynamic nature of JS. We were able to iterate on our Node based APIs much more rapidly than we were our C# APIs. What we found was easily quantifiable differences. The interfaces were identical and interchangeable. We went a very unconventional route for deciding between the two. That's a long way of saying we decided against Ruby as it doesn't play nice on Windows. We were also at a point that we were using that infrastructure to it's fullest and could not afford additional servers running Linux. At the time we owned our infrastructure, racks in cages, that were all loaded with Windows. That said, in balancing practicality we chose to focus on 3 options that our team had deep experience with and knew the pros and cons of.įor us it came down to C#, JavaScript, and Ruby. ![]() Our team has always been driven by the right tool for the job rather than what we know best. Once we nailed down the API design pattern it was time to decide what language(s) our new APIs would be built upon. To that end we spent several months studying API design patterns and decided to use our own adaptation of CRUD, specifically a SCRUD pattern that elevates query params to a more central role via the Search action. In 2015 as Xelex Digital was paving a new technology path, moving from ASP.NET web services and web applications, we knew that we wanted to move to a more modular decoupled base of applications centered around REST APIs. the freelancing options are virtually non-existent (and I would expect them to stay limited, as rust is better for long-term software than prototypes) See more it's harder to learn (expect to put in years) it's super versatile (you can do high-perf system stuff, graphics, ffi, as well as your classic api server) it's got potential to grow big in the next year (also with better paying jobs) it's satisfying to work with (after the learning curve) Then, later, for back-end programming languages, Rust seems like your best bet. it's everywhere and not going away (well not yet) can also do back-end if needed (I would personally avoid specializing in this since there's better languages for the back-end part) more freelancing opportunities (starting to work short after a virus/crisis, that's gonna help) I would start focusing on Javascript because even working with Rust and Python, you're always going to encounter some Javascript for front-ends at least. JavaScript has a broader approval, being mentioned in 10528 company stacks & 37503 developers stacks compared to Processing, which is listed in 13 company stacks and 4 developer stacks. Here's a link to Processing's open source repository on GitHub.Īirbnb, Instagram, and reddit are some of the popular companies that use JavaScript, whereas Processing is used by Rosenblatt Securities Inc, Seeed Studio, and AndyMark. Processing is an open source tool with 2.9K GitHub stars and 786 GitHub forks. JavaScript and Processing belong to "Languages" category of the tech stack. It is an open programming language for people who want to program images, animation, and interactions for the web without using Flash or Java applets. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles Processing: A programming language for people who want to program images, animation, and interactions for the web. ![]() JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. JavaScript: Lightweight, interpreted, object-oriented language with first-class functions. JavaScript vs Processing: What are the differences? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |