I prefer spaces and smaller print but someone with bad eyesight might need tabs and bigger sized text, or maybe one prefers to write keywords in their native lang, or organize imports differently. Whatever the case it shouldn't matter how we choose to see it.
-
-
Prikaži ovu nit
-
Sad about tooling again
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
I like this idea in theory but I think about all the tools that touch source code and how much work it'd be to make everything play nice and I have to go lie down for a bit.
-
I think you need a language that has this built in from the start too, but maybe just maybe we could have nice things.
- Još 2 druga odgovora
Novi razgovor -
-
-
I used a system like this; it was a MUD programming language with a vaguely OO C-ish syntax. It got translated to a straightforward token stream that could be directly interpreted or pretty-printed back to something very close to the original. Did not miss the control.
-
As in you liked it or no?
- Još 3 druga odgovora
Novi razgovor -
-
-
This is a good tweet, but your handle is


Novi razgovor -
-
-
Could you do some of this in a backwards-compatible way by parsing the source on disk and using that representation to present it to the user?
-
I guess if everyone else uses the on-disk version to review, fix merge conflicts, display on GitHub, etc. that would just alienate the person using the tool :(
- Još 2 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
