|
Nolgthorn posted:I love Haml and Sass, to the extent that I think that support should be implemented natively in all browsers. Whenever I don't get to use Haml or Sass I find myself annoyed, like I need to cross a stream but before I do I'm told that I am not allowed to use the big piece of plywood that has been laid down over the stream for me to cross with. HAML and SASS are fine the way they are, and unless you have to be observed hand-writing invalid HTML for a class project or something, you can use them on static site projects just fine. CoffeeScript is even better than HAML & SASS just because JavaScript is more powerful and has more space to be annoying.
|
# ? Apr 24, 2011 15:56 |
|
|
# ? May 30, 2024 04:20 |
|
Yesterday I discovered that Ruby 1.9 can do Javascript style hash forms. hash = {dick: 'butt', clown: {fart: true}} Going with that, I now understand the point of the -> lambda in 1.9. validates :dicks, with: -> { 10.days.ago .. 1.day.ago} So now I get the point of why 37s is gay for Coffeescript, since it maps almost 1-1 with Ruby 1.9.
|
# ? Apr 24, 2011 16:46 |
|
Jeez, if you aren't going to learn to write in multiple languages with confusingly distinct syntaxes implemented in crucially differing standards, why not just make a robot and have the robot write the website?
|
# ? Apr 25, 2011 01:25 |
|
BonzoESC posted:HAML and SASS are fine the way they are, and unless you have to be observed hand-writing invalid HTML for a class project or something, you can use them on static site projects just fine. When you say Haml and Sass can be used for static site projects, you still have to compile those pages. I'm dreaming of the day you can just use them, send the haml ans sass to browsers the way they are. And, potentially, if coffeescript is as good as you say, let coffeescript be native as well. I don't see them as having strictly Ruby syntax, it's just good syntax.
|
# ? Apr 25, 2011 14:18 |
|
Nolgthorn posted:I'm dreaming of the day you can just use them, send the haml ans sass to browsers the way they are. And, potentially, if coffeescript is as good as you say, let coffeescript be native as well.
|
# ? Apr 25, 2011 19:09 |
|
Nolgthorn posted:When you say Haml and Sass can be used for static site projects, you still have to compile those pages. The big benefit is I can set my editor to run rake on save, or run rake output:push to build and publish the pages in one quick step.
|
# ? Apr 25, 2011 19:53 |
|
You could in theory write a Javascript handler for HAML, it wouldn't be that much different than what Sproutcore does with Handlebars HTML templates. I guess SASS is in Rails 3.1 now as well https://twitter.com/dhh/status/62491857082527744
|
# ? Apr 25, 2011 20:34 |
|
Obsurveyor posted:I sincerely hope that day never comes. The downside is that third party tools, such as web crawlers, would be much more difficult to build. With that said, we're pretty much already at that point: See NSS's post as an example. We're a lot of things in Javascript already to simulate what a full virtual machine should be doing. Why not just go all the way?
|
# ? Apr 25, 2011 20:48 |
|
skidooer posted:I look forward to the day the browser is just a virtual machine and the HTML engine is a downloadable component. Do you want to have the security history, compatibility, and accessibility of ActiveX, Flash, or Java applets? Much of the web stack is focused on providing a way to incrementally implement tools that use it, and any replacements or improvements to it will be just as modular and easy-to-implement.
|
# ? Apr 26, 2011 02:59 |
|
Obsurveyor posted:I sincerely hope that day never comes. How come?
|
# ? Apr 26, 2011 15:53 |
|
The idea of being able to send any type of document type and scripting language was one of the ideas of HTTP. That's why you have content-type: text/html, the browser knows to render HTML instead of a text file. It would be possible in theory to create an addon for Chrome or something that has a HAML parser and send files from the server using content-type: text/haml. Huh, that would actually be an interesting project.
|
# ? Apr 26, 2011 16:37 |
|
So Im outputting a blog post using .html_safe (Im using tunyMCE) and I need to allow iframes for youtube videos. Is that possible?
|
# ? Apr 26, 2011 23:13 |
|
html_safe is a flag on String that determines how the string should be output in the template. http://yehudakatz.com/2010/02/01/safebuffers-and-rails-3-0/
|
# ? Apr 27, 2011 02:37 |
|
If any of you are interested in the post mortem, it's over at http://status.heroku.com/incident/151 . It's fairly through.
|
# ? Apr 27, 2011 05:24 |
|
So, is Ruby missing a 'case' construct or what?code:
|
# ? May 2, 2011 21:39 |
|
Bob Morales posted:So, is Ruby missing a 'case' construct or what? wuhh..what? http://www.techotopia.com/index.php/The_Ruby_case_Statement Am I misunderstanding your question?
|
# ? May 2, 2011 21:50 |
|
Bob Morales posted:So, is Ruby missing a 'case' construct or what? code:
|
# ? May 2, 2011 22:40 |
|
Just code from work. I don't know why they wrote it that way. There's also tons of IF NOT/UNLESS FALSE instead of 'if' as well.
|
# ? May 3, 2011 15:25 |
|
Bob Morales posted:Just code from work. I don't know why they wrote it that way. My guess is that it was written by C programmers used to using magic negative return values for errors.
|
# ? May 3, 2011 16:31 |
|
Pardot posted:My guess is that it was written by C programmers used to using magic negative return values for errors. Used to be a .NET/ASP shop, I guess. What are you guys using to find errors in your production apps? Here's what we have now:
|
# ? May 3, 2011 18:08 |
|
Try Hoptoad. It's really popular with iOS devs and they have Rails components.
|
# ? May 3, 2011 18:40 |
|
NotShadowStar posted:Try Hoptoad. It's really popular with iOS devs and they have Rails components. We're basically using gmail+filters based on the app causing them, and the type (javascript, etc). I think we're just hoping for something magical that will identify 'real' errors before the users do. I think what we really want is other sources of errors.
|
# ? May 3, 2011 18:51 |
|
You're going to have to be a lot more specific on 'magical sources on finding any potential errors' because what you're asking is as magical and existant as a unicorn. The only way you're going to be able to head off gremlins is to keep the project in scope, have good test coverage with a CI intermediate, keep people accountable. Essentially core agile techniques. And actually if you're a smaller agile outfit, user errors feedback are THE best source, because your turnarounds are supposed to be so short that a user stumbling on an error you should be able to get it fixed and pushed out to production very quickly. The fact you say that developers are ignoring errors getting sent to them is telling me there's a systemic development problem. NotShadowStar fucked around with this message at 19:02 on May 3, 2011 |
# ? May 3, 2011 18:57 |
|
NotShadowStar posted:The fact you say that developers are ignoring errors getting sent to them is telling me there's a systemic development problem. The problem is there's a few hundred a day so they get ignored, unless they start repeating. And they're probably things that should be fixed anyway. But they might as well be 'warnings'. Like I said, until a user contacts a CSR with something like "Hey, this page is showing up wrong" or "This button doesn't work on the site", we don't know about the problem. The bad thing is that when you have a CSR come up to you 5 times a day, you can't get other stuff done. Some stuff is application problems but other stuff is things like issues with certain browsers and/or general web stuff, that the devs don't need to be bothered with and I, or an intern can fix. CSS changes and crap like that.
|
# ? May 3, 2011 19:16 |
|
Bob Morales posted:The problem is there's a few hundred a day so they get ignored, unless they start repeating. And they're probably things that should be fixed anyway. But they might as well be 'warnings'. So quit being a baby about it: every morning, pick one, write a test, fix it, deploy it.
|
# ? May 3, 2011 19:40 |
|
NotShadowStar posted:The fact you say that developers are ignoring errors getting sent to them is telling me there's a systemic development problem.
|
# ? May 3, 2011 19:46 |
|
Just looking at those exception titles, that doesn't look at all like stuff that should be 'just warnings' but serious application errors that need to be drat well fixed. I had pretty big Rails apps that went for a good long while without a single exception thrown, and lots of other people do as well. Actually looking at the quality of the code you put up before I'm getting a better picture. There's some seriously wrong things happening at your outfit that need to change.
|
# ? May 3, 2011 19:47 |
|
Obsurveyor posted:My guess: No tests. We're going to have a meeting about this tomorrow, I think. I'll bring up the goal of 'zero exceptions'. I think the biggest problem is that we have ~15 apps, and they are all basically copies of the first app. The core application is the same but the 'gimmick' of each one is different. You're basically entering in information, but in one program you might be using a Javascript basketball court, one uses a Javascript 'blender' that you put vegetables in, etc. You have 'teams' of people and you record progress of eating vegetables/fruits, recording steps, exercise minutes, whatever the gimmick is for that app. So basically we'll have poo poo left over from one that doesn't belong in another. Or we'll update/fix stuff in one, but the other doesn't get the updates. I'd say that's often due to laziness, but some of the changes are specific to that app for whatever reason. For instance, yesterday a CSR couldn't remove a user from a program because the user model was trying to remove 'locations' from an exercise table, but this app doesn't use locations to track exercise, just minutes.
|
# ? May 3, 2011 19:54 |
|
Yeah, I have no idea how to get my shop to use tests.
|
# ? May 3, 2011 20:15 |
|
Trabisnikof posted:Yeah, I have no idea how to get my shop to use tests. So quit and go somewhere that does it right. There's a huge demand for Rails developers who want to do things the right way.
|
# ? May 3, 2011 20:21 |
|
BonzoESC posted:So quit and go somewhere that does it right. There's a huge demand for Rails developers who want to do things the right way. Where oh god I want to leave the midwest frozen wasteland where people can't stop using PHP
|
# ? May 3, 2011 21:25 |
|
Trabisnikof posted:Yeah, I have no idea how to get my shop to use tests. I've mentioned it before and there really is no interest in it. The one guy actually told me to not bother learning them because they don't use them, back when I first interviewed.
|
# ? May 3, 2011 21:44 |
|
NotShadowStar posted:Where oh god I want to leave the midwest frozen wasteland where people can't stop using PHP PM me if you're serious, at least one of my friends is looking for Rails people in Miami; they don't pay for relocation but here's a sample of our January weather:
|
# ? May 3, 2011 22:08 |
|
NotShadowStar posted:Where oh god I want to leave the midwest frozen wasteland where people can't stop using PHP
|
# ? May 4, 2011 03:23 |
|
I'm having some issues installing gems: when I try to install XmlSimple (for example; this happens for every gem), I run into this error:code:
code:
code:
|
# ? May 4, 2011 03:35 |
|
You could download and install the latest rubygems from http://rubygems.org/
|
# ? May 4, 2011 03:49 |
|
Okay, after going down that route, I'm lead to another error. Here's the output, after running setup.rbcode:
|
# ? May 4, 2011 03:53 |
|
Gee Wizard posted:Should I know anything about upgrading Ruby? Install, use, and love rvm and use ruby 1.9.2
|
# ? May 4, 2011 04:03 |
|
NotShadowStar posted:Just looking at those exception titles, that doesn't look at all like stuff that should be 'just warnings' but serious application errors that need to be drat well fixed. I had pretty big Rails apps that went for a good long while without a single exception thrown, and lots of other people do as well. Latest update: quote:I love that zero-tolerance idea. But "you have to fix this" conflicts with "you have to build that" where "this" is yesterday's app and "that" is tomorrow's.
|
# ? May 4, 2011 14:06 |
|
|
# ? May 30, 2024 04:20 |
|
I worked in a shop like that, where the pressure to deploy anything at all was interfering with my ability to make quality software. I went to the management and said, "my last day is in two weeks," and haven't looked back. If they won't let you make quality software, they deserve what they get, and you don't deserve to get stuck with it.
|
# ? May 4, 2011 14:19 |