skysight-inc/HackerNews huggingface dataset:
I'm glad git is decentralized.
How do you protect your intellectual property posting online?
How are they making this news? News is simply news - there are no opinions here.

Click on the business section of Reuters, this isn't even a headline.
Blazor Mobile, Uno Platform, and WebAssembly
Until Swift stops requiring stuff like import Glibc for basic IO and actually supports Windows, I would consider it an Apple only language.
It was internet BS, not rust BS. Sorry if I wasn't clear. Cheers.
Both teleportation and Death Star are impossible with current technology, but the folks anyway are building the Death Star?
Obviously being vocally abused is not OK no matter what the victim has done. This is a big problem and I think Steve's article that is currently on the top page of HN gives a good overview of that part of the situation.

My problem with viewing all open source as a gift to the world, take it or leave it, is that when people create open source packages, market them as being ready for production use and as the best option for said production use, and then act unprofessionally towards security issues and reject patches that fix the security issues for no reason other than being "boring" and "not creative enough" people should be able to call them out on it as unacceptable behavior for an open source maintainer. If actix didn't claim to be production ready and instead stated that it was an experimental code base designed to advance the state of the art in web server performance I wouldn't have a problem with how it was managed. However, once you claim that something is production ready I think you need to be ready to take responsibility for it.
I'm not very involved in the browser/web standards space, so I just started to realize the stranglehold Google has there. It's terrifying! I was quite involved in the 90's and reminds me of Microsoft with IE, but no one seems to care this time.

I've been wondering the last couple days how people can best support Mozilla, aside from simply switching to Firefox. And how to best share the message with others who aren't technical or normally wouldn't care, like my friends and family. I'm willing to put up with some conveniences from not using Chrome, but that might be enough for them to not care.
> They were hateful and virtrolous

Who's they? Most of PR commenters were courteous. The last few were rude, but so was the fafhrd91. https://gist.github.com/mafrasi2/debed733781db4aba2a52620b67...
> Having a project maintainer then call those patches boring or otherwise disregard them? That's childish

So what? Along the same lines, it's not a maintainer's responsibility to follow best-practices, respond to feedback/PRs, or respond in any coherent way to anything asked of them. The fact that you call them childish for not acting they way you want them to makes me think you are the childish one.

With those PRs written, _anyone_ on the internet can apply them and use them in their software. I agree with GP, you aren't owed anything, and that extends to any form of social behaviors online. And let's not forget that even the most 'perfect' maintainer still deals with shit on a regular basis from the masses of people demanding features as if they got paid to write the free software people are using.

This expectation of being served high-quality open-source software for free, and then outrage when it isn't, is absolutely ridiculous and will make people not want to maintain software.
People reading your comment as entitlement really need to pay more attention to the last paragraph. People really need to stop bandying about "entitlement" as if it deflects any and all criticism.

You are, of course, free to write whatever unsafe, insecure code you want. You are, by leaving the issue tracker in Github enabled, inviting public feedback on the quality of the code you write.

When you implicitly rescind that invitation by closing issues demonstrating concrete safety problems, people are well within their rights to call out the safety issues in the project as well as your violation of reasonable expectations and community norms. And don't bother posting the "warranty disclaimer" from FOSS licenses, that's not what anyone was ever talking about.

Deleting the entire project as he did is an incredibly petty and immature response. If he just wanted to quit, the project could have been archived (made read-only) and marked unmaintained.
So he was paid by Microsoft to handle their pain points. How much did any of the reddit guerilla pay him to be able to make similar demands?
That is Uber's secret sauce - they defeat regulation better than anyone
Typhoid vaccine 'works fantastically well'
I always chat a higher up or coworker asking if they have a minute for a chat before I go seem them. The fact that this is not common courtesy is annoying.
Cheaper and/or better products in the future that can't use USB C to deliver the same product at that price/performance.

For example say I have a small < 100W device that needs to be powered and send data and I'd like to use the same connector for it. But wait, I'm going to put this gadget in an environment where people might knock the cable out so I'm going to use a different connector with a latching mechanism to prevent the cable from coming loose.

Oh no, I can't do that because the government says I can't.

Like OP said if it bothers you don't buy it. That's the market working for you. Diversity is good for the market and connectors aren't one size fits all, no regulation will change that.
Ask HN: Choose your 5 top qualities to assess for general personality-job fit?
Grassmann.jl – Differential Geometric Algebra
I mean Apple built a trillion dollar business by charging customers high prices with huge margins
FWIW, I don't have a dog in this fight. On the one hand, there is the maintainer who is within his rights to accept or reject patches as he wishes (although it's not great that he's allegedly falsely advertising his project as secure) and you have critics who are within their right to criticize (although it's not great that much criticism is vitriolic, etc). As TFA says, it's a sad affair all around.

> The problem wasn't the criticism, but the expectation that said criticism invokes a certain behavior of the maintainer.

Of course it implies that the maintainer should change. All criticism implies an expectation of change, at least when the opportunity to change is still available.

> Everything else is just trying to force people to do stuff for you, and that's rude.

Criticism isn't "force" or "attempted force". This is just criticism. If you think criticism is rude, that's fine. Hypocritical, but fine.

You can't rationally say the maintainer is within his rights for rejecting security patches and then argue that critics are wrong for criticizing these practices.
As a maintainer of a medium-ly popular library that I also use for work I can say that I love getting (quality) bug reports since these are bugs I didn't know I had. OTOH pull requests for the bugs I'm not as excited about. I wrote my library with a strong vision for the api and how everything fits together. Many times the pr submitter isn't aware of the vision nor has taken the time to understand how everything fits together. I'll read and understand the submitted code but many times I'll end up writing the fix myself.
The quoted article says they donated a total of $22K dollars to misc representatives. If I'm not mistaken, that wasn't even the company, but the PAC making those small donations. I'd even go as far as to say those donations seems insignificant relative to this $1B investment.

Feels a bit like you might be throwing out the baby with the bath water.
I recently had a conversation at work where I commented how great Caltrain was since I used to commute on BART. My foreign-born coworkers all laughed at me. I look forward to riding some nicer train systems in the future.
I imagine GitHub could make a reasonable amount of money if they implemented a bounty system, taking a little off the top for each bounty.

Each issue could have a donate button. The bounty would be split to the authors that contributed, with some remainder left for unfinished work (documentation, unit tests, etc).

To settle how the bounty is split for multiple authors, they could go through an anonymous round of "bids" to propose splits, with the bounty locked until they agreed. Maybe the maintainer/reporter able to settle disagreements by choosing a split ratio that lain somewhere between the range of those bid on.
Belmont at least has some density and Main Street. Atherton’s density is 1/4 of Belmont’s and it occupied the very center of SV.

Atherton
1,438.97/sq mi (555.53/km2)

Belmont
5,843.98/sq mi (2,256.45/km2)

San Mateo
8,570.40/sq mi (3,309.14/km2)
>you get this weird dance of finding a spot sufficiently far away from each other to be able to stick with the policy and not also hear each other directly, with no latency.

See if you can talk to your boss and get everyone over-ear headsets with a boom mic, and spend some time tuning them so the mics only pickup the person talking.

That way you can have several people all in the same area all on the same or different calls, and for the most part it won't be an issue.
The Enclosure Movement is worth reading about. People tend to think of the Anglo-Saxon world as having been individualistic (in theory, and oligarchic in practice) since time immemorial, but it was much more communal until relatively recently.
For me this says more about the drawback of easy and automatic dependency management. When I write C code, adding dependencies is often a huge pain in the ass. You need to figure out how it's packaged, how it's build. Should I build a custom version or just use $distro's pre-packaged version? How do I tell my Makefile/configure/CMakeLists where to find the headers and libraries?

This is generally a bad thing. It leads to NIH, to poor portability, to difficult integration in other dev environments etc... But it does mean that you carefully consider every dependency that you must use. The quality of the packaging is often an indication of the quality of the code too, a well polished build system inspires confidence, a crappy buggy bespoke shell script less so.

Meanwhile take this example: I've re-started working on a PlayStation emulator a few weeks ago. I haven't reached the point where I need to display images or output sound, it's pure algorithmic code with no I/O so far. That's 0 dependencies.

But then I wanted to add some basic logging infrastructure to be able to do 'warn!("this thing shouldn't happen")' or 'debug!("this register has value {:x}", val")'. I could just use println! but, hey, adding dependencies is super easy and I'll end up with more flexible and expressive code, so let's do that instead. So I add these two lines to my Cargo.toml (note the simple in simple_logger):

[dependencies]
log = "0.4"
simple_logger = "1.3.0"

And as easy as that I have a proper logging framework available. Amazing. Except that when I then run `cargo build` I see the following:

Compiling autocfg v0.1.7
Compiling libc v0.2.66
Compiling log v0.4.8
Compiling lazy_static v1.4.0
Compiling cfg-if v0.1.10
Compiling num-traits v0.2.10
Compiling num-integer v0.1.41
Compiling atty v0.2.13
Compiling time v0.1.42
Compiling colored v1.9.0
Compiling chrono v0.4.10
Compiling simple_logger v1.3.0

That's 12 dependencies for a glorified println! implementation. Did I vet this code? Of course not. It would be faster to just reimplement it myself. Do I trust that somebody went to the trouble of doing it for me? Not really. I just cross my fingers and hope for the best. It's wonderfully convenient but I'd be very wary of trusting any security-critical project with a dependency graph like that, and it's quite paradoxical since Rust is all about safety.

Oh and beyond that Reddit is a terrible place that manages to be the worst of 4chan and the worst of Facebook in one convenient package and should be avoided at all costs, but we already knew that.
Do not shoot people who work for the government and then expect the Second Amendment will get you off the hook.
Yeah, and interestingly, a lot of unsafe functions use "unchecked" in their names.

The issue was that by the time this was recognized, there was too much Rust code, and there was no clear alternative that people universally liked. This kind of conversation is the definition of bikeshedding. I submitted an RFC and it... didn't go well. (I think I picked "trustme" though.)
Super neat idea and tool!

I tried to clone it and run it locally, but it doesn't run. Tried with both yarn and npm.

> node-sass src/index.scss > public/index.css

sh: 1: node-sass: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
I'm not talking about people mistaking juniors for seniors. I'm talking about when a reviewer lacks the context to understand what your code is trying to accomplish - which happens all the time, even on well-functioning teams. Those situations require you speak up and at least try to clue the person in.

And yes - if you automatically fire off any change requested of you, then it does give the impression that you don't know what you're doing or don't care. I'm talking from experience.
"Feeding the search machine only makes google stronger. If businesses stop giving away their content to google for free, it will stop being so important"

So, let's say you are a business. You can only control what you do, not what all the other businesses in the world do.

Is your strategy to keep your content off Google, in hopes that you will starve the "search machine" and thereby weaken it?

My guess is you won't be a business for long with that strategy.
Hit this link and use the Wage Level filter. The poor are seeing faster wage growth than any other income quintile. The richest wage earners are seeing the slowest growth - income equality must be dropping quickly, even if wealth inequality might not be do to stock ownership.

https://www.frbatlanta.org/chcs/wage-growth-tracker.aspx
> Google allows competitors to purchase ads on Basecamp’s trademark, and then blocks consumers from reaching its site, Co-Founder David Heinemeier Hansson told Reuters in an interview.

Emphasis added. What does "blocks" means in this context?
Don't break them up. Just don't allow them to act monopolistically.
It partitions/firewalls the impact of the fraud to an individual state.

The voting power of Georgia residents may have been compromised here, but the voting power of the rest of the country was unaffected. In a popular voting system, that would not be the case (if the fraud increased reported voter turnout, seizing more voting power into the fraudulent election, for example).
This is a sad day for open-source at large, as well. I think it's very important to keep having conversations about proper stewardship of open-source projects, until we eventually reach new models that are more fair/reasonable.
I purposefully ignore certificates when looking at CVs. Once upon a time, I actually looked at them prejudicially, because the kinds of candidates I saw with certificates were generally inferior and couldn't code their way out of a paper bag. These days I just don't really give them any weight one way or another.
wow, great job!
rust has no future, its syntax is way to noisy and daunting, they made opinionated, sect-ic choices; rust reminds me of scala, wich is not a good thing
I've written a lot of Rust code that's in production in web, messaging and telephony contexts. I considered using Actix early on, but as soon as I saw the large amount of unsafe code, I stopped considering it at all.

I did not go on the Internet and try to convince other people not to use it. I did not complain at the maintainer that he should manage his project differently. I just didn't see why a library doing what Actix does should use any unsafe code at all, so I didn't use it.

When I later saw the way the maintainer responded to well-meaning bug reports, including patches, that validated my decision.

There's no need to flame people for running their open-source project the way they want to run it. You can just not use the code.
No, it would be enforcing the same requirements on chinese companies as the US enforces on their own. If they don't then fine them just as much, to have access to the US market.

It is not like cheap manufacturing, where the US has to cede ground to China because they simply can't compete. Tech is where the US excels.
I didn't say get rid of Lisp. It's indeed a great teaching tool. What I'm against is the implication that if one doesn't like it or use for production systems, they're doing something wrong or bad.
It's not at all a serious question. It's entirely speculative and there is zero hard scientific evidence that such a thing is even possible. Science fiction.
In my country government projects are distributed to software companies via tender. To be able to participate, they often require company to hire some number of certified professionals. For example I got Sun Java certification because of that. Naturally those companies are looking for people who already possess those certificates.

Government projects tend to be not very sexy, though. But they definitely help real world people with real world tasks, so it's a good bonus.
That’s not what I am saying at all. What I am saying is that if your business is only viable by shafting employees, that’s not a business at all
Is there an easy way for companies or individuals to offset (or more than offset) their carbon footprint?
The Unites States will always pay the coupon. QE4 is currently supporting our record issuance in the repo market - you know, the support that was supposed to be unwound by now, but has in fact grown in position since the beginning of the year.

We will monetize our debt forever, just like Japan, until there are currency consequences. The MMT people argue there will never be said currency consequences. We shall see.
> there’s this style of response

This type of reprehensible response will keep happening until society finally learns how the internet fundamentally changed the nature of fame. The best explanation of the problem is the video "This Is Phil Fish"[1] by Innuendo Studios. If you haven't seen it, please watch it. It's not about Phil Fish; he is simply a useful example of how fame works on the internet. Please watch the video!

The core problem is that fame used to be opt-in. Becoming famous required infrastructure. Gaining access to that infrastructure required the permission various gatekeepers, time, and resources. You had to work to become famous, because media access was a scarce resource.

On the internet fame became something that happens to you, because the internet IS media access. We're used to seeing fame as something that was chosen; if you didn't want to be famous, you could walk away from the media infrastructure and go back to your "normal life". The famous band could quit touring. Now that everyone has media access, that "normal life" can become famous directly. When that happens, walking away from fame means walking away from your normal life.

[1] https://www.youtube.com/watch?v=PmTUW-owa2w
Not that I entirely agree with the parent, but as you said:

> if one cannot make the payment, they are in trouble.

That's a function of cost of borrowing, not the amount borrowed.
Is this program dead? I had a look through the website and couldn't see much to suggest otherwise other than their writing prize in July last year. The list of partners too was a bit weird, all branding consultants and design agencies.
The 1k True Fans Theory: How to Earn a Living Doing What You Love
I got confused for a second, thinking of https://en.wikipedia.org/wiki/Venona_project
As a maintainer, I treat almost all PR submission with kind words.

What actix developer did was, to pardon my French, inexcusable. Deeming security patch boring? Making your own `Cell`, implementing it badly and misusing it, because it's faster on some stupid benchmark site?

If we designed cars like that, they would have no breaks, no gears and no cabin.

Honestly, I think it's better Rust abandons `actix` asap. Before it gets any real traction.
I reject the axiom. No one is above criticism provided the criticism is rooted in fact (i.e., defamation is not criticism).
The "unsafe" keyword should probably just be called "unchecked," otherwise it is a bit of a misnomer.
Show HN: Cross-platform UI client that runs in a browser or as Win/Mac/Linux app
How many hours of other people's worktime do you consume every day? Obviously they want you to work for them too. That's what trade is.

So what does fair trade look like? How much forced charity is fair?
Before Google, the local newspaper had like 80% of advertising market share in each city, and many were owned by national conglomerates.
>this would also make interstellar travel time scales irrelevant.

Not really. You're assuming this "machine storage" mechanism can preserve state forever. Even if you manage to upload consciousness losslessly and maintain all the ineffable qualities of "life" or "soul" or whatever (that we don't even really have solid philosophical definitions for), you'd still need to contend with data corruption and bit rot over cosmic time-scales.
Could you elaborate please? Genuinely interested to hear your take.
Did the patches obviously maintain the exact same behavior? If so, why should the author care about them? If not, it’s not the author’s responsibility to ensure they’re correct patches, but it is the author’s responsibility to ensure their package is correct. If it was correct already (not sure about this, but it seems it was very popular and used in production, so I imagine it worked well), they have no responsibility to vet incoming patches that do nothing besides change internal workings for the sake of changing internal workings.

I don’t write Rust, I write TS. If I produced a package that was had a clean and correct TS interface, but internally was filled with dirty dirty `any`s, I would be very unlikely to accept a patch that simply changed the internal typings for the abstract goal of “fewer any”s.