skysight-inc/HackerNews huggingface dataset:
A common misunderstanding.

My wife is from a very comfortable middle class Polish family and went to one of the best universities in Poland. In her summer holiday before starting university she worked in a factory in the UK for minimum wage assembling car headlights. She did this because the pound-złoty exchange rate made this work more financially rewarding than anything she could have done in Poland.

I have more examples of Poles who are working in the UK right now, simply because of the exchange rate.

I've met many UK-based Poles and not one has preferred life in the UK to life in Poland.

If anything, the exchange rate allows someone in the Polish bottom 10% to climb out of that 10% much more easily than a bottom 10% Frenchman could: Go to western Europe and work for the minimum wage for ten years. Upon their return they'll have more than enough for a nice house.
Doing an import is hardly going to ruin your existing installation. Back up your blog and do the Jekyll import, and see if it’s worth switching to you. :)
Make a script that adds the comments to the static page. I made a small static site generator that has comments, search, etc. for my own use. https://github.com/Harri/Spage
>I positively hate bloat in all its forms. Take the Google homepage. It’s a one liner text field and two buttons. It weighs in at a whopping 1170 kilobytes! That’s more than a megabyte for what technically should not take more than a few hundred bytes.

That's because you didn't consider the business reasons behind it being 1170Kb.

If it was your "few hundrend bytes" design it would have sank the company (or only have worked in the early days, when VC money took care of lack of income sources).
Nokia’s Here Maps Sold for $3B to Audi, BMW and Mercedes
That used to be the case but now it is not entirely so. If reputable people (e.g., high-karma HN users) continue to use either word it will eventually be "redeemed" wherever they are reputable and become acceptable to use.

edit: For the record, I didn't downvote you.
Well, this is a basic skill of a programmer, or even an engineer in general. It's not about fitting a very warped vision, it's about applying different models to the same situation. As long as you keep in mind that you're just applying models, you'll be fine. If you forget about it, you'll end up becoming a politician.
I wrote about a similar issue, but with Web Development - a much more routine branch of software development (IMO). Plenty of room for automation here.

My Job Went to GoogleBot (and all I wrote was this lousy article): https://www.symfony.fi/entry/my-job-went-to-googlebot-and-al...
> inlined the stylesheet (there is a cache penalty here so you have to trim it down as much as possible but the page starts rendering immediately which is a huge gain at the cost of a little bit of extra data transferred)

I guess you're optimizing for people who only visit one page and bounce away?

Well, come to think of it, the majority of visitors who followed this HN link is never going to navigate past the single page that was linked. So it probably makes sense for optimize for them, at the expense of repeat visitors who will have to download the stylesheet over and over again.
People forget to mention that Santa deserved it. And they didn't just boo him, they threw snowballs at him.
>doesn't inlining the CSS make the page require more data in the long run? Especially if you're not changing it often
Browser caches solve a lot of things for us.

Apparently they don't. I remember reading 2-3 articles on the issue, and most things we'd expect to go there, don't even touch the browser cache.

Maybe for Google (a page we visit every day multiple times) that would be different, but for your average site the browser cache could as well be a forbidden zone with all the competition for the same limited resource.
You gotta be careful when using BETWEEN.

BETWEEN does

a >= x AND a <= y

Usually, you want

a >= x AND a < y

http://www.postgresql.org/docs/9.3/static/functions-comparis...
anyone downvoting you has clearly not read the Halloween Documents[0].

0. http://www.catb.org/~esr/halloween/
For small datasets[1], latency may dominate bitrate. So it may be advantageous to receive everything with a single request and a single response.

Also, if your blog doesn't change often, it will also be seldom visited[2]. So the browser cache may not help here - either due to cache invalidation, or because you changed a tiny bit of your CSS in the meantime.

[1] And honestly, from that perspective all blogs are small.

[2] Ideally, all your readers use Atom/RSS.
> Take the Google homepage. It’s a one liner text field and two buttons. It weighs in at a whopping 1170 kilobytes! That’s more than a megabyte for what technically should not take more than a few hundred bytes.

The Google homepage does a lot more than that. Since it is one of the most important pages for Google, I think that the engineers over there know what they are doing.
I don't think it is a good example of bloat.
Fix windows 10
Sigh... this is just offensive and ignorant. Philly threw snowballs at Santa Claus. We wouldn't let him off with a mere booing.
There was a documentary a while ago about the building of the QE2 in Scotland in the mid 60s. One of the former trade union leaders interviewed remarked that in hindsight the giveaway that things for the UK shipbuilding industry was going to go badly was they were using equipment built in 1905. We see this stuff all the time across the world.

The short term risk of upgrading can be an awful lot more than financial. Vested local interests can often cause all sorts of problems. Especially if your investment in new equipment leads to you essentially trying to compete on highlighting local environmental and labour abuses. Combine that with humanity's natural "it's been good so far, why wouldn't it continue?" inclination...
That's a good point, there is a lot of functionality behind the google homepage. Bad example! I'll search for a better one.

I've updated the article with another example (a BBC news page).

Thanks!
Mine is faster :) https://github.com/kaihendry/natalian

X1C3:~$ httping http://natalian.org
PING natalian.org:80 (/):
connected to 54.192.159.125:80 (147 bytes), seq=0 time= 91.36 ms
connected to 54.192.159.123:80 (147 bytes), seq=1 time= 28.63 ms
^CGot signal 2
--- http://natalian.org/ ping statistics ---
2 connects, 2 ok, 0.00% failed, time 1394ms
round-trip min/avg/max = 28.6/60.0/91.4 ms
X1C3:~$ httping http://jacquesmattheij.com/the-fastest-blog-in-the-world
PING jacquesmattheij.com:80 (/the-fastest-blog-in-the-world):
connected to 62.129.133.242:80 (329 bytes), seq=0 time=550.05 ms
connected to 62.129.133.242:80 (329 bytes), seq=1 time=550.08 ms
^CGot signal 2
--- http://jacquesmattheij.com/the-fastest-blog-in-the-world ping statistics ---
2 connects, 2 ok, 0.00% failed, time 2760ms
> "(For related information on SDF and the history behind this public access UNIX system, read "The HACKER CRACKDOWN" by Bruce Sterling)" @ http://pdf.textfiles.com/books/hackcrac.pdf (use something like ePDFView and rotate the book)

This text is available so many places online it isn't even worthwhile to go to that much trouble to read it.

Project Gutenberg:

http://www.gutenberg.org/ebooks/101

MIT:

http://www.mit.edu/hacker/hacker.html

Cory Doctorow reading it (link to first episode):

https://archive.org/details/CoryDoctorowPodcast86

Podcast feed with all episodes:

http://xiph.org/~giles/2008/hackercrackdown-ogg.xml

http://xiph.org/~giles/2008/hackercrackdown.xml

Boing boing boing boing:

http://boingboing.net/2008/01/13/podcast-of-bruce-ste.html
you've given great examples as to why Windows does not compare favorably to an automatic transmission. thank you.
Not to hijack the thread, but is anyone else noticing all the anti (or even neutral) MS posts are being greyed?
His rants are excellent. Under the coating of expletives hides a goldmine of no-bullshit common sense.
Mt. Gox CEO’s misdeeds may run into the tens of millions of dollars
I didn't get the hype about their soup, yet can recommend the whale steak.
G+ could be more popular if Google knew how to launch products - not tech demos. They launched the thing and made it invite only, when people were eager to try it out. I don't know who had this clever idea, maybe they thought they could repeat the Gmail launch or FB exclusivity.
So I think that you are not alone :-) I don't really know how, but we should take the better side of this situation. Your story was really interesting. PS: have you just learn piano?
My idea of a secular community. Every member put 100 dollars on the table, then people decide what to do with that money, REPL. That force people concentrate on actions and look for directions or goals.
<form method="post">
<input type="text" />
<button type="submit">Post</button>
</form>

That will probably load really fast. You can server-side cache the post comments section fragment (or the render of the entire page really) to get nice results
Small correction: Heroku is owned by Salesforce.com.
On the contrary, I feel the exact opposite: the entry bar for the search engine market is not high. Google delivered a good service from the first day, which was not improved so much since them. A newcomer have to reach only this quality and combine it with some spice, like P2P and it can reach a big market share. Although some revolutionary improvement in the search result offerings wouldn't hurt also but this has less chance (waiting for a better AI).
I can't recall the source, but the story goes as follow.

In some game, menu was written on stone tablets. Due to the bug tablets received guard AI and would randomly walk away to patrol the island.
https://developer.chrome.com/multidevice/android/installtoho...
Grothendieck’s “Long March Through Galois Theory”
Several works cite “La longue marche a travers la theorie de galois”. The work by Leila Schneps "Grothendieck’s “Long March through Galois theory” ( http://webusers.imj-prg.fr/~leila.schneps/SchnepsLM.pdf ) tells us that there is as TeX format of the Long March.

I have looked on the Internet, and was able only to find the repository http://webusers.imj-prg.fr/~leila.schneps/grothendieckcircle/LM/ . It has part only the part B of the work ( http://webusers.imj-prg.fr/~leila.schneps/grothendieckcircle/LM/LMIb.pdf ). In the libraries the manuscript seems to be only available on the bookshelves of several University libraries. Neither Amazon, or other online stores has the manuscript.

Does anyone know if there are scans of the work on the Internet? Or maybe someone has a digital copy of the published work?
Cheap Choker Necklace Makes You More Glamorous and Gorgeous
I would have said Debian up to the whole Jessie debacle with systemd and abandoning core precepts. Now I have to recommend a different base.

I've never done a graphical debian install. how does it compare to KaOS?
>the entry bar for the search engine market is not high

You just need millions of computers, millions of petabytes of net traffic and a lot of time to have the same index as Google. Easy.

For example, look at how useless Bing is. And that's Microsoft!
Cool book, I hope you will get some success with it. I don't have a kid (yet) but I will maybe buy it as a gift as I live in one of the countries with publishers.
You never share some things only with certain groups of people, because of relevance or intimacy ?
I'd rather buy a new mac and photoshop than windows 10.
Nolan Bushnell made terrible pizza. soapbox denied.
Coldtea pointed that out as well, I've changed the article to reflect this. Thank you!
because everyone who doesn't worship Apple is a "hater".
There used to be a bug in Kerbal Space Program where solar panels would be occluded by the UI windows.
This is absolutely brilliant if the only metric your audience cares about is page load time. For most sites that's only part of the story.

Take the first paragraph, about how Google's homepage of just a textbox should really be a few hundred bytes instead of a megabyte. Google's homepage does a lot more than just enabling you to enter a search - there's the autosuggest feature, there's analytics, the apps tray, G+ integration with live updates, etc. Google's homepage looks basic but under the hood there's a lot going on. Which is the real crux of the matter - Google have designed something that doesn't get in the way of searching but is really a powerful portal to Google's suite of services because that's what gets them the data that makes them money. The fact they might be able to shave a milliseconds off the domContentLoaded time (which is only 394ms on my work PC) wouldn't make anyone happier but it would damage their bottom line because they'd know less about us.

If Jacques blog gets a significant amount more traffic by loading super fast then that's a definite, measurable success. If the only change is that it loads faster, and he doesn't grow his audience, then he hasn't really achieved anything.

There's a good lesson in this that's analogous to startups that spend huge amounts of time and money doing things that get them no additional customers. Optimising things that don't affect the metrics you use to measure how successful you're being is a waste of effort. Put your time in to things that actually matter.
I bet if you forced yourself to use Bing, and weren't turned off by its look and feel, you'd find it to be an equal replacement. In fact, I don't have to bet: both companies have detailed metrics that consistently show them within a few percent of each other on precision, recall, etc.
You either don't know the meaning of the word "irony" or you have some issues with cause→effect relations.
There is a small penalty but it does not seem to weigh up against the advantage of having all the data in one shot even on first page view on that site. Total overhead of the CSS 'in flight' is about 6.6K, versus doing another request which would require another round-trip to the server.

Inlining the CSS was considerably faster in all my tests.
Does anyone know what the implications are for the phone application? Its default map application on the Ubuntu phone, and although its missing some features, its quite nice overall.
Looks great.

Recently, I was trying to wrap my head around eigenclass inheritance mechanisms and it was pretty tough. Not to mention the object model, where classes are also objects and the Object - Module - Class relationship. I wouldn't recommend Ruby as a first language to anyone — it may look easy at first, but to grasp it, you need to invest much more time in future.
I looked at all the recent smartwatches for a while -- I hadn't worn a watch in 20 years. TL;DR, I didn't buy one -- instead I discovered the world of real mechanical watches which I had totally ignored for years and bought some of these instead...
I really wonder how many people went thru this same process... I mean, 'disposable income' can buy a smartwatch that will be landfill in 3 years, OR it can buy something that'll still run in 30 years with a bit of luck... as far as the 'nerdy factor' (and 'new toy' factor) is concerned, a mechanical watch does hit quite a few sweet spots too...

So that Swatch doesn't 'do' it for me here -- you can already buy automatic watches with chinese movements for a LOT less than $150 -- in fact, you can get one for $15 (check aliexpress); with movements that are actually quite nice and fairly precise (most of them). Oh and they are not sealed, so can be serviced.

Mechanical watches of reasonable quality need to be services at <=5 years intervals; so one can assume that Swatch useful lifetime without a way to service it will be in fact rather similar to an Apple Watch in the end.
if you care about bytes, you could minimise the css & html also
I'm glad I had a better experience with AirBnB in NYC.
The Search Engine?

Maybe not in the sense of "A site where you enter text and find pages containing that text". Just like Microsoft Windows might never be replaced as the most popular Desktop OS. Desktop OS just become less and less important.

But certainly in the sense of "A way to get answers to your questions". I expect computers to learn about the world and give answers directly. Just like image recognition software can tell you the answer to "Does this image has tomatoes?". Software will be able to answer "Do tomatoes grow in China?". Or answer "Paint me an image of tomatoes in China" the way Googles deep dream net can already "paint" lots of things [1].

It will be interesting how this turns out for "content creators". When computers learn and become creative, there will be no more SEO :) Because your site will just be read and ingested by a bot and make it better to answer questions. No more clickt-hroughs to your website.

[1] http://www.reddit.com/r/deepdream
The amount of float point arithmetic done on the CPU in modern games is less than you'd think. For graphics you are looking at no more than 1000s of matmuls on the CPU, 10 000s at worst. Games that do their physics on the CPU still struggle to saturate it even with SSE. In games a good amount of CPU time is spent moving bytes around, which is precisely why we have data oriented programming.

The reason the CPU bottlenecked pre-DX12/pre-Vulkan games is because a hefty amount of it was used for the abstraction: likely little of which was FLOPs. Basically: you forgot to profile first ;). For a purely graphics workload the CPU will be doing relatively small amounts of work.

In addition I can say with fair certainty that a smaller portion of the gamer market upgrades their CPU on a regular basis (so-called enthusiasts). Taking myself as an example: I haven't upgraded my CPU since 2010 and I've only started feeling that pinch this year. That's a lot of CPUs without AVX2 support.

TLDR; AVX2 is currently in the "solutions looking for a problem" bucket.
German automakers buy Nokia maps unit for $3.1B
I'll presume you're not someone trying to rationalize their own laziness or manipulate young whippersnappers not to make geezers look bad.

For anyone that wants to be a rich founder, almost sensible but definitely effective workaholism can help. The main issue is that only a few people are motivated enough (irrespective of vesting schedule and equity share classes) to get shit done while everyone else wants to look busy or shift work to those sort of folks. They have a name: dead weight freeloaders. Be the fast, effective shit doer because there's no room in awesome for sloppy, lazy crap and excuses like retail employees try to pass off every day.
> physical proximity is an absolute requirement for a community

Quite possibly, but what happens when you move? Labour mobility is an inescapable part of the modern world, as is the desire for young people to move to the "big city".

This is particularly bad for inter-generationality. Perhaps that will improve once the long term diversity acceptance values shift has completed.
The google homepage doing a lot more was pointed out earlier, I've updated the page to reflect that.

> If Jacques blog gets a significant amount more traffic by loading super fast then that's a definite, measurable success. If the only change is that it loads faster, and he doesn't grow his audience, then he hasn't really achieved anything.

If audience growth were the target, then yes that's true. But what matters too is that the audience that you already have does not spend more money (downloaded bytes on mobile for instance) or time (delay time waiting for stuff to load) than they really need to. On top of that I suspect (but can't prove) that a faster site will lead to people viewing more pages on that same site simply because of the convenience. For ad driven sites (which this is definitely not) that might turn into more turnover, and for e-commerce sites (which there is plenty of proof for) faster load times result in more turnover.

Keeping your users happy is important, even if you don't attract more of them directly. (Retention is a very important factor in a growth strategy...)

Premature optimization is definitely the root of all evil, but bloat is something you can do without. It's a matter of striking the right balance and I think that this blog probably is on the 'wrong' side of that balance but I just wanted to make an example of how much bloat there really is.
Having played on (and heard people play on) a pBone, I'd have to say that even though it's quite impressive to see what they've been able to do with just plastic, it's still quite some way off from being a 'quality' instrument.

And they do not prove at all that the same can be done for any kind of instrument: trumpets and trombones are a lot cheaper to make than things like bassoons - you can find very cheap brass trumpets on ebay for very little money, some of which are surprisingly acceptable; and a rather good trumpet will set you back quite a lot less than a basson only fit for a beginner.
many of us have avoided (or selectively/safely used) the accessories of this era, because we value our liberties.

Seychelles/Iceland-based cloud storage providers, and rk3xxx-based mobile devices (with VoIP) keep us relevant and reasonably modern while preserving our rights.

There are more of us than you think.
To consider function types, or unjustified assumptions about bitfield unions, or use of parentheses to control nesting of arrays and pointers in declaration "strange" one must be averse to the C language to the point of intolerance. Backlash from working on a C compiler and wishing the task was easier?
That's a nice short story, but I'm not sure what the intention is. Is this supposed to be a hyperbolic description of the typical Airbnb experience? If so, I must have been extremely lucky so far (but maybe it's a regional thing -- I've only used Airbnb in Germany and England).
Isn't Heroku a subsidiary of SalesForce? Google's equivalent is Google App Engine.
This is why I despise mathematicians. Everything was going smoothly, until they obscured the whole concept behind that awful notation. Why? Notation is the destroyer of understanding.

Letter, pipe, letter, superscript. Yeah, real nice. Clear as mud.
How to build a data science team?
then the ultimate, which would be whether you use web components to minimize tag lengths/define structures to compress.

Though at that point gzip is probably the better solution.
Not that the comment trick has anything to do with Duff's device, but any editor with syntax highlighting would display the commented-out lines in a different font, making the situation considerably more clear.
By my measurements (and pagespeed and a couple of other tools like that) it's actually faster for repeat visits and multiple pages on the same site as well (which surprised me but I'll yield when the data is that conclusive).
As someone who is using both HERE maps and Ovi maps on my smartphones, I wondering that as well.
One of my favorite entries: http://www.ioccc.org/1988/westley.c

#define _ -F<00||--F-OO--;
int F=00,OO=00;main(){F_OO();printf("%1.3f\n",4.*-F/OO/OO);}F_OO()
{
_-_-_-_
_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_-_-_-_-_
_-_-_-_-_-_-_-_
_-_-_-_
}
Pretty much what I was thinking. If there is too much logic at the app level, its often worth revising your database models. Though a lot of the youngsters these days don't seem to bother with relational databases.
with a baseband exploit, it's trivial to install a keylogger on an iphone.

all it takes is one skilled user to make all the dumb ones their slaves.