brokkoli_origin has quit [Remote host closed the connection]
fercell has joined #ruby
brokkoli_origin has joined #ruby
fercell has quit [Ping timeout: 255 seconds]
Linux_Kerio has quit [Ping timeout: 246 seconds]
fercell has joined #ruby
fercell has quit [Ping timeout: 255 seconds]
hightower3 has joined #ruby
hightower2 has quit [Ping timeout: 240 seconds]
donofrio_ has quit [Remote host closed the connection]
konsolebox has joined #ruby
fercell has joined #ruby
fercell has quit [Ping timeout: 255 seconds]
konsolebox has quit [Quit: .]
konsolebox has joined #ruby
konsolebox has quit [Quit: .]
<_0x1eef>
In the era of digest filenames I forgot that a query string can be used in a similar way. It works well, and since nanoc doesn't support digest filenames, it's the best option.
fercell has joined #ruby
fercell has quit [Ping timeout: 255 seconds]
cappy has joined #ruby
teardown has joined #ruby
gaussianblue has joined #ruby
TomyLobo has joined #ruby
grenierm has joined #ruby
cappy has quit [Quit: Leaving]
Cork has joined #ruby
fercell has joined #ruby
fercell has quit [Ping timeout: 255 seconds]
___nick___ has joined #ruby
Linux_Kerio has joined #ruby
grenierm has quit [Ping timeout: 250 seconds]
Inline has quit [Quit: Leaving]
pages has quit [Ping timeout: 264 seconds]
gaussianblue has quit [Quit: leaving]
jaredce has joined #ruby
xdminsy has quit [Read error: Connection reset by peer]
xdminsy has joined #ruby
mange has joined #ruby
konsolebox has joined #ruby
fercell has joined #ruby
jaredce has quit [Ping timeout: 240 seconds]
hightower2 has joined #ruby
hightower3 has quit [Ping timeout: 268 seconds]
fercell has quit [Ping timeout: 255 seconds]
Inline has joined #ruby
mange has quit [Remote host closed the connection]
Linux_Kerio has quit [Quit: Konversation terminated!]
Na_Klar has joined #ruby
<Na_Klar>
when I loop through the bytes of a huge variable (as string), the access with var[x] gets slower and slower the higher x gets. is there a faster way to access a specific position within a long string?
<Na_Klar>
I think this is because var[x] seeks for x every time from the beginning, so I'd need smth like a pointer for a variable in memory.
<Na_Klar>
well, converting the string to a bytearray solves the issue. but still would be interested if there is a faster way to access an index within a string.
<adam12>
_0x1eef: Yep. IIRC, gemdocs.org I just manually increment the # and on Suspenders, I use Time.mtime. I am going to use asset digest eventually.
scottg489 has joined #ruby
scottgy has quit [Ping timeout: 272 seconds]
Linux_Kerio has joined #ruby
Linux_Kerio has quit [Client Quit]
<_0x1eef>
I use the commit sha that's been deployed, basically: /js/foo.js?v=`git rev-parse HEAD`.chomp (at build time). It took me months to realize it was a viable alternative -_-
mweckbecker has quit [Quit: leaving]
Linux_Kerio has joined #ruby
___nick___ has quit [Read error: Connection reset by peer]