Yeah, this is still at the top for me. Moving it along! I wonder how far it would have to go before it starts having problems. Or before apps start having problems. Doing this from my phone, and the comments are starting to get fairly difficult to read.
Have music services really fragmented yet? I seem to remember some larger artists trying that, but I don't recall it being successful.
It's pretty rare that I can find something on Spotify that isn't on Google yet (or vice versa), and even then they usually catch up to each other eventually.
Empathy aside (which I agree is quite depressing), I've seen enough videos where multiple officers shout conflicting commands (put your hands up / get on the ground). In that case, it's impossible to comply. What do you do then?
And then of course there's the implication of "comply or die", which is also a huge problem on its own.
Not to mention you probably want to pick it up last, so it stays colder longer. This way you don't have to carry milk around the store while you look for all the other items you need.
Although, maybe that's an argument for putting it by the checkout lines instead, which I suppose are by the entrance. Hm.
Thats disappointing. After visiting, I found I really enjoyed both Sweden and Norway, and wouldn't mind moving there someday. Sounds like that may be difficult.
It's the worst when the automatic restarts kick in again, but you're stuck behind an update that consistently fails at the same point. Super frustrating.
When I was learning assembly, one of my favorite things to see was what assembly got generated (more or less) from really, really simple higher level application code (C, C++, etc). Code consisting of really simple arithmetic, loops, function calls, object creation, etc.
For real though, the difference between 60 and 144 is night and day. I can't go back to 60 after playing with 144. I wonder if going beyond 144 would have the same effect.
Does it touch on mixing / mastering at all? I have a suspicion that some of my friends will be looking to me to put together some demos in the near future, so I'd be very interested in some beginner/intermediate knowledge around that.
Isn't reference counting just a different style of garbage collection? I see lots of articles saying that swift both is and isn't garbage collected, and I'm curious what the proper answer is here.
I don't find myself actually using gradual typing though. Not very often at least. Even in prototypical stages of an application, I usually just put together the types of what I currently have, even if I think they will change later.
I'm pretty sure whitespace in F# is one way to control blocks. So anything further indented than an if is part of the if block. I'm definitely not an F# expert though, so I'm sure there's more to it than just that.
I also think there's a way to write F# that doesn't have significant whitespace, but uses a lot more keywords. Verbose syntax, I think that's called. I almost never see examples written that way, though.
You mean in general or specifically for PostgreSQL? Ctrl+c definitely works in cmd in general, which is what my original post was referencing. I use it all the time.
Not sure about for PostgreSQL in cmd off the top of my head (posting from my phone). I suspect because I got down voted that it may not work there.
Saw an interesting viking museum in Norway that had a skeleton of a man who had his leg shorn off by an axe in battle. That one may be a bit more obvious I suppose, but I suspect there's a ton you can learn from just a set of bones.
It really bothered me in python, but for some reason I didn't mind it in F#. Of course, some of that may be related to the fact that I enjoyed F# so much that I was willing to put up with significant whitespace. Or perhaps it's just been too long since I've used python and today it would bother me less.
Don't they still have to wait for the spec to finalize / hit stage 3?
Don't get me wrong, I'm super excited for this functionality because I love it in languages like F# and Elixir, but it looks like the pipe proposal is still stage 1.
You could use vbscript for, well, scripting. Essentially taking the same position / purpose as batch files on windows. Pretty sure that still works. I wouldn't do it anymore, personally, but I'm almost positive it's still functional.
Working out before going home works great for me, too. And it has the added bonus of helping you skip some of the traffic on that commute home by pushing the start time of that commute back a bit. Depending on where you live and when you work, I suppose.
That looks pretty awesome. Thanks for the suggestion. Looks like it gets to a good amount of functionality too, with first class functions and closures and the like.
I worked on an application which was essentially a multi master, offline capable, synchronizing app that utilized websql heavily. Websql wasn't perfect (it was essentially an old version of sqlite, I think), but as a whole it worked pretty well. Was sad to see it die.
You are allowed to use both event and element, as they aren't strictly reserved keywords.
I think it's generally frowned upon, though. For example, I believe "event" is defined as a global in browsers (on window, perhaps?), so you run the risk of shadowed variables and accidentally referring to the wrong thing.
I didn't have too many problems with typescript and ramda. I occasionally have to explicitly send in types to the first function of a pipe, which is a little annoying, but for the most part it seems to just work for how I use it. What problems have you run into?
The music is phenomenal. Soundtracks are floating around on YouTube and such if you don't have time to play the game. I found it great to listen to while working.
I'm in the same boat as you. Error handling and code generation (to support the lack of generics) in go always left a poor impression on me. I ended up going back to node for work, f# or typescript for personal projects.
These two changes alone are enough to get me to pick go back up.