If you like chamber music, this is a very nice string trio: https://www.youtube.com/watch?v=feOK6VidKI4&feature=youtu.be&t=28s
It was sort of a blueprint I started with in college for learning to write idiomatic music for a small ensemble.
It handles emojis in the timeline really well. Would be cool to have helm completion on emojis in the toot buffer...
I'm tooting from Emacs :laughing:
Emacs is still not great at async, so fetching new toots from the timeline is rough, but this is still neat!
Bless you Emacs and your `set-buffer-file-coding-system` function
Oh fuck now there's carriage returns in my bash scripts fml
Also: BAT files are the worst. Jesus.
Instead of finishing exception handling I figured out how to find `devenv.exe` and pipe its `/Build` output into Emacs ๐
It's slow to start up. A "handmade" build.bat would be faster, but I much prefer using GENie
I've done similar things before, but now I'm slowly parameterizing bits of it to be relatively easy to setup for future projects instead of cobbling a half-working form of it together each time.
Relevant:
http://lucumr.pocoo.org/2011/12/22/implicit-scoping-in-coffeescript/
I can't believe a lot of Atom was originally written in this language >_<
I've been waiting for Bob Nystrom to put out the next chapter of Crafting Interpreters, so I go check his twitter feed today and see this thread started by the creator of CoffeeScript:
https://twitter.com/jashkenas/status/870301410679717888
I cannot get behind this dude's mindset about language design.
Guess what this compiles to without warning in coffeescript:
```
x = 42
dbler = (y) ->
result = () ->
x = 2 * y # oops reused x
return x
return result
```
@borko @hisham_hm I keep trying to politely hint that Unix people should look at Microsoft PowerShell to see a piping environment and system shell done *right*, but nobody seems to understand or care.
Hint: It involves being able to pipe *objects*.
Second hint: It involves objects whose fields can be added and removed at runtime.
Third hint: No, neither Perl nor Python come *anywhere close* to touching what you can do with such a facility.
Lead: "Your fix didn't work at all!"
Me: "Really? Hmmm. <checks github> Well, uh, you just blasted my changes to the file that made everything work when you merged and pushed."
Lol apparently java just copy-pastas finally blocks after every catch
Can't tell if I'm getting better at formulating IRC questions, or if people on freenode#proglangdesign are just particularly courteous ๐
Some yak shaving brought me to comp.lang.c where I saw someone who's like a wholesome version of Terry Davis. Has a grand religious quest to build computer systems soup to nuts in god's name, but also chastises people who are rude to newbies asking questions.
Here's part of one of his responses:
"You don't have to dip into the hate-laden waters of sidelong passive-
aggressive insults. There is another way to be. You'll find it's a much happier, and much nicer way than what you're used to. "
I read the Joe Duffy blog post on error handling in Midori, and they ultimately settled on semi-checked exceptions. It seemed to be not totally terrible, but still required static types.
I'm not against adding types to this thing later, but this is still new to me and dynamic typing seem easier to make work for babby's first language.
I'm making a piddly little dynamic language, and deduced that I just need to byte the bullet and implement exceptions.
Is there any other reasonable error handling mechanism if you have no static types?
Reminder: The suggested price ($4) is just that. If you're broke and just want to play a game DO NOT feel weird about grabbing it for free. I left the option to get it for free there by choice so you could use it. ๐
If it makes you feel better about it. Your feedback is worth more to me than the $3.60 I'd get if you paid.
That said, paying is super nice too, if you can swing it. ๐ธ ๐
Greenlight votes are also super cool. ๐
Explaining Wookiepedia to my cousin because she just got job at Hasbro designing Star Wars toy packaging. The lyf
Our main Vehicle script has this horrible attribute called RacerType, which conflates 3 things: whether or not the vehicle belongs to a human, whether or not the vehicle is networked, and what is currently controlling the vehicle (player input vs net events vs AI)
Don't do this to yourself
#programming language design question: are exceptions (or *conditions*, if you really wanna go there) the only realistic option for error handling in dynamically typed languages? Feels like error codes and/or multiple return aren't enough.
(Dynamically-typed -> e.g. dict-oriented langs like JavaScript, Lua, Python, or Self)
I'm working on one, and I've been punting on error handling, but I should probably do it soon so that "42" + 42 will report an error instead of just __debugbreak()'ing...