skysight-inc/HackerNews huggingface dataset:
>Fox News, for example, started conservative but far less radical.

I think you're really stretching the definition of radical. That the views may be far from your own does not make them radical.
"At this point" is key, actual copying was important earlier in this case but is now a decided issue.

This appeal is strictly about the copyrightability of APIs. The supreme court generally doesn't address cases as a whole, but specific issues brought up to it on appeal.

If I remember the decisions on the actual copying part of the case correctly, it was decided that Google copied something like a dozen lines of uninteresting code directly (not api's, just some method implementation), and that this was de minimis copying and didn't constitute infringement. You should check if you really care though, I might be wrong.
SHA1 isn't broken for hashes.
I Work Remotely
First, rust provides safety checks you don't get in C. Second, the only way you'd improve compiler performance via C conversion would bypass these checks. Third, transpiling through C without these safety checks loses the point of rust in the first place.

The fact is, that there are a great many bugs in the wild that never would have happened in idiomatic rust in the first place. Yes, there is additional overhead to compiling. By comparison, if you use static code analysis on your C/C++ code there is additional overhead, and even then a greater chance of security bugs slipping by compared to rust.

In the end, used server hardware is relatively cheap in most of the world, which does pretty well with this type of code. There are a lot of people using mid-upper range x86 hardware and even to cross-platform compile to lower end arm64 support. At some point, it's less worth maintaining legacy hardware either for pragmatic and/or practical reasons.

Rust was started well after x64 and other 64-bit hardware was in the wild, and 32-bit hardware was for the most part no longer being produced. Supporting such systems is work that practically speaking is less valuable to most people.

As someone that really likes the old DOS based BBS software and related tech, and even supports Telnet BBSes today, I don't always like seeing this left behind to some extent. Last year, a large portion of the community blew up when 32bit was going to be dropped from Ubuntu, mainly because of the need required by wine and the gaming community.

This isn't about supporting 10+ year old apps and programs in an emulated environment... this is about porting existing code in an automated enough way to improve stability and support-ability over time by leveraging a safer language.
...who nonetheless has solid journalistic methods.
a purely random sequence of letters has greater Shannon information than a string of words that make up a sentence, because the words and the sentence have some higher-order patterns in them (like statistics of letters that typically follow each other, such as a “u” following a “q”), which can be used to compress the message. A random sequence has no such patterns and thus cannot be compressed.

Thinking in those terms naturally leads to the kind of “counting arguments” that Bengio makes. These seem to take each gene as a bit of information, and ask whether there are enough such bits to specify all the bits in the brain, usually taken as the number of connections. Obviously the answer is there are not enough such bits. (There aren’t even enough bits if you take individual bases of the genome as your units of information).
A union only works if everyone joins it, and that's not even close to happening in tech.
Confirming the window opening speedup! Previously FF spent a lot of time compiling shaders when opening a new window. Perhaps these are now been cached.
"Never noticed" is doing a lot of work for you there. Making line employees work more to achieve goals that cannot otherwise be reached except by pushing those employees to crunch is what managers are for. Why would an executive or a founder "notice" this? The work's getting done, what else do they care about?

It's possible that iD was well-run when he was there. (And, from what I've anecdotally heard, that's probably true--Todd Hollenshead gets a lot of respect from folks I know!) That doesn't mean other studios are run so well and it doesn't mean that Carmack's anecdotes cancel out, or even meaningfully put into question, those of people not in his rarefied circles. There are a lot of game developers out there and most don't have nearly the funding or the schedule luxuries that iD always did pre-Bethesda, when Carmack was most involved.
> This right here illustrates something I've been thinking about a lot - the various ways you can define freedom, and how differently it tends to be defined in the US compared to how I as a European define it. It seems that in the US it's common to define freedom as simply the absence of obligations and demands. So low taxes and small government = more freedom.

That's an exaggerated and misleading description. Per person government spending in the U.S. ($22,500 per year adjusted for purchasing power) is well above the OECD average, and right between Switzerland and Germany: https://www.oecd-ilibrary.org/sites/reg_cit_glance-2018-41-e.... (Factoring out the difference in military spending, about $2,000 per person in the U.S. versus $600 in Germany, doesn't change the ranking. The next country below Germany is Ireland, at under $20,000.) Four of the largest five EU countries (Spain, Italy, Germany, U.K.) spend less per person -- again, adjusted for purchasing power -- than the U.S. France is only a little higher, around $23,500. Excluding Norway (oil money) and Luxembourg (tax haven), the highest is Denmark, at $26,000.

We have a big government in the U.S. It's often not very efficient. We consistently spend more to get less in terms of education or healthcare. But that's a very different issue.
First Look: OpenGL Shaders in React Native
Cryptographic engineers do not in fact think you should use SHA-2-512 so that you can maximize the number of times the round function is applied.
The best known attack against AES reduces attack complexity by about two bits over brute force. Given the history of block ciphers, the idea that AES might not be broken in this life time is not uncommon.
We've created a peer to peer database at https://www.ditto.live . It runs on servers, WASM, and mobile all with a shared code base. Each row in the database is a robust CRDT that can sync deltas (or diffs) very efficiently. In addition, we are just about to add binary file sync that is quite reminiscent of bittorrent and has all the goodness of retries, resuming downloads, canceling, and pausing all baked in.

The most unique feature of Ditto is really our networking stack. Devices that have the database can sync over any available transport: mDNS, WiFi Direct, AWDL, Bluetooth Low Energy.

Here it is in action: https://www.youtube.com/watch?v=1P2bKEJjdec

Here's a video of how being p2p allowed us to architect a database that fall back to mesh networks if the server can't be reached:
https://www.youtube.com/watch?v=0IAle9BYlxQ

We're launching with several massive enterprise companies this year and some mid-to-small ones as well. On your next flight, if you notice that the flight attendants and pilots are using mobile devices to collaborate in realtime even if the internet is down: it's us ;-)!

A couple of notes about how the SDK works:

1. The CRDT that backs our data structure for each row in the database looks like a JSON object to the end user.
2. It is capable of substring modifications, array and map mutations
3. Conflict resolution is automatic and deterministic, the default behavior is LWW but can be customized as long as it's deterministic.
4. It's written completely in Rust!
5. If peers in the mesh network have the same CRDT and only minor mutations are made to part of the CRDT, then they can efficiently sync a subset of them to reduce bandwidth limitations
6. Our replication protocol is tied to queries. Peers will broadcast what they are interested in and devices that have relevant data will send it as long as the proper authorization certificate is there.
Thanks, this has more details.

> Police allege the fires were set to garbage bins, items placed outside for council clean-up, and motor vehicles.

These are definitely arson, but still not people deliberately trying to burn down forests.
I think the vast majority of these iot applications are something like “read; send; sleep 60”. But your point stands that people needing high precision and timing probably won’t reach for this.
You can and people do but it’s important to note that that the raspberry pi CPU is a tiny part of the SOC and the Broadcom proprietary part that bootstraps it is completely closed.
As an aside Java's concurrency is outright confusing and just plain hard to get right. Doing concurrency in golang was like a breath of fresh air.
There are plenty of examples where there is absolutely a side that is correct and one that is not.

Do you think the earth is flat or that people who say so should be given equal time?

There are plenty of other instances where one side is demonstrably correct.
Reality Check: Tesla, Inc.
This reminds me of the (possibly apocryphal) story of old VMS (?) systems hanging if their console, which was often a printer, ran out of paper.
Mostly recalling some of the claims and allegations they pushed during the Kavanaugh debacle, which were very quickly destroyed even by other publications carrying more serious allegations.
> The basic idea is that public keys need to be exchanged to perform encryption from one end and decryption at another end. An example is encrypting with the remote users public key and they decrypt with their stored private key. It’s complicated though because you don’t want to exchange the public keys without restrictions where they can be obtained by unauthorized parties or disseminated without your consent. You also may not trust the distant end.

This is acdtually not true. You completely mixed up asymmetric with symmetric encryption.

The former is also known as private-public key encryption and doesn't require DH, because each party has their own private key which doesn't get shared and a public key which does get shared, namely publicly, so no reason to use DH. This is what RSA is.

The latter is conventional encryption which uses a single private key which must be shared between two parties over an insecure channel. Before you establish a secure channel via encryption you must first exchange the secret piece of information that allows both sides to decrypt a cipher message. That exchange therefore happens over an insecure channel, which is a problem. DH is an algorithm which allows a secure exchange of a private message over a public/insecure channel.
That just replaces the first word with what is essentially a synonym. It's the second word "intelligence" that's the issue.
> At every single point in time, state of the art cryptography is going to be able to produce fake random that the current state of the art cryptanalysis cannot prove as not random.

That may not be true. (As in, I'm not sure it is.)

For many useful crypto algorithms where we give a nominal security measure (in bits), there is a theoretical attack that requires several fewer bits but is still infeasible.

For example, we might say a crypto block takes a 128-bit key and needs an order of magnitude 2^128 attempts to brute force the key.

The crypto block remains useful when academic papers reveal how they could crake it in about 2^123 attempts.

The difference between 2^128 and 2^123 is irrelevant in practice as long as we can't approach that many calculations. But it does represent a significant bias away from "looks random if you don't know the key".

It seems plausible to me that a difference like that would manifest in statistical analysis that state of the art cryptanalysis could prove as not random by practical means, while still unable to crack (as in obtain inputs) by practical means.
This seems like an argument against unions. I certainly don’t want to live in a world where somebody is guaranteed a wage or a job due to age or seniority. This just seems really entitled.

It’s up to you to create value, regardless of age.
Action Potential Mechanism
It does not. It expands at every point in spacetime. This effect is quite literally negligible on all length scales smaller than far extra-galactic distances.

It is equivalent to asking why a car driving towards me does not turn blue due to doppler shifting. Except even more negligible than that.
Yes, but being a professional journalist doesn't presently correlate with journalism skills or integrity. His work is closer to good journalism than most TV news programs or "news hours".

Funny world we live in.
The Ladies Who Launch: Lingua Franca and the Rise of the Resistance Socialite
Yes, and sometimes you want to validate a performance change and you need the release build to run in the benchmark fixture, and then it's irritating that the build takes forever but what can be done? ThinLTO's real benefit is that it uses so much less memory than legacy LTO and can be applied to larger programs (like Chrome).
One thing I did not see compared is overhead. I haven't tried Dat yet but IPFS seems somewhat fat from my tests of it. It eats it's fair share of RAM and CPU. I expect a distributed everything store to eat disk but being light on RAM and CPU can be important. Disk is cheaper.
> The problem with RPC is that people are not familiar with it.

Your response seems to indicate to me that you are not familiar with it to know its downsides or long, complicated history. RPC as a concept dates back to the beginnings of inter-process communication in the 60s and has an equally long history in network communications.

There's always been a pendulum swinging between tightly coupled RPC standards and loosely coupled data interchange standards (or one made from the other in all sorts of combinations). It's a fact of software development life since essentially the dawn of the industry.

It's the "tightly coupled" part of RPC that caused REST to be evangelized over SOAP, an XML-based RPC standard. It's the "tightly coupled" part that GraphQL tries to balance in its looser query syntax embedded in its RPC dialect.

There's nothing wrong with "tightly coupled", just know that it is a trade off. You almost seem to realize it in your realizations that RPC is complicated when working with third party developers. You are almost close to the enlightenment of why REST became so popular and SOAP faded away.

> basically by introducing a schema to RPC

COM has IDL. SOAP has WSDL. gRPC has proto files. GraphQL has its schema language. These wheels have been invented many times, it might be useful to research some of them if you wish to further discuss RPC.

ETA: Which is not meant to discourage you, I want to encourage you to learn more. It's not wrong that you don't know these things, it's an opportunity, and I really do hope you explore it.
Fascinating explanation of neurons by Prof. Eric Lander, part of OpenCourseWare published Introduction to Biology https://ocw.mit.edu/courses/biology/7-012-introduction-to-bi...
> Horizon said the added protein comes from “organic milk protein concentrate made from high-quality complete proteins naturally found in milk”.

They are adding extra concentrate to the milk. That's why it is 12 grams of protein per cup instead of 8 grams as it comes from a cow's udder or 2.5 as it comes from a human breast.
Elizabeth Wurtzel, author of “Prozac Nation,” is dead at 52
Most of Arduino's value proposition is easy programmability by non-professionals, with a vast library of examples. Cheap and powerful STM32 boards have been around for years about as long as arduino, supported by a number of free toolchains. But the care and feeding of said toolchains and libraries requires a lot more technical knowledge than Arduino's ecosystem.
Yes, but they are really part of the Entertainment industry, more specifically. Unionization is very much part of that industry, so maybe game developers should recognize that and try to join/expand those unions.
Care about robotic process automation
> Passing 200 Gbit of network traffic in software with firewalling is non-trivial and the number of cycles you get per packet is pretty modest

If that's the only function of the program, are we still talking about an "Operating System" ?
You are saying "contributing" while the reporting, which I copied verbatim, specifies the relationship as direct. Lots more where that comes from.
Raising public school teacher pay: What the research says
It may be true that programmers at the top 5-10 tech companies are well compensated but the vast majority of tech workers (programmers and operations) work for enterprises and small shops where there are some really egregious practices and not particularly great compensation. Being in hot demand means little when these practices are universal in the industry. This is the perfect scenario for workers to get together to demand better treatment and ending of these sorts of practices:

Uncompensated overtime,
On-call (if the work is important pay someone to be available to do it),
Expectations of 24/7 uncompensated availability,
H1-B use/abuse,
Lack of training on systems workers are responsible for,
Age discrimination,
Lack of decent work environment (open plan offices),
Lack of vacation options (sometimes masquerading as unlimited time off)
FreeBSD Bhyve WiFi PCI Passthrough
I was 37 when I joined Google in a senior IC role in 2008, so nearly my entire 40's. It's still work, there are still issues with coworkers and there's still stress compared to the startups I used to work at. The company isn't going to go out of business but you can still get a manager who doesn't communicate well and gives you bad performance reviews as a result. Google turns over more employees in a month than the entire headcount of some of my previous companies. And GOOG is a huge company - if anyone says it's either great or horrible that's probably true for them, but it doesn't mean much for what your experience is going to be. I honestly don't think that being young is really much of an advantage one way or other here - there are successful people in the 40's here, even ICs, there are a lot of new grads who wash out after a year or two and go elsewhere. Big companies have much more idiosyncratic tech stacks so knowing any particular technical skill isn't that huge a deal as we probably don't use it anyway. Know the basics, know how to write, know how to manage up.

edit: reading some other comments I think it's easier to be an older IC at big companies than startups/small companies. But whether you should pursue a management track is a completely different question.
This is a challenge for me because I also felt the need to do the Willy Loman thing for a while but then realized that other people needed me to be more open about negative emotions or pessimism.

But I feel I've gone too far in the other direction now, that if you go through a difficult stretch you can't let yourself be a dark cloud. It doesn't help anything, people want progress, joy, hope, etc.

It's a tricky balance to find, especially since my actual internal experience seems to vary more by week or month than by day.
He's not. They could be made. They'd just cost more.

The race-to-the-bottom pricing effect is not one caused by line developers and it's not caused by customers buying the games. It's caused by management and executives eating the seed corn. It's going to have to stop.
I'm in a similar position. I think if you have experience they really try to interview you for senior positions where you are defining technical architectural standards and teaching others. That makes it tough if you just want to code, but maybe suits you.

At least in the initial stages it seems FAANG companies at least are very good at ignoring age for applicants, later stages though are tougher when most people interviewing you are half your age.
You're assuming at that point that you're already compromised or running malware, though. If you aren't already infected with malware, this is not a problem. If the installer itself is malware, then switching to an admin account to install it obviously offers no protection.
I'm not quite as old, but I struggle with this question too. Programming and building shit is my passion, and I'd probably be a terrible manager, but I've been conditioned to believe management is the wise path for aging software engineers.
It's one thing to wear a pin on your sleeve, but it's another thing to use the force of gvt to attempt to enforce morality, by banning things deemed "not good" like vapes, private cafeterias, plastic bags, straws, etc..

On a side note, trying to put a label into one or two buckets is very short sighted.
The problem is that the expectations of software are much more akin to the expectations of a bridge than those of a bulletproof vest
Blocksize is clearly not literally a rate; that's a ridiculous statement. When you artificially cap it, like putting a limiter on your car in your analogy, it can be rate limiting, i.e. limiting the transaction rate - an actual rate. That chart you posted in meaningless in this context, but clearly just greg being greg, trying to manipulate; are you seriously trying to suggest that the tiny increase from segwit shenanigans is responsible for that (cropped) decrease in tx fees? That's demonic.
Yes that’s what I meant to say.
> I found a google groups pseudo-newsgroup comp.os.vms discussion dated 2017

Saw that too in my googling, fair warning that several commenters on there seem misinformed. (The code sample at the start is incorrect and some comment rebuttals seem to misunderstand or get it partially correct. In particular some people seem to think time_t is a struct with int components or that sizeof(int) has something to do with time_t.)

> Pretty sure the posted article is wrong about 63-bit because at the intro it clearly says, "All Versions" yet here we see that as of 8.3 it was still 32-bit.

The point is that the kernel doesn't keep the time as time_t. It has a different epoch and unit, and the C runtime needs to convert it to time_t. So the fact that 63 bits (64 if you count signed bit) is used internally says nothing about time_t at the libc layer.

Windows has it similarly. There, the epoch is 1/1/1601 and the unit is 100ns, stored as 64 bits.
> many of them require that you buy a huge chunk of inventory up front whether or not you sell it, which is one of many abusive tactics of current American MLMs

Purchasing unrefundable stock is not inventory loading. It does not “resemble an MLM” in a meaningful way - you might as well say that any company that offers a recruiting bonus to employees resembles an MLM.

If you want to talk about predatory business practices, there’s plenty of it around in the franchise model. When you keep saying “like an MLM” you sound like you think these attributes are specific to MLMs.
Our first brand is "Ono Blends", a smoothie truck in LA (onoblends.co)

To address the sibling comment, we don't use much TypeScript yet, but I'm open to it. I'm also looking at ReasonML because I'm cautious about half-measures when it comes to type safety.

Much of our complexity stems from race conditions between PLC and the JS server, so the next system is likely to use node.js on linux boards instead of a PLC. We currently have a supervisory safety system with all safety-rated hardware and controls, and will almost certainly continue using this approach as we replace the PLC.
Steps to Secure Your Facebook Account from Cyber Threats
Seriously, why am I being downvoted? It’s well established that FB groups are being used as niche channels for spreading misinformation. The only difference between one of these and HN is the quality of moderation.
For the love of what's holy, I think the versioning system adopted by all browsers is just crazy.
Mm. I sure do love to create value. That's certainly why I live. Not to, like, experience the world, or to do things I care about. Nope! I live to create value.

Work to live, not live to work. Well-run unions help workers do that, both young and old.