|Hacker News, Reddit, Stack Overflow Stats|
No public GitHub repository stats available
No public GitHub repository stats available
|Description||Lightweight, interpreted, object-oriented language with first-class functions||A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible||A popular general-purpose scripting language that is especially suited to web development|
|Why people like using this service||
|Companies using this service|
December 15, 2015 02:36
PHP drives 80% of the web
July 11, 2014 01:42
Rants about PHP are everywhere, but during the last years the language and the whole ecosystem has evolved.
The lastest versions support namespaces, closures, traits, generators and with composer a dependency manager that changed the way PHP developers work and collaborate.
Used in all my roles. Love the npm ecosystem and the fast moving landscape. Experience with a variety of frameworks: angular, express, react, backbone, ember, jquery. I like building things from the ground up.
→ Sud Web
For bells and whistles on the UI, and for making the game Whack-A-Mol. I purposely avoided jQuery or other 3rd party frameworks, as I was aiming to make a low overhead website system, rather than a complex web application like I make most of the time.
The only notable exceptions were the use of SCSS (augmented by Compass) for styling, Bash for a few basic 'system chores' and CLI utilities required for development of the app (most notably git and heroku's CLI interface), and a bit of custom SQL for locations where the ORM extractions leaked (the app is DB-agnostic, but a bit of SQL was required to fill gaps in the ORMs when interfacing with Postgres).
All of our Frontend code is written in ECMAScript 6 using React/Redux, running on Node.js
Used Angular,Express,Mongo,Node.js and plenty APIs to support web or mobile application development.
Also used Sequalize for Object relational mapping in case the database shall be relational database, such as postgreSQL, MySQL, MariaDB, Oracle database.
Aside from usual web UI stuff, the user support widget/chat client, Z-XMPP, is written in it.
There are a couple js front end pieces that make my page look a little better.
JS on the config pages as well as within the watchapp for communication with the Foursquare API.
Used along with jQuery to add site interactivity, tag management and analytics.
Pretty much everything - Java is reasonably fast, reasonably safe, and reasonably expressive. I wouldn't call it the best at any of those things. The real advantage to me is that the virtual machine is ubiquitous and many people can understand it. Since I have the most experience in this language, it's my tool of choice for most projects.
I've also been learning JavaFx so that I can build user interfaces without the web. I've started several single-page-application projects that worked, but felt like workarounds or hacks and would be better-served as self-contained applications.
끊임 없이 작성해야 되는 행사 코드로 지치게 만들지만, 그래도 좋고 견고한 라이브러리 들이 많아 좋다. 어떻게 하면 행사코드를 줄이고, 간결하게 할 수 있을 지 그건 아직 내게 남겨진 숙제 인것 같다.
→ My Stack
제가 최초로 배운 언어입니다. 저의 첫 프로젝트는 자바와 스프링을 이용해 진행했습니다. 당시엔 sql 쿼리도 직접 만들어야 했기 때문에 이 부분에 대한 학습도 함께 진행되었습니다.
Do I really need to explain? Well to me, the most appealing factor in Java besides the unbelievable community and vast array of available libraries, is just the amount of effort that has been put in the modern JVM. Decades of optimization and improvements have lead to a terrific piece of technology. I admire the people contributed to that.
Business logic microservices implementation. Integration against external systems via RESTful/SOAP.
SelectPdf Web/HTML To PDF REST API for Java Samples: http://selectpdf.com/web-html-to-pdf-rest-api-for-java-samples/
The engine that reads and processes an ODF file is in Java. Still need to release the code for it.
bytelore.com makes extensive use of Java in its applications. We use Java due to its performance, community and the number of other projects built in the language. We have many projects and libraries built in Java.
Our web application server and SDK are all Java-based to give us access to a broad range of languages for web app development (e.g. Python via Jython, Ruby via JRuby, etc.)
Most of the internal pipeline (machine learning processes, search, db interactions). Most of this functionality consists of in-mem Gearman workers handling very specific tasks.
현 상황에서 java 는 생산성이 높은 언어라고 볼 수 없습니다. 또한 아직 우리에겐 java 를 사용해야 할 만큼 미션 크리티컬한 이슈는 존재하지 않습니다. java 를 사용하는 단 하나의 이유는 안드로이드 개발을 위해서입니다.
PHP to me is a legacy technology that I have years of experience in, and can step back into when necessary, but I do not choose to use in new projects.
worked with php for around a year helping a client automate their backend and optimize their existing infrastructure.
PHP powers 90% of our application; both rendering the front-end, as the background processes (data capture, processing, etc.)
To generate websites from data, and to serve my UI for defining that data. Also many small personal tools, such as icon converters (rather than bash scripts). PHP is my go-to tool for server side logic.
Built an API with Composer, PHP Unit, Doctrine, Zend Validator, Zend Filter, and Stack PHP, and a PSR-7 micro framework that someone built called Proton that does not have any documentation.
Most used web development language, we use the latest version 7 which is about twice as fast as previous versions.
We happened to write the frontend in PHP. Hey, it was 2006, and we were high school students ;-)
An older ticket purchase system as well as nearly all management tools are still written in PHP. It's a long process to migrate away from it given available development resources.
PHP is what powers the server and dynamic content pages. It may be old school but it works.
How to use SelectPdf for HTML TO PDF Conversion in PHP: http://selectpdf.com/web-html-to-pdf-rest-api-for-php-samples/
→ Tom Z
Because it is required although the server is running HHVM every bit of code is PHP friendly it's an awesome synergy.
Legacy code that, although maintained slightly, will be phased out as we migrate the 2 backend tools that rely on it to other, more robust languages. See: http://bjorn.tipling.com/if-programming-languages-were-weapons