skysight-inc/HackerNews huggingface dataset:
Skipjack was designed using building blocks and
techniques that date back more than forty years.

I think it's safe to assume they have much stronger stuff now.
Agreed. The post title is wrong, it should read "Another iptables frontend, this one aims for all distribution."

And yes, real men use iptables directly. I never understood the need for wrappers, just makes it harder to debug and see whats really going on.
It just seems so foreign to work on something that you might not get to see operational in your lifetime :(
Is this something people even want in content driven sites though? Imagine reddit in real time, it would be a mess and impossible to keep track of what you last read.
What's your rate per hour?
Obfuscation to name one. I don't see any enterprise moving to a platform where you can't protect your code from prying eyes. Although it's not inherently a language problem per se, (it could be solved by browser technology) it would help a lot if the language could be compiled.
They're restricted to only escaping currently active stack frames, not jumping anywhere like full continuations. They're basically equivalent to having a default cascade of

if (ret == -1) return -1;

after every function invocation, which is why I was calling that aspect a syntactic feature.

It's this implicit return after every function that trips people up (when prematurely exiting from stateful computation). So what I was saying that making the call of an exception-throwing function (slightly) more verbose would alleviate that and pay for the complexity where it was used.
"shire reeve" -> sheriff

Well I'll be. That is so cool. Thanks!

http://www.etymonline.com/index.php?term=sheriff&allowed_in_...

Edit: Allow me to repay in kind. Did you know that rhubarb is called "rhubarb" because the Greeks thought only barbarians would eat it?

http://www.etymonline.com/index.php?term=rhubarb&allowed_in_...
I think I'm going to vomit if I see another web page written in the 21st century that condones the use of ICO format.

Please, please, please can we have some kind of multi image PNG format ?

How about multiple PNG images wrapped in a TIFF container ?

With cross browser support, pretty please.

Anything but ICO. ICO format is nasty.
Javier Pérez - EN PUNTAS
Progressive Enhancement is still important for CONTENT SITES

Why? Search Engine accessibility.

It used to be that Googlebot wouldn't find content loaded asynchronously, or links that rely on Javascript. Now it's different - You can confirm that Googlebot discovers a lot of Javascript links using Webmaster Tools: https://www.google.com/webmasters/tools/home?hl=en

BUT - There's still no way to break from the "Page Paradigm" - Google needs URLs to send searchers to. They don't yet send people to specific states of a page. That's why I still use Progressive Enhancement, it forces me to ensure each piece of content has a URL that points to it.
I agree with all of his points. I think a lot of the counter-arguments are centered around "Yeah, but I see websites that unnecessarily use Javascript when a simple text-based solution will work". That's not a Javascript problem; that's a site-design problem.

I'm sure you could make a dynamic page that has a negligibly different loading time compared to a static page that both display similar (static) content, but it's the way that you do it that matters. Loading a page, that loads a library, that pulls in another library once the page is loaded, that then displays spinning gears while pulling in a bunch of static content is of course the wrong way to do it for a lot of things. But that's a design problem.
Reflections from London skyscraper are reportedly melting parked cars
Javascript-dependent content _can_ present problems for search engine accessibility
The vast majority of cost of the project goes towards building the track (through the mountains, 60% of the distance will be inside tunnels). That investment will probably still be useable when train technology improves.
This Is How ClearView Works
A walk through as to how ClearView™ Dashboard can Accelerate the Meeting of your Business Objectives.
That depends on whether the rumor is a subset of the truth. Sometimes true, sometimes not.

Truth: Joe Smith has never beaten his wife.

Rumor: Joe Smith no longer beats his wife.

There's some truth in the rumor, but no rumor in the truth.
This post does nothing to address the biggest reason people might have Javascript disabled: security. If I'm browsing through Tor (or whatever), I'm not going to turn on Javascript to use your site. If your site doesn't work without it, you've lost a customer.

Granted, people who disable javascript are obviously vastly outnumbered, but just saying "fuck you" to security conscious (and most likely tech-savvy) users seems like a mistake.
Nor do they 'Merican history.
Not 2000, in antiquity, they only earned some laurel (and it was as common as today). Gold and silver medails started to be given 150 years ago. But now it's finished, they only get worthless gold plated medails, plus e sponsorship deals.
Surprising views of startups on fundraising
We asked ~60 startups their fundraising experience and got some surprising results.

1. 40% startups raised money from angels, 30% from friends/family, 15% from VCs, 10% from accelerators and 5% still deciding. This is against popular notion that friends/family contribute more than angels.

2. 50% startups pitched to <5 angels/VCs, 30% pitched to 6-10 angels/VCs and 20% pitched to >10 angels/VCs. This too is against popular notion that one needs to pitch to many angels/VCs.

Is this variation because we have emerging market startups too in the respondents?

You could also please share your fundraising experiences at: http://bit.ly/18aFwFC
Which is silly. If I'm just trying to view a news article from yesterday or a year ago, I shouldn't have to worry about what some silly script is trying to do.

If the core of the content is or should be text, then there's no need for countless silly layers around it.
This author is making an assumption that progressive enhancement exists only so that people who are browsing without Javascript can have a better experience. Of course, this isn't true. Progressive enhancement is a good thing because it encourages you to be as descriptive as possible at every layer of your technology stack.

Why does it matter in practice? Well, there's more than one reason, but consider that not every user agent is a browser with a person sitting in front of it. Your website also should be interpretable by content indexers like search engines, accessibility devices like screen readers, and so on.

Some services don't fit this model and really are better off being designed like desktop applications written in HTML and JS. But in my experience, most services can be modelled more like websites without making the design any more difficult to reason about, and almost all users' experiences are bettered by it.
Not to mention stuff like accessibility that ends up being an afterthought for a lot of people.
Five Forces Fueling FrontBack's Fame
The Bookstore Goes On
Even with BI guaranteed to all, not everyone would receive it because of income tax withholdings.
How many cases has english? While there are some artifacts like "whom", "I" vs "me", about two.
Even with the fact that planes fly slower now than in the 60s, I'll gladly fly DEN-SFO. I can be finishing dinner in Palo Alto when you're in the Salt Flats.
> Don’t be ashamed to build 100% JavaScript applications. You may get some incensed priests vituperating you in their blogs. But there will be an army of users (like me) who will fall in love with using your app.

We all want wonderful experiences as users. The crux is almost a question of "how we want things to be" and "how we want to get there".

For me, the 100% JS MV movement is wonderful for a specific genre of app: An app that is:

* Behind an intranet

* Behind a paywall

* Behind a login-wall

* Prototypes / Demos / PoCs / etc.

But for the open web -- wikipedia, blogs, discussion forums, journalism (etc.) this movement detracts from the web as a whole, in that it excuses developers from having to worry about degraded and/or non-human consumption of their websites' data.

We have to ask ourselves what we, as humanity, want from the web. Do we really want a web of 100% bespoke JavaScript MV web-apps with no publicly consumable APIs nor semantic representations? If that is the intent and desire of the developers, designers and otherwise educated-concerned web-goers, then fine, let's do that and hope it works out okay...

But there is an alternative that has its roots already planted deep in the web -- the idea and virtue of a web where you can:

* Request an HTTP resource and get back a meaningful and semantically enriched representation

* Access and mash-up each-others' data, so as to better further understanding & enlightenment

* Equally access data and insight via any medium, the latest Chrome or the oldest Nokia

So, please, go ahead and create a 100% JS front-end but, if you are creating something for the open web, consider exposing alternative representations for degraded/non-human consumption. It doesn't have to be progressively enhanced.

Imagine for a moment if Wikipedia was one massive Ember App... And no, Wikipedia is not an exception from the norm -- it is the embodiment of the open web.
I was skeptical, but I found a lot more than I thought there would be.

GTK+ & Javascript == https://wiki.gnome.org/Gjs

Windows app store:
http://msdn.microsoft.com/en-us/library/windows/apps/hh77084...

Qt 5 is moving this way as well:
http://arstechnica.com/business/2012/04/an-in-depth-look-at-...
My Opportunity - John Divramis Internet Business Blog : Paramarketing
If this site was made by a male you wouldn't even see it on the front page of HN.
(=ｘェｘ=)
AppleScript works like this. When you save a script it's compiled down to a system representation, and when you reopen it it's transformed back into the english script language. This means:

* Formatting isn't preserved and the file is retabbed each time you save it.

* Earlier versions had French and Japanese compilers/decompilers

* Each application can add AppleScript syntax (like VBA/OLE or whatever). If a script uses commands for an application you don't have installed, you see the raw FourCC codes in the code instead.

It's actually a quite interesting language. http://en.wikipedia.org/wiki/AppleScript
I've thought about this.

If I have a blog or similar media site, and require javascript, I might offer a 15/month option to allow access to a text only interface and an RSS feed. No graphics, no pictures, a very simple link and text interface.

And the moment I start seeing subscriptions coming in, I'll believe in progressive enhancement again.

(Progressive enhancement doesn't affect me as an application developer in the web space. But if it did...)
I think that English words tend to be very short; so in English one has to type less - having concise commands is an important feature for a programming language;

I don't know if it is an urban legend: I read that in English the length of a words is shorter than in Japanese; so in WW2 the English language was better for shouting out orders - less time for communication means more time for action;
Moreover, it's skewed by which disciplines tend to publish in arXiv, as opposed to more traditional venues, ie conferences and journals. Physics has always been the main mover on arXiv, computer science surprisingly (?) rare.
Thanks for the feedback! I was having a bit of a debate with myself on whether or not I should keep the font, since the punctuation kind of bugs me, so I'll definitely look into that.
"primary web server" is the key word. Seems like they were clients though.

We support RSF. We do not support Bahnhof exploiting the privacy and goodname of their clients for marketing purposes. - Wikileaks
I don't understand the problem with the <center> tag. It does the job and even though its deprecated its a long way away from being unsupported.
First, the accessibility argument is a red herring that I'm getting frustrated people continue to try to throw around. Screen readers support JS, okay? Let's put this argument to bed.

http://words.steveklabnik.com/emberjs-and-accessibility

Okay, thank you for letting me get that off my chest.

Second, one nice thing about "embracing 100% JavaScript" that I talk about in the post is that it requires you to implement a really solid JSON API, because your web site is now a true client that consumes an API. This makes it really easy to integrate with third-party services that consume your content. I agree that putting content behind JavaScript sucks; I'm just advocating that the content be JSON (or some other normalized format), not HTML.
http://www.jonathantneal.com/blog/understand-the-favicon/ this is really related and clear!
Not quite the main point of the article, but this stuck with me: "I don't know most of the words needed to refer to objects you find in a kitchen for example"

I grew up in the Soviet Union; I learned the names of trees, and birds from my grandma, and the names of tools in a shop from my dad. We emigrated to New York; It's been 20 years; I am fluent, I speak with a slight accent, but no one ever claims they can't understand me; yet, only now, barely, have I started to learn things like names of birds, trees and tools. I, of course, don't mean the basic ones like "owl" or "pigeon", or "wrench" and "screwdriver", but things that are slightly more obscure like "bluejay" or "vicegrip" eluded me for a long time.
I highly recommend you check out Bootstrap[0], especially since their recently released version is mobile first.

[0] http://getbootstrap.com/getting-started/
unless it's a 6 years old.

Which says a lot about how sexism works both ways :)
(Sorry for the late reply) I spent too much time over the past few months putting a budget together, and I'm about to head back to school to finish the last year of my degree while working, after which I'm likely getting married, so I'm being frugal. My response to my car crash was, "get through this spending as little money as possible. Also make going without a car hurt so that paying for rental car coverage next time is easier". I also thought the ordeal would be handled by my insurance by last Friday, but the police report hasn't been finished and is holding everything up.

As for the laptop, I've got a Samsung Chromebook (the small, ARM one) running Ubuntu and I recommend it. It's ARM, which makes getting things running a bit hard, and it's not the beefiest, so if you want to wait for the new ones this year that will likely be x86 and beefier for $250, you can do that too. I don't take it on the bus though. That was the first bit of advice I got from someone else on the bus.
Accessibility is a red herring. JavaScript apps work just fine with screen readers, especially if you support WAI-ARIA.

http://words.steveklabnik.com/emberjs-and-accessibility
Grammar does differ, though, in subtle ways that don't necessarily impede communication but that mark the speaker for region. The participle gotten is probably the most prominent example; it is essentially unknown in most British English varieties and tense construction has more irregularities in British English than it tends to have in US English. (We Canadians speak both and neither, and nobody really knows the rules from day to day. They change on a pseudorandom sort of schedule covered by the Security of Information Act, and those in charge will neither tell us what's going on nor reveal their identities.)
Strongly agree. The day that merely reading Wikipedia requires JavaScript will be the day that the open Web is dead.
yes, cultural differences and training are important for sporting success. this still can hardly explain the pattern pointed out above...
i m still opening a dozen tabs and reading them whenever i want, unfortunately most newer js only web blogs such as inc mobile, end up having a lot of errors and white pages..

i understand your newly found js excitement with your full ember.js app, but do'nt forget the lessons from java the browser plugin and flash.

1. ok you re real time, but don't assume i m watching your site like a tv

2. dont consume my precious cpu power.. otherwise app throttling will come to browser tabs..

3. dont end up in lots of clientside errors due to various problems, including local storage.. twitter mobile client is an abysmal example where tweets are lost on screen and inc mobile is another with empty ehite pages
Ugh, once again Marco succeeds in making Apple's way look like the only way. Here's two reasons why Marco and especially that hack Gruber are both fantastically deluded:

1) Nintendo is the Disney of Video Games. Lots of companies make cartoons & there's tons of theme parks, but there's only 1 Disney. It's a seal of quality, of fun, of playability. Nintendo's reputation, and the consumer mindshare is in this.

You fill yours and your kid's shelves with Disney books, movies, and Nintendo video games and other assorted merch. A $500 very breakable phone with a $100 a month of data services for my 9 year old? I don't think so. A $130 handheld with a few games he's earned from doing chores that he can beat around, drop and otherwise drag and kick around is where it's at. Sure you see the occasional bored kid at a family dinner using their mom's phone to play angry birds. But you see 20x as many with their Nintendo xDS playing Mario Brothers.

Nintendo generally makes lots of money by using slightly older technology to make this year's great new gaming experience. They've survived generations of very competitive onslaught. They've never targeted the high end gamer...from the beginning.

"Nintendo needs the profits of the high end" is quite simply, incorrect. Nintendo profits from pretty much every unit of everything they move. And on top of moving games and systems they have a substantial merchandising business probably second to only Disney.

The only surprise is that Nintendo hasn't been able to get into theme parks and cartoons in a bigger way. A Disney/Nintendo cross licensing for characters would be amazing. Bring your kids to Walt Disney <insert park>, your daughter gets to meet all her princesses and your son gets to hang out with Samus and Mario.

2) "But but but", Marco argues, "people are getting used to paying <$10 for a game". Yeah, but those games suck compared to a new Mario title. But let's say that suddenly amazing $4 games started coming out.

Let's play a game, given that kids abuse systems so badly and selection of Apple handhelds is...limited. Would I rather buy a free/cheap Android phone for my kid to abuse or an expensive and fragile iPhone? I can guarantee it would be the one with the lower replacement cost, especially after the first couple phone go in the toilet or down the stairs.

But let's be serious, there's zero possibility that Nintendo will go the way of Sega in the next generation or two. They dominate handhelds in a way Microsoft used to dominate the desktop business and the WiiU, while a technological disappointment in some ways was a carefully calculated system designed to ensure that the big N never lost a dollar on any part of their vertically integrated gaming empire that they sold. There's no such thing as "loss leader" at Nintendo.

And let's face it, phone gaming frankly sucks compared to holding a DS and working a d-pad.

- edit -

for anybody to get what Nintendo is about should read up on Gunpei Yokoi's "Lateral Thinking of Withered Technology" (枯れた技術の水平思考) It makes analysis like this really seem very uninformed about the company.
You know, check out bustle.com -- I used to agree with you, but that's really fast for both the first load and subsequent loads.
Wow, the size of the Ember app vs. Typical webapp + JavaScript is impressive.

Inspecting the Bustle app with the new Chrome Ember Inspector is very cool.

Has Bustle open sourced any of their components or written on how they developed the app?
you can't get good bone and muscle structure from a needle!
> My long term hope is that soon or later different accents could converge into a standard easy-to-understand one that the English speaking population could use as a lingua franca.

I'm puzzled by this comment. The generic midwest accent that most people on television use would seem like a good, obvious candidate. Even newscasters in Europe seem to target this when using English.
Dear Guy Who Just Made My Burrito
Downvotes continue. I have seen this story before. For a self-styled "hacker" community this place values orthodoxy an awful lot. And passive aggressiveness to boot. I think it must come from an excess of javascript and VC bullshit. ducks

Also they are unable to tell when I am joking or exaggerating.
Gondor's Year Two
Sorry, offtopic mini-rant coming: this site (and so many others) become much more readable if you disable the body text CSS. Actually this specific site does quite well when you disable all CSS.

What is with the trend of mid-range gray on white or light gray these days? Does anyone find that easy to read?
I know, I receive Webster's Word of the Day and most of them are Latin words: really easy for anyone who speaks a Romance language. The last five were: incipient; indissoluble, indoctrinate, infantilize, inscrutable. So maybe Webster should have two mailing lists. One for anglo-saxons and one for speakers of Romance languages.
It's a great site for a beginner! (altough I am not sure if it deserves such a high spot on HN)

It's definitely a big step up from this - http://www.tiffany-young.com/gexpro.html :)
There have been techniques for dealing with this for a very long time: https://developers.google.com/webmasters/ajax-crawling/docs/...

And this is only an issue for pages where you actually want to expose your content to search engines.
Why does Twitter.com/nsa crash my browser?
When you visit http://twitter.com/nsa. Any browser experts know how to debug, or maybe twitter has been experimenting with some awful code?
Every Ember.js app, by definition, connects to an API that does all of the things you are asking for.

Seriously, open up any Ember.js app and look at the network traffic. You'll see a series of requests, usually using very RESTful URLs, that requests the document.

The only difference is that, instead of HTML, where you are conflating the markup and the content, you get a nice, easily-consumable version of the document in JSON form.

There is literally no change to the web here, other than the UIs are faster and better, and it's easier for me to consume JSON documents than trying to scrape HTML.
REMOTE possible for the "right" candidate?
Wohoo I can sleep well again. Looking pretty good Tiffany!
No, I totally agree that accessibility is possible if your app is JavaScript based. But if you're unaware of or you forget to add in accessibility features, you run the risk of failing much less gracefully for people who need those features than if there were more static content.

(This is, of course, a generalization; specific use cases may vary.)
"The issue is not that it is "bad". It a matter of separation of concerns. This tag is intended to be used for presentation only. It has no other semantic meaning.

Since the move is to have presentation handled by CSS and HTML should only be used for semantic markup, the tag has been deprecated."

http://stackoverflow.com/questions/4873491/what-is-so-bad-ab...
Unless it's raining/snowing/windy in Denver or SF (or even an unrelated location like Chicago or Boston which might prevent your aircraft from getting to DEN in the first place) in which case you might be sleeping in an airport terminal while masklinn is finishing a late supper in Palo Alto.

I write this as someone who has had two cancellations and 6 delays over ten air trips in the past three months.
You have no patience. Plus you could just sign up for cryonics.
I have 104 keys on my keyboard and 4 of them are modifiers. The English alphabet isn't the Latin/Greek alphabet either. And I am absolutely astounded that Russians apparently have never invented the concept of an abbreviation or contraction.

One does wonder how soviets ever managed to program their computers.
Mercurial website hacked?