DeeJayh-L

Activity Graph

Page 1 of 1

2017-07-15

[17:32:27] DeeJayh-L: Ping timeout: 260 seconds

2017-07-13

[06:10:33] DeeJayh-L: has joined #ruby

2017-07-11

[18:58:57] DeeJayh-L: has joined #ruby
[21:03:29] DeeJayh-L: Ping timeout: 248 seconds

2017-06-01

[00:26:06] DeeJayh-L: has joined #ruby
[21:22:36] DeeJayh-L: Read error: Connection reset by peer

2017-05-31

[00:43:52] DeeJayh-L: has joined #ruby
[09:01:04] DeeJayh-L: *.net *.split

2017-05-22

[11:23:55] DeeJayh-L: has joined #ruby
[11:44:05] DeeJayh-L: Ping timeout: 258 seconds
[12:32:41] DeeJayh-L: has joined #ruby
[12:51:05] DeeJayh-L: Ping timeout: 240 seconds

2017-05-20

[11:00:25] DeeJayh-L: has joined #ruby
[13:17:44] DeeJayh-L: Read error: Connection reset by peer

2017-05-11

[04:58:05] DeeJayh-L: has joined #ruby
[05:41:27] DeeJayh-L: Ping timeout: 240 seconds

2017-05-07

[03:34:30] DeeJayh-L: Ping timeout: 258 seconds
[13:42:26] DeeJayh-L: has joined #ruby
[17:36:44] DeeJayh-L: Ping timeout: 255 seconds
[17:38:35] DeeJayh-L: has joined #ruby
[18:14:27] DeeJayh-L: Ping timeout: 260 seconds
[18:24:11] DeeJayh-L: has joined #ruby
[19:05:27] DeeJayh-L: Ping timeout: 240 seconds
[19:35:27] DeeJayh-L: has joined #ruby
[20:12:50] DeeJayh-L: Ping timeout: 240 seconds
[21:40:25] DeeJayh-L: has joined #ruby
[22:54:51] DeeJayh-L: Read error: Connection reset by peer

2017-05-06

[02:36:05] DeeJayh-L: has joined #ruby
[02:52:46] DeeJayh-L: elomatreb, do you think an ifelse would truly be better? I thought they were interchangeable for the most part and it was a matter of preference. Also, when you say "refactor the ranges into clearly named methods" can you give me an example?
[02:57:16] DeeJayh-L: I think I understand what you mean, but this only needs to happen once, normally you break things out into methods to write less code (by not re-writing the same functions over and over through your code) but in this case it's going to actually add code and spread it out more, seems counter-intuative
[03:29:15] DeeJayh-L: I skip rails altogether, seems like unless you're building a very basic DB based site, it's not as useful as it first appeared.
[03:29:38] DeeJayh-L: I write my backend in ruby and have a frontend guy, then just communicate between the two
[03:30:26] DeeJayh-L: I did until I realized there was true power in the freedom of ruby without rails
[03:30:52] DeeJayh-L: I mean if you want to create another twitter, great! Rails away! Otherwise, unfortunately, it seems more of a hinderance.
[03:34:35] DeeJayh-L: I mean, rails is just a framework for ruby. Rails is ruby language with structure to generate a website
[03:34:48] DeeJayh-L: but the structure seems too limited
[03:35:33] DeeJayh-L: I can create a site like twitter or netflix and host database information all day with it, but if I want a site with a roulette wheel on one page and something else on the next, seems to get pretty difficult from there
[03:38:08] DeeJayh-L: but that's what I'm saying, to display a database entry it's fantastic, but what if I want a spinning wheel displaying the results of a roulette game, starts to get cumbersome to stick to rails when something is easily made in HTML that doesn't require that framework. Add a little javascript to make socket connections to the ruby backend running it all and you got the best of both worlds
[03:38:47] DeeJayh-L: easy for the front end guy, easy for the backend guy, and your own custom language between the two of you for your socket reads/writes
[03:39:10] DeeJayh-L: of course, being a full stack developer is better
[03:39:49] DeeJayh-L: as far as employability and such, but from a purely hobbyist/oss standpoint, it's better for each piece to be as easy as possible
[05:38:19] DeeJayh-L: Read error: Connection reset by peer
[14:03:11] DeeJayh-L: has joined #ruby

2017-05-05

[16:25:25] DeeJayh-L: Quit: Leaving
[16:31:17] DeeJayh-L: Quit: Leaving
[16:31:46] DeeJayh-L: has joined #ruby
[16:32:14] DeeJayh-L: Client Quit
[16:33:04] DeeJayh-L: has joined #ruby
[18:38:28] DeeJayh-L: Ping timeout: 240 seconds