skysight-inc/HackerNews huggingface dataset:
>Someone will eventually drag the topic to your door.

This has already happened, I expect it will continue to happen as along as people engage in behaviors contrary to their signaled beliefs.

>European end users care and so do businesses doing business with them.

If Europeans visiting our site is now considered doing business with them, then this is an example of European user behaviors acting contrary to their signaled beliefs.

"So right away, let us cast aside the technological protocols, that are usually referred to as “the internet”, that of which was built upon that make accessing or publishing information public between two or more machines…

Because talking about such things would require most internet users to cast aside social constructs they willingly suspend on a daily basis upon engaging with such technology/services (without any care to understand for oneself, one might add) and then demand collectively in retrospect to have their cries pacified while continuing to use such services (of which, most for free).

Yup, let us look past all that and believe (because that’s all we can do for ourselves) that institutions/organizations/companies/governments, that all consist of our fellow human beings in all of our qualities and flaws, can provide for the individual that which he chooses not to do for himself, to a satisfactory level in which his desires are forever coddled and placated." "The Banality of Privacy As A Service" [0]

[0] http://pictobar.tumblr.com/post/63785124046/the-banality-of-...
Bitcoin Is “Under-Owned” Among Institutional Investors Says Dan Morehead
Same. Messengers used to just work, now we have a bunch of walked off shit with no intercommunication. "Are you on Slack / Discord / Skype / Telegram?" question is getting pretty annoying.
NoScript creates problems, too.

I have no problems with the use of JavaScript. I have a problem with tasteless dickery.
Design patterns feel completely obsolete now.

Not only does no-one at all talk about them, most of the design patterns themselves were harmful and are now completely unnecessary due to functional language features being available in modern languages.

Design patterns are like TDD, no-one wants to come out and admit it, but they were really, really bad outside of theory.

InitiatorFactoryFactory I do not mourne thee!
What you may not understand about crypto’s millionaires
I do get the impression that the ceiling for attorneys is higher.
>Microsoft has one included with Outlook whose name escapes me.

Mircrosoft's current stab at this is called Teams. I think it actually has potential: it's pretty much a clone of Slack, except that MS is willing to declare it compliant with, e.g., HIPAA.
The majority of game engines scene graphs are retained mode 3D abstractions.

Everyone thinks that they can do better with an immediate mode API, then we start building some kind of data structure to track down what needs to be drawn and when, with the result being similar to the traditional joke of half-implemented Lisp or ORMs, but applied to retained mode rendering.

Sure, some experts manage to get it right, and those are the ones that get to write AAA game engines, but many don't.
Why not kill yourself today? The answer may be similar.
I read it, it was interesting but if you are looking for actionable advice I'd go for the William Irvine book first.
Building and balancing a k-d tree is not free, either. I suspect that the GP's approach is roughly the same in terms of theoretical complexity, but effectively trades memory for smaller constants and a chance to trip over edge cases like dense groups of points.
Sadly, I would that 99% of companies don't care, unless mandated by government regulation.
Indeed, Federation was only a part of their Enterprise offering. :rimshot: It is only Slack-to-Slack, so it is not interoperable in that way. Shared channels are a thing now too, and danged if I can keep up with all the new bells and whistles.

Slack is very much an organizational groupware product, with chat done well. Not the utopia federated XMPP promises, but frankly, XML just needs to die. (Which, not coincidentally, is part of what attracted me to work on the telehash specification.)
Developers that don't want to bother how to properly use a linker.
The W3C attempted to say version X.Y.Z of SQLite will be the SQL standard for the web, mandating 1) that it be frozen in time 2) that the only way to be compliant was to put SQLite into all browsers, bit for bit, there would be no other way to be compliant.

As much as I wanted it, and was bummed that Mozilla protested so much, they were/did/are doing the right thing by saying that SQLite cannot be used as a standard, it isn't a spec.

What one can do, is compile SQLite to emscripten or wasm, or write a SQL engine in JS and use that in the browser. That is totally fine.

https://github.com/kripken/sql.js
This is not right.

The GDPR allows for reasonable usecases like this. The principles are pretty broad and only stifling once you get into the realm of sharing data between organisations [0]

Such uses are "Appropriate", but you would be expected to maintain this information securely and you would not be allowed to use it for some other surreptitious purpose?

This actually enables further innovations for instance you can log a cars behaviour without a user fearing you might sell this information on to their insurance company.

What upsets people about GDPR is it does away with the notion of data being the holders property and enforces obligations to the subjects of that data.

Of course in this day and age where "data is the new oil" this is upsetting for some.

At the end of the day however this demonstrates how regulation, apart from propping up inneficiet markets also serves to protect the public from rampant commercialisation of every aspect of their lives!

[0] https://united-kingdom.taylorwessing.com/globaldatahub/artic...
Peopleware: Productive Projects and Teams

I mostly wish this to my ex and future managers, but colleagues wouldn't hurt as well.

Working in Berlin I'm constantly baffled how ignorant of the "old" research people are. Time and again.
To be fair, I wouldn't have found him on IRC in 1998 either. IRC has really always been a relatively niche thing and I think it's fair to say it's doing well if you define that as remaining popular within the niches it's always been associated with. Though I think this is starting to change with the popularity of Discord.
An honest day's pay for honest day's work, but without the willingness to get education / skills required for that work, to move to parts of the country where the existing skills are in demand, or to use collective bargaining to get a larger share of the results of productivity.

The fantasy that coal mining jobs with wages that allow high school dropouts to support a single-income family living a middle class existence are coming back en masse to back country West Virginia is just that.
But, the real difficulty seems to be writing a retained mode abstraction that actually fits everyone's use case.

I can't think of a retained mode API that works as well for RTS games as it does for FPSs, to say nothing of non-game uses like CAD.
That's likely the mean salary. Median starting salary in that space is likely $160k. Some market leaders have recently moved to $180k.

But yes. The debt burden is incredible. I am nine years out of school and - albeit primarily due to working in the public sector - I still have six figures in federal student loan debt. And 55 hours/week is on the low end. Most firms require around 2100 billable hours. If you figure 50 weeks worth of working days, that's 42 hours of real, substantive work per week, which you have to account for in six-minute increments, plus all of your normal basic admin and staff meeting nonsense. During busy times, we were told to aim for as much as 300 hours/month.

There's a reason burnout is so high among lawyers at large firms.
> Yet Cloudflare’s use of edge servers that cache clients’ content inside Europe has, according to Mulhall, raised the prospect that they are breaking laws by storing content that breaches domestic legislation.

Nope, otherwise anybody who caches stuff would get into trouble.

The far bigger problem is how something so terrible can pass as journalism. It's basically a hit-piece to try and guilt trip Cloudflare into becoming part of the censorship machine the UK wants. And the "journalist"/hack who wrote it knows this, hence the very careful wording ("according to Mulhall"). But I suppose any nuance or a counter-opinion/point would be effort. For example, the UK is quite happy blocking sites for right-holders - why stop there [0]? Will somebody please think of the children!

[0] https://www.theregister.co.uk/2013/11/29/ukgovs_interwebs_mi...
However the way Wayland (or its broader ecosystem) "fixes" security is just stupid. Instead of using a fine grained whitelisting based permission system to grant different clients all the permissions they need to do their work (taking screenshots, reading the color of a point, listening to a certain key combination, apply some filtering to the display, get the size/position of a different client, ...) it treats every client as untrustworthy with no standard way to change that.

And let's not forget that just using Wayland doesn't grant any improved security compared to X11. There are numerous other ways to get input data, display contents, etc., so you need further sandboxing anyway, at which point you might just as well sandbox X11 clients you don't trust to get the same security. The benefit here is that you can decide if you trust your color picker and let it do its work by not sandboxing it, while Wayland just decides for you that no color picker can be trusted.
>All the reasons why I was happy to live without a computer in my pocket four years ago still hold true today: Certain choices are easier to make without digital temptation, like reading physical books on my commute and being fully present with my friends at meals. But there are new reasons, too.

These reasons are quite absurd and a bit silly. There's no benefit to reading physical books above digital ones, and if you want to simply because you like the feel, you'd choose physical anyways! And if you can't make yourself "fully present" at meals simply because you have the option of doing something else, you either have a terribly uninteresting friend group, or a complete and utter lack of self-control - in which case a smartphone is the least of your worries.
Easy, Windows already had dynamic loading on Windows 3.x, which was the same model used by OS/2, while UNIX was still trying to figure out how to implemente dynamic libraries.

The first versions of dynamic linking on UNIX basically required patching a.out files, before ELF was designed.

So of course the expressetion regarding compatibily issues with dynamic libraries came to be "DLL hell", there weren't .so to talk about.
> This is kinda funny to me but I feel like it shouldn't be.

It's funny to me too and I don't even know any of the answers. I think Trebek really showed why he's the host because his comments MADE this entire thing a funny moment rather than an incredibly awkward waste of air time.
Easy, one links to the binary library.

It really feels strange that young devs find it so hard to use a linker.
The gdpr does mention encryption and pseudonymisation. It does not mention ip adresses because the law is very clear about anything being in scope that can be used to identify individuals.
World Energy Outlook 2017 (2017)
It changes everything. Each platform brings its own preferred build system with it, which needs a copy of a definitive and explicit lost of all source files to compile the project. This is cumbersome to maintain. Header files on the other hand are licked up be the compiler automatically after seeing the include statement in the source. So this is actually much less time consuming to maintain.

Also, it shows that building C and C++ is a sad affair.
I'm not following, what caused the fire?
It’s usually pretty clear why you can’t have both: because resources can’t be used more than once (like money), or recharge at a certain rate (like mental energy).

I think the bigger issue is that future payoffs are inherently riskier. Spending a resource now for some utility now (like buying a movie ticket at the cinema) carries a much lower risk than even the safest 5-year investment.

I think that risk is the primary cause of time discounting, although there are others. Certain goods may have inherently less utility if you buy them later (an obvious example being a medical treatment for an ailment you have now).

What is interesting to me is why different people have different time preferences, other than obvious variables like age, wealth, education, etc. Is just a personality trait like any other? I’m also curious what people think about their own time preferences. Do people wish their discount functions were different? Obviously I sometimes regret decisions like staying up late, where I knew full well I was “screwing over my future self,” and I obviously can’t yet know how I’ll think about my long term low-discount actions, like saving money for retirement.
Yeah it looks like they are afraid of touching a linker.
I would not like to see employers discriminate (per se) against alcohol or cannabis users, even though I don't consume myself.

If alcohol (or cannabis) in fact cause problems, then it is not necessary to discriminate against all users, just those who manifest the problems.

I am unclear on why many people (of a libertarian tilt) think that discrimination based on stereotypes is to be defended.* It seems to me to be a way of shifting internal costs of evaluating people onto society, and therefore we should not expect an unregulated market to provide an optimal amount of it.

* Provided it is not against a legally protected class.
How to create good visualisations for data analysis
AI? Wouldn't they just automate regular colour theory?
Facebook Messenger Web is becoming unusable. Back in 2015 it was great, but slowly, they made it so that the website lags in all browsers if more than 100 messages are on screen, and the scrolling is now wonky.
I think you meant this, love2d running in the browser.

http://tannerrogalsky.com/mari0/
> Honestly i think the GDPR is a great idea, unfortunately after going through 3 different firms who are supposed experts on the GDPR. We are still struggling. When you ask them about a possible situation, and the response you get is "that is kind of a gray area", to "that is open to interpretation".

In the USA, this would be an opportunity for entryism by opportunistic outside consultants who would propose all manner of insane policies, and hang the threat of noncompliance over management's head like a Sword of Damocles if they are not followed. See Sarbanes-Oxley compliance for a relevant comparison and note that SOX is probably one reason why we've seen a precipitous drop in IPO rate in recent decades.

But the US regulatory infrastructure is, compared to civilized countries, from fucking Mars, so I have no idea if it will hold for GDPR.
Election forecasts in campaign coverage can confuse voters and may lower turnout
Processing data about political views is not permitted under GDPR without prior approval that HN certainly doesn’t have. Your position commits you to supporting evisceration of YCombinator by the EU for accepting your comment into its database.
There's some evidence of a genomic component to future discounting. There's a section on it in Robert Sapolsky's excellent book, Behave: The Biology of Humans at Our Best and Worst.
Noise from high power motors will be the bane of all operators, even when the car just drives by. However the junk yard will soon be a good place to source 48v generators.
RL agents (and humans) don't actually need perfect internal simulation of the environment. Instead we need ability to quickly recover from deviations, when the model diverges from reality, like self driving cars. We are using the world itself as a "simulator".

The problem with AI agents doing the same is that it's expensive. We'd need cheap, fast, indestructible robots and environments to do that. Humans benefited form millions of years of evolution, and previous species took billions of years to evolve up to our species. That's a lot of "high resolution environment time" which would be impossible to recreate in silico as of now.

Then there's the problem of sample complexity - humans need less examples than AI agents to learn, and that's because we have prior knowledge about the world encoded in our genetic code by evolution, while RL agents don't. We have to bake in some pretty clever prior knowledge in RL agents if we want them to be efficient.

So AI's can make due with imperfect internal simulation, but they need perfect external simulation of the same complexity with the real world in order to become smart like us.
Heat, if I had to guess (and no I'm not being sarcastic).

When you design your own hardware there's way too many things that can go wrong.
One way to isolate applications, common for server daemons, is to run them under their own user. The real "human" user can sudo into any application account, and does so on application execution. Marketing would have to rename things and slap a GUI over the feature, but I don't see why it wouldn't work for arbitrary Cocoa apps. (And the screen-capture API should be limited to capturing parts of the screen the application is currently drawing to, with overlaps clipped out, etc.)
No, Wayland doesn't close any of those huge holes. That's like saying: We removed all the windows to your house, you should now be safe from people spying on you or stealing your stuff.

Wayland doesn't grant Wayland clients permission to those resources, but without further sandboxing and using technologies like Linux namespaces, AppArmor, SELinux, ... that's completely useless in itself. Wayland only makes it harder/impossible for trustworthy applications to do their job, while malicious applications just take one of the many other routes to get what they want.
Okay. So far I haven't had to use the span thingys.

For mobile, I'm just assuming that the users smartphone has a Web browser. For fitting on the smartphone screen, each page is just 800 pixels wide, and smartphone screens are that wide? But even if not, my pages are still usable
with only 300 pixels wide.

My most complicated page sends for just 400,000 bits which seems small enough. There are just two files, HTML and JavaScript (JS). The JS file is written by ASP.NET and is small and optional -- so I'm expecting fast page loading.

I didn't see any good reasons to do anything special or different for mobile. What am I missing?
i think we are allow to log the IP etc. as long as there is no link to another identifying key in the same log.
Could you please elaborate that? I still see patterns like Builders, Factories, Singletons and even sometimes a Strategy in Java. Why do you think they are bad? What are the functional alternatives?
The act of spending does not create money.
Finite Markov Decision Process a High-Level Introduction
> It's not as bad as getting the flu

Arm soreness is nowhere near as bad as getting the flu, not even the same ballpark. I get my jab annually and in exchange for those few days of soreness I can't remember the last time I had the flu. No idea what the Tamiflu side effects are like, they sound nasty -- unfortunately I've never had opportunity to take it.
+9000 Votes to you edem.
http://the83rdelement.wordpress.com
Not really. That's just yet another instance of web browser, this time with chat-specific tab switching and - as I learned recently - a need to create yet another cloud account...

In Pidgin, you actually had it all in one place, with the UX defined by Pidgin.

That's another bad thing about current fragmentation. You have no way to unify the UX.
Fascinating. Within my social circles, we use Hangouts extensively. It still feels a lot like the original Talk for us. The Android app works, on desktop the Chrome extension is solid, I've never lost an important message, and the features he laments the loss of (busy status, XMPP support, off the record, contact blocking) just don't matter to us. I haven't had his experience with adding people (if I want to chat with someone, I input their @gmail.com address, done), message delivery is reliable, multi-media (photos, video) works fine, voice and video calling works, search is in the Gmail we already use, and group chats are easy and straightforward.

My social circle is almost exclusively Android, which may help, although the few iPhone users do work, and a lot of chatting happens through the Chrome extension/gmail window, so there's that.

I don't particularly want to chat through Facebook (Messenger is a busy, ugly mess, and the app is pretty heavyweight) and many of my contacts aren't on Whatsapp or WeChat. SMS often delays message sending and delivery in areas with spotty mobile coverage. Hangouts uses wifi first, which is ubiquitous in our homes and at work.

It's really interesting to see the different perspective. I do worry about the future of Hangouts, it feels like it's just coasting now. Duo/Allo/Meet may be an okay replacement, if they migrate all of the data over and swap it in Gmail. I've played with their slack-competitor (Chat), and it's interesting. Still doesn't feel as good as slack, but it's been okay.
1. install node.js
2. npm install create-react-app
3. create-react-app your-app
4. npm start

Now you have a react app with a development up and running. To create a production build write "npm run build". To add a package write "npm install the-package".
Basic support for H.264 in HEIF container file
Wait, is using more than one question mark not an internationally recognised sarcasm marker???
Vulkan is such a pain that one of the GDC 2018 talks is "Getting explicit: How hard is Vulkan really?".

https://www.khronos.org/news/events/gdc-2018
While I agree that can devolve into a dogmatic belief system, I also think that that's partly a people problem.

Many of the ideas in Clean Code make code more readable (for example small methods, each containing only one level of abstraction; or good naming). It's on the coders to know how far to take these ideas and when to be pragmatic and say "good enough".
The Book Every Programmer Should Read
As someone who hates needles, I would gladly have the flu 10 times a year than get one shot! But I work from home so I rarely get it or have the chance to be contagious.
We used to have a relatively open internet based on developing, using an adhering to protocols and open standards. This is probably because everything was new and there was a lot of money on the table for everyone.

We would joke about peoples' theories of the "Balkanization of the Internet" and mostly we would look at it from the wrong angle (nation states).

Now we have an internet of walled gardens. Your data is precious and no longer yours.
Perhaps, the most unusual puzzle game
UNCARED HIGH LEVEL OF CORRUPTION AND MEDICAL CRIMES WILL COLLAPSE THE WORLD
I'm not him, but probably either shoddy PSUs and/or there were lithium batteries involved. It's the curse of "modern" equipment.
Oh sorry, I figured out that if a media company is serious they'd run the server for their journalists. https://conversations.im/ also uses E2E encrypted chats and I don't need to setup any "random VoIP numbers".
ICQ is now owned by the Russian company behind Mail.RU. AOL sold it for $187.5 million, less than half what they paid for it:

https://techcrunch.com/2010/04/28/aol-sells-instant-messagin...
Are you implying that TDD is bad in practice?
Calling Slack "interoperable" is a bit much to me, though I admit it's better than everyone else in the "new crowd".

I wonder if we need a new word for "interoperability in the time of SaaS" - the kind of where SaaSes talk to other SaaSes via locked down APIs, under absolute control of the vendor.
You can get the vaccine as a nasal spray if you really hate needles.