| Time |
Nickname |
Message |
|
00:54
🔗
|
yipdw |
joepie91: yeah, Ruby's distributable story is pretty bad; there's only a few things I know of that actually manage to make it work (e.g. homebrew) |
|
00:54
🔗
|
yipdw |
it works best with proprietary webapps and the like |
|
00:54
🔗
|
yipdw |
no prizes for guessing which tech community likes to push it |
|
01:25
🔗
|
dashcloud |
http://www.vice.com/read/trolls-jamie-bartlett-289 Great piece on old-school trolling |
|
01:26
🔗
|
joepie91 |
yipdw: hehehe. |
|
01:46
🔗
|
balrog |
joepie91: that's why discourse uses a docker image |
|
01:46
🔗
|
balrog |
easier to distribute that way |
|
01:46
🔗
|
balrog |
rvm and bundler helps a ton btw |
|
01:56
🔗
|
yipdw |
balrog: sort of. one problem you run into with rvm and bundler is getting the process environment set up |
|
01:57
🔗
|
balrog |
hmm, how exactly? |
|
01:57
🔗
|
yipdw |
it's particularly annoying with exec |
|
01:57
🔗
|
yipdw |
the environment variables used by rvm and bundler aren't publicly documented |
|
01:57
🔗
|
yipdw |
BUNDLE_GEMFILE is |
|
01:57
🔗
|
yipdw |
sometimes that's enough |
|
01:58
🔗
|
yipdw |
additionally, once you have that Ruby environment set up, you pay a substantial startup time cost for bundler to start up |
|
01:58
🔗
|
yipdw |
it gets worse the more gems you have |
|
01:58
🔗
|
yipdw |
rvm is not so bad |
|
01:58
🔗
|
yipdw |
rvm is, however, a nightmare to automate |
|
01:58
🔗
|
yipdw |
the official distribution is a shell script that you're supposed to curl | sh |
|
01:58
🔗
|
yipdw |
you can save the shell script and install from a known good source yes |
|
01:59
🔗
|
yipdw |
but you've got to make all sorts of fiddly special cases in your chef/puppet/whatever scripts to do it |
|
01:59
🔗
|
yipdw |
sometimes you can find rvm chef recipes or puppet modules but then you need to verify them |
|
01:59
🔗
|
yipdw |
rvm also moves too quickly for any distribution to have reasonably up-to-date packages |
|
02:00
🔗
|
yipdw |
none of these annoyances are problems if you want to just run your own app on your own hardware, but start depending on them for distributables and you quickly end up with the reasoning that the least-effort solution for your customers is to ship a VM image |
|
02:00
🔗
|
yipdw |
fine for server apps, insane for just about anything else |
|
02:01
🔗
|
yipdw |
you can also, I suppose, bundle a complete copy of the Ruby VM and all dependent gems with you rapp |
|
02:01
🔗
|
yipdw |
that however will make the runtime bigger than your app in most cases |
|
02:02
🔗
|
yipdw |
these are just issues I've run into getting Ruby environments and apps to deploy nicely over the past few years |
|
02:03
🔗
|
yipdw |
it has gotten much better but I would in no way call it anywhere near as convenient as unpacking, say, a C/C++ binary package and saying go |
|
02:04
🔗
|
dashcloud |
take a look at the recommended directions for installing calibre in this article: http://www.tuxarena.com/2014/10/calibre-2-5-released-shipping-bug-fixes-and-three-new-features/ |
|
02:05
🔗
|
yipdw |
dashcloud: yikes |
|
02:07
🔗
|
yipdw |
balrog: all my bitching aside, I have found solutions that I am reasonably happy with for deployment |
|
02:07
🔗
|
yipdw |
chruby and ruby-install |
|
02:07
🔗
|
yipdw |
neither require the constant updates that rvm does |
|
02:09
🔗
|
yipdw |
still think it's unreasonable to expect an end-user to install those, though -- they're sysadmin/dev tools |
|
03:27
🔗
|
xmc |
ruby, yes, ruby is a nightmare made of snakes |
|
03:34
🔗
|
* |
LD100 is running qwiki discovery on a university computer ... |
|
15:47
🔗
|
joepie91 |
[03:46] <balrog> rvm and bundler helps a ton btw |
|
15:47
🔗
|
joepie91 |
you had a problem, and decided to use rvm. now you have a problem environment |
|
15:47
🔗
|
joepie91 |
:) |
|
16:32
🔗
|
xmc |
hahaha |
|
18:34
🔗
|
RedType |
just imaged two DVD-Rs from 2006 |
|
18:34
🔗
|
RedType |
or earlier |
|
18:34
🔗
|
RedType |
no errors |
|
18:34
🔗
|
RedType |
i got lucky :| |
|
20:23
🔗
|
SketchCow |
Archive Team! |
|
20:23
🔗
|
SketchCow |
http://fos.textfiles.com/jsmess/keyboard-arcade/ |
|
20:23
🔗
|
SketchCow |
If you could run it |
|
20:23
🔗
|
SketchCow |
And after the arcade machine boots, hit "insert coin" and "player 1" and see if those do something expected. |
|
20:26
🔗
|
BlueMaxim |
Works for me, SketchCow |
|
20:27
🔗
|
BlueMaxim |
Chrome 37.0.2062.124 m on Windows 7 just fyi |
|
20:29
🔗
|
aaaaaaaaa |
smooth control, but the audio sounds choppy |
|
20:30
🔗
|
BlueMaxim |
I would say more staticy |
|
20:32
🔗
|
aaaaaaaaa |
maybe, but either way it is off. |
|
20:33
🔗
|
Arkiver2 |
Awesome game, working for |
|
20:34
🔗
|
BlueMaxim |
what game is it, can't quite put my finger on the name |
|
20:35
🔗
|
Arkiver2 |
Firefox 32.0.3 totally working |
|
20:35
🔗
|
BlueMaxim |
nevermind, I remember, Scramble |
|
20:35
🔗
|
BlueMaxim |
and yeah the sound is indeed a bit off in the browser version |
|
20:36
🔗
|
Arkiver2 |
But, the first time the sound normal, if I wait a few minutes an play it again the sound is not totally working, sounds cracked |
|
20:39
🔗
|
aaaaaaaaa |
Seems I can only do a max of 2 credits |
|
20:45
🔗
|
aaaaaaaaa |
nevermind, must have clicked the button too fast or something |
|
20:50
🔗
|
SketchCow |
Faster in firefox |
|
20:50
🔗
|
SketchCow |
Fastest in test firefox |
|
20:50
🔗
|
SketchCow |
Regardless, just testing the movement. Might make it pacman shortly. |
|
20:53
🔗
|
SketchCow |
Yes, let's pacman that shit. |
|
21:13
🔗
|
SketchCow |
Pacman'd |
|
21:42
🔗
|
yipdw |
first person to hit the kill screen in JSMESS Pacman without doing some voodoo hackage gets, uh, I dunno |
|
21:42
🔗
|
yipdw |
bitcoin |
|
21:42
🔗
|
yipdw |
for a new CPU because yours will have probably melted :P |
|
21:43
🔗
|
yipdw |
runs great on a Core i5 in Kubuntu and Firefox for me, though |
|
22:05
🔗
|
godane |
i got 2195 microsoft research videos uploaded |
|
22:05
🔗
|
godane |
*in collection anyways |
|
23:03
🔗
|
danneh_ |
Whoo, Pacman works great in Chrome 39.0.2171.7 dev (64-bit), OSX, sound and all |