I just don’t know how to.

Fritzpatrick: I guess even nazis like funny jokes

Lamie: Tejasmanohar: the p****r reports an unexpected token because it read ‘await’ as a name, so it’s expecting or or . or + or the like, not another name or ‘this’

Lamie: And of course it reads ‘await’ as a name because it’s not in an async function

Lamie: For backward compatibility

Gargano: Do a lot of libraries use exceptions?

Cawley: I don’t feel like i’m using them commonly, they are just debugging help

Galen: Meaning try/catch is not a normal thing to me

Lamie: What would you do instead?

Kimple: I nearly never use try/catch

Kimple: I dont like it. it makes code harder to reason about

Gardino: Well Lamie i just feel like it doesn’t come up. like an exception isn’t something that i’d want my code to recover from

Pullian: Though i suppose if you’re working with databses and stuff and there’s an off-site error, you’d want a try/catch

Rybak: Obviously it’s not like oh the database is off, well ****, ok i’m out

Kimple: I dont mind it so much if its localized but it has the effect of requiring you to apply nonlocal reasoning to your code

Kimple: Since now when you call a function oh hey it might actually return from you

Jorge: Tcsc: when i first played with it in java like 10 years ago it seemed alright. it seems to fit a lot with java paradigms

Marotto: Maybe for exactly the erason you just stated

Dickensheets: In java you pretty much EXPECT an exception

Kimple: Its a real cluster**** in c++ too since it basically means theres now yet another difficult to avoid cl*** of errors that your program can be vulnerable to

Hausler: Golang seems to deal with it by having multiple returns

Kimple: Thats the sane way to do it i think

Kimple: If i need the extra information about why its an error i return { error: ., data: . }

Larzelere: It’s weird because i was reading someone saying that was a stupid design decision because the data will be meaningless and you’ll have an error. yeah that’s called typing though, how else would you deal with it? you can’t place an error into a memory container expecting something else

Baker: Is there a tutorial that can show me how to “scan” a folder, find all jpg

Kimple: Usually i dont need it and can just return null and maybe log something or draw some error visual thoguh

Theroux: S in that folder and add the url location to an array I have access to?

Kimple: Idk. i think multiple returns solves most of the issues with error results

Furby: I mean, i’m not saying there aren’t a million ways to do something, but go has a level of tradeoffs. lot of people don’t like gc and sees it as antithetical to the purpose of most of other go’s tradeoffs though

Kimple: Probably tagged unions or whatever fp people call them is better though

Dorce: And i can understand that

Truehart: Is there a best practices for scanning all the images in a folder, getting their paths, and returning those paths into an array for access to each url to the image?

Mozzone: Claytonzaugg: node.js or browser?

Spielman: Can’t be anything else but Node

Spielman: Claytonzaugg: Try the node.js channel

Kimple: Dash: i’ve never written anything with it, but it seemed sanely designed

Tin: It’s actually for meteor

Layman: Rcyr: the way he’s describing it, yeah, but it’s possible he’s trying to do something like it on the browser because he thinks he has file access. in which case we could feasibly help him “emulate” that

Brieno: Claytonzaugg: is this in your public folder?

Spielman: Tcsc: Yup, no generics in a statically-typed language in 2015. seriously

Rulapaugh: Can a variable be defined for an ajax response?

Lamie: Kamuela: http://nedbatchelder.com/text/exceptions-in-the-rainforest.html

Stidstone: I just don’t know how to access them, so I can then populate the images on a page