skysight-inc/HackerNews huggingface dataset:
> there are other cases like these if you really start to look for them

Good luck with that. The US Government has its own firewall against control of this form, by its people.

Or, is there some reality TV show about Guantanamo and other associated criminal operations of the US around the world that I've missed?

In an environment where the government can remove the truth at will (with its formidable NSL weaponry), the battle is no longer about fair and equal society. Its a battle for justice, instead - and when all legal means of obtaining justice have been tied down by the "OMG! Terrorism!" crowd, the gloves need to come off. Citizens need to reign in their out of control government - otherwise they will become the (rightful) targets of the enemies that government is making ..
TrainTimes already has a map (http://traintimes.org.uk/map/#bhm) although I'm not sure of their data source.

I've looked at this before and it's already doable through the network rail api (https://datafeeds.networkrail.co.uk/), which differs from the national rail enquiries api and as far as I can remember (and can see) is free.
Well Erlang is running on RTEMS in production in industrial control systems http://www.grisp.org

Hard realtime processes to come
Show HN: XprobePlugin – Objective-C App Memory Browser
Thank you for saving me some time. I missed that and thought Kohana was still being supported, but I just checked and found this: http://forum.kohanaframework.org/discussion/12509/final-rele...

So you are absolutely right. Will drop it from the list to try and will update the article.
The page indicates that it works on Macbook airs from 2011 and newer. However I own a 2012 version and it will not work, because it actually doesn't have Bluetooth 4.0. Which is a bummer, because I already had one app that use 4.0 before that I couldn't use on it.
I'm also a bit frustrated with the Yii situation, although I do understand why they're doing it. Yii 2.0 is a total rewrite, and it is technically very impressive. However they have had the disadvantage of not being able to ship until it reaches feature parity with 1.1 which has been a huge undertaking.

The lead developer, Qiang, is literally the second most active developer on github[0], so it's not like they're not trying - the guy is currently on a 370+ day streak - it has taken a huge amount of effort for them to get to this stage.

I would personally build on the beta at this point because I have a lot of faith in the core team and they've had a lot of time to iron out any major problems, at this stage any changes are likely to be quite minor or fixes, so the real release will probably ship before your new project does.

Kohana seems dead and CakePHP has historically been rather slow and ungainly.

The lack of library support for Lua is a bit annoying, but it's getting better and can possibly be mitigated by using Lua's FFI to talk to C. If the eco-system was a bit more mature OpenResty[1] would be pretty compelling.

0. https://gist.github.com/paulmillr/2657075
1. http://openresty.org/
Yay for Nintento and boo to patent trolls.

The article is rather lightweight and short. It doesn't say what the claims actually were.
New dual carbon battery charges 20x faster than lithium ion batteries
I like how all the replies to your post are appealing to tradition.

“If you lived forever you'd starve people of resources and never evolve, that'd be bad!” If you lived forever, you wouldn't need to evolve, because you wouldn't be dying due to the environment. If you are still alive: you are well suited to be. Reproduction is just a form of genetic immortality if not individual immortality.

All of this presupposes that some immortal people were born and just died out because being immortal wouldn't be rewarded by reproducing.

And ignores the fact that animals that live for a very long time reproduce slower than animals that live for a short time.
Leaflet – JavaScript library for mobile-friendly interactive maps
Yet you draw further attention to it.

But frankly, consider that he is posting all over the place anyway, trying to hide his issues away accomplishes nothing. Drawing attention to the fact that his often extremely offensive comments are due to mental illness rather than malice is not a bad thing in that context.

He's accomplished a lot of things that most people never will, despite his illness. He's one of the reasons I have showdead on.
No problem, looking forward to the verdict. :)
I'm imagining Alia of the Knife.
I disagree.

Weasel words are a way of introducing opinions disguised as facts while absolving yourself of the need to make a specific, verifiable (or falsifiable claim). "Some say Hacker News is the the most important website about startups." The actual information in that sentence is that 'some people say this thing' but it reads like 'this thing' which is misleading. It's misleading regardless of citations.

There is nothing wrong with saying 'this thing' if that is what you mean to say. 'The Arripis is also known as the Australian Salmon' is a true and relevant statement. It's common for fish to have different names in scientific, culinary and angling contexts as well different places. Wikipedia needs to address that to be useful.

That's the reason weasel words are a hard problem. It's subtle. Sometimes opinions are important and relevant and they should be included (with citations) on their own merit. "Commonly referred to as.." is an important fact about lots of animals.

What this is is basically just a simple case of falsehood. Nobody called anything a Brazilian Aardvark at the time of the edit. It wasn't true. It's an interesting story because it became true.

Every common name for an animal had to be invented at some point. Here, because of the magic of wikipedia' revision history we can see exactly when that happened.
I have to disagree with this strongly. There are significant economies to scale in any streaming service. For example, in terms of costs (streaming services require a lot of hardware). But also in terms of branding and reaching a critical mass in terms of content.
I tend to agree. I use Mac OS only because it natively supports Photoshop and MS Office and I may need to install these at some point. It also has first class support for the kind of dev I do (e.g. most other devs in my field also use a Mac) making troubleshooting slightly easier.

As for the UI, until Mavericks I think it was behind the last stable Gnome 2 release. Now it is ahead in some areas but still behind in others.

Finally, Ubuntu continually screwing up things like audio support or ruining areas of the UI (ironically to make them more like OS X) also helped me make the switch.
Customer engagement, requirements engineering, product managing - all good things that are (stereo-)typically hard for software engineers...
He's reiterated that in a (dead) comment on this post:

> Yeah, I did. Now, I use Linux. Normally stuff like this launched me into an existential crisis. "Oh, God, the stress! Why God!? My world has a MAJOR thing to worry about -- misleading people maybe or something like that."

> I'm not quite as much a coward. I think I had good reason. Cowardess is not a virtue. God loved King David.

>Damn, I look awful. Oh well. I've become a freak hermit-- don't know how to smile, anymore.
> Using <script async> you don't know how much of the DOM will have been constructed at the time it executes.

If you are including jQuery or similar, there is the option of having your code hook into the "document ready" events. If you are not using something like that then you could pull out what they use and implement that part yourself.

Another option, which is less clean but might be useful if you don't want to wait for all of a load DOM to transfer for instance, is to check for the parts you do need and if they are not yet present set a timer for a few 10s of ms time to check again.

> doesn't work in IE9 or below

I don't suggest holding back on using features because of old IE. Instead make sure your code works in everything but can take advantage of the extra feature in newer browsers. PEople using old IE might get a less than optimal experience, but it'll work, and those using something better get the optimal behaviour.

Of course, this falls down when maintaining backwards compatibility requires noticeable code changes rather than just accepting old browsers won't display things as nicely and/or responsively.
I went to OpenTech 2013 and by far the most packed session was Peter Hicks' (Poggs) talk about open rail data[1]. I worked at Rockshore, who maintain the Network Rail datafeeds, and I remain grateful but astonished at how passionate people are about this data.

[1] http://www.opentech.org.uk/2013/audio/streamC/session4.mp3
Show HN: 56 Hours left to support my iPhone Development Training Kickstarter
It's the developers I'm talking about, not the users. I've yet to see any breakout company that's using a proprietary IoT platform (but correct me if I'm wrong). There's an inherent risk associated with trying to build a big company that way.

Yes, the developer could still sell everything to a third party but that's not really what I'm trying to tackle. It's the problem of building and connecting such applications/services in the first place. You shouldn't need a 'platform' to do that.
Visualizing botnets, malware and network traffic
Well now I feel bad. It was meant lightheartedly, and your comments were valid!
Yay progress!

Don't let it die that's a pretty significant step forward.

Regarding Lever 3 and all other Tier 1 providers I suggest they build a database of all ISP's that let their connection saturate and if this keeps happening they cut connections and ban their ass.

All ISP's on the ban list should be forced to pay a large fee to be able to connect back with any Tier 1 providers.

At the end of the day regardless of how big you are you're not an ISP if you don't have access to the Internet.

If Concast and friends want to play the who is more important game i would wager Tier 1 providers are in a better position to win it.
Interesting indication that Apple is really making an iWatch
If I read that I would have scanned the phrase " complex flows " ... and left the page.

I guess Stripe it is. I was kind of looking for a UI analogous to the Toy's R Us giraffe with a big "Buy" button attached, preferably with little mini arrows labeled 'pay to' pointing to other smaller giraffes representing all collaborators involved.

but this shall do. Thanks :)
Qiang being so much of the driving force behind Yii is actually a strike against Yii. It would be much better if that load were spread out more, even if that probably would delay a release. SPOFs are not good.
Soft is the new hard ;-) If you reason about hard realtime you pretty soon end up with the question: how high can the probability be that it misses a deadline. If you run on modern embedded CPU's with pipelines and caches its often all you can do (I am aware that some are modeling the CPU with caches, memory and everything to achieve 100% but thats very expensive and if you switch CPU's there is half a year worth of modeling down the drain)

The real world hard realtime systems often are built like: lets test it (with deadline miss triggering a failure) and if it works make sure we still have 10% of safety margin (which will later be melted down because of features ;-)
Stanford discovers way of beaming power to microimplants deep inside your body
I'm really not sure, and I'd rather not speculate blindly. I've read
about the basics of Mercury Line Memory in the past, and have some
books that describe it, but I don't know the hard details.

BTW, Mercury Line Memory was not the first form of memory used in
programmable computers. The "oldest" or "first" is debatable, but
the earliest were switches/relays and vacuum tubes (AFAIK). I'd
bet jgrahamc would know...
Polisforcongress
I am at the same time in awe at the technical accomplishment and cringing at the religious twist. I've never seen the two concerns merged quite so tightly.
Kohana has died as far as I'm concerned. Such a shame, but it was a great replacement for CodeIgniter back in the day. CakePHP tried to hard to be Rails and messed it up, and I've never forgiven it, and it was horribly slow in my benchmarking.

Out of PHP frameworks, I would rule out anything that doesn't use Composer. If you can't use the best bit of tooling PHP has gained lately (other than HHVM) and are stuck copying libraries in by hand, well if you want it to survive then you've made the wrong decision IMO.

Personally, I would pick either Symfony or Laravel, the latter for development speed, the former for robustness and power (and explicitness, I'm working on a 400k line web app in Laravel which has had too many shit developers hacking on it over the last 12 months, and we get bitten by magic weekly because a long since fired or quit dev worked against the framework rather than with it).
It wasn't even mentioned until you brought it up.
Know when to use a JPG and when to use a PNG and always Squish them both
Lenteen note 3
lenteen note 3
Finding the right tool for the job – FAIL
Ah, cool. You used to be able to define your own characters on Amstrads, and that's how I wrote most of my first games.
Dropwizard is where it's at right now for Java frameworks. It's a superproject that glues together the best pieces out there. Surprised it wasn't on the wikipedia list.

Which brings up another point: if we're talking about web frameworks for the next decade we should really be looking at service-oriented architectures / single-page apps or whatever you want to call that model. It's quite different from the web frameworks of yesteryear that generated UI on the server. Dropwizard can do web views but it really positions itself as a REST service framework.

So, that brings javascript frameworks into the consideration. And the author has a paragraph where he just dismisses it as a "terrible hack"...??? I think that is going to seriously hamper the outcome here. It's good that modern web apps leverage the power of the browser and JS frameworks are the way to do that.
"require guarantees that erlang can't give" ... at the moment, working on it.

In the meantime note that the percentage of stuff that really needs hard realtime in many systems is quite low. What I do at the moment is run Erlang on RTEMS (see my other posts) keep the hard realtime parts as simple as possible (always a good idea), write them in C and run them on a higher prio than the Erlang runtime which handles all the complicated things. Works like a breeze in practice
This is awesome. I just ran ImageOptim over my blog's images folder and saved an average of 10% per file.
I think another question is how much you want done on the server (HTML rendering?) and how much on the client. It seems like we're definitely moving towards having the client handle all the UI. I understand this may not be appealing, especially as client side frameworks have even a shorter lifespan than server-side frameworks, but that seems to be the direction. If that's acceptable, for the backend I'd choose Java and Dropwizard (or Jersey+Jetty instead of Dropwizard). Spring Boot also seems nice. I discuss the state of modern Java web development in a non-comprehensive recent blog post[1]. For a more complete discussion of JVM web frameworks, you can take a look at this[2] and this[3].

[1]: http://blog.paralleluniverse.co/2014/05/15/modern-java-pt3/

[2]: http://zeroturnaround.com/rebellabs/the-curious-coders-java-...

[3]: https://www.youtube.com/watch?v=ygW8fJVlDxQ
The other consideration needs to be "How did this mature framework evolve?".

Symfony dumped all symfony1 users up s* creek when Symfony2 came out; Zend framework 2 is an entirely different beast to ZF1...

Are these mature frameworks any more stable than the new ones, or are they new frameworks, phoenix-like in assuming the name of the old one?
I (naturally) think that the article's summarily dismissing Haskell is unfortunate. It's probably just the result of poor PR on Haskell's part.

Haskell is not only for surpassingly intelligent people, or even optimized for them. If anything, it's the opposite: one of its core tenants is that we're not smart enough to reason about our programs in most languages. Much of the design work focuses on unloading complexity into the language, tools and abstractions.

Haskell goes out of its way to prevent common errors and help you design your program. In a very real sense, it trims the "search space" of possible programs, helping you zero in on a reasonable solution. To an extent, I use Haskell because I'm not smart enough to use C.

Haskell is unfamiliar. And people mistake that for some sort of innate difficulty. But the two are not the same.

I would argue that overcoming unfamiliarity is one of the most important ways to grow as both a programmer and, more generally, a person. That's why I think the article focuses too much on choosing a language that's familiar, codifying it as "just about all the good advice". This mindset is far, far too exaggerated in most programmers, and its what really slows down progress, especially for popular programming languages.

The blub paradox is also a bit misrepresented. Being a "blub" programmer is not a matter of being more or less intelligent—it's a matter of not knowing what you're missing. "Beating the Averages" is not "we used Lisp because we were smarter than you"; it's more like "we used Lisp because it offers some incredibly powerful tools that non-Lisp programmers have never used and so do not really appreciate". It's a matter of habits and experience, not intelligence.

My advice? Do try something unfamiliar. Especially if it seems to be higher in the great partial order of programming language power :).
>Dropwizard can do web views but it really positions itself as a REST service framework.

That would eliminate it for me.

Not everyone is coding APIs and fat client web apps. I'd prefer a framework geared up to do standard web apps as well.
I think most projects have natural leaders, but if Qiang was hit by a bus tomorrow it would be a tragedy but Yii would not die with him. The other core developers, especially Alex and Carsten, are more than capable of picking up the reins, and the project has enough momentum, and has received huge investments of time and energy - it isn't going to go away at this point.
Don't underestimate the power of a simple change of scenery. I moved from one city to a, on paper, basically identical city (same size, same climate, same 'feel' etc.). The place I moved to was in no way better (or worse) than the place I left, but the change it had on my life was huge. Sometimes you just need a fresh start.
"JavaScript web frameworks seem to have a half-life of about 6 months..."

Express [1] has been the dominant framework for Node.js since 2009-2010. What frameworks are you talking about?

[1] https://github.com/visionmedia/express
No. Evolution selects based on relative fitness. Killing older members is obviously more efficient for the population as a whole. However individual genes that "defect" and continue reproducing into old age will make more copies and spread themselves more into the next generation than the "aging" genes. Even if it's inefficient and they use more resources (which isn't true, it takes a lot of effort and energy to raise a child, keeping an existing body is way better.)
Looking from the top of todays technology some can observe subtle transition from desktop to mobile to wearable electronics (intelligent clothes). From this point of view Web becomes obsolete. Everyone prefers native apps on mobiles. Honestly I can't see bright future for Web in wearable electronics world now. I'm almost 100% sure there won't be HTML inside.

Web was designed with desktop in mind. The further form desktop the less Web. The future is not on desktop. C forever? Low memory footprint and small executables are still there.
It could be that something within your OSX is not quite right.

My primary machine is a 2013 MBA, and I always switch between IntelliJ, couple vmboxes, spotify, 5-10 Chrome tabs, Pages/Numbers, and Skype. Often, I also run VMWare with Windows. My MBA never makes a squeak, and the only time I feel underpowered is when I have to open all of this at once.

Your hardware runs circles around mine, and should not struggles with such a basic workload - I would look into potential problems on the OS level or start afresh.
I'd consider this more of a flaw in humans, and manifest in Wikipedia, but definitely something not Wikipedia-specific. The basic problem is that people 'believe' something on the basis of collective consensus - whether its true or not, if everyone else believes it, individuals are motivated to believe it too - because of course, the group of believers is bigger than the individual. Thus, even if its not a truth, it is something to be believed - because everyone else does.

And this 'because everyone else does' is the #1 cause of problems in the world. If only we, as individuals, could resist this fallacy that something is true because others believe it. Wouldn't it be great if collectively-derived agreement was in fact an effective way to create a reality .. well, it is. And that's precisely the problem: we create the world we live in. Collectively.
If you are still considering PHP frameworks, then your choices are really Symfony or Laravel (maybe Zend at a stretch).

Yes, Laravel does have a high "bus factor", but for me personally its the number one choice in terms of ecosystem, features, support and community,
This may be a stupid question, but why is there a convention to split?

I saw that in set three of the crypto challenge, as well, and wondered.

Is it so that you can always start counting at zero when re-starting the application, as long as you're randomly picking a new nonce?

And if you just picked a random counter value at each restart you might get very unlucky and at some point reuse a counter value, so by this convention you're separating counter values belonging to different restarts?
Still says it. It's on the article index as well:

https://www.paypal-community.com/t5/PayPal-Forward/bg-p/PPFW...
To me, the most interesting thing about this post is that there is no clear answer. We're mired in, frankly, a lot of junk. There's no winner because nothing is really very good.
400kloc on Laravel, holy shit snacks what the hell does it do?

I just cloc'd my projects root and including laravel and some dependencies (/vendor) that's 295,000loc).
As far as those two frameworks, it's mostly about retaining brand recognition.

On the other hand, major version releases are when you make such dramatic departures from what's come before. At least in ZF, they got a lot a lot of things more-right.

I moved a (pretty complex, line-of-business transactional-type) project from ZF1 -> ZF2, and I'm happy I did. Some things changed a lot (dispatch, routing, forms), while other things were very easy to translate (caching, logging, etc).

In that case, most of the business logic was built around Doctrine2, encapsulated nicely into service classes, and therefore fairly framework-agnostic.