skysight-inc/HackerNews huggingface dataset:
Yes, I agree. It is problem of implementation. But nevertheless it is a problem. I didn't tried namespaces myself, but I'm pretty sure that to do in in Linux it would be harder for me to get it to work. Even if I became familiar with namespaces.

Multiuser model is settled, simple and transparent model, that just work. You have abstraction of user and abstraction of file access rights, and it is all that you need.

namespaces have no such a simple model. How can I run program from other user but give it some special rights to access this git-repo in my home directory? Do I need to write a special C-program for that? Or maybe existing tools already can be configured with some obscure xml-file? I do not know, and maybe I'm mistaken, but knowing the general laws of linux software development, I guess that the best software for it I can find is a complex overengineered corporative tool with bells and wistles, and the easiest way to use namespaces in my case is to write C-program. (If I'm mistaken, please, correct me at least by stating my mistake aloud, or better point me to a docs, please.)

And here we came into real issue. To write a good C-program for my tasks, I need to start thinking as a software designer, to invent new simple model of process separation, that allow me to solve 90% of my tasks with ease, and the rest with some headaches, but everything must be possible. The only way to do it in a week is to refuse to think, and to replicate multiuser model on top of namespaces. But I need no replica of multiuser model because I have an existing one. What the point of discarding multiuser model, just to move to another implementation of multiuser model?

The only good thing I see is a lack of need to log into a root shell to create or delete users and groups. It would be nice, but I'm not ready to spend a week to write a C program and then unknown amount of time to maintain that program, just to stop using su/sudo for such tasks.

So, I can agree that multiuser model is bad for a linux desktop. But we have no real alternative. And the mobile OS approach is the worst. It reminds me of DOS, where you can work with one process at a time, where you cannot run two copies of a program, where all is done in the single global namespace, and any process can do anything it wants. The only choice you have is "to run program or not to run".
By serverless it looks like you mean literally in-browser and not the usual microservice nomenclature, yes?

I like "Go and Talk" as a phrase but think it will lead to some confusion amongst technically literate people. I assumed your platform was built around the language Go (and something else) at first, which I assumed was running as a microservice.
How is that a chip in a mainboard? The mainboard story was a propaganda piece in Bloomberg aimed at China.
I checked out Posteo and noticed on the sign-up page it does not allow certain symbols in passwords. I get the error message: "[password] is invalid (must have at least one lower case and one upper case letter as well as one number or symbol - diacritics and exotic symbols are not allowed)"
Wonder why that is.
Heartbleed was caused by a class of code error prevalent in the toolchain used to write that code. It was not caused by the specification itself.

Here is the exact change if you're able to read the code: https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h... -- if that is not within your skillset to read that change, the patch is essentially doing a bounds check on a set area of memory. The language being used is notorious for allowing this type of code error and is the source of many exploits and bugs. It has nothing to do with the specification.

For some reading material see this wikipedia article on the subject: https://en.wikipedia.org/wiki/Buffer_over-read

>Programming languages commonly associated with buffer over-reads include C and C++, which provide no built-in protection against using pointers to access data in any part of virtual memory, and which do not automatically check that reading data from a block of memory is safe; respective examples are attempting to read more elements than contained in an array, or failing to append a trailing terminator to a null-terminated string. Bounds checking can prevent buffer over-reads

We mitigate against attack vectors before there are known instances of software using those attack vectors. I'm not sure why you want to argue against that, or even how because we do it all the time. Take Spectre/Meltdown as another example. Preemptive measures were taken before any known usage of that attack vector had been discovered.
The Vive gives a rough tronlike outline (or even a transparent camera overlay) that solves this for me (a backlit keyboard helps, too, so I can turn it mostly transparent and it still stands out). The outlines appear when you go outside the standing-room boundaries and my flight chair setup is right beside that area.
Wouldn't the following be an embrace of Conway's Law rather than a defense against it?

> It is much better, and more and more implemented as such, to deploy teams around a bounded context. Architectures such as microservices structure their teams around service boundaries rather than siloed technical architecture partitions.

> So, structure teams to look like your target architecture, and it will be easier to achieve it. That's how you defend against Conways's law.
Component: Experiment in moving towards higher-level Elixir components
No one outside of Bloomberg has seen any evidence of mainboard spy chips. You must be thinking about CPUs.
Every single of these vulnerabilities are crashes and infinite loops. The worst thing you can do - if I am running a 5-year old Wireshark - is to make it crash if I am visiting one of your web services. And you probably can already do that in newer versions if you dig enough.
> 80s style Basic does not have functions.

> No naming, no abstractions, nothing.

This is not entirely true. BBC BASIC (certainly the versions I used on the Electron and Master 128) had both named sub-procedures and named functions, with local variables and allowing recursion. While limited in some ways they did allow programming without sight nor sound of GOTO/GOSUB, which I actually used to do.

You could even do away with line numbers with a little hackery: write your code in a text editor (View, as built-in to the Master series and which we had as an add-on to the Electron we had at home before that, was what I used), I forget how due to the mists of time but I had a method of having the file repeated as if typed from the keyboard (adding in the line numbers via AUTO) and executing it directly. I felt rather clever, particularly as I did it mainly because a CS teacher had said it was not possible!
Somewhere I lost a t, it seems
I'm confused about what part of the parent you're replying to, I haven't downvoted you, but it's just not clear what you're talking about in the context of the conversation.
Notes on the Implementation of Lua 5.3
California lawmakers introduce plan to end surprise ER bills
> Multi-process Firefox

So the claim is that it would have been less expensive for Firefox to start over from scratch and make a new multi-process browser while at the same time maintaining a single-process browser that stayed current with web standards in the interim?
PyCM 1.9 released: Machine learning library for confusion matrix stat analysis
>> But are there any guarantees that Facebook won't insert code

Kinda hard to "insert code" into an open source product without everyone knowing.
Any plans to include compatibility outside of Oculus Go?
There's not exactly a consensus these days on what is correct. Either is valid, but I generally prefer _Brooks' Law_ to _Brooks's Law_ since it looks more clean. Of course, Brook's Law is incorrect, as there is no "Brook"

Here's an example of the lack of consensus:

Either is acceptable:
https://data.grammarbook.com/blog/apostrophes/apostrophes-wi...
https://owl.purdue.edu/owl/general_writing/punctuation/apost...

Chicago vs AP style:
https://apvschicago.com/2011/06/apostrophe-s-vs-apostrophe-f...

APA style suggests appending the extra 's':
https://blog.apastyle.org/apastyle/2013/06/forming-possessiv...
Meh. Sounds like a run of the mill shitty job. You can destroy your body laying bricks and unloading trucks or you can destroy your mental health doing something like this. Of course they're not paid well enough to compensate for the long term damage. Nobody ever is.

There's all sorts of shit you might have to put up with in a shitty job, the work, the environment the customers. This job is shitty but some people are bothered less by this particular kind of shitty than they are by by angry customers yelling at you or laying bricks in the Arizona weather. Sure you might have to see some really screwed up shit among the sea of nip-slips and racial slurs but you get to do it in an air conditioned office without killing your body like the guys in the Amazon warehouse. Some people prefer that.

Different people have different degrees to which they'll tolerate the various ways shitty jobs are shitty. At least one person the author interviewed said "well, it sucks less than Walmart". Back at the point in my life when I was doing shitty jobs I would have preferred brick laying or custodial work but I wouldn't have turned down this job if I needed it. Of course it's terrible for you and turnover is high but all the equally shitty jobs are this way. There really is no winning in the "minimum wage or thereabouts" income bracket.

Edit: Since apparently this opinion is unpopular can anyone tell me why this particular implementation of shitty job is worse than all the other implementations?
thanks for the comment :)
Carbohydrates used to come from fruits (with fiber), vegetables (in small amounts & with fiber), and starchy vegetables (starches are complex & slow to digest). Today, carbohydrates are consumed in simpler forms and refined to be more concentrated.

In the former case, they digest slowly. In the latter case, they digest quickly. The practical implications of this are immediately obvious if you have ever heard of glycemic index and glycemic load, but in short, fast digestion & large quantities results in a big spike in blood sugar which is hard on your body & leads to diabetes.

Also important is that the original forms of carbohydrates came with all kinds of other nutrients. A sweet potato includes vitamin A, vitamin C, manganese, copper, pantothenic acid, vitamin B6, potassium, niacin, vitamin B1, vitamin B2 and phosphorus. Sugar on the other hand is the quintessential "empty calorie", carrying no vitamins, minerals, only calories.
How is a Vitamin D lamp supposed to promote the creation of Vitamin D without UV?
Exoscale has the best support and privacy of any of the cloud providers. They also offer more enterprise features like prepaid accounts (with proper invoices!) that Linode doesn't offer.

We've used their services happily and would recommend them to others.
"Welcome to hell."

All i needed to read :)
In my experience the re-write always takes much longer than expected. Sure you might be able to redo the core pieces to handle the new problem in X weeks, but then it's going to take another 4*X weeks to handle all the edge cases and make sure you're not breaking anything your clients/users have grown to depend on.

From another HN thread today: https://news.ycombinator.com/item?id=19245485

> The first 90% of the code takes the first 90% of the time. The remaining 10% takes the other 90% of the time.

And

> With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody
On the other hand UV tends to lower your folate levels. Populations' skin colors tends to track the latitudes they live in but also the ratio of vitamin D to folate in their diets. That's part of the reason the pre-agrigultural population of Europe with their fish heavy diet had skin colors so much darker than modern Europeans

https://www.bbc.com/news/science-environment-42939192.
In my opinion, software "rot" is most likely where software has been passed on through a number of lead contributors over time. The original reasons for a particular set of design decisions are forgotten.
Someone else comes along and doesn't quite understand a particular nuance, tries to add factionality, but it doesn't quite work, so writes a bit of code that ends up reimplementing an aspect of the original, so you have two lots of code doing the same thoing in different ways, perhaps with their own set of variables.

Then someone else comes along and is faced with real confusion and before you know it you find yourself with a system which, if you update data one way, the changes are sometimes picked up by another part of the system, sometimes not and... its rotten.
You can google for people's experiences with O1. You can move the needle a bit by writing articles and getting some awards...you can also apply for an O1 and H1B.
One thing the author missed about htm is that you don’t necessarily need to parse it at runtime— there’s a Babel plug-in to compile it to plain js function calls. This way you can develop without a transpiler and add one later when (if) the extra performance becomes necessary.
I work on a library for doing Python bytecode transformations like this, but with a more abstract API. Here is a similar transformation with this library, which works with Python 3: https://github.com/llllllllll/codetransformer/blob/master/co...
Correction: you have a single authoritative view of the world, plus a secondary cached view of the world in a different language which probably doesn't perfectly map to the original one. Many people choose this approach, but it isn't without its own issues.
I get that email was not originally designed to be secure, but do you really not want to keep your amazon account, with your credit card number and home address, secure and private?
That reminds me of a place I used to work at, where initially we had DBAs embedded in the teams. They switched that and the DBAs were all grouped together and all hell broke loose. They were always have meetings, throwing out emails about they were dictating this and that, and had very little direct communications with the teams they were supposed to be supporting.

I ended up leaving during the peak of all of this, but in an exit-interview, a director asked me about the problems this was causing.
Murphy's Law has electrical engineering roots. I have a fun anecdote.[0] My wife is electromechanical and I'm computer science so we would work on projects together since we make a good team. I remember in college I was working with my wife on one of her projects and we were using force transducers. The damn things kept breaking at the worst times so we kept calling it Murphy's Law. After a while we looked it up. Turns out Murphy was working with transducers when he coined the phrase [1]. So I have this little back pocket anecdote about the time I got to use Murphy's Law in the original context. Which I can bring out in times just like this.

[0] I think it is fun. Your milage may vary.

[1] https://en.wikipedia.org/wiki/Murphy%27s_law
Datomic is stritcly more(than SQL) between both worlds, you have half of your schema in the database(attributes) and the other half in clojure code (integrity checks, constraints, some validations, etc...).
> this isn't cancer research that informs treatment regimes nor social science that informs public policy. it's code and theorems

This is a dangerous line. Being a reviewer in CS, I don't think peer review is easy. The work in this field is complex and require a lot of time to correctly evaluate the claims.

First, CS/maths is not just code and theorems. There is indeed a lot of research which requires data and empirical validation, or propose new models.

Second, it's not easy to verify claims, even for code or theorem. This is why peer review requires many reviewers, often from 2 to 6, to evaluate one paper for a conference or journal. No one can evaluate in 5min whether a 40 pages paper on ArXiv makes sense or not. When I read a 70 pages complex crypto paper, I prefer a peer reviewed, community-backed work than a PDF not verified by other researchers. When you're a reviewer, you realize that many papers are often butchered, or contain (partially) false statement, not always easy to spot.
I think the big difference is how oversensitive society is now. Before, your moderators just had to deal with outright illegal content, maybe a flame war or two (or just move the discussion to the flame war section). If you ran into anything as a user, it was understood that you should report it and that the moderators would get to it with varying degrees of speed. There was no expectation of a perfectly safe bubble.

Now, if even the most milquetoast comment which could possible be offensive if I assume the absolute worst about the poster, isn't moderated post-hate, you'll be reported to the media who will almost certainly archive it and use it to fill the next 1 - 24 hours of their outrage media cycle. I honestly see a future where people file lawsuits against web sites for not moderating enough, a failure to keep safe or sort of negligence. "Your web site gave me PTSD or enabled cyber-bulling". What's worst, they'll win.
Sulfur-based polymer transmits long-wavelength IR better than any known plastic
I think not just this one, a few of the top ones are of similar vein at the moment. Seems a bit off-colour, as usually the quality of content was rather consistent.
That can happen. But in a significant (the majority?) number of cases of patients diagnosed with Schizophrenia there is no difference between their brains and 'normal' people when comparing MRI scans. Note this is with early onset - the "medication" provided for schizophrenia is well known to cause large structural changes in the brain.
Unfortunately we currently don't have plans for that. We think compatibility is important, but are more focused on getting the product to a more stable state before we expand to other headsets!
Understanding ROC Curves with Python
You could use something like JOOQ[0], which (optionally) generates Java code based on your SQL schema.

[0] https://www.jooq.org/
i wanted to comment on that lol
thanks :)

Can you recommend an essay or paper by either that focuses on the "starting point." IE, why a "chemical computer" version of consciousness can't exist.
FWIW, I've found the Go standard library `net/http` to be reasonably productive. It's pretty well-designed and intuitive for me, but YMMV. I've observed that ramping up in it from a Python/flask background is relatively painless.

If you're willing to dive into the Go landscape, there are a few quality web frameworks available, ranging from the small highly-performant https://github.com/buaazp/fasthttprouter, to the more opinionated and feature-creepy https://github.com/gobuffalo/buffalo. I'd skim the selection, see what trade-offs they make, and pick the one that suits you best.
https://www.theguardian.com/world/2018/aug/07/china-bans-win...
Close a video if its a shaky video of some guys with machetes. You dont have to figure out how it ends.

You only have to watch it through if you have to make sure its actually gore. Which an individual different to an employee doesnt have to.

Or simply automatically collect reports and if a high enough percentage of views vs reports comes in it put it nsfw.
Got an email pretending to be from IRS? It’s not from us
Your Dad Owned a Mac
I'm not sure who they should be named after, but I'd like to suggest two more:

> Redundancy is bad, but dependencies are worse.

https://yosefk.com/blog/redundancy-vs-dependencies-which-is-...

> Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.

https://stackoverflow.com/questions/876089/who-wrote-this-pr...
Especially in the java world. It can no longer be considered quick by the time IDE boots up.
This part is scary:

The moderators told me it’s a place where the conspiracy videos and memes that they see each day gradually lead them to embrace fringe views. One auditor walks the floor promoting the idea that the Earth is flat. A former employee told me he has begun to question certain aspects of the Holocaust. Another former employee, who told me he has mapped every escape route out of his house and sleeps with a gun at his side, said: “I no longer believe 9/11 was a terrorist attack.”

I have a hope that people will eventually develop immunity to conspiracy theories after falling for enough of them and eventually seeing them disproved. But with things like pizzagate/Qanon it seems some people just keep going deeper.
Full rewrites aren't great either, Netscape[0] is a classic example.

[0]https://www.joelonsoftware.com/2000/04/06/things-you-should-...
As someone who was serially consumed by various philosophers when I was younger, I totally disagree.

Going all in on a philosopher at least once, especially when you're young, is the best way to really appreciate philosophy. It's the difference between understanding what the philosopher thought and understanding what it's like to truly think those thoughts and be immersed in the value system.
The Dirty Energy Powering Data Center Alley [pdf]
> It's important to note that the "kind of abuse" AGPL is fighting is denying the end user the four freedoms.

But which end user would that be? The end user of the licensed program is Amazon. They're the ones running the program and using it to provide database services to their customers. Those customers are end users of Amazon's database services, not a particular piece of software.
Publishers Reportedly Struggling to Monetize Privacy-Centric Apple News
Camels and Rubber Duckies: Joel Spolsky on Pricing (2004)
That makes sense. However (and this is just my isolated experience) I found some good teachings in Feynman in my teens/early 20s without really ending up mimicking his style or behaviors. Some anecdotes in Surely You're Joking were comforting--for example, that you can pick up new skills very late into adulthood that are typically thought of as only accessible by starting early, if you approach them with curiosity.

And some were politically inspiring: with the Challenger disaster, he was an outside mind investigating a systemic problem where people's incentives were en masse preventing them from seeing an ossified power structure. At least that's how he described it, and I'm convinced the lesson was valuable even if it was more complex than that.
Book Summary: Why We Sleep, by Matthew Walker
Google, Facebook, etc presumably have rather large and competent security teams, and they presumably do things like extensively monitoring CT logs and BGP. And Google's properties nonetheless get hijacked on a semi-regular basis by BGP attacks. (A very small amount of looking suggests that this happened last November.) I'm not aware of anyone using such a BGP attack to get a certificate for a site like YouTube, but I see nothing that prevents it.

I don't actually know why Google doesn't enable DNSSEC on its own properties for this exact reason. They may be relying on the fact that any serious CA will have "google.com" and similar domains in a list of high-risk domains.

(Heck, I can't easily personally monitor BGP for a website even if I wanted to.)
We used hibernate, which does the opposite (Java classes/annotations -> SQL). You'd still have the same disadvantages: having an imperfect "clone" of your schema.
Communication?
There is a difference, that cancer has a biological cause (a genetic lesion). "Mental illness", e.g. schizophrenia, has no such origin in a bodily abnormality.
That's somewhat true, I should have s/American/other/
Is there a law about the probability that an article about programming will reference XKCD?
So, the usual clusterf*k of opinions instead of a clear spec. People should be speaking SQL.

Thanks for the links. Plenty of educational value there!
Ask HN: Books you don't recommend?