JavaScript vs. Markdown vs. HAML

We use javascript extensively in the client and server stack.

Everything. For the frontend. For the backend. Eg for Unity.

Javascript is cool to manage the front end interaction with end users in my apps.

Client side programming.

Client-side interaction.

Front-end UI.

kjjlk

The Opstax website uses some Javascript for effects and functionality.

Externalization and product extension are all handled with this universal language

Generates and refreshes the chart on the trends dashboard using the Keen.io JavaScript API

All our front code and an increasing share on our backend. We love JS.

We use JavaScript as the primary language of the project for running the app in the browser.

JS JS JS

Used along with jQuery to add site interactivity, tag management and analytics.

I used JS to make things go!

JavaScript makes it possible to build novel and engaging interfaces for our Web apps. We're keeping up with the rapidly improving ecosystem, including the new language features in ECMAScript 2015.

Website front end

Transpiling ES6/7 to ES5 using Babel and WebPack

EcmaScript6 with Babel

The frontend game canvas is powered by JS

Minor Features

JS on the config pages as well as within the watchapp for communication with the Foursquare API.

art of the MeteorJS prototyping for internal business interface.

frontend

Front end magic.

Our web applications use JavaScript extensively to provide rich, interactive data visualization and include real-time data (from RabbitMQ via cometd).

Fancy effects.

React Native and private npm library for business logic

Used to detect page images, optimize, process CSS, and push to the CDN.

It's pretty much the whole stack.

Front-end application logic.

As the main programming language for the server stack

There are a couple js front end pieces that make my page look a little better.

JavaScript is the base-platform. I like to code in CoffeeScript and in other small languages that eventually compile down to JavaScript.

JavaScript gets a bad rep, quite undeservedly so in my opinion. Today, JS is closer to functional languages than to the traditional-OO languages, and when used as such provides a great development experience. The pace of development is just picking up with transpilers like Babel making future advanced language features available to the masses today. At Cloudcraft.co, we write 100% of both the front-end (with React) and the backend (with Node.js) in Javascript, using the latest ES6 and even some ES7 features. This is not your grandfather's Javascript!

This GNU/GPL licensed Javascript library allows you to draw complex organizational charts that can't be drawn using Google's tool or equivalents. Orgchart structures are specified with JSON and can be generated on-the-fly by server-side scripts and databases. Events can be attached to clicks over the boxes. Multiple options can be defined; look at the repo for examples. This 1300-code-lines software component with contributors from 8 countries (and others for which I have to integrate their works) appears in the first page of Google Search results when searching for "Javascript Organizational Chart Library".

Just about everywhere on front-end as glue.

Here and there, particularly google maps snippet and some stats are using it. Maybe sometime I'll rewrite HTML generation to JavaScript too (i.e. website will become completely API-based).

На фронтэнде тут и там есть кусочки Javascript: google карты, статистика и т.д. Возможно, в будущем напишу на нём и генерацию HTML (таким образом сайт будет основан на API, типа как questhub.io).

Today I use JavaScript practically everywhere...

Makes things run on the client side

JavaScript is used to build the DOMScope Inspector, which connects our users' devices with their Dashboard.

Programming language

DOM control, user interaction, animations, etc.

cause raisins.

Aside from usual web UI stuff, the user support widget/chat client, Z-XMPP, is written in it.

Just for gui manipulations.

Javascript is used for client side logic

Front End: The client side programming language.

Agile Toolkit allows you to bind JavaScript on View objects.

Heh, see NodeJS.

JS supports our React+Reflux frontend.

We all like to embed things, don't we?

mostly *trackers, pun intended

Lots of great things with JavaScript, I use it especially with jQuery to get some heavy-hitting animations and front-end logic done. Also great for making AJAX calls to an API or back-end.

Primary Language for the Front-end.

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.

The Console Frontend uses a lot of JS to make AJAX calls to the server.

All of our Frontend code is written in ECMAScript 6 using React/Redux, running on Node.js

Everything is built with JS: fronted, backend, browser plugins

Built an AngularJs powered front end.

The whole application consists of both a Javascript frontend and backend.

Almost the entire app was written in Javascript, with JSON-based configuration and data storage. The following components were written and/or configured with Javascript:

• Most server-side scripts, all unit tests, all build tools, etc. were driven by NodeJS.
• ExpressJS served as the 'backend' server framework.
• MongoDB (which stores essential JSON) was the main database.
• MongooseJS was used as the main ORM for communicating with the database, with KnexJS used for certain edge cases.
• MochaJS, ChaiJS, and ExpectJS were used for unit testing.
• Frontend builds were done with Gulp and Webpack.
• Package management was done primarily with npm - with a few exceptions that required the use of Bower (also configured with JSON).
• "Templating" was done with Javascript dialect JSX.
• The frontend was build primarily with ReactJS (as the View) and Redux (as the Controller / Store / frontend model).
• Configuration was done with json files.

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).

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.

We use JavaScript to create eye-pleasing animations and dynamic content on our website and to create web-sockets and interactive sockets to enable live-features to create a unique way of interacting with our website.

Building websites

Lorem Ipsum

Our programming language

expert

We use JavaScript for rendering the content of a Google Spreadsheet in a Single Page Application.

JavaScript is the current supported scripted language to create games using the Game Pencil Engine.

Modern language

javascript 는 쓰기 쉬운데 까도까도 자꾸 새로운 면을 볼 수 있어 재밌는 언어 이다. es2015 이후 최신 트렌드 및 대부분 언어들이 갖는 기능들이 추가되 엄청 좋아졌다. babel 없이 es2015 를 쓸 수 있는 날이 왔으면 좋겠다.

Front-end development.

i have a love and hate relationship with javascript. feels like no one knows what to do with it. the spaghetti code and callback nightmares... whew. although it is a mess its quite powerful when used correctly, thought it gets abused so much. i'm hoping my jump into clojure will lead me into clojurescript.

3+ years experience with Javascript. Heavily adopting ES6 (and ES7) syntax.

API Gateway functions and logic

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.

Javascript is the language used to write React components. Because React Native leverages javascript, you can write mobile apps in a language you know and have it compiled into a mobile app.

For both the backend and frontend.

Easy DOM manipulation and data connectivity.

All components which run in a browser

A few Lambdas which couldn't be done in Python

프론트, 백엔드를 가리지 않고 활용할 수 있도록 하고 있습니다.

Javascript is a necessary evil. I try to avoid it and web development in general, but of course it's impossible to ignore this language.

All of the build scripts are written in vanilla Javascript.

It powers react

Good for DOM manipulation.

주력으로 삼고 싶은 웹 서비스의 뿌리. Node 등 다양한 프레임워크의 등장으로 정말 JS 하나만 있으면 풀스택 흉내도 내볼 수 있을 것 같다.

Well, what other choice do we have? JavaScript is de-facto standard web language today.

Frontend language

Web UI.

Tough to build a web app without it. Are you responsive? Are you interactive? If you are, you're using it in some form. Hate it or love it, you need it.

Web Scripts

Front-end data manipulation + interactions

The bot is written in javascript

• pure 자바스크립트 보다는 제이쿼리를 더 많이 사용하였다.
• 회사에서 레거시 프로젝트중에 제이쿼리가 없는 프로젝트에서 자주 사용함

프론트엔드 로직 언어

I try to use Vanilla JS where ever I can. But all those "use jQuery" replies to my Javascript-Questions make it really hard...

JavaScript is used on the frontend when needed.

Read more on how to extend the OutSystems UI with Javascript here.

OutSystems provides a very simple to use AJAX mechanism. However, developers can also use JavaScript extensively to customize how users interact with their applications, to create client side custom validations and dynamic behaviors, or even to create custom, very specific, AJAX interactions. For example, each application can have an application-wide defined JavaScript file or set of files included in resources. Page-specific JavaScript can also be defined.

front를 손대야 할때 그냥 native로 만들면 어떨까? 를

늘 변수에 넣어 고려해봅니다

실제로 vue, react, angular를 사용하지않고 native js 만으로

개발한 프로젝트가 있습니다

Using JavaScript for everything related to user interface management.

I use javascript to interact and change the content of my website using AJAX.

ApertusVR can run JavaScript code through it's JsAPI plugin. It is served by Node.js.

Most of our web frontend code is built in JavaScript with Aurelia and GWT.

Getting powerful everyday, it has carved its path and gave the dynamic approaches to web building.

all frontends (backbone.js, require.js)

Javascript is our main language to build systems and products.

I have used it in my Front-end here and there but not XOR-ly for that purpose like using React or angular which I have not used because I'm bad at front end but I want to get better. I used to like web hacking and so there was heavy javascript use. IT WAS ALL ETHICAL I SWEAR!!

as front-end

You want to use technologies that will help you succeed in the short and long term and I'm a fun of front-end programming

Necessity.

It's the assembly of the web

Well, we already have jQuery in our stack, so we couldn't not have plain JS too. We will write most JS to use jQuery methods, but to improve client-side performance we'll typically defer jQuery loading in. So if there's some client-side operations that need to happen before jQuery is available, then vanilla JS is how we'll typically handle that.

Hndhld used JavaScript for it's speediness using the V8 engine within Google Chrome, the most used browser.

I believe in this scripting language, there is a lot to see in the future about JS. Fast!

In process of Learning Technics

Frontend Scripting

client development (via typescript)

Client side scripting language for event driven web interfaces. Handles events triggered in client side

Mandatory language of meteor.js

front-end stuff. I'm not an expert, but I can get along with it. (JQuery, Typescript, Node.js and native javascript)

With out you would have a site that doesent change

We use JavaScriptCore to implement some very interesting features in our app.

we would be implementing Stack Data Structure in Javascript. Stack is a very useful data structure and has a wide range of application.

Language

https://github.com/odykyi/javascript-idiosyncrasies

All documentation and blog posts are written in Markdown

We use Markdown primarily for documentation and other forms of writing.

We’re using Markdown parsers for Reviews, Blog Posts, and Stack Description (the text you’re reading right now). We’re using Bootstrap Markdown for content input (except for reviews) and RedCarpet for rendering in certain places.

Users can format their contributions with Markdown. Great way to post tutorials with code.

Authoring of content

News articles consumed in markdown and injected into React components using Showdown with an XSS filter.

Define the project pages.

By now, almost all my text content is created in (some dialect of) markdown. It's easy to process and extend in javascript.

Using StackEdit to edit markdown files for blog roll and about sections. MD files are stored in Google Drive and pushed to GH pages through StackEdit.

For when you need to write.

Project documentation.

Documentation and tutorials about the app

Markdown is how I format all my posts. Uses the "smart" and "footnotes" options.

Update with Parsedown

Markdown represents a highly portable and lightweight text formatting. I had converted all of my Wordpress posts to Markdown prior to migrating over to Jekyll and eventually to Hugo. The fact that many generators support Markdown means that my content remains portable regardless of the platform/engine I use.

We use this internally, but there is also Markdown CMS plugn-in for Agile Toolkit.

We use NimbusKit/markdown as a convenience wrapper around NSAttributedString

저는 markdown 덕후입니다

Almost everywhere except Python documentation.

wiki notes, internal how-to guides, technical docs, change-logs, release notes

All specifications

Writing README.md's is very important to us. Also a lot of our content is maintained in Markdown (using contentful.com). We are also cool with org-mode.

We use Markdown to write posts for our blog, and also document our processes.

Huge fan of markdown

Mainly for github Readme files, and occasionally for other documentation as desired.

간략한 문법을 통해 깔끔한 문서가 나오는것에 매료되어있습니다.

Write Blog Post @ Github Pages, Documentation like API Blueprint

Use it on a daily basis to create beautifully formatted documents / pdfs.

Because it is almost an effortless markup language without ever having to write an HTML tag. Of course, you'll want to use it in environments that make it look pretty (GitHub, etc.)

Code documentation.

Markdown is awesome and becoming more well-known. It is also easier than using some proprietary markup language.

Yes, we have a README

Standard for editing readme markdown files.

For notes and documentation

For READMEs in code respository

Personally, I really like HAML. Not having to use open and close tags is a huge time saver. As a result, writing markup with HAML is much more pleasant. HAML essentially forces you to be very strict about spacing, organization, and structure. It also makes the markup easier to read. Protip: I use this pretty frequently: htmltohaml.com