Japanese learning has a second valley, I just found. It’s the point when you realise how full of homophones the language is, and that like half the words you thought you were picking up in spoken content (or music) may not mean what you thought they did, and you won’t know for sure until you have enough vocabulary to understand the context around them. And that’s just content without intentional double meaning, which is an art form in Japan!
Why, yes. Yes, I am a character designer that works in the game industry. How could you tell???
… it’s very impressive you could notice without even seeing the boobs or the “armour”.
Refreshingly different. It’s nice to not worry about saving or tabs anymore, just tell it what file you want. It feels more like all files in my project are open in background tabs, than none. It doesn’t (yet?) have so much of an ecosystem, so it lacks some features I’d like — especially Stylus syntax — but it’s a solid editor.
Especially liked: the new take on files. Built-in preview panes. The installer contains 3 files; not quite as good as a system-integrated .deb, but you have to appreciate the no-nonsense approach. The “save when blur” approach is a beautiful match for Meteor; I do some coding, then switch my focus to the browser, and just have to wait for things to reload without any further action from me.
similar-but-different problem as with Atom; I don’t know how it decides where’s my project root. It does seem to index a reasonable set of files, but how? Also, it indexes a lot of stuff I don’t need, notably .js and .css files built by Meteor; I tried the blacklist options but it took some effort to get it right.
Final verdict: this might be The One, but possibly it’s not quite mature enough yet…
Update (June 14th): I don’t know where my brain was when I wrote the “dislike” section above. Obviously, it’s a project-centric app, and each window is a project; you choose the project root when you open the window.
So yeah, it kind of does have the same problem as Atom though, in that I can’t open a file from outside the project e.g. to read/reference or copy code. There’s a more native version coming up, based on node-webkit, and now that’s what I’m running here; with that it’s possible to open arbitrary files from the command line, but not the UI (yet).
This is currently my main editor. I still feel it’s not quite mature, but it’s really nice and I feel it has the potential to speed me up a bit more.
This thing feels quite polished, clearly has momentum, and a nice ecosystem of add-ons. Unfortunately my workflow requires tons of tabs, and there seems to be no way to navigate to other tabs using the keyboard, so that became a show-stopper really early on and I couldn’t evaluate too deeply.
Especially liked: embedded terminal (handy to run my meteor app on a tab, rather than keeping a separate terminal taking precious screen real estate). Installer can build a .deb and installing that gets the app neatly integrated in my system, with launcher and all.
Especially disliked: bit of a project-centric design, each window is operating on one folder, and opening a file outside that tree automagically opens a new window. You can move the tab from that new window to the old one, but closing the new window closes all tabs that originated there. If the first file I open is not at the tree root, trying to open something else will also cause a new window; so probably the best is to start the window by opening the folder itself. Being a Github (the company) project, you’d expect it would traverse the tree up looking for a .git at least, so it would guess where your project starts?
Also for such a project-centric design, it’s surprising that it doesn’t save a project and/or workspace when I close it, so that next time I can pick up where I left off.
Final verdict: good-looking but I’m not sure it fits my style/workflow. That may change though.
The Time Lords are trying to come back, using a leftover plot point from the metaplot of a previous season, but if they do come back the whole universe might be destroyed. A former enemy (who just had a big origin explanation/retcon) joins forces with the Doctor to prevent disaster, and a former companion hated by many fans and loved by others makes a cameo. In the end the Doctor regenerates, although the regeneration takes much longer than has been previously established, and sends the TARDIS crashing, as a cliffhanger for the next Doctor’s first episode. Oh, and the Time Lords do *not* come back.
That was not the best episode, but a nice enough, worthy sendoff for Tennant. Looking forward to the Matt Smith era!
Oh wait… damn wibbly wobbly timey-wimey writing.
I don’t usually share chain posts, but this is really great… I always wondered how this is done.
(via Luciano Ramalho)
(and therefore of course also Game of Thrones ending)
This is all speculation, but I’m like 96% sure, so I’m putting it below the fold :-)
Read more …
IMO, closing down an airport because people who leave nearby complain of the noise is civically backwards and a shit excuse. I mean, the airport was there first, and you moved in knowing that full well, no? One of the few things that irk me in Germany is this knee-jerk anti-DDR tendency to put the whining of the few over the needs of the many. What about the people who live near Tegel and want the airport there? What about the stupid farce of Google Street View where business lose customers because one idiot in the building above didn’t want their Balkondekor viewable by all? It’s silly and we all lose.
Reposting this here so people can see it without logging in to Facebook; photo by Justine Lera. This absolutely disgusting excuse for advertisement for a bar was seen in Schönhauser Allee 10, Berlin, this morning. If you’re in Berlin or planning to come here soon, mark the name and place and make sure they never see your money. If you have the time, file a complaint.