<\/p>\n
Frontend Frameworks (<\/span>React<\/span><\/a>, <\/span>Vue<\/span><\/a>, <\/span>Angular<\/span><\/a>)<\/span><\/h2>\nOne of the prevalent forces in the web development world as of late is the introduction of frontend frameworks. In a web app, you typically have some code that shows stuff to the user, ie. the frontend, and code that processes data on the actual web server, or the backend. \u00a0Frontend frameworks help bridge this gap. Utilizing frontend frameworks save development time, which saves costs, which makes everyone a little happier. Frontend frameworks have been trending upwards for a few years now, and it doesn\u2019t appear that they are leaving anytime soon.<\/span><\/p>\n![\"npm](\"https:\/\/blogs.swarthmore.edu\/its\/wp-content\/uploads\/2019\/02\/Screenshot-2019-02-11-10.05.42-1024x422.png\")
<\/a>Click the image to view a larger version<\/figcaption><\/figure>\nAI \/ Machine Learning<\/span><\/h2>\nThis is an interesting one because machine learning has been around for a while. There\u2019s nothing new conceptually being introduced here. What is changing is the ability for users to access this kind of technology. Cloud computing<\/a> is quickly gaining traction, and with it, access to high-powered computers that are too often costly for consumers. Developers have also been keeping up with this trend. TensorFlow<\/a> and ml5js<\/a>, two of the largest players in machine learning (at least on the web) are catching on by offering easy to use machine learning libraries to developers. With this kind of technology, developers can create ways to recognize objects, detect spam, customer support automation, and more<\/a>. I’d say expect machine learning to really start to catch on this year.<\/span><\/p>\n![\"Happy](\"https:\/\/blogs.swarthmore.edu\/its\/wp-content\/uploads\/2019\/02\/Screenshot-2019-02-11-10.05.23-300x200.png\")
<\/p>\n
GraphQL<\/span><\/a><\/h2>\nGraphQL has been around for a few years now, but it\u2019s now in a state where it\u2019s robust enough to be a game changer. GraphQL is a query language that you can use to access your APIs<\/a>. With GraphQL, the developer is able to define an interface into their API. With this interface, the developer can define exactly what data they want from their API. Normally, you\u2019d have to parse the request after it\u2019s been received, but with GraphQL you don\u2019t have to. This saves time, which saves money, and is fairly easy to implement, which is why it you\u2019ll likely be seeing more of it soon.<\/span><\/p>\n![\"GraphQL](\"https:\/\/blogs.swarthmore.edu\/its\/wp-content\/uploads\/2019\/02\/Screenshot-2019-02-07-14.30.49-1024x187.png\")
GraphQL allows the developer to first describe their data, then send requests in that format to get their results.<\/figcaption><\/figure>\nHybrid Applications<\/span><\/h2>\nHybrid Applications are programs that combine elements of native apps (applications designed for a specific environment) and web apps. Computers, televisions, smart watches, and many other devices are becoming increasingly able to run these kind of apps (which is both scary and exciting). Hybrid applications ease development time in that developers can code the web app and then encapsulate that code into whatever renderer the device its deployed on uses. Some examples of hybrid applications that are already out in the wild include\u00a0Slack<\/a>, Skype<\/a>, and Atom<\/a>. Hybrid applications greatly reduce development time and allow apps to be deployed quicker. Because of that, and the steadily increasing internet of things<\/a>, we are likely to see many more hybrid apps in the near future.<\/span><\/p>\nNodeJS<\/span><\/a><\/h2>\nNodeJS is a JavaScript runtime based on Google Chrome\u2019s V8 JavaScript engine. In simpler terms, NodeJS allows you to run JavaScript server-side. This allows frontend (client-side) JavaScript developers to transition easily to backend (server-side) programming. Again, this saves time, which saves cost, which is why it\u2019s not going anywhere. Not only does it save money, but NodeJS also has several enhancements over the competing PHP language. Andrew Neagoie, a software developer and blogger on Medium.com<\/a>,\u00a0has a great writeup on the similarities and differences between PHP and NodeJS<\/a> that I’d encourage anyone looking at either of these languages to read.<\/span><\/p>\n![\"NodeJS](\"https:\/\/blogs.swarthmore.edu\/its\/wp-content\/uploads\/2019\/02\/Screenshot-2019-02-11-10.04.57-300x198.png\")
<\/p>\n","protected":false},"excerpt":{"rendered":"
<\/a>AI \/ Machine Learning<\/span><\/h2>\nThis is an interesting one because machine learning has been around for a while. There\u2019s nothing new conceptually being introduced here. What is changing is the ability for users to access this kind of technology. Cloud computing<\/a> is quickly gaining traction, and with it, access to high-powered computers that are too often costly for consumers. Developers have also been keeping up with this trend. TensorFlow<\/a> and ml5js<\/a>, two of the largest players in machine learning (at least on the web) are catching on by offering easy to use machine learning libraries to developers. With this kind of technology, developers can create ways to recognize objects, detect spam, customer support automation, and more<\/a>. I’d say expect machine learning to really start to catch on this year.<\/span><\/p>\n<\/p>\n
GraphQL<\/span><\/a><\/h2>\nGraphQL has been around for a few years now, but it\u2019s now in a state where it\u2019s robust enough to be a game changer. GraphQL is a query language that you can use to access your APIs<\/a>. With GraphQL, the developer is able to define an interface into their API. With this interface, the developer can define exactly what data they want from their API. Normally, you\u2019d have to parse the request after it\u2019s been received, but with GraphQL you don\u2019t have to. This saves time, which saves money, and is fairly easy to implement, which is why it you\u2019ll likely be seeing more of it soon.<\/span><\/p>\nGraphQL allows the developer to first describe their data, then send requests in that format to get their results.<\/figcaption><\/figure>\nHybrid Applications<\/span><\/h2>\nHybrid Applications are programs that combine elements of native apps (applications designed for a specific environment) and web apps. Computers, televisions, smart watches, and many other devices are becoming increasingly able to run these kind of apps (which is both scary and exciting). Hybrid applications ease development time in that developers can code the web app and then encapsulate that code into whatever renderer the device its deployed on uses. Some examples of hybrid applications that are already out in the wild include\u00a0Slack<\/a>, Skype<\/a>, and Atom<\/a>. Hybrid applications greatly reduce development time and allow apps to be deployed quicker. Because of that, and the steadily increasing internet of things<\/a>, we are likely to see many more hybrid apps in the near future.<\/span><\/p>\nNodeJS<\/span><\/a><\/h2>\nNodeJS is a JavaScript runtime based on Google Chrome\u2019s V8 JavaScript engine. In simpler terms, NodeJS allows you to run JavaScript server-side. This allows frontend (client-side) JavaScript developers to transition easily to backend (server-side) programming. Again, this saves time, which saves cost, which is why it\u2019s not going anywhere. Not only does it save money, but NodeJS also has several enhancements over the competing PHP language. Andrew Neagoie, a software developer and blogger on Medium.com<\/a>,\u00a0has a great writeup on the similarities and differences between PHP and NodeJS<\/a> that I’d encourage anyone looking at either of these languages to read.<\/span><\/p>\n<\/p>\n","protected":false},"excerpt":{"rendered":"
<\/p>\n
GraphQL<\/span><\/a><\/h2>\nGraphQL has been around for a few years now, but it\u2019s now in a state where it\u2019s robust enough to be a game changer. GraphQL is a query language that you can use to access your APIs<\/a>. With GraphQL, the developer is able to define an interface into their API. With this interface, the developer can define exactly what data they want from their API. Normally, you\u2019d have to parse the request after it\u2019s been received, but with GraphQL you don\u2019t have to. This saves time, which saves money, and is fairly easy to implement, which is why it you\u2019ll likely be seeing more of it soon.<\/span><\/p>\nGraphQL allows the developer to first describe their data, then send requests in that format to get their results.<\/figcaption><\/figure>\nHybrid Applications<\/span><\/h2>\nHybrid Applications are programs that combine elements of native apps (applications designed for a specific environment) and web apps. Computers, televisions, smart watches, and many other devices are becoming increasingly able to run these kind of apps (which is both scary and exciting). Hybrid applications ease development time in that developers can code the web app and then encapsulate that code into whatever renderer the device its deployed on uses. Some examples of hybrid applications that are already out in the wild include\u00a0Slack<\/a>, Skype<\/a>, and Atom<\/a>. Hybrid applications greatly reduce development time and allow apps to be deployed quicker. Because of that, and the steadily increasing internet of things<\/a>, we are likely to see many more hybrid apps in the near future.<\/span><\/p>\nNodeJS<\/span><\/a><\/h2>\nNodeJS is a JavaScript runtime based on Google Chrome\u2019s V8 JavaScript engine. In simpler terms, NodeJS allows you to run JavaScript server-side. This allows frontend (client-side) JavaScript developers to transition easily to backend (server-side) programming. Again, this saves time, which saves cost, which is why it\u2019s not going anywhere. Not only does it save money, but NodeJS also has several enhancements over the competing PHP language. Andrew Neagoie, a software developer and blogger on Medium.com<\/a>,\u00a0has a great writeup on the similarities and differences between PHP and NodeJS<\/a> that I’d encourage anyone looking at either of these languages to read.<\/span><\/p>\n<\/p>\n","protected":false},"excerpt":{"rendered":"
Hybrid Applications<\/span><\/h2>\nHybrid Applications are programs that combine elements of native apps (applications designed for a specific environment) and web apps. Computers, televisions, smart watches, and many other devices are becoming increasingly able to run these kind of apps (which is both scary and exciting). Hybrid applications ease development time in that developers can code the web app and then encapsulate that code into whatever renderer the device its deployed on uses. Some examples of hybrid applications that are already out in the wild include\u00a0Slack<\/a>, Skype<\/a>, and Atom<\/a>. Hybrid applications greatly reduce development time and allow apps to be deployed quicker. Because of that, and the steadily increasing internet of things<\/a>, we are likely to see many more hybrid apps in the near future.<\/span><\/p>\nNodeJS<\/span><\/a><\/h2>\nNodeJS is a JavaScript runtime based on Google Chrome\u2019s V8 JavaScript engine. In simpler terms, NodeJS allows you to run JavaScript server-side. This allows frontend (client-side) JavaScript developers to transition easily to backend (server-side) programming. Again, this saves time, which saves cost, which is why it\u2019s not going anywhere. Not only does it save money, but NodeJS also has several enhancements over the competing PHP language. Andrew Neagoie, a software developer and blogger on Medium.com<\/a>,\u00a0has a great writeup on the similarities and differences between PHP and NodeJS<\/a> that I’d encourage anyone looking at either of these languages to read.<\/span><\/p>\n<\/p>\n","protected":false},"excerpt":{"rendered":"
NodeJS<\/span><\/a><\/h2>\nNodeJS is a JavaScript runtime based on Google Chrome\u2019s V8 JavaScript engine. In simpler terms, NodeJS allows you to run JavaScript server-side. This allows frontend (client-side) JavaScript developers to transition easily to backend (server-side) programming. Again, this saves time, which saves cost, which is why it\u2019s not going anywhere. Not only does it save money, but NodeJS also has several enhancements over the competing PHP language. Andrew Neagoie, a software developer and blogger on Medium.com<\/a>,\u00a0has a great writeup on the similarities and differences between PHP and NodeJS<\/a> that I’d encourage anyone looking at either of these languages to read.<\/span><\/p>\n<\/p>\n","protected":false},"excerpt":{"rendered":"
<\/p>\n","protected":false},"excerpt":{"rendered":"