jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
> My eye doesn't have a zoom. I see things at their actual size and even holding my phone right up to my eye I can't get it as large as those images. Details that I can't see without artificial zoom are the same as details that I can't see period.

They're zoomed because it's the only way to demonstrate the difference when the display you're looking at almost certainly has a lower PPI. It's no different from having to zoom in on a print sample to show how clear a printer's text is on a monitor.

> Clearly, higher resolutions up to some point are better for display purposes, but there's tradeoffs involved. I believe smaller pixels means less light gets through, it's more work for your processors which means less battery life, etc.

Which makes it all the more impressive that iPhone 4 has four times the contrast ratio and better battery life than previous iPhones, with the speed of an iPad, in a physically smaller space. Given that everything has been improved, it's clearly not much of a tradeoff.

FYI, iOS is perfectly capable of running applications designed for other resolutions. It's not for lack of 'flexibility' on the operating system's part that Apple chose not to utilize intermediate resolutions for its hardware.

It's also a little strange to see Android phones' variety of resolutions being described as some sort of path that Android has trailblazed. For one thing, the operating system has nothing to do with it, and for another, that sort of thing has been standard practice for a long time now, whether you're considering computers in general or even just mobile handsets.
Learning the concepts? A few hours

Using the concepts in how you naturally think about problems?

That will only come from experience. I can't say exactly how much but I'd imagine something in the realm of 6 months minimum of applied usage to different problems.
"It would be so simple"

It may seem simple but your scheme a fraught with equity issues. The ability to respond in a timely manner or arrive within a limited timeframe such as you propose is likely to reflect the luxury of privilege. And yes, equity concerns are more important than concerns over whatever minimal delays or waste they create.
How is this not solved by simply selling portions into fiat that cover expected spending needs, i.e. budgeting, and then transferring to bank account which is tied to your current credit card?

"Spending" and "transacting" is a solved problem, namely fiat and credit.

Why do crypto-assets, specifically Bitcoin, need to solve this problem?
Thank you for your points!

As I said in the article about the benchmarking-- I definitely did it the "quick and dirty" way, testing the whole application 2.9 vs 3.0 on just my device-- not testing specifically for difference in power usage, GPU usage, etc. I would love to have time/resources enough to more microtests as you describe.

Micrio used OffscreenCanvas for a long time. Turns out (apart from occasional flickering screens in Safari) while it did great for Canvas2D operations, it didn't seem to make a difference for WebGL. It actually adds more rendering steps, since you're basically rendering to a framebuffer first.

As someone else pointed out below, with loading the textures using WebWorkers, I indeed didn't use the transferable objects, so it was basically copying a lot of buffers, explaining the performance hits. I'll definitely be experimenting with that.

About the gzipping solution; I've just run a benchmark. It takes 14ms to gunzip & parse the JS base64 to ES6 string, and 59ms to run it inside the `new Function()`-parser. Comparing that to 65% CPU saved per frame drawn (not to mention the general V8 ES6 optimizations compared to the previous ES5 JS-version), I think the cost is worth it :)
Our welfare system is entirely rife with abuse. the tricks to avoid healthcare costs are exploited by foreigners and Americans alike, people who shift assets to enroll in medicaid or come here to retire with free health care are entirely abusing the system.

prioritization in vaccination at the cost of incredible inneficiency is celebrated by the media and our political class. I'm not so upset about the cost as much as the delays it causes to herd immunity. which is presumably what this vaccination program is all about.
Similar boat, except also with a kid and a nanny. The year we had to deal with employer taxes for the nanny we tableflipped and stopped doing taxes by hand, going to HR Block instead. Was tempted to try an accountant but the HRB product seemed solid enough to just go with it every year after. Anecdotally it finds credits/refunds that I know I would never have found on a manual tax return. It's not a ton of money but it saves a lot of work.
This is a link to actual free turbotax and hr block: https://www.turbotaxsucksass.com/

It was on Patriot Act with Hasan Minhaj
> Why in the world would you build an air filter around a system that does not directly interact with 93% of the air it moves?

Dyson fans produce a continuous stream of air. Regular fans produce choppy air. I don't think anyone actually notices this effect until you point it out though.
That was a misunderstanding where they saw that there had been no commit activity for 3 years, and no responses to issues/PRs filed in the past 18 months, and assumed the upstream was dead.

Making that assumption was reasonable - moving forwards without at least making an attempt to contact the maintainer "just in case" was not. It would have been courteous to at least try.

But it's not exactly the deliberate hostile takeover that you make it out to be.

https://bugzilla.redhat.com/show_bug.cgi?id=1614277#c9

>> To my knowledge, there is no need (legally) to obtain consent to use the name 'dstat' for a replacement command providing the same functionality. It might be a nice thing to do from a community perspective, however - if there was someone to discuss with upstream.

>> However, dstat is dead upstream. There have been no updates for years, no responses at all to any bug reports in the months I've been following the github repo now, and certainly no attempt to begin undertaking a python3 port.

>> Since there is nobody maintaining the original dstat code anymore, it seemed a futile exercise to me so I've not attempted to contact the original author. And as pcp-dstat is now well advanced beyond the original dstat - implementing features listed in dstat's roadmap for many years, and with multiple active contributors - I think moving on with the backward-compatible name symlink is the best we can do.
The article's description of the Schrödinger's cat thought-experiment is one of the worst I have ever heard. It makes it sound like someone is actually killing cats in boxes to prove some part of quantum physics.
Well said. Skills and attitudes from improv are incredibly useful in all kinds of situations ...

A variant I'd suggest when playing the game in real life: as well as imagining an ace on your own forehead, imagine that the other person also has an ace.
You probably want to ditch the official client join a mining pool to get anything, but sadly without a GPU you won't get much. I just started goofing around this weekend and earned like 0.07 BTC from three computers over at http://btcmine.com/. But I was surprised I actually could use the GPU on my MacBook Pro, not that it's anywhere as fast as the ones serious miners are using.
Agreed. Nothing more be said.
I've never seen anyone so dissatisfied with $200M. They'll probably end up losing all of it in legal fees if they keep this up.
A true AGI will solve robotics itself, whether it is already instantiated in a robot or not.
There are definitely two conflicting forces at work here - social networking making every action seem both insignificant (in comparison to the barrage of updates we receive every day) while also making almost every event quite significant (Hundreds of comments, comments on comments, etc). But one force might not necessarily prevail over the other - they can work it tandem, leading to interesting results.

One issue with jdietrich's initial comment is that his views on social networking revealing our true insignificance assume that the selves we display in the "unreal" world of social networking are, in fact, accurate representations of our "real world" selves; in reality, this is hardly the case. I know I've caught myself thinking "How will this Tweet or that FB update make me look to my friends/followers..." - hardly a parallel of how one lives and presents themselves in the unpredictable, variable real world.

This, in my mind, is the product of the conflicting forces of exaggerated significance / insignificance - the intense crafting of our online personalities. We've seen the blue marble - have realized that with all of the white noise, we must seem better, funnier, more interesting, to break through the noise. Yet at the same time we know that, should we actually get noticed, we will get noticed in a serious way - hundreds or thousands of people might see our update. The pressure is on.

As I see it, this is the product of these two conflicting forces: A high-pressure culture, a culture of scrutiny wherein every action and sentence is specifically crafted and cultivated. Orwell's 1984 comes to mind, but rather than Big Brother watching over everyone, it is the public that constantly watches each other.
You excluded from consideration all the people who would see/rent/buy the movie, but are satisfied with the pirated copy (shifted to group 3). Why do you think them rare?
Why not find somebody local and pay them a chunk + referral fee for representing you on the day?

If you vet properly it will be far cheaper than flying, cost a few hundred and could get you some solid contacts anyway.
I don't think Google would give Mahalo preferential treatment - although sites like TechCrunch sometimes give us the impression that Jason Calcanis, Google Brass, Kevin Rose, etc... are all part of some sort of untouchable Silicon Valley illuminati, that's really not the case.

Google cares more about the quality of its search results than any personal relationship - I don't think they'd hesitate to burn some of Mahalo's domains if they thought it was negatively impacting users.
I think that Facebook has a right to protect their data, but leaving robots.txt wide open and trying to enforce some random TOS that a developer might not even know about is the wrong way to do it. I think a much better method would be to ban all bots from robots.txt (and crawling) except the major search engines and provide data to others through APIs or other means that are controlled (and the TOS can apply to the API rather than random crawling). Maybe not what a developer wants to hear, but the truth is that the internet is infested with bots that do nefarious things, and I think it's better for the privacy and security of their userbase to control the spread of their data as much as possible.
Premium features basically. That's how Blogger stayed afloat before it was bought by Google. Posterous got tons of new features since it launched, and it wouldn't be hard for them to hold a few back and create a compelling package. I believe many customers would pay for a solid templating system, for example.
I disagree with point one:

*Email has no place in social media*

People prefer to keep social media messages and email messages separate, and moreover do not want the two mixed together in some weird tech soup.

I have a active community website that has areas that are not auto subscribe for email notification, and some areas that are email auto subscribe. The areas that are auto subscribe are what draws in the traffic to the site to remind them the site exist and are the ones actively posting. Most seem to prefer this and many time are not even aware of the others areas of the site. I am working to fix this awareness
"These immortal cells have multiplied to the point that if you were to weigh all of them that live today, they’d weigh about 50 million metric tons"

I would say yeah - a couple more :)
Doesn't include email addresses, which is what this whole kerfluffle is about.
everything is shared under the ge.tt (domain's root name can't be a CNAME). you obviously think you won't need a content delivery network at scale, do you?
The description:

On December 9, 1968, Douglas C. Engelbart and the group of 17 researchers working with him in the Augmentation Research Center at Stanford Research Institute in Menlo Park, CA, presented a 90-minute live public demonstration of the online system, NLS, they had been working on since 1962. The public presentation was a session in the of the Fall Joint Computer Conference held at the Convention Center in San Francisco, and it was attended by about 1,000 computer professionals.

This was the public debut of the computer mouse. But the mouse was only one of many innovations demonstrated that day, including hypertext, object addressing and dynamic file linking, as well as shared-screen collaboration involving two persons at different sites communicating over a network with audio and video interface.
I agree fully. I focused on the front-end because squeezing milliseconds out of the backend is my day job, and I'm pretty confident I can generate pages in < 50ms. Given that, I thought it would be interesting to see just how much I could squeeze out of the delivery time.
While I think there are tons of areas computer science applies to, I think this article is a little ridiculous. It's main point is that people who study computer science know how to us Google for answers to computer problems.

This XKCD flowchart sums up a lot of what the article says are advantages to a computer science education.

http://xkcd.com/627/

Granted, CS students get really good at using Google and reading manuals and things because of the virtually endless supply of new libraries/plugins/APIs and other tools that are used.
I didn't see the link come up myself, but my immediate thought isn't that people were discouraging playfulness; they were flagging seemingly inappropriate material. If the article is about link baiting, say that in the title.

"Read the article first" isn't a good defense. What if someone were to post something called "XXX Free Porn"? You don't want to be clicking that in the wrong company, even if it is just a joke title. At the same time, you don't want spam links to persist, so you flag it without reading the article.

Anyway, if people miss out on a good article because it was poorly titled, it won't be the end of the world.
Our company is a Greek word so we tend to use Greek names/words.
Same thing on Windows. Since Windows XP many new APIs are exposed only via COM interfaces.

Only masochists use COM from C.
I've did some research a while ago and found that https://github.com/crazy-max/docker-matomo dockerizes it the best.
It is not my codebase, I had to clean it up. I managed to do it though and it basically looks like every other libGDX project. I can even create a single JAR file that works! I am pretty happy about that. Everything is up to date, and I am converting the codebase from Java to Kotlin. Still a long way to go, but we (my partner and I) will get there. :)

By the way: I also use `googleJavaFormat` and `ktlint` to format both Java and Kotlin files. I also pack textures before running the game.

In any case, my old hardware may be at fault here, or the fact that I also run multiple things in the background, or that I run a couple of Gradle tasks, or a combination of these things.
The biggest difference is that the post doesn't come with the upvoting rings. So unfortunately OP won't ever find his product featured here
> My understanding is that most voters don't support universal healthcare.

They don't support the version of universal healthcare that's usually proposed, but give them a way to make their own choices to keep them out of a Charlie Gard (a.k.a. "Death Panel") situation, even if it means having to pay extra, then there would be much more support.
Same in mine, but instead of WhatsApp it is Rakuten Viber, which is massively popular in Eastern Europe. Beats me why, I don't like it that much and don't have a slightest idea about what are they doing with our data. But it became an issue trying to communicate without it. I'm a WhatsApp user from the early days, and I'm still dreaming about a day WhatsApp will be "independent" again.
From your link:

>"According to Kelly and Laycock’s book, the United States has invaded or fought in 84 of the 193 countries recognized by the United Nations and has been militarily involved with 191 of 193 – a staggering 98 percent."

"Invaded or fought in" - that's a pretty big "or" there no? The theater of operations for the US Military in World War II was easily 84 countries in itself [1]. Also 84 countries is not all but 3 is it? Nor would it be considered "most" as you stated.

Further that's not really a citation that supports your assertion. It's a post with a single reference to a book entitled "America Invades: How We've Invaded or been Militarily Involved with almost Every Country on Earth." The phrase "or been Militarily Involved with" is casting a pretty wide net no? That's quite a nebulous clause. If you sell someone a tank you are "militarily involved" with them. By that dubious measure much of the globe is "militarily involved" with each other.

Have you read this book? What's seems to be notable about this book is the absence of any footnotes or bibliographic information. This is quite odd for a history book. I think this book could be accurately described as "entertainment reading" as it seems to lack any academic rigor.

[1] https://en.wikipedia.org/wiki/United_States_theaters_of_oper...
Been working on a 'FashTech' project - A menswear styling platform - https://www.unstitched.xyz

The idea is to help men learn more about what matches through peer review and by providing a framework to experimentation. By sharing capsule collections other users can mix-and-match different combinations and create outfits that people can like/up-vote. Going further I'm trying to add the ability to find outfits that contian items they have in their wardrobe. With the eventual goal of adding a graphing data base (and possibly some ML, to help try figure out what clothes match - This is usually VERY regional, based on occupation, music taste, and a lot of other factors, the fact that it's so subjective is what makes it a fun project to work on :)

I've build the main app using Rails & VueJS but would be really interested in teaming up with someone technical to help drive the platform forward, but especially somone (no tech skills necesssary) to help build the community and try get more people on board (I have lots of ideas and thoughts on how to do this, but not enough time between a full time job, and trying to build it.

Feel free to contact me on HN or send me an email to paris@unstitched.xyz if you're interested or just wanna chat a bit mroe about it :)
Why does AWS insist on building this way? Has anyone tried to get the teams together and say, "stop, let's evaluate and simplify where we can?"

As an AWS customer, I find AWS a huge pile of overcomplicated offerings that is dense with its own jargon and way of doing things. IAM is a trash fire. Everything built on IAM like IRSA is also a trash fire. Why are there managed worker nodes, spot managed worker nodes, Fargate worker nodes, self-managed worker nodes, and spot self-managed worker nodes? Why are there circular dependencies for every piece of infra I stand up making it almost impossible to delete any resources? Why can't I click on a service and see how much it costs me in one or two clicks?

This is a completely insane way of building software to me and I have to eat it.
Yeah there is a difference, but there is also a similarity. Google links to news articles with or without permission. They even got sued for doing so. Just because Google is doing it doesn't mean it's legal, and even if Google has permission it doesn't mean everyone else has permission.

As for what a judge would think, the fact that you had to find a way around their content protection gave a clear sign that they were trying to protect their content. The DMCA doesn't really discriminate when it comes to the difficulty of copyright circumvention.
This from wikipedia is where it started to click for me:

"In the 18th century Euler studied the rotational motion of a rigid body and discovered the importance of the principal axes. Lagrange realized that the principal axes are the eigenvectors of the inertia matrix".

So the eigenvectors are like the directions that describe position of an airplane: roll pitch and yaw.
Thanks for an extremely thoughtful and well reasoned contribution.

FWIW, I wonder if the decentralization / popularization of access to space technology will contribute to lower costs that can iteratively enable higher research goals without needing to cajole wrist-slashing degrees of government spending?
The four pros I spotted were "cool", "learning and having fun", handle "a huge amount of data" and "distributed processing."

There's no claim that it's trying to give the complete picture. It's trying to solve a specific task for chess board analysis. Nor did it reject that Hadoop was always the wrong solution, only that a single node can be faster than Hadoop. An existence proof is a low barrier to cross.

You say "this is a different scenario" and I have to shrug. I used to do molecular dynamics distributed across a compute cluster or using a supercomputer. That's yet another different scenario, and also one where Hadoop doesn't work. Last I heard, simulation software I helped write now runs across 8,400 cores. (See http://www.ks.uiuc.edu/Research/gpu/files/gtc2013_phillips.p... .) The visualization project I used to lead now analyzes 100+ TB of simulated trajectory data. (See http://on-demand.gputechconf.com/gtc/2014/presentations/S441... .)

MD definitely falls into "Big Data", yet the examples I gave don't use Hadoop or data partitioning like you suggest, so your statement about Big Data frameworks is really restricted to only a subset of what people do in Big Data.

So yes, you're right. The original essay isn't complete. Neither is this new one, which didn't include all the problems with Hadoop, like poor inter-node latency, and lack of support for MPI. The 'real choice' isn't as dichotomous as you make it out to be. A set of powerful non-commodity hardware, like Blue Waters, may be the right approach for some scenarios.

"Without the complete picture"

I disagree. The new essay gives a different picture. A lot of pictures fit well in the frame of Hadoop, for the reasons given in the new essay.

In this case the pictured scenario is chess data analysis. In this case it looks like a single node is faster. However, it's not better for the original original task, which was to experiment with learning Hadoop. ("I was skeptical of using Hadoop for the task, but I can understand his goal of learning and having fun with mrjob and EMR.") As the original original spec no longer exists, I cannot tell if fault-tolerance was one of them. As it was a personal learning project, no doubt it wasn't.

So this new essay is adding details that weren't relevant to the original task, then complaining that the details weren't addressed. This is poor form.

You ask "how can you say when you need one, ten or 100" and the easy answer is to go ahead and implement it on one node. If it takes an hour to write a single node solution would take, and it's fast enough for your foreseeable needs, then you're a lot better off than spending a day to try out a Hadoop solution. Plus, without the single node solution it's hard to know if you have a good baseline.
That's interesting, thanks. Khan academy has been on my crush list for a while, it's fun to consider taking a break from consulting work to apply for an internship...
Wow, I had no idea there were over 300 ASCII art fonts.

Actually, I had no idea there were ASCII Art fonts at all.
Movies have motion blur which smooths out the judders of a low framerate