skysight-inc/HackerNews huggingface dataset:
I'm amazed by the negativity and prejudice in your response.

>> Outsourcing or no outsourcing, if someone walked up to me and said no to doing something in software team setting, I will likely be finding somebody else to do the job. And yes, I will likely never ask that person for doing anything ever again.

Precisely why I said - "Saying No is not the engineer's prerogative here." in the context of a developing world. You just explained my words :-)

>> For saying NO? Doing nothing and saying NO requires 'true passion and creativity', while doing what it takes to achieve the task doesn't?

I said - "Engineers working for product companies where they get paid and recognised for good product instead of outsourcing companies show true passion and creativity." Somehow you connect it to saying NO?

>> These things are called requirements documents, and yes you are supposed to code what the requirements say.

Although I could have explicitly said it was not a requirements doc, I hoped that you'd give me the benefit of doubt that I wouldn't ramble about a basic software engineering artefact. In this case, it was a Word doc with variable names(not variable naming conventions), loop variables, and pretty much the entire code within quotes. That is what I was pissed about. The doc screamed - "I don't want you to think, just be a monkey and do this."

>> Please. Passport tourism among Indians is now well known. Also bad mouthing your former employers and colleagues isn't exactly how you go about justifying other reasons to move out of the country.

So, you call going to another country for studies "Passport tourism"? I sure am very happy that I'm not as close-minded to think like that. I pursued what I wanted to study, and what I wanted to do with my career.
For the record, I still proudly hold my Indian passport.

Living outside your home country, and exploring other cultures opens one's mind like no other. Please give it some thought.

>> Bad mouthing former employers...

Seriously? I was contextually explaining my personal case about what I didn't like, to provide an example of things that happen at an outsourcing setup. So, you think one should never speak of what happens at work and be "loyal" to companies? Welcome to the open world of discussions and improving for the better.
I'm guessing, but I think the tricky part for Rust might be the automated construction of the Error-union type. E.g., at a certain call-point, the full union of all possible errors is ErrorSet<E1, E2, E3, ..., En>. The compiler determines this union, not the programmer. At the next call point, the union may be entirely different. To my best knowledge, Rust doesn't currently allow for variadic type constructors (i.e., where the number of parameters may be knowable at compile time, but the arbitrary-length parameter list cannot be expressed in the abstract syntax of the language).

https://ziglang.org/documentation/master/#Errors

edit: when I say "full union of all possible errors", I just want to be clear that this means "all the possible errors that could occur at this call point, and no others." It's not just a bag of "all possible errors that the language/library declares to exist."

edit #2: On second thought, I guess it might be possible for a Rust tool to build these types, although I think it would require changes to the language implementation. Variadic type constructors aren't necessarily needed. Another approach would be that every (type-specialized) function returns a Result<T, ES> type, where ES is some type that implements an "ErrorSet" kind, and where ES is very possibly unique to the function (that is, no other function might return Result<ES>). For example function A() might fail due only to two cases (say, out-of-memory or disk-full, but never network-error), and function B() might fail only on disk-full. Then the ErrorSet type for A has two constructors (OOM and DiskFull), where the ErrorSet type for B has only one (DiskFull). You could then use Rust's (excellent) pattern matching to exhaustively handle all cases (i.e., the specific constructors of that ErrorSet type) at the call site.

So the tricks would be:

1. Instrument the language to tag each specialized function with its error-set; this is computed recursively by examining the failure modes in the function body, as well as the error-sets of every function it might itself call, and taking the union of those sets. (Side note: I believe that, in Zig, a type-specialized function maps to a single error-set -- i.e., the error-set doesn't depend on runtime arguments in any way. But I could be wrong about this.)

2. Generate a potentially new ErrorSet-ish type for each function, or more spefically, for each error-set that is generated using the process in step #1. (I suppose you would have to give the type a name, but maybe it could be an anonymous internal type if there is language support for that.)

3. Then you could naturally "match" on the function's return value, and know that you've covered (exactly) the possible failure modes.

But this is just armchair-quarterbacking on my part. I don't know the internals of the Zig error system, nor what changes Rust would actually need.
Hey Andy, dev/ops nerd turned marketer here. First of all, AWESOME that you quit your job and are attempting to make a go at this! Huge congrats!

I would recommend you put in a couple higher levels on the Patreon and think about what people would want from you. For instance, I ran a popular blog and asked my readers what they would pay monthly for. Turns out one of the biggest requests was just a private webinar (I hate that word, so you could call it something else, like "knowledge brain dump") once a week. I ran them for 60 or 90 minutes and took questions at the end. In fact, I may do this again in the future, since I continue to get requests for it long after the fact.

People here have expressed how articulate you are when describing the language. Setting up a group at say $19/mo or even $49/mo where you deep dive into software dev, practical applications of Zig, and/or programming languages in general "live" once a week might be something people are willing to pay for, and would get you "out of the red" more quickly.
Trust isn't a binary, it can be extended to differing degrees. In absence of advanced comms, you have to extend trust, but how far? That comes with an opportunity cost -- I wouldn't loan money to someone I'd only communicated by 8 week delayed handwritten letters, but I (possibly) would do that to someone I'd talked to on Skype for an equivalent amount of time.

(This might not be rational.)
Ethereum Plasma for AdTech
Github watches mean much more than stars imo. it means people are actively paying attention
yeah it’s really something that half of all adults have more wealth than the cost of a shitty beater car
Well, yes. I was mostly wondering how this works from a legal perspective.
By mandating solar you reduce the value of the power generated with each new home. The ROI will continue to decline until it's near zero.
You should get out and meet real people in America. It will probably change the first half of your post
Minor League Baseball Provision Shows How Broken the Legislative Process Is
It will never happen. There will always be some lower labor cost region where manufacturing jobs can be sent, and there will always be some loophole which corporations can use to get around restrictions.
Lex Luthor went from mad scientist to ruthless CEO sometime in the 80s or 90s.
California screwed itself over with such a stupid mandate.
> Why didn't the journalist at least cite the source of the informatoin?

In the article, they cite enough statements made by specific people at specific organizations to support the headline - it's not peer-reviewed academic research, sure, but it's not like they are just making stuff up either.
Would you contribute money to other people so they can take risks? If so, maybe consider becoming a backer to a company.
Absolutely nothing.

More interesting is what uses it (if it is a library), when the last commit was, and is there any old issues with no updates from owners.
To me they mean merely that other people have also looked at this project and found it interesting enough to star, so I might expect less resistance from others to using it if I too decide it's cool and want to use it.

I wouldn't be comfortable inferring much about adoption from number of stars, based on my own starring behavior, which is often "this seems cool, maybe I'll look into it more deeply later".
I would expect most developers to do the same thing if the offer was good enough, but I suspect they would be far less open to mention it. I'm assuming this is just a difference in cultural knowledge of how it looks. They might have been thinking of it as social proof of desirability where as more local developers are aware that culturally you are supposed to pretend to be loyal to the company.
Not a whole lot by itself. But certainly an indicator of quality/use that I'll use when evaluating options. # of stars, contributors, commits, branches, what the README looks like, check out the pulse on a weekly/monthly basis, contributions per person (is 99% of it written by 1-2 people). When were the last meaningful commits, is the build passing. Many other things go into evaluating a project when I'm considering taking it on as a dependency. But those are just a few I look at glancing at the repo for a minute or so. And of course, I compare all these metrics to the alternatives.

Edit: another couple I forgot was # of issues (and what those issues are ie. bugs vs feature requests), and types of PRs open
every foreigner is always a wierdo, thats wat makes this world so much fun and exciting.

foreigner by nation or state or city or apartment or school.
> I'll include a section in the privacy policy on what's sent in the request, which is just the application UUID and the licence key.

And the complete URL of the originating page, as the parent commenter mentioned.
I do the exact same.

However I put more weight on the number of issues a project has. If there are a lot of stars but not many issues, that could indicate a project that isn't really used that widely, or actively.

However, if it has a lot of issues that means it's a popular project with a lot of users that are actively working on making it better.
But does this also include negative wealth? Especially in the US, it seems to me that many people have a lot of debt – staring from credit card debt to a too expensive car lease (and a new one ever 3 years) to the house they have payments on for ~50 years? This way, it seems to me that a lot of people (especially younger ones) have a wealth of ~-10,000€.
I was curious, so I threw it into Wolfram alpha:

(weight of a sheet of paper) * 5^64

.4 x Milky Way mass

Almost half the galaxy mass, that's a lot of grains of rice!
It depends where you are I guess. In general, it's still more of a bad news than a good news.
Since Zig is pretty unknown language, I would actually buy swag. Cap/t-shirt. It's not like a monthly donation but if it can get you extra cash...
>Everytime a company pays their employees so little they need welfare to live, that's redistributing wealth from society to shareholders

I'm curious what you believe would happen if we could magically remove all welfare programs. Do you believe those employers would be forced to raise wages? Or do you believe the lives of the poor would just be that much worse?
> The probability of hiring an under qualified candidate is entirely unaffected by refusing to interview white/Asian people.

But the probability of false negatives for white and Asian candidates rises drastically. There is a very high probability that the most qualified candidate was rejected immediate on the basis of race.
You make my point. I don't believe there has ever been a redistribution from wealthy to poor without war and violence.
Not really. Obviously money spends differently in different places, but the sum of EVERYTHING that someone owns being less valuable than my computer, cell phone and the cash in my wallet is very bad.

Never mind the idea that there's still an extreme minority of the population in possession of an obscene ratio of the world's wealth is "awesome" in the sense that it "inspires awe that our society has continued to allow this to happen" but that doesn't mean it's good.
It also happens whenever we do QE or lowering discount window interest rates - that's wealth distribution from everybody (that happens to disproportionately hurt those with lower earning power) to banks and those privileged enough to obtain government grants, and indirectly, away from everyone saving for retirement to publically traded corporations.
It's cash flow positive from day 1. Your mortgage increases by $20/month, and utilities decrease by $40/month, or whatever.

This is why there are companies willing to lease your roof space to install residential solar.
Well I star things just to remember to go back and see if they're any use to me: so I think that should give you an indication of how reliable they are as a measure of quality.
That's probably because nobody uses savings accounts for large amounts of wealth. I have $0 in a savings account because a 3 month T note yields significantly more than the 1.4% Ally saving account that everyone seems to love
The Quasar Method
Some banks are pushing towards a 2% interest rate and still FDIC insured, though they're only online. It's not great but part of a diversified account structure for us.
I know what you mean. Often enough any minority is criticized at all it is initially brushed off as simple X-ism..
According to his Patreon I linked he is.
The way I see it is that your face is kind of like your license plate number. The government being able to map your likeness to your official metadata (taxes, license, etc) is somewhat legitimate. It's when they start tracking it everywhere that I have huge issues. Feeding security camera footage into facial recognition software is like putting up an ALPR at every street corner. It's not an invasion of privacy per-se but because technology allows all that metadata to be sifted through on demand at scale it's basically government stalking.

The facial recognition ship has long sailed for 1st world citizens thanks to how many pictures most of us have online, official photos for ID, etc, etc. The government can already map your face to your identity.

This particular program is probably more targeted at the non US residents crossing the border because the three letter agencies don't have access to as much good data and metadata on them. Because all the Mexican government agencies don't share ID photos with the three letter agencies the three letter agencies have to do it themselves hence facial recognition at borders.

As others have said I'd be very surprised if they weren't just trying to legitimize something they were already doing.
Imho both US-americans and Indians tend to oversell themselves to a degree of perversion.
You mean if someone decides to work for Amazon instead of Infosys, it is a bad decision? If you really believe that you sound like one of those thousands of employees from the likes of services companies like Cognizant or dated product companies (looking at you Cisco and Oracle) who want to justify it to themselves and others that they are in a place as good as any FANG and there is no good reason to work for FANG. This sounds like crying sour grapes. Sorry to burst your bubble, but things are really really that much better in FANG than the Ciscos and Oracles and Cognizants.

I began my career in the services industry. Later I have worked for two FANGs for two years each. I quit them not because the work was bad. The work was damn good. I quit because I got a better job with a better salary and easier working hours.

And what's with this silly comparison of SREs at Google with programmers of Cognizant? Why compare SREs with programmers? That's comparing apples to oranges!

Compare apples to apples. A programmer at Google or Amazon is going to be doing far more interesting work than a programmer at Cognizant. A programmer at Google or Amazon is going to be far more skilled than a programmer at Cognizant. Likewise for a QA at Google vs. a QA at Cognizant. Likewise for an SRE at Google vs. an SRE at Cognizant.

If someone who wants to be a programmer chooses to be an SRE instead, then the choice of profession, not the choice of the company, is the problem here.

And SREs are not some kind of low class work that you seem to believe in. If you really think a programmer at Cognizant is somehow a better job at SRE at Google, please come out of this service industry mentality where one kind of work has to be better than another. One is not better than another. They are just different. They require different skill sets. A lot of very smart people I know are SREs. They enjoy the thrill of cutting through the complexity of network topology, load balancers, DNS, container orchestration, system performance, hardware and software issues to resolve puzzling issues when services go down.
Red Bull does not contain any other stimulants.
Literally nothing. If it's a thing I need to use, I look at how actively it's being maintained, whether issues get responded to quickly, and whether issues get closed within a reasonable time or linger for three years.
AI is sociopathic, that's why.
And all thanks to the DMCA! I hate that law with a fiery passion.
I agree, but Trump just compounded the matter with this stupid game he’s playing. I am not conflating the issues here: both CA and the Trump administration have pushed me farther away from being a California homeowner.
Depends a lot on the type of project. If it's something trendy, like a new JS framework, it means nothing for me. If it's something more specific and there are other alternatives, then it starts to mean something.
Than I have ~$500 most of the time. Why would anyone willing lose money every year by hoarding it in a savings account/in a jar
Reconciling Abstraction with High Performance: A MetaOCaml Approach
You leave it in checking accounts or, if you are looking for interest/return, put it in an investment account. The movement between these accounts is pretty seamless at many banks these days. In my case, there are no fees associated with putting the money in investments so it makes it very cheap to put the money to work.

Savings accounts are essentially restricted checking accounts, so what's the point? The interest rates on both types are the same, at approximately zero (pennies of annual interest on a thousand dollars).
Also, „hands were not detected“ does not mean that they really weren‘t on the wheel. Maybe someone who drives a Tesla can comment on how reliable the hand detection is.
LibreOffice 6 review: The open-source favorite gets an update
I agree, but the big question is "why ?". And, more importantly, why has the appetite for risk collapsed so much in the software industry, an industry that has traditionally been the beneficiary of very, very low bootstrapping costs. It's cheaper than ever to lease dedicated machines with tons of memory, disk space, and bandwidth, as well as very cheap to purchase machines for in-house use.
Might be reflective of a world where we fear oppressive systems (created by maybe evil maybe naive tech guys) more than strongmen (who now act as mere agents of said system).
That basically hits the nail on the head, but it's not the full extent of it. We have ["Jugaad" culture](https://en.wikipedia.org/wiki/Jugaad), where we actually take pride in doing things that would be labeled outright fraud in a lot of places.

I also can't see how its changing, I've become rather cynical from having to deal with it constantly. I sure hope you're right, though.
i feel stars is a fair indicator of popularity but is low on the list of metrics used to evaluate the project.

documentation over everything, followed by using a rough mental calculation of open issues and recency of commits.
It strangely only worked for me the second time I viewed the page.
Yes exactly. People harp on cryptocurrencies for their rampant scams and problems. They are correct. But it's still competitive because our current system is embroiled with significant corruption.
Debt is “bad” when used for depreciating assets (cars, credit cards). Debt is “good” when used as leverage on appreciating assets (real estate) or working assets (tools, business vehicles, servers, or anything else being used to generate cash flow).

If I have an interest only loan on something like a taxi medallions (thanks Planet Money for the example!), I generate cash flow with that asset, and can walk away from the debt at any time through bankruptcy of the owning entity, that’s still positive wealth (cash flow).

The less capital you need to obtain access to greater amounts of cash flow, the better the cash on cash return/investment quality.
"Enter the field" doesn't just mean majoring in CS. It broadly refers to everyone working in tech. The point remains, if only 20% of people in tech are diverse, then Google hiring 25 or 30% doesn't change overall diversity. It just means some other companies will have less than 20%.
Couldn’t it also mean that the code quality is poor?
Oh, but, if you have wine or some virtualization software you can run quickly get started using 'haxedevelop'...

I guess it's not that multi-platform, after all.
That’s not actually true. With InnoDB the data is largely cached specifically by the database in the Buffer Pool.

Of course they are using MyRocks here and while I don’t actually know I’d be very surprised if it wasn’t the same. File system cache only really helps you with reads in an ACID-ish system and write speed ups/journaling require a more actively managed cache.
If I were rapidly approaching a barrier at full speed on a highway, I might put my hands up and guard my face before the crash.
There's definitely there's a distinction here between the approach you've described (Rust can indicate that a function returns only IO errors -- but doesn't tell you which subset of "all IO errors" might actually occur at this call point) and Zig's (the function call can result in an arbitrary set of specific errors, some of which might be IO and some might not; and only the actually possible errors are included in the set).

Is one better than the other? I doubt that question has an objective, one-size-fits-all answer. I'm happy to see experimentation in this domain! My point really is just that Zig is different from Rust in how it handles errors, even if there are some superficial similarities.
Yeah but, who's happier? That's not easy to answer btw. I've read studies that show evidence for both:
-Money brings you happiness (up to some asymptote most never reach)
-Poor (by western standards) rural tribes or hunter-gatherers are very happy.

I think it's illustrative to compare assets across the world but perhaps a more normalized metric would be overall "happiness", whatever that means (no its not easy to define).

My own western-biased experience tells me it's a bit of both. Money does in fact bring freedom of time which can bring happiness, but I've met some extremely happy people living on peanuts, eating very healthy and living on islands off the coast of Japan.
Well, then you have to live in Yakima! ;)

There are excellent inexpensive places to live in Washington that offer a lot more than Yakima does. Spokane, for example, is still very inexpensive compared to Seattle and offers a lot more in terms of both city life and accessible outdoor activities. It's too bad the dev scene there is pretty limited (Itron and Seven2 are really the only companies that I can think of off the top of my ahead employing devs, and the salaries are nothing to write home about). Of course, if you're doing remote work anyway, this isn't really an issue.
Thank you! but we are from IIIT Bangalore xD
Keras 2.2.0
Don't forget, you can pay for Robinhood Gold and get access to margin!