skysight-inc/HackerNews huggingface dataset:
Why would you assume that models can be ranked on a single one-dimensional scale from good to bad? I mean, they can, but only retroactively and by throwing away a lot of other useful information.
Every computer component can fail in arbitrary ways, including drives.

If you’re not robust against that, then when things like fsync fail, then you’ll lose availability and/or data.

Even though Linux’s fsync behavior is clearly broken, it is far from the craziest behavior I’ve seen from the I/O stack.

Anyway, the main lesson here is that untested error handling is worse than no error handling. They should have figured out how to test that this path actually proceeds correctly (on real, intermittently failing hardware) or just panicked the process.
Thanks koalalorenzo!
>... Such as?

For one, a less competitive/macho culture, less booze friendly, less nerf guns, less nerdy references, -- on the other hand more agreeable collaboration, more petty antagonisms, etc.

Those are from empirical experiences working in a few XX and XY heavy environments.

But psychologists and social scientists have also long studied group dynamics in mens vs womens teams...

>Btw, the issue isn't really "the tendencies 22 year old men" so much as it is people hiring for friends and drinking buddies instead of hiring for employees and colleagues

Sure, but in startups and smaller companies in particular people also hire to match their idea of cool lifestyle, not just seeking employees and colleagues to maximize professional performance...

(Heck, they might even think that professional performance is secondary, and a 10x programmer that doesn't fit the culture will bring everybody down)
When I see an article on Hacker News about how macros might be dangerous to humans and other living things, I at least expect a comment from Paul Graham.
Brand new device every two years for me - and I can request any device.
I've seen plenty of if(!(var != true) == false) and the like --- some people just seem to not really understand the concept of booleans.
There is nothing natural in invasive species. Doing nothing to stop them to take all the reserve, would be like a museum curator welcoming termites, insects or fungus as a natural part of valuable antiquities and oil paintings.

This subverts totally the main reason for having this nature preserve, saving rare and valuable ecosystems (instead using the space for another cornfield).
Precisely.

What if I decide to put ads on my personal blog because I've noticed that I have enough readers to make that make sense? Am I now a business? What if I decide to sell a plush design I made because people kept asking about it? Let's say that it becomes so popular that I choose to make a business out of it, at which point do I need to start making my website "accessible"? Is it when I file for a business license, or when I reach some amount in sales?

Personally, I don't understand the "accessibility as a right" crowd. Yes I want the web to be accessible to people with disabilities, but I don't think it makes sense to force people to cater to any particular group. Perhaps it makes sense as a requirement for publicly listed companies, and absolutely for any government entity or entities that receive government funding, but not for the average person or small business owner, and the internet blurs the line between individual and company.
"Your [sic] coming from a site that we don't like."

Well, gosh.
Out of curiosity - if a memoized DOM is faster than virtual, why doesnt the React team to move that?

I wonder if its technical complexity and what it would be under the hood. I know Fiber was redone recently-ish.
Why is management paying for all those overdesigned web pages?
> heats the tissue to a temperature of 107 K
In case this confused anyone else, it should be 10^7 K, ten million degrees.
The Vampire is FPGA-based which means they are emulating the chipset (AGA in the works) and the CPU (they came up with their own version of m68k and named it 68080).

It’s impressive but it’s not a traditional Amiga. It also has compatibility problems.
"I believe OOP and relational database get a lot of flack because programmers tend to be bad at design, not because they are broken paradigms". This is very true. Another more charitable interpretation is that sometimes deadlines prevent programmers from thinking their models thoroughly and so an imperfect model ends being used, causing problems in the future.
Ah ok, they’re saying don’t use a new promise to do async logic not don’t use them for more sync things later down the chain. Thank you!
I dunno, hardware errors really aren't a thing that is well handled by local APIs. I mean, it all feels to me like the PG folks (and you) are expecting this to have all been fine if they just called fsync() a second time to be sure the busted write got to disk, and then everything would have been OK.

No, that's not the way it works. In virtually all circumstances, that second write is going to fail too, because the machine done broke! And even if it works, you have a situation where the machine broke and something somewhere worked around it, and you need to be screaming like crazy for an operator to fix it. That's not an API situation, that's a deployment thing, and it's exactly the regime where Google applied the protocols that you don't seem to like.

That's not to say that the linux fsync behavior is correct here. I think clearing the error having reported it once is kinda broken too. But... fixing that doesn't actually "fix" the real problem.

Really the best suggestion in that thread was up at the top, where it was pointed out that ext3/4 support remounting the filesystem read-only on errors, which sounds like a great policy to me.
>> Two things puzzle me each time a public figure is shamed for draft dodging the Vietnam war

What exactly does this have to do with the article or the discussion at hand?
Speaking of model risk: the model code for this paper has no tests that I could identify.

https://github.com/INET-Complexity/isle
It's impossible to for me to say if it's bad idea or not. It could be either. I would consider the following points. But first I want to mentioned that the country just recently changed its name to North Macedonia.

Do you speak the language?

Can you easily get the correct visas to visit and work there?

Do you really want to depend on personal favours from a friend to handle the legal part of running a business? You should probably account for the cost of professional legal and accountancy advice for the long term.

North Macedonia is one of the best ranked countries (by the World Bank) for ease of doing business. https://en.wikipedia.org/wiki/Ease_of_doing_business_index

North Macedonia is not in the EU yet, so exporting or importing to/from the EU will not be totally frictionless.

What would you lose/gain if you just incorporate in your country of residence and hire contractors working remotely in North Macedonia.

If the venture is successful, you may well end up spending a large part of your life in North Macedonia. Does that appeal to you? For whatever it's worth I've met someone who lived there for 3 years due to work, and they loved it.
I'm an R advocate. I call R the "Excel Buster". I think reproducible research is very important and tools should follow. Excel has its place in fast mathematics prototyping but for reproducible research it is quite lacking.
IMHO that shouldn't be too much of a concern. As long as it's just the sources leaked and you only distribute your modified versions of it plus binaries, but not all the games assets, players still need a copy of the original game to actually play it. (So as long as people don't pirate it, it should be fine and if it's still on sale make them an additional buck or two, but that question is somewhat orthogonal.)

I'd even argue that you could be smart as the IP holder and release the code with a clause saying any modifications and extensions must be open source too and the IP holder had the right to use those and make money off of it. Then you can decide if you wanna take the risk of potentially working for some company for free when you take on porting that 90s racing game to the PS 4 in your spare time.

Taking down leaked source is obviously pretty simple due to DMCA, but as history has shown that just leads to groups working on it behind closed doors and only doing binary releases. Which might be technically illegal too but probably much more involved for the IP holder to prove, so they don't bother in most cases.
Just as immigrants can be criticized without using the terms "rapists" and "murders" and "enemies of the state" and "send her back". But why should Trump be exempt and immune from one particular criticism of something he actually did?
They couldn't be assed to build a not morally compromised version of their page.

Ads are still possible with GDPR if you forego invasive tracking or obtain explicit permission.

Arguably ads with tracking is going an extra mile over just displaying some ads anyways.
I was confused by this and it’s the first time I’ve heard of EOUSA.

What’s the real story here?
LaTeX and Math Typesetting – A Comprehensive Intro (2019)
It is broken but there's no behavior that isn't, and the Postgres developers quickly understood why changing Linux's behavior isn't really possible.

From https://lwn.net/Articles/752063/: "Linux is not unique in behaving this way; OpenBSD and NetBSD can also fail to report write errors to user space. [...] If some process was copying a lot of data to that drive, the result will be an accumulation of dirty pages in memory, perhaps to the point that the system as a whole runs out of memory for anything else [...] a fair amount of attention was paid to the idea that write failures should result in the affected pages being kept in memory, in their dirty state. But the PostgreSQL developers had quickly moved on from that idea and were not asking for it".
> Is it unreasonable to assume people will read the fine print?

Unequivocally, yes. Even if someone hypothetically had enough time to read every TOS they've agreed to I would venture to guess the average user wouldn't be able to comprehend most of the terms[1] anyway. Disclosure documents are written by lawyers (corporate CYA) for lawyers (regulators, plaintiff's counsel, judges).

The law, however, disagrees with me entirely.

[1] Edit to clarify I mean "terms" as in the terms of the agreement
I'll start. I am an engineer and every day I spend at least one hour online reading tech news. Use twitter, techcrunch, hacker news etc.
> Did the Geiger counter click or did you hallucinate or did the counter misfire, etc.

Doesn't matter. What matters is that objective observers listening to the counter independently will all agree on how many clicks it made in a given period of time. It is this agreement that needs explaining. One possible explanation is that the counter did, in point of physical fact, click that many times. In fact, that seems like a very plausible explanation for the agreement to most people. That plausibility doesn't necessarily make it correct, but it does mean that you cannot dismiss it as "simply incorrect." If I hallucinated the clicks, why then do I agree with all the other observers, including inanimate ones like electronic counters? Are we all experiencing the same hallucination? If the counter "misfired" then why do geiger counters give the appearance of producing random clicks in response to radiation?
The main difficulty is that networked apps have a network to deal with and generating those bindings coupled with today's demands for interactivity etc. makes things tricky. RPC frameworks like gRPC tend to be quite rigid in this aspect too (requires setting up exact specifications), despite making things easier for the client. Also, the threat vectors are completely different. If all browser apps run on a iOS device (i.e. locked down tightly with secure elements, can be used as Point of Sale machines, very difficult to temper) with data piped over TLS then it might be another story. But we don't live in that world. Browser apps have to deal with the fact that they can be tempered with easily. That a lot of things requires securing on both the client side and the server side (just think about how many times you have had to write two validations for form input). Servers have to be designed not to be easily compronised. It forces data and state to be clearly specified and mapped out. You can't just hold everything in-memory when you have to pipe things down the wire.

Potentially soon we will be seeing more of such things. MSFT WebForms didn't work out for all sort of reasons, but with stuff like front end Flutter, WebAssembly, the whole server-control GUI over WebSockets thing with Phoenix LiveView, Plotly Dash, .NET server side Blazor we are seeing a resurgence of this idea. Building rich UI and having to manage state both ends is a pain in the butt and makes stuff like authentication/authorization tremendously difficult to implement properly and correctly. We have come a full circle.

What's almost ridiculous is all the manpower and engineering effort that was put in over the years just so we can have a better UI and UX. You can build a shiny GUI in React and use the same COBOL accounting software code running in a DOS simulator that once powered a TUI software and the end user would not know the difference and would be more than happy to hand over money.
Hi dingo_bat!

Here are a few unofficial implementations on Libp2p in C.
- https://github.com/squishyhuman/c-libp2p
- https://github.com/Agorise/c-libp2p

Here are Go, and Rust (Official)implementations:
- https://github.com/libp2p/go-libp2p
- https://github.com/libp2p/rust-libp2p
You can find the interfaces in the codebase. If you are having a hard time finding the interfaces in the codebase, or not able to figure out how to use them, then PLEASE head over to discuss.libp2p.io. There are a ton of people who will be more than happy to help you :)

I will try to add all this info in the article wherever possible. Is there anything else that you what to be improved in the article?
Then a lot of business operator would not support it and hopefully will even fight for the law to be changed.
The peat consists of methane, fyi.
> This may suggest that our lineage has evolved specific adaptations to digest starch-rich foods, underlining the long and continuing importance of these staples in our diet

This reminds me of the interest in keto dieting and the frustrating misunderstanding that carbs are the cause of excess weight, diabetes etc. If that were true, the whole world would be diabetic and obese, since everywhere has a staple carb. It's only with excess calories and fat that carbs contribute to, but are not the cause of, the problem.
Your maths example is incontestably true so no-one would waste time debating it.

Claiming js is essential to all modern browsing is not true and I am contesting it because in practice its use opens up bloody great security holes.

And you are still not addressing my obvious and relevant point, that not using js closes those holes. Stop downvoting and explain why you think compromising browsing safety is your right.
Thanks, shrutigarg12
Writing code that is well designed but not over-designed is a great skill.

It is in every engineer to write the gold plated car, as it is in marketing and sales to always need the future tomorrow to gain competitive edge.

The number of times I wrote beautiful code are quite numerous, the number of times it is still not used to its potential as well. In the end I spent too much time over engineering for a disastrous moment or extension that never happened, or was never requested by a customer.

I have written godforsaken shortcuts that are used so frequently it made me feel proud and ashamed at the same time.

Now, I have come to believe that knowing when to stop is the greatest skill of all.
Most programmers work in passes, and don't write everything in one shot. But a common mistake I see is not doing enough passes still. Programmers jump on making polished commits they can show off to their peers.

Instead, what should be use more often is what I would call "postit commits". Simple strokes of code that are certainly not final (if any code can be final) but achieve a purpose. Their postit nature makes it very easy to change. Those commits still need to point in the right directions though because they may stay here for a while (think 15 years). As long as they aren't hurting the customer or the codebase (like a supposedly-temporary hack, even though those are sometimes required), then it's all fine, a program is never finished anyway.

Working with more passes allows you to think more at every step and shape a solution that's more efficient. For example, take a piece of code that's too slow for the requirements and for obvious reasons. Don't necessarily jump on optimising it right away. You may find later that you will finally get the whole subsystem in which that piece of code is included better by using another more powerful idea. And when you come up with that new idea, the only thing that will stand in your way is "postit commits". You can change things now because you're not facing polished ones. You can change things now, not in 10 years when you find out every one of your competitors has finally implemented that idea, in which case you would take the cost of a full rewrite.

This is essentially how you do things well from scratch (and by extension, how you do anything well with code). Keep postits as long as you can, because it's a better strategic position. Only harden a solution when you can't give it more time or because it just hardened itself with cool ideas. At the end of the day, you will win time, if you worry about that. You will crush your competitors even. They will have 3 times more code with bad solutions, you will have 3 times less code with all the super cool stuff and nice subtleties (it doesn't always play out like that, but often enough).
Thank God I thought I was the only one left.
Many, yes. I expected better from the BBC though :(
It’s not an argument, just a plain statement of fact. Remember, the context here is an article about the reasons why a huge number of Americans live paycheck to paycheck. It’s quite relevant to mention that having everyone buy old cars can’t solve this problem.
Not GP, but the book 'Domain Modeling Made Functional' does explain advantages in modeling with types quite well.
CGI security depends on the framework you use after. It's just different from reverse proxy.
In case someone reads this and gets the impression that running PG over NFS is in general safe or a good idea, I'm pretty sure it still isn't, unless like the OP you have a complete understanding of what you're doing.
Sure, but the fact that the desktop became less important compared with mobile/web doesn't actually solve the problem of Microsoft having a monopoly on PC operating systems. Gnu/Linux is almost unusable for non-techies, not because it's deficient, but because almost all third-party software and hardware is built with Windows in mind, because that's what people get when they buy a computer.

In a well-functioning market, all you would have to do to beat Microsoft would be to make a better operating system. In the current market, to beat Microsoft, you have to make a better operating system, target a new category of device, and own one of the biggest companies and several of the biggest websites in the world.
That's what !! is for!! :)
Comprehensive data points on why this is happening. Formulate your own conclusions.

* "Every Chinese citizen is only allowed to exchange up to US$50,000 in foreign currency a year at their bank, and also faces major hurdles to buying foreign exchange within that quota" https://www.scmp.com/economy/china-economy/article/3017203/c...

* "New Restrictions on High Tech Technology Transfers to China" https://www.chinalawblog.com/2018/11/new-restrictions-on-hig...

* "Something Just Broke In China As Repo Rate Soars To 1,000% Overnight" https://www.zerohedge.com/news/2019-07-19/something-just-bro...

* "Transfering money is getting more and more difficult, even perfectly legitimate business transactions." https://www.reddit.com/r/China/comments/c5qwd7/transfering_m...

* "China’s Banks Are Running Out of Dollars" https://www.wsj.com/articles/chinas-banks-are-running-out-of...

* "China’s Economic Growth Hits 27-Year Low as Trade War Stings "https://www.nytimes.com/2019/07/14/business/china-economy-gr...

* "China No Longer Expected to be World’s Largest Retail Market in 2019" https://wccftech.com/china-no-longer-expected-to-be-worlds-l...

* "Hong Kong’s GDP grinds to near halt at dismal 0.5 per cent growth" https://www.scmp.com/news/hong-kong/hong-kong-economy/articl...
This needs to include the class of users who'd don't care because they don't understand. If they knew, they'd be upset too.
One thing I took away from this thread: when someone tells you something surprising, it's best to ask, rather than deny. It doesn't look good to say things like:

"Moreover, POSIX is entirely clear that successful fsync means all preceding writes for the file have been completed, full stop, doesn't matter when they were issued."

When you have plainly not actually verified that it is the case.

Instead, you could say, "doesn't Posix say . . .?" This has the following benefits: you avoid egg on your face, the conversation takes on a less aggressive tone, and problems are resolved quicker.
Ah, I had mistaken your reply, and assumed it was to /u/u801e and not the linked article.
I don't get client side navigation. It's a worse experience in every way. It's slow, often doesn't support things like command-click, it usually breaks the back button, and even if it doesn't it breaks the restoration of the scroll position.

The only thing worse is a custom scroll UI.

Why do people try to reinvent the most basic features of a webbrowser? And if they do, why do they always only do a half-assed job at it?

It's infuriating.
you get it wrong :)

> Objects are actually arbitrary mixtures of lower level primitives: functions and data.

Nope, everything is an object, numbers, array, function, etc, are objects.

Objects allow you to describe user-defined data by composing objects

address1 = Address { street: "..." }
address2 = Address { street: "..." }
john = Person {
name: john,
addresses: [address1, address2]
}

Methods are functions biased toward an object, which allows polymorphism, so you can abstract over data

function f(data) {
data.add("foo");
}

works for every data that provides a method "add".

so OOP is complementary to function.

That said, OOP has several flaws:
- at some point someone decides that OOP was about inheritance or prototype chains but those mechanisms are more bad than good.
- existing mainstream languages tend to favor mutable objects by default which leads to bugfests.
Suppression of dissent. What else?
Obviously at the time the texts were written, they were in circulation, but it predates modern copyright law. So maybe there's a loophole in the law they're exploiting, but regardless it's unethical, and Archive.org has the power to not accept works under those circumstances.
Do you have any more information available on this? I'm curious about the use case for using compiled binaries directly over PHP.
you have a simple choice: either have those collections be kept and preserved, OR have them disappear forever. We can all be grateful we at least have one non-profit who does give a fuck at all, no for-profit business will ever do any preservation work like it.

Gutenberg is only preserving public domain works, MANY are lost to humanity way before that.
No, mildly unrelated and orthogonal. Not everybody cares for their website to be read well on mobile (I, for one, don't), and not everybody who runs a blog has/wants control over the posting environment (they just pick an engine and them and be done with it -- if the readers find their work valuable enough, they can spend some effort to read it).