Glad to see this showing up every few years. After its initial launch, I think I helped the creator add the localization and lightspeed features: https://joshworth.com/updates-to-the-solar-system-map/
...and we eventually met up and had lunch.
104 karma · joined March 6, 2013
...and we eventually met up and had lunch.
The formal language specification came fairly late in AS3's useful life, but it also describes the syntax: http://help.adobe.com/livedocs/specs/actionscript/3/as3_spec...
> [Jordyn Castor] was a driving force behind accessibility on Apple's soon-to-be released Swift Playgrounds, an intro-to-coding program geared toward children. She's been working to make the program accessible to blind children, who have been waiting a long time for the tool, she says.
RMS's response was:
> These MIT professors ought to know better than to smear us hackers by using the word "hacker" as synonymous with "security breaker".
It's been a while, so I'm not completely sure this is true, but I think any XHTML within an XSL document also had to be valid XML (that would also validate against the XHTML schema), so you couldn't get away with as much as you could with rendering a plain XHTML page.
> I have a working prototype of a JavaScript VM that is highly optimized for NGINX’s unique requirements and we’ve begun the task of embedding it within NGINX Open Source.
Oh neat. I don't recognize your username, but I submitted the first entry in the logo contest for that library in 2008, which ended up being fairly close to the final logo.
> Flash is certainly alive and well.
There's plenty of developer activity, but I'm pretty sure Adobe only has a life support team maintaining most things now.
AS4 was cancelled, so Falcon was the last notable language change. Most of the AoT iOS/Android targeting stuff was completed years ago, so now AFAICT it's just being kept compatible with new releases.
FP12 was supposed to be a huge jump, but now 12-17 (and the accompanying AIR APIs) have come and gone without pushing things forward meaningfully.
This suggests to me that the most anti-sloppy languages like Rust would benefit the most from sloppy input inference techniques. Has anyone been working on developer tools to make writing Rust code easier? (Lifetime management is the obvious new language feature to target.)
[1] http://groups.csail.mit.edu/uid/other-pubs/sloppy-programmin... (pdf), or less-detailed: http://groups.csail.mit.edu/uid/projects/keyword-commands/in...
I think companies like Spotify end up spending 60-70% of that $12 on paying license fees, which include per-play amounts that eventually end up with the artists. And the structure of those deals is such that the groups with the biggest licensing deals get most of your $12, even if you didn't listen to music from that particular artist.
I agree that it's not what you (or I) want, but it does make sense from the perspective of the largest parties involved in these negotiations.
Yeah, I think that's probably the most common motivation behind the interaction spotlighted in the article.
> Here's a sample interaction between an experienced programmer and a beginner who is just learning programming
I think the interaction happens between programmers of all levels of experience, but it might be most harmful when it's an experienced programmer talking to a beginner.
> It does get discouraging as a noobie when you hear people in forums throwing around the latest tech jargon and some esoteric C library just to show-off how much they know more than you.
If that's really their intent and if you (the noobie) are the one they're talking to, then sure. If I'm a noob walking deep into a HN thread on an esoteric C library, I'm probably not going to be discouraged that people are using jargon, unless I've identified myself as a beginner and the comments are replies to mine.
Including some aesthetics-stretching cases seems like a fairly honest/transparent thing to do for an open-source project that someone is blogging about.
> It breaks the semantics of what the underline means — any bit that's underlined is supposed to be the link, and if it's not underlined it's not a link.
That's a reasonable way to look at it, but humans like us can be pretty flexible with semantics, thanks to pragmatics. If I see a link that covers most of a set of letters stuck together without a space, I tend to assume that the whole thing is a click target. Even if my assumption is wrong, my clicking error rate probably won't be too high, since I think that people tend not to hit the edges of pointing task targets.
Brownie-wise, I would wait a while because lunch would fill me up. But at 3 or 4 pm, I'd be hungry again and something the size of a brownie would really hit the spot.
I don't dog-ear book pages, if that makes you feel any better.
I like brownies better when they're warm, so I came up with a few ways to warm the pre-packaged treats while still sitting in my office. I first tried sitting the brownie atop my laptop charger: http://images.reclipse.net/warmed_brownie.jpg
This worked fairly well, but the charger was less hot when my laptop was at 100% charge, so I sought alternate methods for heating up the brownie. For some reason, I had stumbled across some recent WebGL demos at the time, and noticed that the fan on my laptop would spin up on that particular demo. (http://madebyevan.com/webgl-water/)
This provided a more consistent heat than the charger, since usually my laptops would be completely charged by the end of lunchtime. I had my own laptop and a company-provided laptop, so it wasn't hard to set one of them aside as a brownie warmer.
- Advisor wanted a one button way to run a convoluted research prototype I had made, and I didn't want to have to dig into Cocoa to figure out how to programmatically click/select options in a few desktop apps.
- Worked at a company and there was silly employee training slideshow+quiz, so I had Sikuli wait for the next arrow to show up once the audio was finished and click it.
- Wanted to heat up my GPU to warm a brownie, so I opened one of those WebGL water demos and had Sikuli repeatedly pick up a ball and drop it in the water.
One reason may be that large companies want ownership of a modern, C#/Java/Go-like language [1]. I was an intern at Adobe when it was trying to develop such a language (ActionScript 4) + VM, and a primary reason not to adopt an existing language is that they wanted control and to be free of legacy baggage as much as possible. Obj-C is reasonable to use today, but its C and Smalltalk underpinnings sometimes feel like anachronisms for people writing App Store apps. This is probably especially true if you're a language designer like Chris Lattner at Apple and are tasked with fixing the most prominent pain points that your language users face.
[1] I realize these are somewhat diverse languages.
There were public betas available about 6 months after the acquisition, which didn't leave Adobe much time to change anything. Even the main APIs, like those in playerglobal.swc, almost all have a copyright stamp of 2005 in them.
Le and Gulwani's paper does cite Little, but the refutation is a bit weak.
> Little and Miller propose a code completion tool that synthesizes the most likely Java expression in a code context from a set of keywords [23]. Smart-Synth is different, in that it synthesizes a complete script and does not require extra contextual information.
From the video, a "complete script" appears to be 1 or 2 simple expressions. And not requiring contextual information sounds like it can't take advantage of contextual information.
Getting a bunch of fresh IPs might be trickier, but you could probably wander around different WiFi access points, use the CSAIL OpenStack installation, or maybe just renew a DHCP lease a bunch.
User-agents a easy to find and change with a browser extension (or scripting).