skysight-inc/HackerNews huggingface dataset:
Start with Stephens' books, Unix Network programming, and then move onto The Design of the FreeBSD Operating System (new edition).
The latest release of my jarg[0] utility supports the HTML JSON form syntax. Writing out JSON at the command line is tedious, this makes it a little nicer. The examples from the draft are compatible with jarg:

$ jarg wow[such][deep][3][much][power][!]=Amaze
{"wow": {"such": {"deep": [null, null, null, {"much": {"power": {"!": "Amaze"}}}]}}}

[0]: http://jdp.github.io/jarg/
Here is the previous discussion for those interested: https://news.ycombinator.com/item?id=6148347
Next time, kids, we'll do the same without support from our fancy IDE! O wait, no. Let's _not_ do that.
Something similar on android: https://play.google.com/store/apps/details?id=mental.care.ac...
I haven't updated it a while, but feel free to try it
Apples and oranges. Its not supposed to be a small app, it's a skeleton being built to support something much heavier.
Thank you for the great works of debuggex, I like it.

My little tool didn't intend to act like a extreme powerful and multifunctional tool which debuggex is. I know debuggex need to conform existing regex engines,so it will be more useful and can be widely applied. But what my tool intended is another side,trying to point out errors strictly.Such as /\1(a)/ or /(\1)/ doesn't make sense, so I think the ability to report errors like this will be useful.Although js interpreter's regex engine still supports octal today,but I remove it radically(see the project README).Maybe this little feature is useful for someone. ;)
It's pedantic, but it's a tad clunky now: I'd use something like "wow/such/deep[3]/much/power/!" to differentiate child nodes from array indexes, and also strongly advise against a node named "!" on principle. Of course then you'd say "but I want '/' in my node name!", and then you get to bikeshed an escape sequence, but you'd need that anyway for a node name with '[' or ']' in it.

However, what they've done is workable if all the browser vendors implement it.
I still use them all the time for just that. You no longer get a choice of 10 different bipolars and 3 different VMOS FETs, but the parts drawer is still pretty useful when all you need is a relay or an Arduino board.
Setting up any web stack is a pain in the ass and probably just as long of a tutorial. For example, write out a tutorial which goes from base Ubuntu install to "hello world" on Rails, I bet it's just as long or longer. I suppose it depends on how much detail you want to include. There are just more "one click" install options for other stacks.
FooNav.js – Simple Navigation Plugin for JQuery
Plasma shield
Also might be of interest: Bunnie's hack of SD cards last year http://www.bunniestudios.com/blog/?p=3554

"An Arduino, with its 8-bit 16 MHz microcontroller, will set you back around $20. A microSD card with several gigabytes of memory and a microcontroller with several times the performance could be purchased for a fraction of the price. While SD cards are admittedly I/O-limited, some clever hacking of the microcontroller in an SD card could make for a very economical and compact data logging solution for I2C or SPI-based sensors."

"The embedded microcontroller is typically a heavily modified 8051 or ARM CPU. In modern implementations, the microcontroller will approach 100 MHz performance levels, and also have several hardware accelerators on-die."

Was discussed on HN, but Algolia search looks to be down at the moment.
Agreed. It's also possible to use frameworks such as Spring Data/Boot, Roo or Grails to get started really quickly - a bit like the django/rails crowd. Lots of interesting things happening in Java world at the moment.

It seems like originally Java drew from the mega complex enterprise application world influenced by people building large scale C++ apps etc so were hardly aware of the complexity they were adding. Now there is a lot of influence from modern web frameworks to quickly developing and expanding an app.

Touch to maintain some of those old Java apps though from 5-10 years ago in some cases.
> In a fluid, we have vortices... because they allow material and energy to be moved much more efficiently than any of the other structures we don't tend to see in stable systems.

As a Physicist, I am wary of making such statements since they put the cart before the horse ( http://en.wikipedia.org/wiki/Teleology ). I'd be more comfortable saying "In a fluid, we have vortices... as a consequence of the movement of material and energy."

In your case I'm assuming it's just a turn of phrase, but there are some hypotheses which actually attribute abstract "goals" to nature, without providing any explanation in terms of mechanical processes; for example http://www.lawofmaximumentropyproduction.com

In constrast, Darwin explained the theory of evolution using the mechanical process of natural selection. The principle of least action can be explained either physically, using quantum interference (eg. in optics), or mathematically, due to the mixture of inductive steps with deductive ones.

In constrast, the existence of vortices in fluids because of their efficiency would be like claiming crater lakes can't exist because water flows downhill.
http://www.e-shelter.ch/ more likely, as they are mentioned in the "technology partners" part at the bottom of the page.
And this is why the last time someone said to me they were building their startup in Java I laughed (internally)

This is ridiculous and unjustifiable. Really. Yes, I've already though otherwise (not with Java, mind you)

It's a circlejerk of "developers" patting themselves in the back for creating solutions to the problems they themselves created. Like XML (which is still better than Corba, yay!)
Games are basically 100% floating point on the graphics side already. Even the color shading is done on floating point quantities on modern engines.

The problem isn't that games are not FP, it's that for games, 32-bit precision is good enough, and for most problems actually way more than they need.
Twitter Guys take it all too seriously and may have lost the plot
that's the trick, isn't it -- it's not so much your burn rate, because you understand that; it's what your customers cut if they decide there's a bubble. eg yahoo during the dotcom bubble: huge chunks of vc were flowing through to yahoo ads.

That said, I don't know what Fred means, but $10k/engineer is ridiculous. That's earning well under $100k/year by the time an employer pays social security, health insurance, employment taxes, and rent. You have to be smoking crack to live in sf, home of the $3k/mo apartment, and earn so little money. A standard rule of thumb, more common in nyc than here, is your gross income needs to be 40x your rent.
In the US, I lived in (in descending order of time spent there)

Illinois, Chicago and rural.
Virginia, several locations.
New Jersey.
New York.
LA, Norcal.
Ohio
New Mexico

Which I'll grant isn't "everywhere", but is a decent sample of East, West, Midwest, and various shades such as "mountain man" and "rust belt" between.

Fully aware, I've been to Xi'an and parts of China most folks don't even know exist - driving across large swathes of the planet is one of my favourite hobbies. Driving west to east across Russia is great, as you barely notice the change as you go, as it's HUGE, but you couldn't mistake, say, Ulan Ude for Novosibirsk in a million years.

Conscription is a potential downside, yes, but I look more at things like "do the people seem fundamentally happy, or neurotic and really messed up?". In the US and Russia, the latter applies. In the US, they all take prescription meds. In Russia, they drink until they don't care any more. Not symptoms of healthy, happy societies.

I don't know where I actually would say is "better" - most of the places I've been to where I've gone "this is nice" have been devoid of humans. We have a knack for turning things to shit.
"But, but.. it's not enterprise!!!111"

How are they going to justify their consultant fees then?

Thank you very much for this comment.
IE9 and above should handle it fine, so it's just a matter of time before this problem goes away. In the meantime there are two things you can do: use an editor which highlights this as an error (e.g. Webstorm), or add a pre-commit hook on your code repository which disallows committing code that doesn't pass jslint checks. We use both practices on a 200 kline js codebase, and it has essentially gotten rid of javascript errors at the customer due to bad syntax (as well as those tricky = / == / === issues).
* on lists can also mean elementwise multiplication, dot or cross product if you treat them as vectors. There's no way to choose the objectively best meaning. I'd even argue that vector math isn't the most popular use for lists in python, not because of + and * semantics, but because of performance.

So it was good design decision not to bother with math semantics for general use datastructure.

And besides Python has nice general syntax for elementwise operations if you don't care about performance:

[x*y for (x,y) in zip(xs,ys)]

I agree it would be better not to implement + for lists at all.
At first I thought this was a big wtf but really there isn't much to it. It is a rather good, detailed step by step documentation of how to set up a hello world example. +1
I don't know about "rush" but they should move quickly because Rust is in a fleeting sweet spot of the developer attention cycle where lots of people are eager to jump onboard and it's really good enough for that now.

You are barking up the wrong tree if you are waiting for Go-level simplicity, like the Rust folks have often said.
Yeah. Like, who needs full stack engineers nowadays anyway? :)
I have to agree - for all the talk of "mental training", is there any actual evidence that arithmetic drills will actually help with problem-solving and critical-thinking?
Explorer Shell Merged
So if I have an idea that might be patentable, the journal will handle all the costs for me? Including maintenance fees and the cost of appeals if the patent is rejected? Sweet! Someone else takes the brunt of the $10,000+ in patent filing costs, and there's no downside for me!

In other words, your proposed journal just managed to increase the cost of publication by over an order of magnitude.
You could just have the servlet write "Hello World" directly.

The Bean is not really useful in the example -- it's mean as a stand in, to know how to write one for your business logic needs, e.g user or product bean etc. (Btw, beans are just lightweight classes used mostly as structs, with getters and setters).
Except that that's not just a "Hello Word" page.

That's routing to the right page, transaction and session control, storing the text of the message in a separate class than the one that returns the response, and using a template to return the resulting HTML.

Looking at the section with the actual example code in it, you could do it in about half that, if you wanted a simple version that just returned "Hello World".

If you don't want routing, templating, separation of concerns, etc. then you wouldn't be using a framework like that, of course.
Yes, it's hard to justify a 48bit fpu or 64bit fpu when you can have 1.5x or 2x the number of computing units (approximately)

Still, "not as fast as we wanted" is a "modern researcher problem" ;) Some years ago they would have been converting it to run in integers so that it's not unbelievably slow.
When the female crafting community gets angry about tax law changes
Transactions: the limits of isolation
I used to joke that "hello world" in Java was twenty files and two security holes.
The Snowden Effect, Quantified
The question is really impossible to answer as it depends on forces outside your control such as the willingness of investors to invest.

One of the things I've seen a lot of in startups is people failing to understand the difference between planning and strategy. Every startup has a plan - a detailed list of things that they're going to do. Hopefully the founders update the plan as they get new data. If they fail to execute that plan they're often "Well, things happened that we had no control over!" and the startup dies.

What startups need is a strategy. The difference between planning and strategy is that a strategy accounts for things that are uncertain and beyond your control. There is a huge difference between "Our marketing burn is $3000/month because Facebook ads are $100/day" and "We'll spend $3000/month on marketing, split between Facebook and Twitter, skewed to Facebook while our acquisition cost is $0.5/user but shifting towards Twitter if Facebook ad prices start to ramp up as they get less effective." The first is planning. The second is strategy.

So yes, success depends on things outside of your control but if you fail because of that then it's still your fault.
You might find this from Laura Thomson (Director of Engineering Operations at Mozilla) useful: https://speakerdeck.com/lauraxt/minimum-viable-bureaucracy
Greentick [i]: Amazon AWS is closing its doors forever, we apologise for the inconvenience
Wow. Not sure even what to make of this. I think the real answer is who cares? If you have the right product and if you have the right backing then your burn should be the right number not to tap out the backing to get to what you (founders) and investor feel is the right place to cover your nut. If you need to burn money for a long time then you had better hope you backers are all in on the company. Either it is the right place to "burn" the money for the long haul or get out. I am on my 5th startup and have a had a hit or two to the point that I do not need to work. In the hits it was because the investors were in it for the long game, they believed in you and the idea and would do right to see it get there. The topic of burn never came up if you were doing the right thing for the successes of the company. In my experience, if the investors were focussed on the burn as anything more then "what number gets us there" then you were likely to fail.
May be true for J2EE. Java EE plays in a different league.
Echo: Amazon’s smart speaker preview
Brum did not have a song.
And now kids let's build something little more complicated. App with distributed transactions in cluster (each step on different node).

Full JEE stack is terrible if you would like to write sad CRUD applications. But if you need something more than simple access to DB it is very good solution.
This is not a simple Hello World app, it's a minimally viable end to end EE stack using one particular combination of many available technologies, intended to be deployed within an app server. And I am pretty sure OP knows it if he's deploying apps with "just Jetty and JDBC". Big deal; so what? Why the snarky post?
I laughed at the end. Reads like a badly written TV script, with so much buildup, tension and all kinds of weird characters in the beginning and middle of the show, then at the end comes a huge anticlimactic duh. "Hello Word!".
> Many (probably most?) of them don't, but I don't know that it has much to do with the syntax.

It has to do with the syntax. Working Lisp "plugins" is very simple because all the code is represented as plain datastructures. Rewriting program is like writing simple data structures manipulation code.
I'm a complete foreigner to web development and JVM. I've been dabbling in setting up Clojure projects a bit at home. It took a one command line call approximately (lein something-something) to get the more or less equivalent web stack up and running (to my understanding). After reading this, I suddenly understand how awesome that was.
Paul Sutter -- founder of quantcast, amongst other companies -- has said he's not suited to employment [1]

[1] https://news.ycombinator.com/item?id=3927216
He is right in the sense that for someone from a programming background, using FPGAs is far harder than it could be. I have looked into it a few times and it is indeed horrible.

It looks to me like a typical situation of legacy tools and some degree of oligopoly. I imagine a hardware person going into programming would have a similar experience (in reverse).
Probably the same reason Wikimedia doesn't: IRS guidance on accepting donations of property (which is what they treat bitcoins as). The safe thing for a 501(c)3 to do is take details.
When Wikimedia started accepting Bitcoin, I was utterly unsurprised that the very first reaction from Bitcoiners was to complain about how WMF was doing it. You'd almost think their interest was in promoting Bitcoin rather than in donating to the charity in question.
>>Setting up any web stack is a pain in the ass and probably just as long of a tutorial.

I beg to differ.

http://bottlepy.org/docs/dev/tutorial.html#quickstart-hello-...

http://howtonode.org/hello-node

(In fairness, I do note that the above examples don't actually have a <button> element to click on before showing helloworld like the Java example)
I love backspace = back button. What I need is delete = forward, so I can undo the action when I accidentally trigger it.
It hasn't been called J2EE since 2006. That's 8 years.
JSON Pointer isn't quite the same thing.
Most of these idioms actually make me sad.

When I first started using Python around 1999, it didn't even have list comprehensions. Code was extremely consistent across projects and programmers because there really was only one way to do things. It was refreshing, especially compared to Perl. It was radical simplicity.

Over the decade and a half since then, the Python maintainers have lost sight of the language's original elegance, and instead have pursued syntactical performance optimizations and sugar. It turns out that Python has been following the very same trail blazed by C++ and Perl, just a few years behind.

(At this point Python (especially with the 2 vs. 3 debacle) has become so complex, so rife with multiple ways to do even simple things that for a small increase in complexity, I can just use C++ and solve bigger problems faster.)
I think its satirical. We all know Java's Hello World is ~10 lines long. I think the point/joke is that Java EE devs don't keep things simple.

Or rather, better put, Java EE devs always want "routing, templating, separation of concerns", because they consider it better, no matter the current problem at hand.
Yes, I thought they were turning into a strange PC-World / odd electrical bits shop too.
> I sincerely doubt that. I've seen E-Banking systems run on Jetty with JDBC directly. No fancy JSRs were needed.

If you need distributed transactions (and sure, most people who think they do don't), you use the fancy JSRs or you will go out of business. That stuff is hard and it's the reason JEE is so horrible, but it solves problems you can't solve any other way.
Ha! What a load of crap! I can't see this "Java" catching on...
How about:

apt-get install php5 apache
echo "<html><body>Hello World</body></html>" > /var/www/index.php

The end.
Ah I was about to inquire were the system calls for async I/O were. That explains it.
I've also done some JEE quite a long time ago and I hated every second of it. I'm not sure however if my experience is representative of the the Java community. There is no problem with the language itself nor the VM which is also working quite fine (while taking a lot of RAM). But I really have a problem with the community, everything seems over-engineered and super complicated in Java, even with simple things.

Nothing works by default, you always have to include stuff here and there, write one or two xml files before anything would work, I'm fine with configuration but I should at least work by default. Maven is a nightmare to use, it's so complicated I would generally not use it. I would just like a package manager which is only doing packages like any other language.

The main problem with the Java community in my own opinion is they are building pyramids while other languages are building stuff out of bricks, it's the opposite of the UNIX philosophy.
This looks like a deliberately anti-java post or something taken completely out of context.
You're not limited to 4 lists on Taskulu! You can have as many lists as you want (and Sheets/Boards within your projects). But To make it easier to follow the process, each list can have up to 4 sections (i.e. todo/doing/testing/done - You can change the section titles.) - if you change it so that each list has only one section it'll act exactly like Trello :)
We have a pretty complex Java EE 7 application but we migrated from JPA to pure JDBC (obviously with abstractions so we can support multiple database implementations, but our current only implementation is PostgreSQL). So it's mainly CDI, JAX-RS (RESTful API), JDBC and timers, and it's pretty great performance-wise and developers are kept fairly productive.
I honestly think that common string handling would be much improved if String could point to either &'static str or an owned buffer, with allocation on modification if necessary, and literals coerced to either &'static str or a String that points to the static buffer depending on type inference.

String would never allocate more than it does currently, but it would do it in less predictable situations which some people probably wouldn't like. However, it would basically allow people who don't care that much about short strings to completely eschew all the .as_slice()s and .to_string()s that are currently ubiquitous in any rust string handling.
So yes, success depends on things outside of your control but if you fail because of that then it's still your fault.

Unless the forces are so strong that it doesn't matter what plan you have in place.

I lived through the 2000 crash (Genomics, but it was basically as crazy as the dotcom area) and survived. I wish I could say it was due to my better planning, but mostly it was luck. When the forces of finance really turn it washes away both the good and bad planners.
A lot of screenshots

http://community.reactos.org/index.php/news/enjoy-the-new-re...
Some comments:

1. Am I the only one that really loves that `print` is a statement and not a function? Call me lazy, but I don't mind not having to type additional parentheses.

5. Dict comprehensions can be dangerous, as keys that appear twice will be silently overridden:

elements = [('a', 1), ('b', 2), ('a', 3)]
{key: value for key, value in elements} == {'a': 3, 'b': 2}
# same happens with the dict() constructor
dict(elements) == {'a': 3, 'b': 2}

7. I see

D.get(key, None)

way too often.

8. Unpacking works in many situations, basically whenever a new variable is introduced.

for i, el in enumerate(['a', 'b']):
print i, el

{key: value for (key, value) in [('a', 1), ('b', 2), ('a', 3)]}

map(lambda (x, y): x + y, [(1, 2), (5, -1)])

Note: the last example (`lambda`) requires parentheses in `(x, y)`, as `lambda x, y:` would declare a two-argument function, whereas `lambda (x, y):` is a one-argument function, that expects the argument to be a 2-tuple.
I normally just do this for multiline strings:

s = "\n".join(["one","two","three"])
But is an expert "politician" what we really need in office? It's true that you need some political acumen and clout though. Anyway, we certainly don't want Carly Fiorina there either.
I didn't argue JavaScript is #1 on the server side, simply that it's the language with the most traction when it comes to that group of languages (of which Python is no part by the way, PHP and Ruby are though). I wouldn't touch JavaScript on the server side with a 10 feet pole.
Do you mean your yearly income must be 40x your monthly rent?
This just showed me the need for a numeric keypad. Half of the time I spent was looking for the right keys or correcting mistypes - normally I think I'm pretty good getting $ and * every time without looking.

I think the change in performance here has something to do with never returning to the home row; I'm just completely lost on laptops.
And are you going to use this process for development work? I doubt that.

Plus, in your example, at the end you're stuck with PHP. I'd rather be stuck with Java EE :)