purr changed the topic of #elliottcable to: a
embri0n has joined #elliottcable
embri0n has quit [Ping timeout: 264 seconds]
embri0n has joined #elliottcable
aredridel has quit [Ping timeout: 244 seconds]
embri0n has quit [Quit: Leaving...]
meowrobot has quit [Ping timeout: 240 seconds]
meowrobot has joined #elliottcable
<pikajude> iterm2 got an alpha build with ligature support
<pikajude> the spacing is fucked up
<pikajude> but it's ligature support :^)
Sgeo_ has joined #elliottcable
Sgeo has quit [Ping timeout: 272 seconds]
aredridel has joined #elliottcable
embri0n has joined #elliottcable
thealphanerd has quit [Quit: farewell for now]
thealphanerd has joined #elliottcable
Sgeo_ has quit [Read error: Connection reset by peer]
Sgeo has joined #elliottcable
<cloudhead> iterm always felt slower to me than terminal
<cloudhead> which is already slow
<cloudhead> maybe I should give it another try though
<cloudhead> by slow I mean input lag
Sorella has quit [Quit: Connection closed for inactivity]
embri0n has quit [Remote host closed the connection]
<pikajude> cloudhead: i've never gotten input lag with it
<pikajude> I don't think
<cloudhead> maybe you don't notice :^)
<cloudhead> lemme try it out now
<pikajude> i play competitive super smash bros melee, i think i'd notice input lag :^)
<cloudhead> :D
<cloudhead> you're right, no lag on the 3.0 release
<cloudhead> I think last I tried was 2.x
<cloudhead> and was noticeable, when letting the key repeat
<cloudhead> as I have my key repeat rate set to max
<cloudhead> the font rendering is strange though
gkatsev has quit [Ping timeout: 272 seconds]
<pikajude> yeah, it is
<pikajude> he fixed it really well in the newest 3.0 alpha build
<pikajude> although i currently don't get box-drawing characters and ligatures are drawn 1 character too narrow
<cloudhead> hmm
<cloudhead> might try it out for a while
<pikajude> but that's alpha builds for you
<pikajude> guessing it'll be fixed next week
<cloudhead> seems a lot better than last I tried
<pikajude> yeah it's quite good
<pikajude> lots more features than terminal
<pikajude> ligatures are really what i was holding out for this whole time
<pikajude> i'm one of those scumbags who likes programming fonts with ligatures
<cloudhead> haha oh god
<cloudhead> you don't use monospace?
<pikajude> of course i do
<cloudhead> or are there ligatures in monospace?
<pikajude> yeah, there are a lot of programming fonts with ligatures now
<pikajude> they're still monospace
<pikajude> the ligature is just 2 characters wide
<pikajude> or 3, or whatever
<cloudhead> oh hm
<cloudhead> don't think I've seen that
<cloudhead> what font do you use?
<pikajude> hasklig
<pikajude> it's source code pro L with some haskell-specific ligatures (although they can apply to other languages too)
<cloudhead> I see
<cloudhead> I use anonymous pro
<cloudhead> I'm not sure I like the ligatures
<cloudhead> heh
<cloudhead> makes it look too much like math
<cloudhead> and not like code
<pikajude> to each his own
<cloudhead> gonna try it out though :^)
<cloudhead> I mostly program haskell so might as well
<pikajude> haskell is like therapy for me
<pikajude> after a long hard day of debugging issues caused by someone having redefined the Date.now() method in javascript
<pikajude> i like to sit back, relax, and write some viciously well-typed code
<cloudhead> hahaha
<cloudhead> I feel you
<cloudhead> I'm trying to switch over to spacemacs from sublime
<cloudhead> but emacs feels too laggy on macos
<cloudhead> it's fine on linux
<pikajude> i've tried to switch over to spacemacs a couple times but i just can't get into it
<cloudhead> but vim and emacs feel slower on mac for some reason
<pikajude> i know i'm going to have to eventually
<pikajude> i use neovim, haven't noticed any speed reduction
<cloudhead> you use it in the shell, or with gui?
<pikajude> shell
<pikajude> that's the other reason i don't really like emacs
<pikajude> it takes awhile to start up
<cloudhead> lemme check, because maybe iterm runs it faster
<pikajude> awhile being around up to a second
<cloudhead> yeah, emacs just feels sluggish
<cloudhead> I've started developing my own plugin for sublime
<cloudhead> but I don't like that state of affairs
<cloudhead> I want the work to be done for me
<cloudhead> :p
<pikajude> emacs has amazing haskell tools
<pikajude> i don't use them though i just have ghci in one pane and vim in the other
<cloudhead> yeah
<cloudhead> ok vim is a bit faster in iterm than in terminal
<cloudhead> still not snappy how I like it
<cloudhead> it's probably the syntax highlighting, idk
<cloudhead> I use like, 1 plugin in vim
<pikajude> man
<pikajude> that's weird af
<pikajude> vim is lightning fast for me
<cloudhead> I can post a gif
<pikajude> ok
<cloudhead> basically if I just scroll through a haskell file with j/k
<cloudhead> it's not butter smooth like sublime
<cloudhead> nowhere near really
<cloudhead> hold on
<pikajude> oh, well, i mean, yeah
<pikajude> it goes line by line
<cloudhead> yeah I guess it can't be
<cloudhead> since it has to rerender the whole screen
<cloudhead> idk
<pikajude> well so does sublime if you want to get pedantic
<pikajude> but you're not likely to get 60fps scrolling in vim because it would be way too fast to be useful
<cloudhead> well there's probably optimizations when it's on the gpu, it just moves the camera
<cloudhead> it rerenders the texture
<cloudhead> hm well it's way better in iterm than terminal, in terms of vim
Sorella has joined #elliottcable
embri0n has joined #elliottcable
<pikajude> hmmm
<pikajude> i was hoping node 6 would be able to install node_modules such that they can then be required
<pikajude> but there's that blind optimism again
<pikajude> i'm an idiot
<cloudhead> hahaha
<cloudhead> who is making you use node?
<cloudhead> who is that evil person?
<pikajude> work
<pikajude> ljharb: i got it to work with node 6, but now 92% of my time is spent in "(program)"
<pikajude> any idea what that means
<ljharb> lol
<purr> lollll
<ljharb> nope
<pikajude> fuck me raw
<pikajude> why am i still doing this
<jfhbrook> keep in mind pikajude that npm installs modules, not node
<pikajude> oh no i'm all done with complaining about npm
<jfhbrook> and you can manage your version(s) of npm separately (outside the context of nvm I mean)
<pikajude> and I found it on the internet
<pikajude> chrome claims that (program) is native code, i.e. part of the webkit profiler
<pikajude> the question remains, of course, why the program runs in the same time inside and outside the profiler
<pikajude> and what that extra idle time is when it's not in the chrome profiler
<pikajude> but i don't know if we can answer that one
<ljharb> *v8
<pikajude> sorry
<pikajude> but i don't know if we can answer that v8
<ljharb> lol
<purr> lollll
<ljharb> i mean s/webkit/v8. chrome doesn't use webkit.
<ljharb> or rather s/webkit/blink
<ljharb> i'm tired today.
<pikajude> oh ok, it's blink
<pikajude> neat
<ljharb> and chrome uses v8, webkit/safari uses jsc (for the js engine)
<pikajude> ok, i ran it again
<pikajude> now it's 99% "(idle)"
<pikajude> same test run speed
<pikajude> same result
<pikajude> but now it's idle time instead of GC
<pikajude> what the FUCK is node doing
<pikajude> i'm losing my god damned mind
<jfhbrook> hah!
<jfhbrook> lmk how that shakes out
<jfhbrook> meanwhile, I'm gonna be grouchy at people that refuse to write idiomatic code because it's javascript
<jfhbrook> heh
<jfhbrook> I got 99 problems
<jfhbrook> but today, v8 ain't one :)
<pikajude> i have 99 problems
<pikajude> i don't know what they are, but v8 is telling me they're all (idle)
aredridel has quit [Ping timeout: 258 seconds]
<ljharb> jfhbrook: what do you mean "because it's js"
<ljharb> idiomatic code matters in every language.
<ljharb> i don't write terse java either, because that wouldn't be idiomatic
embri0n has quit [Quit: Leaving...]
aredridel has joined #elliottcable
<jfhbrook> ljharb: I mean "I wish I was working in java so I'm going to write code that's like what I would write if I was working with java"
<ljharb> lol yeah
<purr> lolololol
<ljharb> set fire to those people's code
<pikajude> god damn it
<pikajude> I hate the fact that if you fuck around with a node project eventually you'll put it into an unfixable state and have to re-clone