tonsky

I think you shouldn’t open random UDP ports to outside world in the first place

It’s a keyboard layout indicator (RU/EN). I’m using non-standard layout http://ilyabirman.ru/projects/typography-layout/

I believe it’s still easier to write a string to a socket than do a full-blown HTTP request. It was designed to be accessible from _anywhere_: bash scripts, build tools plugins, etc. To me single UDP packed seemed like a lowest common denominator

What editor do you use? Is it listed as supported here? https://github.com/tonsky/FiraCode#editor-support

Also, just got report that MacVim supports ligatures in latest version

Agree, but no language uses both -> and -->

On what planet people still use teletype emulators to edit code?

️

Are there any problems with installing otf on windows? I installed and used them just fine

It’s possible with classes https://medium.com/@larsenwork/class-based-contextual-positi...

And assume we only support 4-10 digit numbers, it would require e.g. 6 rules or so.

But substitutions are done left-to-right, that might be a problem

Glyphs.app provided a free license for Fira Code since font is open-source. I’m using it because original Fira Mono is developed in it as well.

Monoid uses FontForge (free)

Strangely enough, I had Terminal.app listed as not supported (at it wasn’t when I checked).

But checking now, ligatures render just fine. Yay! (that implies console vim & emacs, of course)

So happy to hear that!

You can try this https://github.com/tonsky/FiraCode/wiki/Setting-up-Emacs

Just give it a try. There’s 3× difference in width, so _in practice_ you won’t mistake them, ever. I’m using that font for a year now, not a single case of misreading

Let’s be realistic. You don’t have learn or retrain your brain to understand Fira Code. Symbols are all the same, they just look better.

You probably mean = and ==. They have 3× difference in width, which, in practice (I’m using Fira Code for a year now), is more than enough to tell the difference.

Regarding the difference between == and ===, latter has three lines (and so does !==), so in fact in Fira Code === and !== the looks implies the meaning, whether in other cases you have to bend your mind to accept that negation of “three equals” is a “two equals and a bang”

Have you tried the font? = and == has 3× difference in width, it’s hard to mistake one for another. I’m using Fira Code for a year now, never had mixed them up

I would rather put it “free as in torrents”. Microsoft https://www.microsoft.com/typography/fonts/family.aspx?FID=3... offers to buy it for €129

DataScript already can run on JVM natively. Only thing missing is durable storages (it’s inmemory only now, same as JS version)

Yes, and some databases have REST APIs. In practice pure REST is usually blurred with RPC calls and optimisations (partial fetch, batch fetch). And the downside of the REST is that it’s not agile (you have to support both new and old clients explicitly), and manual: you have to write it manually for every endpoint. Good and efficient data fetch API for client-based rendering will very soon move very very far from REST.

As I understand it, this is what you’re talking about: an iteration on top of CouchDB: http://cloudwall.me

Check out v. 0.5, I’ve made changes to === and !== so they are easily distinguishable from == and !=

(I’m one of the authors of Acha-Acha)

Just to set expectations:

* This is a project we’ve build for ClojureCup.com hackaton

* We haven’t figured out how to do a proper hosted version yet and how to handle any real load. Please be patient as I occasionaly clean up/delete some repos so site remains responsible at least

* Some repos are too big or hang at some point so please accept I’ll drop them in that case. We’ll try to fix that but not in real-time

* There’s a self-hosted version you can use at your company internally (e.g. you want achievements but repos are private). Instructions are at https://github.com/someteam/acha

* Blog post about implementation details’ here http://tonsky.me/blog/acha-acha/

* Some interesting highlights:

We use client-side DB (DataScript), all stated is downloaded to the browser, and all rendering happens without page reloads _and without API requests_ because all data is already there.

We use websockets for server push. So everything that happens on a server gets immediately pushed to the client. Including actions by other users, e.g. new repo added. No page refresh required.

And thanks for the warm feedback!

There’s also a separate post discussing how we’ve used DataScript to build Acha-Acha: http://tonsky.me/blog/acha-acha/

We’re at https://github.com/clojurecup2014/acha

Current votes ladder: http://acha.clojurecup.com/ladder.html (updated every 5 minutes)

It is accessible from browser (and is fast, on par with JSON), it has rich set of basic types + extensibility built in

Just a concept

I’m writing exactly about that. GIT model is simple and operable, so UI should not hide it behind “wizards”, but incorporate more direct use of it.