skysight-inc/HackerNews huggingface dataset:
Salt is not safe to drink. Vinegar is to some extend (you can take several gulps)

Glyphosate is not. Claim was BS. Good journalists to challenge them on the spot. Bad Monsanto for making that claim. It is clearly not safe to drink. Not one gulp. Microdosing is not the point there, the claim was not made for microdosing, the claim was safe to drink.
When people are watching porn and jerking off in the server closet, it’s toxic.
A Custom WordPress Dashboard with MongoDB Atlas, Azure, and Serverless Functions
Sure? My point is just that the case wasn't about glyphosate but about a particular Monsanto product. I sort of don't care what happens to Monsanto.
Also, I was curious, and by the Wikipedia definition[1] TN doesn't qualify as "deep south". We definitely still have our share of problems and there are "southern" things that drive me crazy but it's not quite as back woods as many people believe.

1. https://en.wikipedia.org/wiki/Deep_South
My mom is another one of these stories. I wish I was exaggerating. I bet there's still Round-up in the her garage. I've spent the last 4 years or my life have been devoted to working so I can afford her treatments and keep her around and happy.

Does anyone have any environmental attorneys they've worked with in the past they can recommend?
If you are fine with roommates, there are plenty of sub 1k options in and around the area. El Cerrito and Richmond aren't too far away and generally cheaper than Berkeley.
> When you mention PHP, the immediate association for some people is invariably going to be "that really bad PHP 3.5 site I made that one time."

Except in the many thousands of companies that are looking for PHP programmers, where not having it on a resume is damaging.
As for Lane, human work caries risks.

The control of speech needed to take that stabbing off the table is excessive.

Real conversations do involve real people who will do real things.

What I put here works.

I have done it with a gun pointed right at my chest, loaded, cocked.

That is no joke. And I could argue I had better tools to work with than the father did. Odds are favorable to me in that case too.

I have a solid set of intense experiences and some training in this area to draw on too. Did the father?

Maybe he should have those things. I would gladly fund them as part of my taxes. Money well spent. While at it, mandatory, blanket gun education would do a lot of good too, and in similar ways, for similar reasons, by way of similie here.

To me, bringing up one ugly fail amidst a sea of successes is counterproductive.

It is also rooted in fear of risks.

With people, speech, there are always risks.

Empowering people, doing more early human work will do more to break down those risks than taking a bludgeon to speech will.

Just one of a few reasons I felt it better to just step away.

We may just have to go through a draconian cycle here. I am not happy about that. And it will not play out like well meaning people think.

And I will be there at the peak to assist with the move back.
> So Monsanto were selling a dangerous pesticide and intentionally obfuscating its effects.

The same Monsanto that manufactured PCBs and Agent Orange? That's a crazy coincidence.
I'm sorry, I meant to get back to you a week ago.

As pmoriarty pointed out, that was indeed a typo, and a rather embarrassing one!

The funny thing was that as I was writing that sentence, I first wrote:

"The vast majority of programmers believe..."

And then I decided to tone down the language a bit. But my initial wording would have made the typo fairly obvious. So it goes. :-)

> functionalities that rely on monospace fonts, such as selecting blocks of text by both rows and columns.

I use that "column selection" mode with proportional fonts too. It works fine, even though the selected block has ragged right edges.
Um, mix in a second randomly-chosen UUID?

My point wasn't so much that I had the perfect solution and that I'd thought of everything. It's that there are much better systems and that we should actually strive to get there.
Therac is one of the reasons I get nervous about "health hacking." Yes, people can verifiably benefit from some of the advancements made in this movement, like the DIY diabetic insulin pump, and yes, I prefer to see such advancements be open source than locked up in proprietary designs and trade secrets. And there probably is room in health regulation for trimming the red tape anyway even for innovations originating from the commercial sector.

On the other hand, when corners are cut (no hardware interlocks, for example) and edge cases aren't considered, even innocently, then you get things like this. It makes products more expensive to design and more costly to buy and maintain to do the extra engineering. It is certainly a barrier to entry, too. But do we want another case like this because people said "this is good enough"?
Everyone seems to look at this from the "large corporations IT" and "mass surveillance" perspective, but let's not forget that everyone should also have the right to inspect and modify traffic on the networks and devices they own. TLS MITM is not necessarily a bad thing.

Do you know what traffic your IoT "smart" things and even your PCs and mobile devices is sending and receiving?

https://news.ycombinator.com/item?id=6759426
Let them spend money on new middleboxes, if they care so much.
Laws don't dictate how companies behave.
The problem goes down to Hanlon's Razor.

In elevator or airplanes, it applies, we try to make as safe as possible, we ironed most of the bugs (over which the maker would lose big), and if they ever fail, would be far more possible to be because human stupidity than malice.

In the other hand, with voting is human malice what matters. The holy grail for that is to paint it as safe and failproof as possible while still rigging things for the intended party at some point of the circuit. And there is big money to ensure that it happens, so the for profit manufacturers of such machines (or their for profit workers/managers) will be very motivated for slipping a subtle/obfuscated bug or backdoor somewhere (remember the Apple SSL bug due a duplicated goto fail line?).

Making software safe from their own makers is complicated. Software itself it runs may be complicated, what makes auditing it not trivial, and with enough resources you still can play with lower layers like the compiler or chipset (for all or a portion significative enough of the machines).

And blockchain is a tool that can be misused too, we already seen a lot of frauds, scams, majority attacks and so on over it. "It is safe because it uses blockchain" is a good intro by someone that have something to win there.
Probably Rentech and Two Sigma. First one is a guess.
Would love to but I don't have access to the book. The website has very little on the design and feature of the OS.
sct is also in debian via this maintained fork -

https://github.com/Tookmund/setcolortemperature
A company monitoring its assets for proper use and the SECURITY and PRIVACY of its customers is not immoral.

A browser extension would not do nearly what a proper web proxy can do.

I am a critic of the surveillance state and a donating member of the EFF, but web proxies are not evil in themselves, anymore than a camera is evil because it can be used to build a panopticon, or cookies are evil because they can be used for cross site tracking.
I believe most dorm rooms are like this for first year students across the US. Where I went to college, it was 2 to a room but some opted for privates. It was kind of odd to do a private suite - living with someone in a dorm room is part of th first year college experience, at least in the US.

I've heard of people who go on to share their room later in college and even into adult life. You do what you have to do. Almost all those cases are temporary anyways.
that fine is far to cheap
xeliux.com for registration, hosting at digitalocean.com
that fine is far to cheap.
Do you really think so? My experience has been that most developers who see me using proportional fonts are surprised that it's even possible to work productively with them. I haven't run into anyone who said, "Oh yeah, I tried proportional fonts too but I didn't like them."
My life's fine and more importantly I sleep great at night and am proud to tell anyone what I do for work.

I've completely plateaued on the happiness vs money graph and you couldn't pay me enough at this point to take a job in the finance or defense industry.
Interesting. But does cixl really do refcounting on stack values? It should only be done on aggregates or objects reaching out into the heap, not on int or float primitives on the stack.
The recent push to get Model 3's out with hand labor is going to wreck them in about six months as the recalls and repairs start to roll in.

Tesla had all sorts of tolerance problems early and moving to hand assembly in a tent won't improve it.
Meteor showers from space
Psychologists say kids are suffering from “hidden manipulation techniques”
>People check their personal email on their work computers, that's just a fact of life.

Well, that's their dumbass fault.

At our company, there is a giant warning on the login screen that "You are using a corporate asset and there is NO expectation of privacy."

Now, as to the safety of browser locks... sounds great until the company patches their Firefox distribution.
The arguments only apply to the sale of copyrighted material, not general goods.
Thing with prefab is it's been tried many times before, and hasn't succeeded. Why? Most companies take traditional construction methods, and simply move them into a factory where there's cheaper labor. But then the assembly process and on-site finish work is laborious and expensive (in this case, 70%+ of costs). For prefab to succeed, there needs to be a ground up redesign of the entire building process, from design and engineering to manufacturing and assembly, with software at the core to enable a system that's scalable and allows for different designs across numerous projects, and with the actual building to be made of parts that truly click together like legos. YC F3 company Cover (i'm a founder) is doing this.
https://news.ycombinator.com/item?id=17740517
And that's a quick way to get the big root stores to start looking very, very closely at you.
You don’t just “get a girlfriend”. Usually having a girlfriend involves being a decent enough human being in the first place that a woman would want to spend time with you. This CEO was clearly a dickhead (in every sense of the term), and I can understand why no woman would touch him with a proverbial 10 foot pole in a romantic sense.
Same, I just picked it up in the Steam sale, and it's what I wanted out of Doom 3 fourteen years ago. I feel conflicted that I just gave $10 to Bethesda while they are pulling this stunt, but it's a great game nonetheless.
There's a tremendous amount of value, in any creative task, in being able to sketch out ideas quickly. The less time you spend seeing if the shape of the thing you're making is broadly okay, the more shapes you will be able to try, and the higher the chance that you'll converge on a good one.

Swift really does not support quickly iterating on a design. It demands that you sit down with your plan fully-formed, ruler and protractor in hand. Due to its strictness, changes ripple very quickly across even a small codebase.

Realized you need another enum case? You can't compile again until you touch all your switches. Protocol would be more expressive with an associated type? Stop what you're doing and write some type eraser boilerplate. Function needs to signal an error condition? Try/do/catch anywhere you call it, right now, before you run again. Need to put another type into that array? Write a new protocol and add some conformances.

Changing a interface as you work in Swift immediately creates a sea of red marks, which hinders the ability to experiment.

You're right that this strictness helps write ~correct~ safe code, and I appreciate that. But it's a tradeoff; there's a real cost in developer productivity/creativity. And I believe that it does not help produce the best design. It takes too long to get to running, which makes it too costly to heavily revise based on what you learn as you build.

EDIT: Actually, I want to go even further, and strike out "correct" in the paragraph above. Swift helps at a certain level of correctness, which is really not much higher than the type system -- it would be better to call this "sound" code, rather than "correct".

The overall point that I'm trying to make is that at the level of application/business logic -- which is the whole point of the program, after all -- Swift does not help with correctness. In fact, it can be detrimental, because, unless/until you understand your use cases well enough to actually lift them into the type system, at that upper level it blocks exploration without adding rigor.
I'm just not seeing how the thing you said is supposed to be in conflict with the thing I said.

Sure, competition isn't the only factor in margins. But it is a major determinant of how much of the total surplus goes to the consumer rather than the producer.

And the point was that if you raise costs for all competitors, it isn't necessarily fatal to the market that the amount is larger than their original margins, as long as it isn't larger than the total producer+consumer surplus. Because when everyone's costs increase by the same amount, the producers may be able to pass some of the cost on to the consumers.
URL to blog post which outlines our mission and approach: https://www.cover.build/post/what-why-how
Indeed, however, the number is usually very reasonable, usually 5+, its not gonna stop a grad student from saving money on rent.

Though the court case that upheld these laws as constitutional, Village of Belle Terre v. Boraas, the zoning law was extreme at limiting only two unrelated persons - which is extreme.
In C++ the default behaviour is for the runtime to call std::terminate, not segfault. It's easy to catch exceptions by wrapping the callable in a packaged_task and then the exception is available in the future.
The key point is that the exception is rethrown when accessing the result through the future.

Swallowing exceptions is a really poor idea. Does Java really do that?
I worked with amputees for around 14 years back in the 70-80s and was kind of shocked when I first heard about phantom limb syndrome. I'd just never imagined such a thing before then.

It's not just "pain", but really annoying "itches" and other sensations too. People with above the knee amputations would tell me their "foot was itching".

One of the biggest issues back that was weight gain/loss. Just a few pounds would change how the the limb fit and since they were held in place in large part via suction (vacuum) when it didn't fit right it could be somewhat painful and at the least very annoying when they got loose or too tight. I spent many hours helping amputees apply and sand "bondo" inside their "leg" where it attached to their "stump" to get them to fit comfortably.

It's been close to 30 years now since I've worked on those and I've not kept up on what's changed. I imagine there have been improvements. I sure hope so.
> second rate developers hide behind. It takes a certain maturity and experience

Also, you really could have phrased this to be a little less inflammatory.
As I mentioned above, the point is not that the actual cost of the furnishings and the bathroom are somehow wrapped into the rent. It's that people are willing to pay extra for something they ultimately don't actually need. People will usually choose superficial quality over something more utilitarian, and will pay handsomely for it because it makes them feel like they're at home in mom and dad's suburban mansion.
This isn’t about it being their social life. Stripping in front of an employee and then retaliating when she won’t engage with you sexually is not “social life”.
One man designed and built the ultimate bush plane
> It should be a formal logical fallacy to critique the economic activity of other people just because they're choosing not to engage in whatever your favorite flavor of saving the world entails.

It should be a formal logical fallacy to pretend there is no difference between "not saving the world in someone's favorite flavor" and "doing something useless".

> It always follows a simple formula: woe to the world that all these {brilliant scientists, talented engineers} decide to work in {high frequency trading, advertising, data mining} when they could be working on {curing cancer, solving climate change, helping the poor}.

In order to be intellectually honest, you should replace the strawman "{curing cancer, solving climate change, helping the poor}" by "anything useful".

> If you're not well enough acquainted with economic theory to appreciate why financial markets are at least somewhat useful then that's your problem, not anyone else's. Don't try to insinuate that society has lost something because some very capable people have decided to engage in work you won't even take the time to understand.

There's no effort expended nor insight contributed here either. You not just refused to make an argument, you baselessly claimed that OP considers the work of Jane Street useless because they are stupid and not for reasons you don't even take the time to understand. That is simply disrespectful.

Also, the statements "developing software to gather more money from the financial markets is useless" and "financial markets are useless" are not equivalent. No one claimed the latter.

> It's simply disrespectful.

There is no reason to respect useless work.

> You also have no idea what kind of charitable work they like to do in their free time or what kind if philanthropy their salaries allow them to contribute to the world.

They didn't say anything about what the workers at Jane Street do with their free time.

> And this is all beside the fact that there are many secondary effects of company flush with money releasing excellent open source software and stewarding programming language development.

That is merely a by-product. Also, it may very well be compensated by the fact that if Jane Street didn't have that money, someone else would.
Dropbox Client Will Only Support Ext4 Filesystems on Linux Beginning November 7
As terrible as it was, that Therac-25 remains one of the most frequently cited examples of software engineering flaws hurting people is somewhat encouraging for the profession. 3 deaths is a tragedy, but the Hyatt bridge collapse a year earlier was a couple of orders of magnitude worse (114 people, https://en.m.wikipedia.org/wiki/Hyatt_Regency_walkway_collap...) from what was also a fairly subtle engineering failure.

IMO, harm from software bugs (so far) have been vastly surpassed by explicit choices in system design. The various emission cheat scandals have almost certainly taken a real toll on human life going into the hundreds of person lives. More subtly, the choices to retain data inappropriately at Ashley Madison (probably) lead directly to suicides and serious emotional harm. Those are just the two recent examples that spring to mind as a practocing developer, not an ethicist.

To somewhat over simplify but when discussing engineering ethics, the harm from software developers building things wrong is swamped by building the wrong things.
DX12 Ray Tracing Tutorials
1. It's definitely been slower than I would have liked. A lot of developments have been hyped up a lot, when in fact they are years away. Modular Implicits (which approximates Haskell's type classes) and Multicore have been in the works since only a little bit after I started using the language. At the time, they were kind of described to me as being "right around the corner" but failed to appear. There have certainly been lots of good additions to the language apart from this (e.g. we got a great inliner called Flambda), but it seems like it's still gonna be >=6 months before Multicore lands and possibly a year or more before Modular Implicits makes its way into the mainline compiler.

2. I think it's kind of a bittersweet future. I think growth is decelerating for OCaml because of ReasonML/BuckleScript making it really easy to get started with OCaml and use web libraries. This is great because it brings exposure to the language, but I think it's caused a number of people to switch over from native to web, which means abandoning some of the OCaml libraries for their web versions. OCaml has a great native backend and it's really a shame for me to see it fade away, but I think in the long-run that's probably going to happen. Still, I think popularity of Reason will continue to go up and that will bring OCaml into the mainstream for hopefully long enough to garner some attention and get people to take the native backend seriously.

3. I'm currently working for equity at a very small startup I co-founded but we're using ReasonML for the web side of things. Previously, I was at an internship where I had a lot of freedom to use whatever I wanted and was paid to write some software in OCaml. I think finding a job writing OCaml is rather difficult, but introducing it in a job (especially for internal tools or web development with Reason) is much, much easier. The "big" OCaml jobs seem to all be at companies where it's really hard to find employment (Jane Street, Facebook, Bloomberg), but occasionally you'll see some smaller ones pop up online.
Weakly held, sure, but why have strong views when you don't need to make a decision? There's value in being comfortable with uncertainty, in collecting interesting questions and not answering them.
I didn't think Slava was involved anymore.

It certainly seems like a neat language, but I could never find enough beginner material to make any headway (not sure if anything has changed in the past few years).

There is a Google tech talk where Slava talks about Factor @ Google.
That's fine. Was anyone forced to work there?
It seems to me taking averages would be inappropriate in all three of those scenarios.

Credit risk is based on total debt, and since credit cards are a revolving line of credit, the entire credit limit is considered debt, even if the balance is zero. That's why you can improve your credit score by closing out a credit card that you never use and that carries a zero balance (which we did in order to qualify for a mortgage several years ago). In other words, it's a sum, not an average; there's no division involved.

Setting aside the fact that there are much more reliable ways to detect a stopped heart than blood pressure: If you're taking a running average of BP over time, a low reading after a heart attack would just be a single data point, and you'd probably have to accumulate a bunch of them in order for it to register (particularly if you got a high reading just before the event). Even if you take a reading every five minutes, which is ridiculously frequent for BP, the patient will be long dead by the time you notice. You should be acting based on the last reading; again, no division involved.

I don't see why a freezer would be based on running averages rather than the most recent reading either. Thermostats generally work off of two thresholds: a higher one above which the compressor turns on, and a lower one below which it turns off. That smooths out any measurement noise without taking averages. Even if you do use averages for some reason, though, presumably it will start measuring at _some_ point and the compressor will turn on; I don't see why the average would stay at zero.

I'm not convinced that `1/0 = 0` is correct in any meaningful way, but I feel like any situation where it would cause bugs more critical than a UI issue probably points to a deeper design flaw. After all, if the alternative is to crash on a failed assertion, that's not necessarily preferable in a life-or-death situation.
Combine your first idea with your second and you may be on to something. A uniquely encoded disc that must pair with the printed CD key in the case. Kind of a public/private key thing, I guess? Crypto isn't my area of expertise so I have no idea if that is feasible.