skysight-inc/HackerNews huggingface dataset:
Although this is a shame it is yet another sign (for me) that the 'Internet of Things' is going to be DoA if we have to also rely on them for a backend cloud service. Most of these devices could be run in a completely decentralised way, such that if the company goes under, your device is hardly affected. e.g. I don't expect my light switches to stop working if the parent company gets acquired or shuts down.

There are real challenges to making distributed systems easier to build but I'm working with others on that c.f http://nymote.org and http://openmirage.org.
I made a service called http://rt2.me which tries to semantic-ify the URLs ... but I seem to be the only one that likes it.
But where will park the cars?
Sorry, I just saw this. Sadly, I've forgotten the page number. But I'm sure it's recreatable.

Thanks for this. The Library of Babel was one of those ideas that first got me thinking deeply about the nature of knowledge as a kid.
Most comments seem a bit too focused on the content. What I'd do is just get some sound clips that you like, put them into something Adobe Audition. Record yourself trying to mimic them, compare the relevant graphs (pitch/time/loudness one being the most relevant probably), you should quickly develop an understanding of what vocally makes them sound the way they do. I did that a bit to examine accents in different languages.
> I did what any sane person should do:

That actually would be to not get such a big lawn.
Ah, but if you are 10 people listening, that's suddenly $10 000 (actually more, as you'd probably need a little more expensive amp to drive 10 good headphones. Nowhere near 10x though).
It's an opensource project. Why don't you contribute a better solution? Or are you too lazy?
>>>the middle and lower classes are complicit

In my opinion, the middle and lower classes don't vote enough, and therein lies the crux of complicity. If it were somehow required that you had to bring 8 other people with you to vote, if you knew of them - i.e. make it a 'thought-crime' - and knew they were openly stating that they were not going to vote - then it'd get fixed right up.

i.e. a voters bounty for registered, un-voters.

I suppose there are huge flaws in this, but I seriously think it'd be fun for a lot of people if there were suddenly 'vote sheriffs' out there, making sure that people exercised their right to apply power to the politics. People always deserve the whips and bonds they freely choose, when done in freedom. If todays democracy is merely the lesser evil, then a lesser evil even still is total democracy.

At least, I favour organized means of encouraging every 18+ person, citizen, to vote. Voting is meant to solve problems created by incumbent possessors of force, who get too used to their power.

(Note: I also do believe in the right to not vote - i.e. as protest over 'the system', but in the immediate reality of our world today, we need more people actually voting to support their point of view than just those who feel the need to express their point of view. Voting is existence.
While this looks to me like a pretty clean and straightforward API, it's definitely not a REST API (not that it claims to be):

* The API doesn't really follow HTTP. It allows GET for state-modifying actions, which breaks assumptions that could be made by browsers, client libraries, caches, and proxies. Also, the "success" field seems fishy; a 200 response code is the usual HTTP way to indicate success.

* The API is not resource-oriented; the URLs "shuffle" and "draw" are verbs that describe the action to take. In a "real" REST API, URLs define conceptual resources (nouns), and you interact with the API by interacting with those resources.

* The API does not use hypermedia.

Hypermedia and HTTP compliance are discussed elsewhere in this thread, but I wonder if others have an opinion on the fact that the API isn't resource-oriented.

This "resource-oriented" rule has always bugged me about REST APIs. My impression has been that REST advocates claim that pretty much every API can and should be implemented with a CRUD-like interface (where the entire API consists of performing GET, POST, PUT, and DELETE on a conceptual set of resources), but it seems like that would be really awkward for this "deck of cards" use case. Is there value in trying to use resources here? What might it look like?
Show HN: Pouch.ly an utility platform give your feedback
Yeah, ultimately I think the Internet today is a lot more open and a lot more beneficial to liberal society than any network was in 1990. I understand why you gag at that, but, I can imagine much, much worse outcomes than we got.
On the other hand, http://en.wikipedia.org/wiki/Haussmann%27s_renovation_of_Par...

Moreover the simpler solution would be to build up. The article just dismisses that in one sentence saying "nobody wants" it, but do people want entire new microblocks built in the middle of streets?

Plus, narrowing streets would come at a significant cost to the city to reconfigure the roads and infrastructure. Not only tearing up sidewalks and paving new roads, but also burying all the wires on those telephone poles and lord knows whether the gas and sewer lines under the street could support construction on top of them (and how would you service them after?). We'd also lose/downsize trees. On the other hand, building taller is entirely privately funded and quite economical in comparison.
There are no AGI because no AI lives in the real world like humans do. Fundamental exposure to the real world is the key to AGI. You can't expect an algorithm to understand real world in similar way we do when all it sees is pictures, graphs and data points. AI needs to be able to interact with world the way we do to gain any kind of sentience.
I have been looking at the idea of doing lots of small speakers with microphones on them attached to a fat lump of computer hardware, that you stick all over and they bleep each other and build an acoustic model of the space they are in, then adjust for it properly.

Would basically be a self-modifying ambisonics system. It looks doable, though possibly a bit expensive.
Lacking a mention of:
https://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thomp...

And of the IBM 1401:
http://en.wikipedia.org/wiki/IBM_1401

The later is relevant, since as you can see from the opcode description on the wikipedia page, the "source code" of an (assembler) program, as characters punched on a card, had the exact binary representation of the machine code executed by the computer. In effect, the source code was directly interpreted by the hardware. Even if this source code being machine code was not close to English like Cobol sources, or to Mathematics like Fortran sources, it was still source code.

Hence the answer to the question: source code was there before the compiler (beside, before compilers were assemblers and autocoders, that had also source codes).
Gamegear.io – SDKs for mobile game developers
It's not necessarily bike shedding though. GET and POST have two different, widely-agreed upon semantic meanings. It's not just terminology.
>>> I'm interested in what belief systems will be employed to move people away from identities based on citizenship.

Identities based on direct participation in citizenship, perhaps? http://ipfs.io/
Show HN: Sort Australian schools by their test scores
This could easily be classed as one of the great crimes in history next to actual warfare.
That's pretty bad.

I think the reason why people are so upset/surprised is because they expect better from the Go team. Sometimes it really feels like they take the lazy route without putting enough thought and polish into things. Which is amplified by the previous statements regarding for example generics where they said they wont introduce them until they find a really good way to do it but then crank out half baked stuff like this.
The Libertarian Futurism of Peter Thiel (2011)
San Francisco’s Entrepreneurial Culture
I started WoW in december 2005, and hit 60 in februari.

Also, when you reach max level, doesn't mean you finished the game. There is tons of instances to do, special loot to earn, and other stuff; even in 2006.
The difference is that an innocuous comment can (and inevitably will, especially since Go apparently does not actually care about comments, only that a line starts with //go:[0]) match the directive syntax at some point and then it's a right pain in the ass to debug, if that doesn't break anything.

[0] https://news.ycombinator.com/item?id=9523187
Can someone more in the field tell me if this is exciting to them, and to what degree?
Hausmann widened some streets because all of them were small.
When most streets are wide, narrowing some is the thing to do.
Many, I took a random class there and had friends there.

1) Decay is tremendous in Medicine: there are pests and cockroaches everywhere. Bathrooms are used very indecently and its not even safe. Girls dont dare go alone to several bathrooms in the building.

2) Under-budgeted: labs are unequipped and classes have an inordinate amount of people for the number of teachers they have.

3) Kafkesque paperwork and Draconian teachers : there are so many people going to medicine in UBA that students get no attention or assistance. The emotional health of med students is disastrous there, people break down a lot.

A few private med schools actually are pretty prestigious and when you study there, you can actually focus on studying medicine and not just surviving an ordeal.
I think this goes far and beyond Enterprise play or anything of that nature. There is a lot at stake here.

This is a response to a bigger paradigm shift that is the web and software as a service and Mobiles.

If you are on Windows XP and windows 7 rolls out, you have the option of upgrading, not upgrading or switching to a Mac (or similar).

Gmail versus outlook is another good example. With Outlook you would need to shell out big bucks and wait for the next major release. A three year release cycle has really got to suck for the team. If your team's major feature X didn't make it in the current release, you could very well end up waiting another three years. Gmail's releases by contrast are liberating.

The Chrome browser versus IE is another glaringly obvious misstep. One doesn't even care about version numbers anymore and releases indiscriminately while the other feels like an antiquated behemoth that rears it's ugly head every few years and then goes back into hibernation for years. It's a shame, really.

The mobile landscape has shifted to something similar. My upgrades on iOS come seamlessly and effortlessly. Apple can push whatever it wants down upgrade pipeline without costs.

For years desktop companies have relied on pushing the hardware limits to force users to upgrade their hardware, followed by the operating system and consequently all the software running atop that OS. It has been a tremendous boon for every Windows-based software company, almost guaranteeing fresh inflows every three years. So this is going to have an impact on the entire ecosystem.

From a developer's perspective:

Software rewrites cause regression. Microsoft has been regressing all over the place, for years now, most prominently with their Windows releases. For anyone who doesn't write software for a living, regression happens typically when you rewrite a piece of code and in doing so reintroduce old edge conditions or have to re-tweak all the features around it. Only after that does the new rewrite start paying dividends.

Continuous release cycles sidestep the regression issue to some extent by making the iterations smaller and the features less jarring for the users (Windows 7).

As a consumer:

I like the AppStore model because it doesn't charge me for versions (I know that might note bode well for developers because lifetime revenue per app becomes fairly static. A good friend of mine is just completing a rewrite of his app and his entire existing user base will probably end up getting it for free. However, this is still the option of IAP, product SKUs or subscription models).
None, i just didn't know about //go: :)
Report by Seymour Hersh Says Obama Administration Lied About Bin Laden Raid
Also, wouldn't little-endianness generally benefit 16 bit arithmetic operations performed on 8 bit ALUs? Because (correct me if I'm wrong) a carry flag always carries over from LSB to MSB, processing the LSB before the MSB allows you to implement the carry mechanism more efficiently.
Tackling the awkward squad: monadic input/output, concurrency  in Haskell
Completely agree. But of course using a cloud service means no need to run a server on your own network/device or have to punch holes in your router to have the device accessible whilst you are not at home. Requiring either of those wouldn't help IoT adoption outside of enthusiasts.
In some sense you are PATCHing the deck by removing a card.
A personal programming language roadmap
There is a shorter version. 1) Launch anything. 2) Fix only things that your client wants to be fixed. 3) Profit
At last! I'm not insane!

I raised this on the golang dev forums and got nowhere:
https://groups.google.com/d/msg/golang-dev/r4rdPdsH1Fg/yjOOz...

The response was basically "we disagree" and I wandered away feeling confused that so many bright people couldn't see the problem here.
Maybe because he went out of his way to capitalize "Older White Male Professors"?

I read your link and could only wonder what this tattooed anti-white author would say about black privilege in any black run country, and Asian privilege in any Asian country? Why only attack whites? Because the author is anti-white, that is why.
Just some cool things I've noticed tinkering with it:

1.) New "apps" come out of out-of-the-box APIs with APIs for analytics (devices, counters).

2.) It's pretty easy to setup and only took a few minutes.

3.) It provides APIs to create relationships between data sets (collections/entities).

4.) It's schemaless from what I can tell (I could be wrong)... Which is great for rapid development of the client, but probably _not_ great if care about consistency.
If the image in your article is from the manufacturer, then they're based in Stockholm, Sweden. (http://www.autobotics.co.uk/automower-265acx.html)

If so, the Swedish equivalent to the FCC appears to be The National Post and Telecom Agency (PTS) (http://www.pts.se/).
I couldn't agree more. It also makes code hard to read. I have to look closely to check if that's a comment or directive. It would be problem when your code grows.

I am in favor of #TAG: DIRECTIVE or @TAG:DIRECTIVE
Just: HTTP for Humans in Swift
Understanding the internet indirectly involves understanding the BBS. Even if you didn't use the BBS this documentary is very informative. What I found intriguing is the sense of community BBS had (and has after it's demise), something that is quite disjoint on the internet...
That has happened to me with DO also.
I give a crap, because when I see an API, I expect a GET to be idempotent. If a coworker implemented this, there would be words.
Jitsu: Just-in time summoning of unikernels
Doesn't Go complain about unused imports ?

So what if you have a bit of code that you are half way through and you want to comment it out as well as the imports. I've done this countless times over the years.
Jason Scott works for archive.org now, BTW.

His main site is http://www.textfiles.com and his blog is http://ascii.textfiles.com
17 % of Android Apps Are Malware: Study
I don't really get how WoW led to Glassdoor, just because he got a call the day after he hit 'max level'. Correlation does not imply causation.
Just because it is open source does not me (a) that your changes will be mainlined, (b) that your changes will be even considered or (c) that you will logistically be able to maintain an ongoing fork.

Saying "it's open source so you can just add feature X or change feature B" only works if you are part of some core team or are respected via other means. Github is littered with projects that have lots of Pull Requests that never get pulled.
Windows shadows make it a lot easier to multitask with many small windows open.

Lack of depth in 8 makes it harder to figure out which window is in focus and which ones are on top of others.
Yeah, it probably is particularly effective in a more jocular setting... but let me add that I'm not proposing to, in a non improv show setting, literally "yes and" everything somebody says. I'm just saying that the general principle of "agree, then add" is a useful tool in conversation, to avoid conflict, which can derail the conversation.

It isn't necessarily so much about "sounding smart" (which, in my mind, is not the real point anyway) but rather about controlling and guiding the conversation in such a way as to accomplish your end (whatever that may be).

If you go and take improv training, you have to be prepared to generalize from it and extract the useful principles, before applying them in other settings. Otherwise, you might wind up telling your boss that the reason the site is down is because a stealthy group of ninjas in pink tutus, riding elephants, stole the Postgres database!
I actually hear many many times that the game starts when you reach the top level ^^ I've unfortunately never played the game enough to confirm though
http://typedrummer.com/zn2p6t
Comments are also not metadata!

CGO, for example, expects a comment immediately before a special import statement. A blank line between that comment and the import statement means that the comment is not attached to the import statement's AST node, and so is ignored. This confused me a fair amount when I started with CGO.

Part of the problem with comment syntax is that it's intentionally lexical and uniform. This simplicity means that you can easily obliterate the content of comments at any point in the input file stream via the tokenizer. However, Go instead has to bend over backwards in it's compiler toolchain to preserve comments beyond the lexer: in the parser, AST, code generator, etc.

Compare to docstrings in SmallTalk/Python/Clojure, where they are actual parsed string literals. Also compare to C#, which has explicit and distinct syntax for comments, metadata, and compiler directives. Comments can be inserted more or less anywhere. Metadata only where it's unambiguously attached to an AST node. And directives similarly to statements, unambiguously detached from other AST nodes.

With proper syntax for metadata, the CGO case would have been a compile time error about no AST node for the metadata to be attached to.

With proper syntax for directives, the //go:generate string-scanning bug would have never happened.

These syntaxes must be disjoint from comment syntax to eliminate the problems.
So suppose I start stealing cattle. I sell them, and hide the money. I keep doing this until I get caught.

What would you suggest the state do, if they do not imprison me, to discourage me from going back to cattle stealing?
It looks like more of a complement to docker than an alternative. Docker does a good job of making apps/services deployable without really having to care about the infrastructure underneath. One of Docker's current issues is a lack of security (a security breach in one container can be exploited to access other containers on the same machine since containers share resources with each other)

If I'm reading the documentation correctly, this doesn't do virtualization ala freebsd jails or true containers but is more like a chroot jail, which grants a locked-down view of a filesystem
I always tell them, "You can have what you want quickly or you can have what you want cheaply, if you insist on both, you won't be getting what you want."
In the early days of Java, there were tons of articles titled XXX written in Java. Just go look at some early Slashdot or JavaWorld.
Well joking aside, its funny because things really used to be this way - sessions/jobs were an invoice line-item, but .. kidding aside - if one tried to practically apply such follies - I think this might be another place that Bitcoin - and micro-transactions - would be useful.

I'd be quite happy to lend my CPU to appservers, knowing it was going to have transactions in my favour somehow.

So maybe there will be a Linux distro that plugs into Ethereum, somehow? Or hell, containers, sorry pardon me ..
Tickets – Sunrise Period Coming for .TICKETS New GTLD
It's a pain. There are better continuous evolution systems on the horizon. Not many people use this. It's hard to select for anything besides growth.
overlapping windows was actually a challenging problem within the constraints of the old hardware.
StackOverflow – Problematic PHP Cryptography Advice in Popular Questions
This pattern predates Go 1.4, we've had it with CGO and build tags since at least 1.0 AFAIK. Even the Output in examples is pretty old I think. The only advantage in it is backwards compatibility with older Go versions, but in general I agree with you.

When PHP did it for Python-style decorators everyone thought it was stupid. And while the build tags in Go are okay by me, doing it for CGO especially seems like a hack.
GetVersionEx is broken from Windows 8.1 onwards, they want developers to query the OS for functionality rather than check a version number. See https://msdn.microsoft.com/en-us/library/windows/desktop/ms7...
Made this weekend url tmp[0], a simple plugin/package manager for tmux.

See also tmux-fpp, a Facebook PathPicker wrapper for tmux[1]

[0]: https://github.com/tmux-plugins/tpm
[1]: https://github.com/jbnicolai/tmux-fpp
This is absolutely true
Instead of depending on a running agent, SSH based remote monitors depend on the consistency of the SSH configuration across the fleet of machines. This is sometimes non-trivial configuration find in heterogeneous environments (usernames, authentication, permissions, sshd_config...).
Another cloud will be part of the "infrastructure I need to monitor", as in "is this thing running and monitoring my services ?"
no difference - both are misused comments.

the main problem is not technologie but semantic. If you agree with me that the meaning of a comments is communication between humans, than you must also agree - in my opinion - that comments can not be directives to a tool chain.

It is ambiguous. It is error prone. It is easily solved using an other token.

And in the long run it may lead to madness like Java testing and documenting frameworks.

as for technical problems - I think some really bad ones are mentioned in this very discussion!
"Nobody wants" cars. Haven't you read the article?
On top of that in vanilla WoW people actually went through all the content in the game. People would complete most of the quests, go through the dungeons in your areas multiple times to get armor sets, and do PvP (open world and battlegrounds). It might take an hour or two to get together a group to do some of the less popular dungeons and Battlegrounds queue times could easily take upwards of 40 minutes. Open world PvP and ganking would almost always take a couple of hours as you had to sometimes infiltrate enemy territory to claim your victims.

Nowadays WoW feels more like a virtual lobby system for the dungeon finder/PvP queue rather than an actual MMORPG. No one really bothers to play the game as you would expect a traditional RPG to be played.
This is completely off-topic but I find it so hard to convince myself to read a 14,000 word (or any other long-form) article anymore.

At least the New Yorker doesn't try to maximise ad revenue by splitting this across 25 pages.
Applied! Looks like an awesome place to work.
I would change "unverifiable" by "unfalsifiable" there. Nothing is verifiable (not even science works that way).
And there's

//line path/to/file:linenumber

and

//go:noescape
Partially agreed. Directives should be visually distinct from comments and syntax should be formally defined such that compilers, code generators, editors and IDE's can use them consistently.
I wonder if it's possible to connect a bunch of modified cruise ships in a sea colony. That would make it readily expandable and modular, plus allowing enough space for all kinds of alternative energy/food sources
uh - that's really bad! :(